From: Nektarios K. P. <npa...@in...> - 2006-04-16 08:41:49
|
As far as I am concerned this thread is *not* about blaming you or the=20 rest of the UPnP team. So there is no need to defend yourself. :-) My intention was to step up and say "Hey something is not going very well with this project!" "I care about this project" "I want to help improving the image" I've never threaten to fork the project. I don't even want to take over the project (I don't have the time). I=20 honestly believe it takes more than a few clicks of the mouse to pass on=20 the torch. I mean you can not transfer accumulated knowledge and=20 experience by clicking the mouse ;-) But: I am willing to help. I can be part of a community that actively maintains the project. I can go through the patches/bug reports and discuss them here in the=20 dev list. I see Remi is already doing this, but I can help. -- Nektarios Dan Baumberger wrote: > I am a little confused by this whole thread. This project started in 20= 01 > and generated little development interest from anybody until late in 20= 05. > After years of not seeing anything really going on, I stopped monitorin= g the > project (other than the mailing lists) because I did not have the time.= Our > intentions when creating this project were not to be the maintainers fo= r the > long term but to find someone willing and able to take over. Unfortunat= ely, > that person (or persons) never turned up. We contacted a few people tha= t > might be interested over the years but were turned down. >=20 > In the last few months, we have received several "threats" about forkin= g the > project. My question to you is why don't you (in the plural sense) step= up > and take over this one instead of creating confusion by forking the pro= ject? > If you have the time and interest to take over the project, I am more t= han > willing to pass it on. The intention never was to ignore anybody's > contributions but with little time and no one to help, it was inevitabl= e. >=20 > Let me know if this is something you would like to do. It only takes a = few > clicks of the mouse to pass on the torch. >=20 > - Dan - >=20 > -----Original Message----- > From: upn...@li... > [mailto:upn...@li...] On Behalf Of qxc@gmx.= de > Sent: Saturday, April 15, 2006 5:45 AM > To: Nektarios K. Papadopoulos > Cc: upn...@li... > Subject: Re: [upnp-sdk-dev] Project UPnP is DEAD >=20 > Hi, >=20 > the worst thing behind these ancient patches: there also has been one o= f a > RedHat developer, that means the project had a contribution from a deve= loper > of the probably most important Linux distribution and ignored it. >=20 > What I completely don't understand is why these patches are ignored for= that > long time. Applying one to the current CVS mostly isn't a big problem b= ut if > they are that old like most of them it becomes nearly impossible to do = that. >=20 > And I think thats the best way of demotivating developers and people th= at > want to help: waiting until their work becomes useless... >=20 > Michael >=20 > PS: Currently I'm a developer within the UPNP project but depending on = the > progress that the project makes I'm still thinking about a fork from it > where the contributions and efforts other people make are more respecte= d. >=20 >=20 >=20 >> --- Urspr=FCngliche Nachricht --- >> Von: "Nektarios K. Papadopoulos" <npa...@in...> >> An: upn...@li... >> Betreff: Re: [upnp-sdk-dev] Project UPnP is DEAD >> Datum: Fri, 14 Apr 2006 10:46:06 +0300 >> >> Hi Dan, >> >> I've been using upnp-sdk for the last 12 months so I've to thank the=20 >> creators/maintainers for this. Congrats! >> >> OTOH, I've been subscribed to the mailing lists for the same amount of= =20 >> time and I'm sorry to say that before 1.3.1 came out, I had the same=20 >> feeling with Mike. >> >> The list of open patches/bugs that goes back a few years is certainly=20 >> giving that impression. I've submitted three of them myself and I've t= o=20 >> say that when I did I was thinking "I don't expect anyone to see=20 >> this...". 2 of them got closed with 1.3.1 release. >> >> When I saw the 1.3.1 announcement, I was totally surprised. The 1.3.0=20 >> released just one day before, was never announced. There was no=20 >> discussion on the list about the plans, no pre-release for us to test = etc. >> >> I mean, even Remi's queries "Is libupnp maintained ?" and "automake an= d=20 >> autoconf for libupnp ?" back in Oct 13 2005 remained unanswered in the= =20 >> dev list. Obviously, they were answered/discussed privately but this=20 >> does not help to attract more developers. >> >> I think you could have been more clear about "help wanted"; as you jus= t=20 >> did ;-) >> So, I'd like to help with the project anyway I can (when time permits). >> >> BR, >> Nektarios >> >> Dan Baumberger wrote: >>> Why should you be surprised if the maintainers are still active? How = did >> you >>> get subscribed to the SDK dev mailing list if there are no maintainer= s? >>> >>> The project was inactive not for lack of interest by the maintainers, >> but >>> lack of interest from the community. For years, no one was really >> willing to >>> contribute anything nor was anyone interested in taking over the >> project. >>> Those of us who started the project have been waiting to see if any >> interest >>> kindled in the project. Only in the last couple of months has some >> interest >>> sparked.=20 >>> >>> As for developer interest, I've been monitoring the mailing lists fro= m >> day >>> one. Other than Remi and John of late, there hasn't been much develop= er >>> interest. I haven't seen much email with patches or queries about >> getting >>> involved. Had I seen that, I would have responded.=20 >>> >>> If you wish to take over as the (or a) maintainer of the project, let= me >>> know and I can add you. I would like to see this project continue to >>> flourish. It is just unfortunate that I do not have the time to >> contribute >>> to this project. >>> >>> - Dan - >>> >>> -----Original Message----- >>> From: upn...@li... >>> [mailto:upn...@li...] On Behalf Of >> qx...@gm... >>> Sent: Monday, April 03, 2006 3:25 AM >>> To: upn...@li...; >>> upn...@li... >>> Subject: [upnp-sdk-dev] Project UPnP is DEAD >>> >>> Not very funny what I can see... >>> >>> - the homepage at upnp.sf.net is totally outdated, not only the lates= t >>> release isn't mentioned there >>> >>> - the maintainers seem to be not interested in the project, the >> bugtracker >>> is full of open bugs >>> >>> - patches and modifications that are sent in by developers are ignore= d, >>> nothing new is integrated >>> >>> So I'd not be astonished if there are also no maintainers active with= in >> the >>> mailing lists. For me that means the project is dead, apparently beca= use >> of >>> the lack of interest of the maintainers while developers are willing = and >>> able to contribute to the project. >>> >>> Also if I won't expect to get an answer: what plans are there with th= e >>> future of the libupnp? >>> >>> Mike >>> >>> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by xPML, a groundbreaking scripting >> language >> that extends applications into web and mobile media. Attend the live >> webcast >> and join the prime developer group breaking into this new coding >> territory! >> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&da= t=3D121642 >> _______________________________________________ >> Upnp-sdk-dev mailing list >> Upn...@li... >> https://lists.sourceforge.net/lists/listinfo/upnp-sdk-dev >> >=20 |