FYI, new release procedures pending.
--- Begin Message ---
<div class="moz-text-flowed" style="font-family: -moz-fixed">robert burrell donkin wrote:
(before this gets out of hand, i'm just asking about the official policy
rather than the rights and wrongs of this policy. my only aim is to be
able to correct any misleading statements posted on lists before they
become major issues.)
in a recent thread, an opinion was expressed by a committer that the
removal of releasable units (eg. sub-projects and sub-sub-projects) from
jakarta to the new functional project is the official policy of the
jakarta pmc - with or without the approval of the current committers.
http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=104517696322936&w=2
after following the discussions on community and elsewhere, i formed the
impression that in the end it would be left to the communities involved.
has a formal vote been taken on forced removal of releasable units from
jakarta (ie removal against the wishes of the communities)?
has a decision been taken at a higher level about enforced removal?
- robert
No. There has been no enforced removals. Nor do I expect there to ever
be any.
Essentially, the only change to Jakarta itself that has been done to
date is the enlarging of the PMC. The only (unratified as of yet by
this PMC) plans that I have is to first enable every PMC member to vote
on every release of every sub-(sub-)*project, and then at some much
later point make it only members of the PMC that can express binding
votes on releases.
Given that I don't expect most of us to express votes on codebases that
we are not involved with, and that by that time all of the thought
leaders of *any* codebase in Jakarta will be members of the PMC, I don't
expect this to be a noticable change operationally to anybody.
With one exception: those that actively wish to exclude others that are
recoginized members of the community from participating will be unable
to do so on crucial release votes. As release votes are majority votes
and not subject to veto, again, I don't expect this to become an issue.
I don't expect to see PMC members participating en masse in technical
issues or issues relating to duplication of function. However, I could
see it occuring on policy related issues, such as licencing, security,
or dependencies on unstable and unreleased code.
Why is this being done? The board wants projects to be accountable for
everything released by that project. I am trying to address that desire
in the least disruptive manner possible.
All this being said, if the majority of committers to any codebase
wishes to be elsewhere (for any reason), they are likely to get not only
my vote but my active support.
- Sam Ruby
P.S. While I would prefer each PMC member to spread this in their own
words, feel free to forward this as you see fit.
</div>
--- End Message ---
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
