Closed Bug 688909 Opened 9 years ago Closed 8 years ago

Update the Get Involved with Webdev documentation

Categories

(Websites Graveyard :: blog.mozilla.org, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: davidwboswell, Unassigned)

References

()

Details

The documentation we're pointing people to right now about how to Get Involved with Webdev only features a few sites and some of the information is out of date.  For instance, there is no mozilla.com site anymore.

There may also be other relevant information to add to the page, such as links to how to create a patch or submit a pull request?
Blocks: 688911
(In reply to David Boswell from comment #0)
> The documentation we're pointing people to right now about how to Get
> Involved with Webdev only features a few sites and some of the information
> is out of date.  For instance, there is no mozilla.com site anymore.

Looks like pretty much all of the source code links are wrong (Socorro is now on Github not Google Code, and pretty sure most of the others are on Github not SVN anymore).

ozten isn't on Socorro anymore, and we have our own channel #breakpad (although using #webdev is fine too).

Also just a note that we have https://wiki.mozilla.org/Webdev:WhoWorksOnWhat which is more complete and probably more up-to-date, but also a bit overwhelming in it's layout and overall verbosity. Not sure if it's appropriate to try to merge/sync these, or if they just serve different purposes (probably the latter).

> There may also be other relevant information to add to the page, such as
> links to how to create a patch or submit a pull request?

I am in favor of this, since we're pretty much all on Github now as far as I can tell. I think requiring contributors to create a bugzilla account, find or file a new bug in the right component, and attach a patch is far too cumbersome.

If we want a non-Github option, I think we should encourage sending patches via email. I think this is probably not necessary though.
(In reply to Robert Helmer [:rhelmer] from comment #1)
> Also just a note that we have https://wiki.mozilla.org/Webdev:WhoWorksOnWhat
> which is more complete and probably more up-to-date, but also a bit
> overwhelming in it's layout and overall verbosity. Not sure if it's
> appropriate to try to merge/sync these, or if they just serve different
> purposes (probably the latter).

I agree that these serve two different purposes and that it would be overwhelming to throw information about more than 200 sites to someone up front.

If we select a small number of sites we can commit to having good bugs and mentors for, then featuring those on this page makes sense.  We should then at least have a link to the more complete docs for anyone who wants it.

> I am in favor of this, since we're pretty much all on Github now as far as I
> can tell.

In true Mozilla fashion I think there are a range of version control tools being used.  For instance, www.mozilla.org is on SVN (although I think James wants to move it to Github).  We also recently archived a CVS based site.

If contributing on Github is substantially easier, then we can make sure that the sites we feature on this get involved page are there.  Figuring out other repos can be a good step to take for someone after they get some initial experience in.
Who has access to change the get involved page?

I have some specific changes based on fielding a couple of contribute-Webdev emails:

* Update screenshots

* First link should be the site-specific "Get Involved" wiki page. e.g., https://wiki.mozilla.org/Webdev/MDN/GetInvolved

* List technologies used. e.g., python, django, php, etc.

* List 1 contact

* Remove bugzilla and tests links

* Keep IRC channel
Closing as fixed.  The old Webdev Get Involved page has been replaced by the new one on the wiki at

https://wiki.mozilla.org/Webdev/GetInvolved
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Websites → Websites Graveyard
Product: Websites Graveyard → Websites
Product: Websites → Websites Graveyard
You need to log in before you can comment on or make changes to this bug.