On Thursday, October 4, 2018 at 5:14:53 PM UTC-7, fantasai wrote: > On 10/04/2018 04:26 PM, Steve Fink wrote: > > On 10/04/2018 03:45 PM, fantasai wrote: > >> Start here, at Mozilla's home page: > >> https://www.mozilla.org/ > >> > >> Give me steps to reproduce to find instructions for filing > >> a bug against Firefox. Ditto for up-to-date instructions > >> for building the source and submitting a patch. > >> > >> (Don't send me links to the instructions; I'm cheating by > >> asking here already. Walk me through the process of > >> discovering how I can contribute to Mozilla and make the > >> world a better place. I wouldn't be here if I hadn't > >> already walked that path 19 years ago, but I can't find it > >> anymore so I need some help.) > > > > I tried it out, and did better than I expected on my first run-through: > > [...] > > I'm impressed! Want to take a stab at finding patch-submission > instructions? :D > > > I agree that a nice path from www.mozilla.org would be beneficial, > > especially for promoting the volunteer aspect of the project. > > We've got a lot of highly-produced (read: expensive) material > promoting the volunteer aspect of Mozilla: > https://www.mozilla.org/en-US/contribute/ > But afaict none of it actually leads to a viable path towards > actually becoming a technical contributor... > > From my discussions with staff at Mozilla, the people actually > working with volunteers (like QA and l10n) find this very > frustrating, but the people whose job it is to connect volunteers > to opportunities to contribute don't think it's useful, important, > or in some cases even a good idea to fix this problem. I don't > know how to break through that resistance, and I find it very > demoralizing that there even is any. :( > > I'm also disconnected enough from Mozilla the last few years > that I've no idea where up-to-date documentation on this stuff > would live. If I ever manage to dig myself out of the backlog > of spec work enough to write a patch, I'd like to know where > to look! > > Fwiw, here's how I arrived at becoming a technical contributor: > https://web.archive.org/web/20000125153750/http://www.mozilla.org:80/ > > https://web.archive.org/web/20000301043132/http://www.mozilla.org:80/get-involved.html > > https://web.archive.org/web/20000302035824/http://www.mozilla.org:80/quality/bug-writing-guidelines.html > > https://web.archive.org/web/20000304015940/http://www.mozilla.org:80/newlayout/bugathon.html > > “One of the things that people seem to like best about the > existing content on mozilla.org is that it is written by people, > for people, without bluster or self-promotion.” > -- jwz, Mozilla Documentation Style Guide, 1999 > > ~fantasai
I would say adding a link to https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines (or maybe https://support.mozilla.org/en-US/kb/contributors-guide-writing-good-bug ) in the "More links" section at the bottom of https://www.mozilla.org/en-US/contribute/ would go a long way toward having a better onboarding experience for filing bugs. https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/How_to_Submit_a_Patch would be the patch for patch submission. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
