earlier replies
Replying to @humphd @rustlang @mozilla @FirefoxDevTools
Suggest less "don't-break-the-web" intertia around those projects? Or are you saying it goes beyond that?
1
I'm also curious what it means, and am surprised by it. I'm interested to see how things play out. I'll follow where it leads, though.
1
I personally don't find it very surprising and don't think "don't break the web" is an explanation at all. Rust compat story is rough too.
2
1
Look at what @rustlang is doing overtly to encourage new contributors and mentor them. "mentoring" is a core team watch word. Matters.
2
3
Hypothesis: GitHub is easier for new contributors than Bugzilla.
2
6
Maybe related: - quality of bug reports & comments → how well teams keep up with bugs → responsiveness in bugs to mentoring requests ?
2
3
Definitely related. Low barrier to entry on GitHub makes upgrading to mentoring easier.
1
1
Heretical but shouldn't be: "bug dependencies" is a much less important feature in a bug tracker than people think it is.
1
1
My heretical bug system idea is that they should work much more like wikis and much less like twitter/email: dbaron.org/log/20130129-bugz…
2
2
Github workflows tend to promote making the first comment a summary.
1
2
Replying to @wycats @humphd @crowder @rustlang @mozilla @FirefoxDevTools
First comment of what? I want to get rid of the stream-of-comments entirely, and just have a description that evolves over time.

Oct 4, 2017 · 3:15 AM UTC

1
Replying to @davidbaron @humphd @crowder @rustlang @mozilla @FirefoxDevTools
Sounds good. I'm saying GitHub people tend to encode this in the stream.
1
2
I don't understand. Where do I look to find the single description that I can read, that allows me to ignore all of the other comments?
1
more replies