Move to freevo-devel On Fri, 2008-06-20 at 17:48 +0200, Dirk Meyer wrote: > "Adam Charrett" wrote: > > The drive to get some documentation in kaa is a great start, but some > > proper architecture diagrams would help all involved. > > I could do that ... but in that case I will not write any code for > Freevo or kaa for a long time. I would prefer for other people to > write some docs. So take kaa.notifier and write some docstrings. Jason > and I will correct errors before checking it in and if you add a doc > to 5 out of 7 functions because you do not understand the other two, > we will add the doc. I only do not want to spend too much time writing > docs. If you have a question, ask. :)
Not really what I was looking for. Your complaint about taking time is true, just spent the last week+ working on some design documents for work myself. But the point is that once these UML designs are in place (not necessarily all the way done to function parameter level) somewhere else can come clean to the project, pick the design up get a good idea of how things are supposed to gel together and start working. The problem with lots of 1 man projects (I'm just as guilty here I've done very little design work for my other project dvbstreamer) is that all the ideas are in the head, which makes it difficult to help :-). Some simple collaboration diagrams show how the different services of freevo are supposed to work together would be useful. > I started epydoc for Freevo 2.0. Run 'epydoc -v --config=doc/epydoc' > in the freevo ui subdir _after_ you installed Freevo 2.0. > > > I've just had a look at Entertainer's web site > > (www.entertainer-project.com another python/clutter based media > > center) and the first thing that impressed me was not their UI but > > the fact that they had UML design documents (sad I know). But this > > did make me think that they had taken the time to think about what > > they wanted and get it down in a form that other people can see and > > understand. > > We had some discussions on irc and on the devel list and some parts > needed some rewrites until we got it right. So no, there is no real > doc. > > > So I suppose Dischi this question goes to you, do you have any firm > > requirements for phase 1 of Freevo 2. > > What phase 1? Besides the gui system I require someone to play with > gstreamer to create a new recorder. > > > Once we have those perhaps we could break the work down so any one > > interested in helping could be assigned an area that they are > > interested in/capable of working on. > > I will find stuff to do, just tell me what you want to do :) > > > Basically I think its time for some project management <spits out bad > > taste in mouth>... > > Right know I am the only one hacking on Freevo 2.0 and Jason and I are > the only two people hacking on kaa modules. Until we have more > developer I need no project management. I'm also very busy with other > stuff at work right now that may affect Freevo in a later version. > > > Dischi > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
