Re: ECF development process (was Re: [ecf-dev] Re: Tool Evaluation: Atl

[Wim Jongman <wim.jongman@xxxxxxxxx>]

Hi,

What is recognizable in every growing project is the burden of
maintenance. All artifacts that are brought into the project have to
be accepted also on the basis of maintainability. For example, making
a .psf file seems like a good idea in the beginning but if there is no
focussed maintenance on it then things like that can degrade the
overall quality.

Mik Kersten once told me that donating stuff to a project is like
giving a puppy. It seems all nice and yippee in the beginning but you
have responsibility for years to come. A great metaphor.

If stuff is accepted then we need to embed maintenance in the
development process as well. Think of articles, wiki pages, helptext,
releng stuff etcetera. It would be great if some kind of workflow
could be hooked to the code-review.

Code review is a good thing but it comes with a price. I would rather
opt for better tests. For code-review to work, we would have to work
in small tasks, clearly document the things that have been fixed, how
it can be tested, etc.. I have been doing some small work for the GIT
project and their Gerrit reviewer seems to work well.

I am very interested in your experiment with Crucible.

Regards,

Wim

On Sat, May 29, 2010 at 9:48 AM, Markus Alexander Kuppe
<ecf-dev_eclipse.org@xxxxxxxxxxx> wrote:
> On 05/26/2010 04:01 PM, Mustafa K. Isik wrote:
>> If - like me - you're a sucker for screenshots, here's a first review
>> request http://img.ly/1lwl
>
> Hi,
>
> Mustafa and me have agreed that I will also use Crucible for reviews
> during my GSoC project [0]. Mustafa, how do we link enhancement requests
> tracked in Bugzilla to Crucible/Fisheye?
>
> On a side note, I am currently prototyping how bundles/features hosted
> with git can be best build with Hucky [1].
>
> @Wim: On a recent ECF con call you said something about an official
> workflow for new contributions you would like to see supported/defined.
> Do you think a review tool is part of such a workflow?
>
> Markus
>
> [0] http://dev.codesurgeon.com:8060/changelog/eclipse-ecf-dns-sd-discovery/
> [1] https://bugs.eclipse.org/314862
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ecf-dev
>