Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [] Eclipse Development Process

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 a
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 repeat
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:
> [] On Behalf
> Of Gunnar Wagenknecht
> Sent: Monday, November 17, 2008 12:35 PM
> To:
> Subject: Re: [] 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* software
> development. I see our role more as someone who is looking at *what*
> the projects produce and *help* projects to understand what others are
> doing and *help* projects in adopting it *if* they want.
> Of course we encourage projects to release often and to use the mailing
> 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

Back to the top