Re: [aperi-dev] Extending Aperi: summary of steps:

[Ted Slupesky <slupesky@xxxxxxxxxx>]

Hi Chris,

I think that's a decent list but it's
at a very high level. For example, an awful lot is hidden in step 1! And
we would imagine folks contemplating changes communicating via aperi-dev
probably during that step. In fact perhaps the first step is to propose
your change on aperi-dev, in order to explore what the impact would be
on the whole of Aperi. I'm sure there are other steps that ought to be
included here as well.

--
Ted Slupesky | Eclipse Aperi Project Lead | IBM: 349-5413 | External: (503)
820-3853

Chris King/Chicago/IBM@IBMUS
Sent by: aperi-dev-bounces@xxxxxxxxxxx

03/26/2007 08:49 AM

Please respond to
Aperi Development <aperi-dev@xxxxxxxxxxx>

To	aperi-dev@xxxxxxxxxxx
cc
Subject	[aperi-dev] Extending Aperi: summary of steps:

When planning a change or addition to an Aperi component
through an extension/plugin, what does an open source user need to keep
in mind? I am looking for a high-level summary of steps, similar to something
like this:

1. Analyze the impact of the changes on the whole of Aperi.
2. Submit a change request to the component design team.
3. Test the change or addition by make an overall build with all the changes
to ensure nothing breaks.
4. Send out a note to the aperi-dev mailing list highlighting the change.

Can anyone add to this list or suggest edits?
_________________

Chris King
Aperi information development
External: 512.687.5166
IBM: 273.5547
chriskng@xxxxxxxxxx
Aperi: http://www.eclipse.org/aperi/index.php_______________________________________________
aperi-dev mailing list
aperi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aperi-dev