[News.eclipse.technology.packaging] Re: Policies for EPP

["Ian Skerrett" <ian.skerrett@xxxxxxxxxxx>]

> I think saying that things can't change because it would be 'hard to 
> explain to users' doesn't really work for me.  Why?  Because new software 
> *is* change.  If the EF (and it's associated projects) want to have 
> 'innovation networks', then things must change.  Like a shark, if it's not 
> moving forward, it's dead :).

Scott, there is lots of change that happens in Eclipse.  We are just talking 
about the packages that EPP is producing.
>
> I guess I'm not so worried about users and change as you are.  Change is 
> constant (especially in sw dev tools).  I don't think that is avoidable. 
> Now I think it's possible to make it simpler for users to deal with 
> change, but I thought that's what EPP was really setup to do.

I agree with Markus.   The packages need to be consistent from one release 
to the next or we run the risk of confusing people.   Change will happen but 
at a much slower pace than in other parts of the Eclipse community.


> Yes, that is my major point...EPP certainly does need policy/instructions 
> for a project that wants to be part of an EPP package.  But those 
> instructions will be useless/meaningless to projects if it is not possible 
> for them to do anything that will lead to inclusion in EPP.

I actually think most projects will NOT be included in the EPP packages.   I 
think this is where you and I probably disagree.  EPP will fail if it starts 
to include too much stuff.   They need to include the base functionality but 
encourage the use of update sites to get additional project functionality.

If EPP is viewed as the primary distribution channel for Eclipse projects 
then we will fail; in my opinion.