Le 22/02/12 01:31, Jacob Appelbaum a écrit : > Dear Tor community, > > We'd like to encourage contribution from the larger Tor community and > help to get 0.2.3.x out as a proper Tor release. Often development > blocks on a few people and at todays Seattle developer meeting, we've > identified that we could use some help! > > First up - please consider subscribing to tor-dev: > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev > > Secondly, are you able to program in C? No? Do you want to learn? Do you > want to learn about tor and help improve it? Consider looking at these > "easy" bugs, helping to close them is a great way to start: > > https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&milestone=Tor%3A+0.2.3.x-final&keywords=~easy > > Are you feeling like you'd like to help us with the most critical, major > or blocker bugs? These bugs must be resolved before the 0.2.3.x release: > > https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&cc=~&order=priority&priority=critical&priority=blocker&priority=major&col=id&col=summary&col=milestone&col=status&col=type&col=priority&col=component&milestone=Tor%3A+0.2.3.x-final > > Every bug is important and we've got quite a few that could use some > help. Please consider looking and contributing to the full list: > > https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&cc=~&order=priority&col=id&col=summary&col=milestone&col=priority&col=status&col=type&col=component&milestone=Tor%3A+0.2.3.x-final > > We'd very much like everyone to consider themselves welcome to help. > We'd love the help and we'd like to grow the number of people willing > and able to lend a helping hand!
It would be nice to have a place describing how to contribute, clearly linked from the top of the "Volunteer" page: - How to checkout the code (may sound ridiculous but all repository hosting services from google code to bitbucket and github print the command required to clone a particular project on their homepage or source page) - I have found a bug, what should I do? (aka "Trac bug search page is daunting") - I have fixed a registered bug, what should I do? - I have implemented a cool feature, what should I do, patchbomb tor-dev? - Coding conventions, prerequisites (test should pass? anything else?) FWIW, I would have patchbombed tor-dev mailing list :-) -- Patrick Mézard _______________________________________________ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
