You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Niclas Hedhman <ni...@hedhman.org> on 2004/04/22 10:25:54 UTC
[Proposal] Keeping Fortress/ECM within Apache
Avalon Community at large!
I have tried to stay out of the subject of Fortress/ECM future as much as
possible.
I have finally made my own conclusions from reading all the opinions about the
subject, so now let me throw another spanner into the machinery, which I
believe to be compatible with _everyone's_ wishes and desires... :o)
If Fortress/ECM is 'not good enough for ASF' (Leo Simons' words) and that the
ASF Board has quite large reservations about a codebase "move" distinct from
a "fork" to a home outside ASF, then let's consider another twist to the same
story.
Fortress/ECM IS at the moment part of ASF, i.e. "good enough" at its current
home.
Let it stay here in Avalon! No fork, no move, no transfer, nothing but
evolution of the existing codebase.
And INSTEAD we request Merlin to be promoted to a TLP (Top Level Project),
with an initial PMC and developer base of;
- Stephen McConnell
- Niclas Hedhman
- Alex Karasulu
- Andreas Oberhack
- Timothy Bennett
- J Aaron Farr
(did I forget anyone?)
Those Avalon PMC members with a Merlin-only interest resigns from Avalon PMC,
and a restoration of the Avalon PMC is conducted, to something like;
- J Aaron Farr
- Leo Simons
- Leo Sutic
- Berin Loritsch
- Hammett
- Carsten Ziegler
- Noel Bergman
and possibly the rest of the BOP gang... (PeterD is an issue beyond my
comprehension and the BOP gang need to sort that out. Personally, I think he
is a very good resource, that get things done.)
IMHO, this is the most sensible conclusion of achieving the goals that most
people seems to agree with;
1. Multiple containers create unbearable tensions and lack of focus.
2. Forking is not good, and forking to outside ASF creates many 'issues'.
3. The best interest of the USERS in all categories.
4. The best interest of ASF (no codebase is leaving or terminated).
5. Putting history behind us.
Execution
=========
1. Merlin becomes a TLP with the help of infrastructure@.
2. Merlin codebase and documentation is moved.
3. Avalon maintain Merlin as a "Related Projects" or similar.
4. Merlin will still depend on Avalon, and will maintain its links.
4. http://avalon.apache.org/merlin and a few others are maintained as
redirects.
5. Possibly some other details needs resolution, like which pieces are
actually moved, what shall we do with the org.apache.avalon package names
used in Merlin sub-parts, and will any Merlin committers remain committers at
Avalon...
World Peace and Extinction of All Diseases will follow...
What do you all think?
Niclas
P.S. Please observe that this is a crosspost to 3 lists. Any replies should
be made to dev@avalon.apache.org ONLY, so if you are interested in posting
and reading more about this proposal, please subscribe to that list by
sending a mail to mailto:dev-subscribe@avalon.apache.org.
--
+---------//-------------------+
| http://www.bali.ac |
| http://niclas.hedhman.org |
+------//----------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [Proposal] Keeping Fortress/ECM within Apache
Posted by Stephen McConnell <mc...@apache.org>.
Niclas Hedhman wrote:
> What do you all think?
+1
Stephen.
--
|---------------------------------------|
| Magic by Merlin |
| Production by Avalon |
| |
| http://avalon.apache.org |
|---------------------------------------|
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [Proposal] Keeping Fortress/ECM within Apache
Posted by hammett <ha...@uol.com.br>.
+1
--
hammett
----- Original Message -----
From: "Niclas Hedhman" <ni...@hedhman.org>
To: <de...@avalon.apache.org>
Cc: "Private PMC mailing list for Avalon" <pm...@avalon.apache.org>;
<us...@avalon.apache.org>
Sent: Thursday, April 22, 2004 5:25 AM
Subject: [Proposal] Keeping Fortress/ECM within Apache
> And INSTEAD we request Merlin to be promoted to a TLP (Top Level Project),
> with an initial PMC and developer base of;
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: [Proposal] Keeping Fortress/ECM within Apache
Posted by "Noel J. Bergman" <no...@devtech.com>.
> > Please see http://wiki.apache.org/avalon/Reorganization.
> I take this as you are in favour of a separation happening within ASF.
I posted at least one note to that effect on the PMC list, to which Peter
Royal responded, and then forwarded to dev@.
> I took the liberty to [...]
Great. :-)
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [Proposal] Keeping Fortress/ECM within Apache
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Saturday 24 April 2004 07:11, Noel J. Bergman wrote:
> Please see http://wiki.apache.org/avalon/Reorganization.
I take this as you are in favour of a separation happening within ASF.
> I am trying to record people's willingness to participate (sign
> up is the last item on each section), and collaborate on the format of the
> reorganization.
Ok, I am playing along and hope others do so as well. I took the liberty to;
1. Fill in some names that I am fairly sure about.
2. Changed "Members" to "PMC" and "Committers" as I for instance, don't want
to participate on Avalon PMC, but would like to be committer.
3. Fill in "my view" of parts.
Niclas
P.S. Your own place folder is no longer needed. :o)
--
+---------//-------------------+
| http://www.bali.ac |
| http://niclas.hedhman.org |
+------//----------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: [Proposal] Keeping Fortress/ECM within Apache
Posted by "Noel J. Bergman" <no...@devtech.com>.
Niclas, et al,
Please see http://wiki.apache.org/avalon/Reorganization. That is a
strawman. I am trying to record people's willingness to participate (sign
up is the last item on each section), and collaborate on the format of the
reorganization. I have started with the idea of a Federation. Every agrees
that there is value and interest in compatibility, therefore those projects
that agree to conform to what will be the agreed upon specifications would
be able to be part of the Avalon Federation.
This is just a strawman to start. I did start with three projects rather
than keep Fortress/ECM within Avalon, but I don't really care how the things
are reorganized, so long as we can reduce the social tensions and allow
healthy development.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: [Proposal] Keeping Fortress/ECM within Apache
Posted by Alex Karasulu <ao...@bellsouth.net>.
> World Peace and Extinction of All Diseases will follow...
Amen to that!
> What do you all think?
+1
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org