OpenHatch wiki

Open Source Comes to Campus/Curriculum/Finding a Project: Difference between revisions

Page Discussion

Open Source Comes to Campus/Curriculum/Finding a Project (view source)

Revision as of 20:47, 13 September 2014

142 bytes added ,  9 years ago
→‎Step 2: Researching Projects
imported>Shauna
imported>Paulproteus
Line 31:
== Step 2: Researching Projects ==
 
Once you've got at least 31 projectsproject on your list, it's time to start researching them. (It's great to have more than 1 -- you might find that the first project you pick isn't a good fit for you.) For each of them, you need key information, including:
 
* website url
Line 40:
* installation guide
 
Write this information down as well. There's a section for this in the template etherpad. Every project will not have every item, but you should look for all of them. Sometimes the url will be the same for multiple items - for instance, the contributor guide and installation guide may be part of the same document. You can write down any other relevant information or links you find as well. (If you want an example, look at the template Etherpad document, but a bulleted list is fine.)
 
Some advice: The simplest way to find the project's main website is to google it. A well maintained project will have links from the website to their source code repository, issue tracker, mailing lists and IRC channel. Sometimes this information will all be bundled together in a “developer guide”. Larger projects may have multiple mailing lists for different people (developers, users, translators, etc) and for different parts of the project. Some code hosting services, such as Github, provide issue trackers as well. You can usually find a link to the issue tracker in the code repository and vice versa. Popular services include Github, Google Code, Bitbucket, SourceForge and Gitorious. Popular issue tracker services include Bugzilla, Github, and Google Code.
Anonymous user
Retrieved from "https://wiki.openhatch.org/wiki/Special:MobileDiff/14378"