Forgot to cc the users list first time. Dirk Meyer wrote:
> > Now to the more detailed answer. > > > > John Molohan wrote: > > > >> >> OK seems how my grand dreams of picking up programming again have >> >> disappeared now that I have less free time than ever I'll offer a >> >> different solution. I'll pay towards this work being done, a couple of >> >> hundred euro, if others donate too to lessen my burden that would be >> >> great. >> >> >> > > > > That would be great, maybe someone here can be moticated to help. And > > of course I also have a paypay account and an amazon wishlist. Search > > for [EMAIL PROTECTED] or [EMAIL PROTECTED] if you feel you want to thank > > me :) > > > Done :) How about you Tack? > > > >> >> I know that the core developers on freevo just don't have enough >> >> hours to deliver 2.0 as soon as everyone wants and there seems to be a >> >> lack of any new blood joining so this might make sense. >> >> >> > > > > That is our main problem. We are two developers (Tack and I). Tack > > "only" works on kaa modules, I do all the Freevo work. We both have > > jobs to get the food on the table, so it is slow. And if I would leave > > the project, it would be dead, nobody else knows the freevo code. Tack > > could start a new project based on kaa in that case, but we want to > > avoid that. So we need new blood joining us, learn to understand the > > code, help us developing some parts. > > > I know that python is gaining in popularity all the time and freevo is a great project so we should be able to attract new blood (I'm trying to convince one of my new staff with python experience to look into freevo :) ). Maybe a web developer is needed to give freevo.org a total revamp and work on increasing the projects visibility. > > One reason for the "Kaa Media Repository" was to split Freevo into > > smaller modules easier to understand. So if some people try to learn > > one or two modules and help us, that would be great (see below). > > > > > >> >> I haven't been involved before in contracting like this in the open >> >> source community so I don't know how it's usually done but I see >> >> that SF has a donate (paypal) option for each project. If I donate >> >> would someone else look after the administration side? >> >> >> > > > > I'm not sure I understand what you mean. > > > Just that I don't know how you would go about attracting the programmer(s). And once they have done the work the 'Freevo project' (you & Tack basically) would pay them (I would have donated to the 'freevo project through paypal & sourceforge already so the funds would there). > > > >> >> How much should be paid per contribution? In terms of attracting >> >> candidates updating www.freevo.org and postings to users local lugs >> >> might be appropriate? This also raises the issue of what would be >> >> the most worthwhile missing code to get done (maybe this isn't the >> >> most important). I guess Dischi, Jason & Rob (if your still around) >> >> are the best people to decide this. >> >> >> > > > > OK, here a small list of task that someone needs to do. What parts are > > worth some money, I don't know. > > > > 1. Mailing lists: I don't have time to read them. I could answer all > > the Freevo related questions in users, but if I do so, I won't have > > any more time coding. So help youself. It would be great if the > > real hard questions could get to me and I answer. Some sort of > > second level support. :) . I try to read the devel list, but > > sometimes users stuff gets into it. The last week I only had time > > for Tacks mails because he is most important for development right > > now. I only saw your mail because someone pointed me to it. > > > I started to (try to) do this a while back but just don't have the time now. If anyone is reading this who knows freevo well from a user point of view please step forward, as Dischi said he'll answer the harder ones, you'll be able to take a lot of pressure off him and give some life to the user mailing list. > > 2. Homepage: someone following svn could post some updates now and > > then. I always want to do it, but again, I have hacking stuff to do > > I like much more. There is a bugreport in one list that the Debian > > install instructions are wrong and I had no time to fix this. > > > > 3. Wiki: we always need more doc. I plan to move the wiki to a new > > server here at the university. I need to check if this is > > possible. Moving away from sf would speed up the wiki. > > > > a. 2.0 API: we have some doc inside the code and start some source > > doc in the 2.0 wiki. But a lot of stuff is missing. This is the > > point were some people could help: read the doc inside the code, > > play with it, learn how it works or read examples and write some > > development doc. As soon as we have good API doc, it is easier > > for new people to help. Don't be shy, just add stuff to the > > wiki. I read wiki the changelog and will fix wrong doc. A > > starting point would be a kaa module. > > > > b. 2.0 internal doc: Some as api but less important. More doc what > > is happening inside. Again, a small kaa module is an easy > > starting point. > > > OK, that shouldn't be too bad if we can get someone interested. > > 4. Coding: Like I wrote before, some important parts are still > > missing. And again, a kaa module is easier to understand than the > > whole Freevo monster. If you want to help but have some questions > > about stuff like kaa.notifier, just ask on freevo-devel or > > #freevo. > > > > a. kaa.player: the module is in a very early stage, much to do, not > > much to understand first (except kaa.notifier). Mplayer and Xine > > need better support for all the cool options they have and > > gstreamer support is missing. > > > > b. kaa.canvas: well, this is where Tack wants to play. But I guess > > help is always needed. Integration of it will be done once > > kaa.canvas is updated (that will be my part). > > > > c. kaa.beacon: my current playground. Most of it is finished, > > integration into Freevo will be the next step. > > > > d. kaa.record: maybe gstreamer based? Hard to tell. Also depends on > > a good steaming solution (kaa.player again). I know someone who > > wants to help, but he has no time at all the next 4 weeks. Also > > missing is teletext support, ad detection, ca support, etc. > > > > > > I guess that's it. > > > > > > Dischi > > > > > I guess a and b are the ones to concentrate on then in order to get a pre2 release out. So would these be the ones to pay for? ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Freevo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-users
