That's fine, I was only talking about translation. Of course, bzr and stuffs like that are not requirements.
Speaking English and Python are. On Tue, 23 Feb 2010 09:31:31 -0000, Luca Invernizzi <[email protected]> wrote: > Hi Lionel. I am aware of a lot of people that know how to program but > don't have a clue about how to contribute to an open source project. > I don't want to tell them how to program. > I want to explain how to get the code, where the documentation for the > plugin api is, and how to do a merge request. > > This way, when a person comes by in IRC and ask about how to contribute, > I can direct him to the guide. Maybe one in ten will actually submit > code, but it's worth trying. > > After all, I'm contributing to gtg thanks to > http://live.gnome.org/gtg/contributing , which is "lowering the > barrier". I simply don't think that bzr is an absolute requirement for > the first merge request. I may be wrong, but it doesn't cost much to > try. -- Create a nice web documentation of GTG functions https://bugs.launchpad.net/bugs/526150 You received this bug notification because you are a member of Gtg contributors, which is subscribed to Getting Things GNOME!. Status in Getting Things GNOME!: Confirmed Bug description: Several potential developers come by IRC or mail someone in the team, interested in helping out with gtg. However, we are not extremely easy to hack into for unexperienced developers: therefore, we are losing patches. I think we should write a simple guide for that, and generate a web documentation of our functions (via http://docs.python.org/library/pydoc ? I'm not an expert on this matter). That should make things seem more easy. _______________________________________________ Mailing list: https://launchpad.net/~gtg Post to : [email protected] Unsubscribe : https://launchpad.net/~gtg More help : https://help.launchpad.net/ListHelp
