Hi Florian, On Dienstag, 26. Juni 2007, Florian Maier wrote: > As i'm (at least at the moment) a non-DD, writing the documentation > for Tracker submitters (Neil McGovern mentioned it in his last > E-Mail) could be a good place to start.
yes, I think trying to do some outstanding TODO items and then updating and extending the documentation [1] accordingly would be a good idea. Some hints - you should subscribe to the commits list [2]. Error messages will be sent there and you can get a feeling how things work - you can check the syntax with "make check" in the top level svn directory - there is a script bin/check-new-issues that helps a bit with sorting out NOT-FOR-US issues - joining #debian-security on irc.debian.org is probably also a good idea - the thread at [3] might be interesting, too If you have questions, just ask. Cheers, Stefan [1] http://svn.debian.org/wsvn/secure-testing/doc/narrative_introduction?op=file&rev=0&sc=0 [2] http://lists.alioth.debian.org/mailman/listinfo/secure-testing-commits [3] http://lists.alioth.debian.org/pipermail/secure-testing-team/2007-January/001023.html
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Secure-testing-team mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/secure-testing-team
