Sorry for not making the context of the call for participation clear, I was head down and it was obvious to me :-) Please keep your ideas warm for until we ship 3.4.
As for the definition of what we want to do in the director application, the easiest is to start from the current command line application provided by UM (http://help.eclipse.org/help33/topic/org.eclipse.platform.doc.isv/reference/misc/update_standalone.html). PaScaL From: Thomas Hallgren <[EMAIL PROTECTED]> To: Equinox development mailing list <[email protected]> Date: 04/09/2008 02:13 AM Subject: Re: [equinox-dev] [prov] Participation opportunity This wasn't apparent to me either. We're still interested of helping out of course but with a two week timeframe I guess you already have somewhat specific requirements for what the director and mirroring applications should be able to do. Where can I find this information? Regards, Thomas Hallgren Scott Lewis wrote: > Hi Jeff, > > Jeff McAffer wrote: >> While we are all loving each other I feel obliged to say that the >> focus of >> this call to action was (I believe) helping p2 *ship in 3.4* with a >> reasonable function level. > > It wasn't apparent to me that the original participation solicitation > was scoped to be 'helping p2 ship in 3.4'...but if that's the > intention then that's cool. > > Scott > > _______________________________________________ > equinox-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
