Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Developer outreach documentation & strategy #426

Closed
11 of 14 tasks
jywarren opened this issue Mar 17, 2016 · 1 comment
Closed
11 of 14 tasks

Developer outreach documentation & strategy #426

jywarren opened this issue Mar 17, 2016 · 1 comment
Labels
outreach issues involve community involvement and helping people who're stuck somewhere

Comments

@jywarren
Copy link
Member

jywarren commented Mar 17, 2016 •
edited

Help new contributors and new coders find the PublicLab.org codebase, and find easy on-ramps for contributing.

I've started with two new sections to the Developers page, leaning heavily on input from @gr2m from Hoodie:

They include notes on the help-wanted and first-timers-only tags, and link to #329 as an example of a well-documented issue appropriate for first timers.

I've also mentioned this to @ebarry and @steviepubliclab on the page about the BostonJS meetup where I met Gregor: https://publiclab.org/notes/warren/03-04-2016/bostonjs-talks-focused-on-welcoming-new-coding-contributors and created JavaScript and Ruby tags.

What are some other steps we can take? My list:

  • create help-wanted and first-timers-only issue labels, and reformat those to be friendly and well-documented for newcomers
  • document outreach steps such as the above on the Developers page
  • ensure clear links to https://publiclab.org/wiki/developers are everywhere (need to add to CONTRIBUTORS.md)
  • label issues with Ruby and JavaScript tags so coders can play to their strengths
  • rewrite the README file to include a better intro
  • add links to Code of Conduct
  • rewrite the README file to include information on testing
  • participate in SpinachCon to get feedback on our docs/efforts (see SpinachCon new developer feedback on install process #427 for progress and ideas from that copied below)
  • create a prerequisites page on the wiki
  • "get involved" should include link for coders (@vzhz)
  • maybe provide container w all (see sandstorm?)
  • ditch node as a dependency with bower-rails
  • write lots and lots of tests
  • make friendlier first-timers-only landing page with list of issues? Possible?
@jywarren jywarren added the outreach issues involve community involvement and helping people who're stuck somewhere label Mar 17, 2016
@jywarren jywarren mentioned this issue Mar 18, 2016
Closed
8 tasks
@jywarren
Copy link
Member Author

All coming together here! https://publiclab.org/wiki/software-outreach

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
outreach issues involve community involvement and helping people who're stuck somewhere
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jywarren