gtg team mailing list archive
-
gtg team
-
Mailing list archive
-
Message #01260
Re: [Bug 526150] Re: Create a nice web documentation of GTG functions
Sounds good ! I'm interested in helping you.
Moreover, I can translate this doc in French if you think that it could be useful.
---
Alexandre COLLIGNON
Le mar 23/02/10 01:52, Luca Invernizzi invernizzi.l@xxxxxxxxx a écrit:
> Good point. Link http://live.gnome.org/gtg/easyguide . It is not
> yet linked from the main gtg wiki page, since it is a work in
> progress.
We do have something similar http://live.gnome.org/gtg/contributing, but
> I was thinking about making it very easier and friendlier (groundcontrol,
> ...)
> --
> 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.
>
>
>
>
>
--
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.
Follow ups
References