https://devsummit.aspirationtech.org/index.php?title=You%27re_doing_it_wrong._How_to_release_free_software_so_you%27ll_get_contributions.&feed=atom&action=historyYou're doing it wrong. How to release free software so you'll get contributions. - Revision history2024-03-29T15:39:58ZRevision history for this page on the wikiMediaWiki 1.35.1https://devsummit.aspirationtech.org/index.php?title=You%27re_doing_it_wrong._How_to_release_free_software_so_you%27ll_get_contributions.&diff=487&oldid=prevVivian: 1 revision imported2015-05-05T18:25:08Z<p>1 revision imported</p>
<p><b>New page</b></p><div>Evan told us how we are doing it wrong. It came out of the meeting that an updated book, or a book specific to non-profits, is needed.<br />
<br />
* Putting it on github and forgetting its broke is not a release.<br />
* Open sourcing components is often more easy and gets more contribution.<br />
* Open sourcing things not core to the mission of the organization is something that commercial companies do, that may be an applicable model.<br />
* (get rest of bullet points from Tomas).<br />
<br />
* Ushaidi did things wrong, but then turned around<br />
# only skype<br />
# no member list<br />
# one had to submit form to get code<br />
# no contribution process<br />
# they read Karl Fogel's book<br />
# open mailing lists ....<br />
# once people made that transition, people showed up to produce code.<br />
----------------------------------------------------------<br />
Points from the report-back:<br />
<br />
# Maybe open sourcing the mission specific part of the stack isn'ft the right investment<br />
# Start by contributoing back to the os tools that you use<br />
# The process is more important than the license<br />
# Think of the programmers as another community you need to organise. Community organising for non-profits<br />
# We need to add to carl vogels 'producing open source software' to create a book for non-profits and funders who want to understand the issues.<br />
----------------------------------------------------------<br />
Below here is the rest of the raw dump.<br />
<br />
<br />
Some things are open sourced to fulfill grant requirements to funders(eg. to Knight Foundation). The code is thrown over wall as a tar ball, so this seldom works.<br />
<br />
does make it easy to then close source it<br />
but get no benefits from contributors.<br />
<br />
To do free software have<br />
* have to use irc<br />
* have to have open mailing list<br />
<br />
<br />
Polymaps <br />
only way to communicate back is 'github issues' <br />
no indication that is how to communicate<br />
they delete the bug record<br />
no way to contact developer<br />
<br />
with Drupal, there is a model<br />
<br />
some academics develop it, get it paid for develop it, live in their own world.<br />
<br />
Best talk, people at github<br />
developers at github<br />
always write the readme first<br />
write the code (as if it will be free software - internal collaboration<br />
when time to make it public, they just flip a switch<br />
3 guys to 45 no hierarchy, no managers<br />
run internally as free software<br />
<br />
knowing others will look at code, great way to improve.<br />
<br />
Funder driven free software, they think its just a license.<br />
<br />
funders starting to see that its not sustainable.<br />
<br />
in commercial world<br />
most developers have a job that uses that software<br />
<br />
open sms stuff - tiny community paid by somewhere.<br />
<br />
companies can see a profit motivation.<br />
<br />
Frontline SMS<br />
does everything wrong, but get contributions.<br />
<br />
code developing and code they are delivering.<br />
<br />
Sunlight foundation<br />
2 people working months, code could not be merged in.<br />
<br />
only helps if two people (?)<br />
<br />
github project account<br />
consistent versioning<br />
etc. (see Karl's book)<br />
book needs updated - distributed version control<br />
making it github specific<br />
people need specific guidelines<br />
<br />
Some projects will get contributions no matter what<br />
Som projects will get contributions if all done right<br />
Some will never get contributions.<br />
<br />
non-profit sector more competitive that profit sector - can't grow the pie.<br />
<br />
nothing funder driven that I have seen has helped.<br />
<br />
commercial clients change the dynamic <br />
(civiCRM vs Drupal), not many pure <br />
civi does not relate to the mission.<br />
free software works better if its building blocks.<br />
<br />
<br />
non-profits hiring corporate shops (ThoughtWorks, Pivotal, etc.) doing good open source work.<br />
<br />
Evan, "Never hire a firm that does not push to do open source."<br />
<br />
Things that you get<br />
community, etc.<br />
<br />
community management, roadmap of simple contributions.<br />
<br />
rails history, one guy, then a few more. Not open process.<br />
people protesting, code got forked, community forked, antagonistic communities, <br />
<br />
eventually the companies (37 signals, etc.) said you will merge these projects.<br />
<br />
Rails is much better for it.<br />
<br />
first contributors won't be worth the investment, but will pay it back in the long-term.<br />
barrier: its good for the long-term, but non-profits live on short term grant cycles.<br />
<br />
newsletter, weekly updates, etc.<br />
<br />
One can share too early. Could not get to contribution part cause could not run.<br />
<br />
need to release it and say clearly 'it won't work.'<br />
<br />
Ubunto: looking for community organizers - watch the mailing lists: no one applied.<br />
<br />
resource issue - did not have the people or time.<br />
<br />
Final product is more useful than the parts to developers, but not to community.<br />
<br />
Difference between open source code and proprietary code. Open source code is made to be extensible. They are different.<br />
People don't contribute to the core, they extend it to do things they want.<br />
<br />
Need good extension architectures.<br />
<br />
Maybe should contribute back to the community on those tools that they use.<br />
Open source everything not is critical to their mission.<br />
<br />
Tomas says we should write a book: focused on non-profits.<br />
<br />
Need to be able to do derivative works on books</div>Vivian