Re: Action regarding umbrella PMCs
From: "Roy T. Fielding" [EMAIL PROTECTED] That is, the PMC is supposed to be elected by the committers on the project, or include all of the committers on the project, because that's pretty much the only way to ensure that what we do remains a true collaboration and doesn't degrade into some sort of consortium or a mirror of our real jobs. This statement would seem to be in conflict with the PMC bylaws. "New members may be elected to the PMC. In order to be elected, a person must have served as a Committer and be nominated by a PMC Member. Once nominated, all of the PMC will vote and those receiving a 3/4 positive vote will become a member." Is the ASF board overriding the PMC bylaws just in this instance or does this principle hold for all PMC appointments? If it is the latter, then do the bylaws need to be amended to that effect? Conor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Action regarding umbrella PMCs
Conor MacNeill wrote: This statement would seem to be in conflict with the PMC bylaws. The PMC bylaws are broken in a number of areas. Is the ASF board overriding the PMC bylaws just in this instance or does this principle hold for all PMC appointments? If it is the latter, then do the bylaws need to be amended to that effect? Roy is not overriding the PMC bylaws, he is simply describing the original intent of the board. That being said, I agree with Roy. - Sam Ruby - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Action regarding umbrella PMCs [long]
Conor MacNeill wrote: Is the ASF board overriding the PMC bylaws just in this instance or does this principle hold for all PMC appointments? If it is the latter, then do the bylaws need to be amended to that effect? Sam Ruby wrote: The PMC bylaws are broken in a number of areas. ... / Roy is not overriding the PMC bylaws, he is simply describing the original intent of the board. -- For reference: ASF BYLAWS RE: PMC's http://apache.org/foundation/bylaws.html snip Section 6.3. Project Management Committees. In addition to the officers of the corporation, the Board of Directors may, by resolution, establish one or more Project Management Committees consisting of at least one officer of the corporation, who shall be designated chairman of such committee, and may include one or more other members of the corporation. Unless elected or appointed as an officer in accordance with Sections 6.1 and 6.4 of these Bylaws, a member of a Project Management Committee shall not be deemed an officer of the corporation. Each Project Management Committee shall be responsible for the active management of one or more projects identified by resolution of the Board of Directors which may include, without limitation, the creation or maintenance of "open-source" software for distribution to the public at no charge. Subject to the direction of the Board of Directors, the chairman of each Project Management Committee shall be primarily responsible for project(s) managed by such committee, and he or she shall establish rules and procedures for the day to day management of project(s) for which the committee is responsible. The Board of Directors of the corporation may, by resolution, terminate a Project Management Committee at any time. Section 6.4. Election and Term. The officers of the corporation and the members of each existing Project Management Committee shall be appointed by the Board of Directors or appointed by an officer empowered by the Board to make such appointment. Such appointment by the Board of Directors may be made at any regular or special meeting of the Board. Each officer shall hold office and each member of a Project Management Committee shall serve on such committee for a period of one year or until his or her successor is elected and qualified or until his or her earlier resignation or removal. Section 6.5. Removal of Officers. Any officer or agent and any member of a Project Management Committee elected or appointed by the Board of Directors may be removed by the Board whenever, in its judgment, the best interests of the corporation will be served thereby. Section 6.6. Vacancies. Any vacancy, however occurring, in any office or any Project Management Committee may be filled by the Board of Directors. /snip ASF BOARD MINUTES RE: JAKARTA PROJECT http://apache.org/foundation/records/minutes/1999/board_minutes_1999_09_16.txt snip D) Jakarta Project Discussion was held on a proposal to create a project for development and maintenance of open-source Java Servlet-related software. Roy submitted a resolution based on Brian's request to establish the PMC, consisting of those people closely involved in the existing jServ project and related projects at Sun and IBM. Ben Hyde had some concerns about the last paragraph in the resolution, where it tasked the PMC with the creation of a set of bylaws. Brian clarified that the project bylaws specify how new developers are brought aboard, old ones retire, and the PMC chair elected by the project participants. Roy observed that the Server project has them, called project guidelines, and that the intent of the resolution is to encourage the PMC to set their own guidelines with the appropriate frame of mind. The following resolution was unanimously adopted by vote of the directors present (Brian, Ken, Roy, BenH, Sameer, Dirk): WHEREAS, the Board of Directors deems it to be in the best interests of the Corporation and consistent with the Corporation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source Java Servlet-related software for distribution at no charge to the public. NOW, THEREFORE, BE IT FURTHER RESOLVED, that a Project Management Committee, to be known as the "Jakarta Project Management Committee", be and hereby is established pursuant to Bylaws of the Corporation; and be it further RESOLVED, that the Jakarta Project Management Committee be and hereby is responsible for the creation and maintenance of Java Servlet-related software based on software licensed to the Corporation; and be it further RESOLVED, that the office of "Vice President, Jakarta" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chairman of the Jakarta Project Management Committee, and to have primary responsibility for management of the projects within the scope of responsibility of the Jakarta Project Management Committee; and be
Re: Action regarding umbrella PMCs
From: "Sam Ruby" [EMAIL PROTECTED] Roy is not overriding the PMC bylaws, he is simply describing the original intent of the board. That being said, I agree with Roy. Oh, I agree too. I am just wondering how all this fits together. For example the recent vote by PMC members on PMC nominees. Is that superceded by this statement? What is the plan from here? Conor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Action regarding umbrella PMCs [long]
Henri Gomez wrote: Pierpaolo Fumagalli is IBMer ? At the time he did accept paychecks from IBM. Now he accepts paychecks from Sun. In between he accepted paychecks from a company named Exoffice which changed its name to Intalio. Who you accept paychecks from and who you are can be quite different things. Pier is a perfect example. - Sam Ruby - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Action regarding umbrella PMCs
Conor MacNeill wrote: Oh, I agree too. I am just wondering how all this fits together. For example the recent vote by PMC members on PMC nominees. Is that superceded by this statement? What is the plan from here? My bias is towards evolution, so we'll try that first. If not, there always is plan B. The first order of business is to get adequate representation of the code bases in order to address the board's concern. Depending on the outcome of the election, this may take iterations. The next order of business is a radical overhall of the bylaws. Ted has been sheparding an effort to do that already. I'd like to consider some more radical changes than the one considered so far, starting with the election process. Other, equally important tasks are underway to make the various subprojects are interwoven into the quilt that is Jakarta. Gump takes a fairly coarse view, and needs to expand into testing. The emerging library/commons subproject attacks this problem from another direction, and focus on reuse. - Sam Ruby - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Action regarding umbrella PMCs [long]
GOMEZ Henri [EMAIL PROTECTED] wrote: Elias Bayeh, IBM[EMAIL PROTECTED] Hans Bergstein [EMAIL PROTECTED] James Davidson, Sun [EMAIL PROTECTED] Pierpaolo Fumagalli, IBM[EMAIL PROTECTED] Craig McClanahan, MyTownNet [EMAIL PROTECTED] Stefano Mazzocchi, Independent [EMAIL PROTECTED] Jon Stevens, Clear Ink [EMAIL PROTECTED] James Todd, Sun [EMAIL PROTECTED] Pierpaolo Fumagalli is IBMer ? Used to be one... Then I moved to a startup called Intalio and finally (thank god) I landed at Sun... And I'm not going to move from here for quite a long time... Pier -- Pier Fumagalli http://www.betaversion.org/ mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Action regarding umbrella PMCs [long]
Sam Ruby [EMAIL PROTECTED] wrote: Who you accept paychecks from and who you are can be quite different things. Pier is a perfect example. Meaning that no-matter who "owned" me, I've always been the usual pain in the ass :) :) :) :) Pier -- Pier Fumagalli http://www.betaversion.org/ mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Action regarding umbrella PMCs
Hello everyone, The Apache Software Foundation exists to provide a solid legal foundation under U.S. corporate law for many of the collaborative activities that were formerly done by a group of individuals called the Apache Group. Our status as a corporation allows us to protect the work of individual volunteers and provide both code and people some insulation from the the legal liabilities associated with distributing software. In order to accomplish that, the Foundation must retain and exercise sufficient oversight of its activities equivalent to that of other legal entities. We accomplish that, in accordance with our bylaws, by appointing a Project Management Committee (PMC) to oversee the activities of each and every project. The purpose of a PMC is to make sure we do things legally and without recklessly endangering the foundation's assets (the good name and all of the code contributed to the foundation). The PMC does not exist to make the technical decisions regarding the project, though it does have the authority to determine who has commit access and voting privileges within the project, and what that means in terms of project guidelines. The ASF board determines the scope of a PMC (i.e., the range of different software products managed under the oversight of the PMC) when the PMC is initiated and when it is refreshed on an annual basis, or whenever the board feels it is appropriate to update the PMC status. The membership of the PMC is appointed by the board in accordance with the desires of the volunteers working on the project. That is, the PMC is supposed to be elected by the committers on the project, or include all of the committers on the project, because that's pretty much the only way to ensure that what we do remains a true collaboration and doesn't degrade into some sort of consortium or a mirror of our real jobs. As I mentioned at the beginning of the year: In my opinion (this time as chairman), many of the sub-projects currently hosted under the XML and Jakarta projects are outside the scope of the the mandate given to those PMCs. There are only three solutions to this problem: 1) board resolutions are required to expand the scope of those PMCs; 2) board resolutions are required to separate each new project into a more focused PMC; 3) the chairman will direct remaining out-of-scope and inadequately overseen projects to cease distributing software as part of the Apache Software Foundation. Needless to say, I was disappointed by the lack of response on the part of the XML and Jakarta projects. Two months should have been more than enough time to set a direction and write a couple resolutions detailing how the projects would be overseen. Regarding Jakarta, the Jakarta PMC has decided to expand its mandate to include its present projects, under the theory that the communication problems can be solved by following the project guidelines and holding more regular meetings, much like the board does for the ASF. Sam Ruby presented a resolution to the board that would expand the mandate of Jakarta to cover all server-related Java software. The board refused to consider this resolution because it did not include a list of PMC members that could reasonably represent all of the projects under that mandate. Sam has been given the task of assembling a proposed PMC according to the wishes of all of the committers on those projects, to be presented to the board at the next meeting (March 21). Regarding XML, the XML PMC did not respond to my request and no resolution was forthcoming. As a result, the board has decided to terminate the current XML PMC and has assigned Dirk-Willem van Gulik the task of assembling one or more project management committees according to the wishes of the committers within each of the projects currently under the XML banner. Resolutions for such projects will be considered at the next board meeting. My expectation is that all of our current XML and Jakarta projects will be refreshed before the end of the March 21 meeting. If not, the next board will be advised to cancel any projects that remain in an orphaned state. Sincerely, Roy T. Fielding, Chairman, The Apache Software Foundation ([EMAIL PROTECTED]) http://www.apache.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
