RE: [eclipse.org-architecture-council] Eclipse Development Process
+1 for a "Top 10 process recommendations" being maintained by the AC.
In my experiences on Mylyn, AspectJ and AJDT, it took a considerable amount
of effort to figure out the Platform practices that we needed to emulate,
and then to figure out how to adapt them to our considerably smaller
projects. The tools that we use, such as Bugzilla and Eclipsepedia, are so
flexible and process agnostic that it takes time for newcomers to figure out
process best practices, ranging from simple stuff like naming milestones to
managing large bug backlogs.
> -----Original Message-----
> From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx
> [mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx] On Behalf
> Of Mike Milinkovich
> Sent: Monday, November 17, 2008 10:05 AM
> To: 'eclipse.org-architecture-council'
> Subject: RE: [eclipse.org-architecture-council] Eclipse Development
> Since I encouraged David to kick off this conversation, let me explain
> I agree vehemently that there is no such thing the single software
> development process that will be suitable for every project at Eclipse.
> However, I do think that there are many projects that would gladly take
> little guidance if it was offered.
> So rather than a methodology, could people imagine a "top 10" list of
> process recommendations maintained by the AC? The goal is not to be
> intrusive. The goal is to be helpful.
> Gunnar's point about mentoring is correct. But if every mentor has to
> the same "top 10" list to each project, wouldn't it be a little more
> effective to write it down?
> Mike Milinkovich
> Office: +1.613.224.9461 x228
> Mobile: +1.613.220.3223
> > -----Original Message-----
> > From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx
> > [mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx] On
> > Of Gunnar Wagenknecht
> > Sent: Monday, November 17, 2008 12:35 PM
> > To: eclipse.org-architecture-council
> > Subject: Re: [eclipse.org-architecture-council] Eclipse Development
> > Process
> > David Carver schrieb:
> > > John I agree, but from my understanding is that Eclipse originally
> > was
> > > founded on Agile techniques...
> > I don't think that this is the case. You are probably mixing up the
> > Eclipse project with the Eclipse Foundation. But I don't know either.
> > IMHO we should *not* define or instruct projects how they *do*
> > development. I see our role more as someone who is looking at *what*
> > the projects produce and *help* projects to understand what others
> > doing and *help* projects in adopting it *if* they want.
> > Of course we encourage projects to release often and to use the
> > lists and Bugzilla, etc. But I see this more as part of our mentoring
> > task to help projects get started and develop their communities.
> > -Gunnar
> > --
> > Gunnar Wagenknecht
> > gunnar@xxxxxxxxxxxxxxx
> > http://wagenknecht.org/
> eclipse.org-architecture-council mailing list
> IMPORTANT: Membership in this list is generated by processes internal
> to the Eclipse Foundation. To be permanently removed from this list,
> you must contact emo@xxxxxxxxxxx to request removal.