On Fri, 2009-03-06 at 08:14 +0100, Andreas Tille wrote: > Please have a look at > > http://blends.alioth.debian.org/lex/ > > It took me about 15 minutes to reach the status as it is with the > tasks pages (I just prepared three tasks as examples) and the bugs pages > for the developers. > > The basic where the tasks and bugs pages are rendered from are the so > called tasks files which are avialable at > > > http://svn.debian.org/wsvn/blends/projects/lex/trunk/debian-lex/tasks/?rev=0&sc=0 > > and which is in fact the "work" I had to do - everything else was done > automatically and even building of metapackages would be possible from > now on using the blends-dev framework. > How to continue from here? > > At first I would ask for a login at alioth.debian.org. Once you have > this login just ask me to add this user ID to the blends project which > enables you access to the svn above. You will see that adding information > to the tasks files is quite simple - advanced examples are for instance > in > > > http://svn.debian.org/wsvn/blends/projects/med/trunk/debian-med/tasks/?rev=0&sc=0 > > Feel free to ask if anything remains unclear (either in private or also > via the list [email protected]).
I would like to read more about debian-med. I remember debian-lex was trying to tee off debian-med, but it was informal. So now all the wisdom has become vested in blends-dev and blends-common? blends-dev is not in etch, the only Debian I can reach right now (writing in Ubuntu). Is it in testing, unstable? I'll ask the noob questions on debian-custom. > BTW, a new strictly blends > oriented list will be created hopefully soon (you might support this > by adding your opinion to http://bugs.debian.org/514023 by sending a mail > to [email protected]) and I would suggest to subscribe this list to > be informed about new Blends related techniques or to influence decisions > about these techniques. Done. > > If you might hesitate to just work on the tasks files directly it is > fine to send me patches for a beginning period. But I see no chances > to break anything important. > > You might decide yourself whether you want continue a discussing about > possible further tasks on the Wiki to enable a wider audience to edit > changes and then move the result to the tasks files or whether you relay > on discussion on the debian-lex mailing list like: > > - please add a new task containing package x > - please add package y to task t > > (Please do not hesitate to ask if anything remains unclear!) I would make use of all the tools that are already all provided, mailing list, wiki, and now a blends subproject. What luxury. > > The next step is trying to involve developers to work down the > todo list which are the "red" entries on the tasks pages (for > instance elawoffice at > http://blends.alioth.debian.org/lex/tasks/admin.html ). > While it is sometimes hard to find an official Debian Developer > for this task you might like to ask whether upstream is able to > do some packaging work (it is also in upstreams interest to have > Debian packages) and ask a Debian Developer to sponsor such a > package to the official Debian mirror. > > I hope these hints were not to overwhelming and wish you good > luck with Debian Lex! > > Kind regards > > Andreas. > It's not too overwhelming, but overwhelming enough, especially at about 10 on Sun. eve. But I see some things are moving ... Elaine -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
