[Systems] [Sugar-devel] API documentation.

David Farning dfarning at gmail.com
Fri Jun 25 08:28:12 EDT 2010

Yes, docstrings themselves will pass through the normal sugar-devel
mailing list review -> commit process.  This is just the setup stuff.


On Fri, Jun 25, 2010 at 2:02 AM, Tomeu Vizoso <tomeu at sugarlabs.org> wrote:
> On Tue, Jun 22, 2010 at 20:45, David Farning <dfarning at gmail.com> wrote:
>> It looks like we are starting to make progress on the API documentation project.
>> As you may be aware, Seeta.in is working on sphynix based api
>> documentation for the core Sugar modules.  Initial work can be seen at
>> http://seeta.in/sugar/api/documentation/dest8/ and
>> http://seeta.in/sugar/api/documentation/dest9/ . But there are also
>> significant advantages to maintaining the existing epydocs at
>> api.sugarlabs.org.
>> I would like to propose that:
>> 1. Manu identify a seeta sysadmin for whom we create an account on sunjammer,
>> 2. Seeta move their proof of concept spynix documentation to sunjamer.
>> 3. The Seeta documentation team continue to maintain the existing
>> epydocs documentation.
>> I can do the required tasks to make this happen.
> This looks very good. Just to be sure I'm on the loop, up to now the
> work has gone into setting up the infrastructure and the api docs
> themselves will be committed to the source tree and not kept separate,
> right?
> Thanks,
> Tomeu
>> david
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel

More information about the Systems mailing list