From: Nicolas G. <nic...@ga...> - 2003-07-28 12:32:14
|
Your project reminds me of a product called "Out-of-the-Box" from EJB Solutions (www.ejbsolutions.com). This is a distribution of Open Source projects for Java and LAMP developpers. It's free but I think it's not Open Source. -- Nicolas Grilly Garden - Marketing pilot=E9 par l'information Tel/Fax +33 1 56 72 21 32 - Mobile +33 6 03 00 25 34 - Web www.garden-paris.com > -----Message d'origine----- > De : sco...@li...=20 > [mailto:sco...@li...] De la part de=20 > Christian Heller > Envoy=E9 : vendredi 11 juillet 2003 17:20 > =C0 : jos...@li...;=20 > jdi...@li...;=20 > sco...@li...; cyb...@li... > Cc : jex...@li...;=20 > jed...@li...;=20 > jas...@li...;=20 > jbo...@li...;=20 > web...@li... > Objet : [Scope-dev] Collaboration [3] >=20 >=20 > ---------- Forwarded Message ---------- >=20 > Subject: Re: [jos-general] Re: [jdistro-devel] Where do we go ? > Date: Wed, 02 Jul 2003 18:46:59 -0400 > From: Gilbert Carl Herschberger II <gc...@mi...> > To: Christian Heller <chr...@tu...> >=20 > At 11:29 PM 7/2/03 +0200, you wrote: > >At first, one question: Is there a reason you didn't send=20 > your email to=20 > >the lists? I didn't find any confidential things. On the=20 > contrary, it=20 > >contains good and important proposals! >=20 > I didn't sent my e-mail directly to the mailing lists because=20 > I thought I might be asking a lot of you. I did not know how=20 > you would feel about that. Now that we agree something must=20 > be done, should you post my message (and > yours) on the various mailing lists? I think you might first=20 > do a little research on the Debian effort. Gather the facts=20 > before presenting it to others. If another project is already=20 > trying to do this, I would like to know more about it. >=20 > I would like to install a Java-oriented--optimized and=20 > enhanced--distribution of GNU/Linux. That would be very=20 > useful to me, too. Is that a goal for Debian? >=20 > Am I speaking of a distribution project? Hmm, maybe I am. My=20 > very first goal for the JOS Project was to provide the JOS=20 > Technical Edition, a distribution of JOS-related stuff. I=20 > made it easier to find stuff. Why? I didn't want others to=20 > have as much difficulty as I did. Certainly, a distribution=20 > project could distribute a collection of "friendly"=20 > applications that are designed to work together. As a=20 > super-project, we might work to "improve" or "upgrade"=20 > existing Java applications so that everything can work=20 > together. We can improve the out-of-box experience. >=20 > Then again, maybe I'm not. As you may have heard, most of the=20 > JOS software does not work together. Isn't that sad? There=20 > are lots of little incompatibilities. >=20 > But of course, all /my/ stuff works together. ;) >=20 > When distributing the files that other people made, I could=20 > do very little to convince them to change their product so=20 > that it worked with other products. I am convinced that this=20 > might be where Java technology suffers the most. It is so=20 > easy to write a Java application that cannot run alongside=20 > other Java applications. But I should be able to run all Java=20 > applications side by side without such incompatibilities. We=20 > have an amazing class loader mechanism that few people are=20 > putting to good use. We have an amazing namespace mechanism=20 > so that different applications don't need to use the same namespace. >=20 > I would like to help define what it takes to build, not just=20 > a Java application that works, but a Java application that=20 > works with other Java applications. Could this be such an=20 > opportunity? Is this the right time? >=20 > This is vaguely familiar. It reminds me of the RedTea project=20 > on sourceforge.net that set out to build a Java equivalent of=20 > RPM, the RedHat Package Manager. I haven't heard from them in=20 > a while. It was "red" because of RedHat. It was "tea" in=20 > response to Java (coffee). The idea was that, with an=20 > equivalent of RPM, Java products could be distributed similar=20 > to the way products are distributed on Linux. The community=20 > wasn't ready for yet another RPM. It seems that it might be=20 > better to determine how Java applications might be tested for=20 > "compatibility" and help authors distribute their products=20 > using RPM. Maybe distribution is a part of it. >=20 > Let's say you wanted the latest version of every Java product=20 > on sourceforge.net. How would you do it? Get a distributor. A=20 > distributor involves people from many projects. They ask=20 > authors to build an RPM for each product. They mirrors the=20 > RPM in a central location, hopefully taking care only to=20 > introduce stable combinations of products, giving you=20 > one-stop shopping. And hopefully, taking care of any=20 > licensing issues. (1) Is every Java product available as an=20 > RPM? (2) Has anyone volunteered to be a distributor? >=20 > Wow! I didn't realize how strongly I felt about this. As it=20 > should be, RedHat is an expert in the distribution of Linux,=20 > not Java. Who is an expert in the distribution of Java=20 > products? Is anyone? >=20 > Thanks, >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email sponsored by: Parasoft > Error proof Web apps, automate testing & more. > Download & eval WebKing and get a free book.=20 > www.parasoft.com/bulletproofapps1=20 > _______________________________________________ > Scope-dev mailing list > Sco...@li...=20 > https://lists.sourceforge.net/lists/listinfo/s> cope-dev >=20 |