Hi Richard, > I think that if you could justify going forward with your idea, or if > others came on board and something independent could be done, this would > be great. I think this is a situation where both the established free/OS > community side of LEAF and your business, and other similar businesses > can all win. > > If you were to provide the Lip's in CVS and submit notification for each > update to a new list, then you could still offer a wonderful VA product > that keeps track of the modules used by a particular subscriber, > notifies them via email when one of there modules needs to be updated, > including a link to the file, and possibly even offering an automated > update mechinism that could be turned on using a special LRP you > provide, for each LRP the end user wants to keep up-to-date. OK, that > last bit may be a bit much, but the point I'm trying to make is that a > balance could be maintained between a base level that could benefit > everyone, and a pay level that anyone that has the $ could not afford to > be without (including possibly me). > I understand what you're saying - and I guess the framework (scripts to handle the update proces) would surely make their way into the Bering uClibc distro. At this point, I'm just not sure if there's enough interest in the leaf userbase to warrant spending business hours on this (I already spend much of my spare time on Bering uClibc, but that's a different matter :-))
As I said - nothing is set in stone at this point, we're still in the decision making process, so we're surely open for suggestions. In the end, it all comes down to the fact that we need to make sure we're not putting in a lot of money and resources into a project that will not at least create some return over a reasonable amount of time. We're not a huge corporation, so we can't pump huge amounts of cash into a project that will not pay for itself at some point. If a model where people pay for the "premium service" (notification of updated packages, maybe even a "push model" for some sort of "auto-update" - even though I have rather strong reservations about updates being installed without the administrator knowing about it) works even if the same packages are published for free on the website, I don't see why things couldn't be done that way. > This slightly higher level of service to the general LEAF community > would also make it more attractive for other LEAF developers to get > involved in this mini project so that the entire thing was not just on > the shoulders of one company. Well, right now the same sort of thing is solely on the shoulders of several dedicated individuals, who do this in their spare time - so even if it's just one company that is adding resources to the project, it would already be an improvement :-) Martin ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
