Re: Jakarta stats
Martin van den Bemt wrote: Vadim Gritsenko wrote: Martin van den Bemt wrote: The result can be a couple of things (probably depending on the response) : - Leave it as is - Move them to emuritus Above two are the only acceptable choices for folks with valid accounts. We can discuss means and mechanisms of moving to emeritus and back, but removing folks who fall into groups 2) to 5) is unacceptable - all IMHO. Removing can also be started on request of the committer... So the third option is acceptable. (it is happening as we speak btw : Jeff Dever, see infrastructure list). Well that's different - we should not hold anybody against their will :-) Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jakarta stats
Martin wrote: > The result can be a couple of things (probably depending on the response) : > - Vote on them (?) I think the most straightforward thing is simply to announce that a vote will be held for which the rules are that more than a quorum of +1's and no -1's are required to remove a PMC member to emeritus status, with reinstatement being achieved by vote on application. In this way any less active (by which I don't mean "older" ;-) PMC member could assert their right to remain by voting -1and vetoing their removal, or confirm their agreement by voting +1. In theory any PMC member who is made emeritus against their will by this action has also demonstrated that they aren't paying enough attention. Jakarta has always been a meritocracy, often described as "the more you do the more responsibility you will obtain" IMHO to achieve balance and vitality at the top the converse should also be true, the less you do the more responsibility you wll lose. d. *** The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient (or responsible for delivery of the message to the intended recipient) please notify us immediately on 0141 306 2050 and delete the message from your computer. You may not copy or forward it or use or disclose its contents to any other person. As Internet communications are capable of data corruption Student Loans Company Limited does not accept any responsibility for changes made to this message after it was sent. For this reason it may be inappropriate to rely on advice or opinions contained in an e-mail without obtaining written confirmation of it. Neither Student Loans Company Limited or the sender accepts any liability or responsibility for viruses as it is your responsibility to scan attachments (if any). Opinions and views expressed in this e-mail are those of the sender and may not reflect the opinions and views of The Student Loans Company Limit ed. This footnote also confirms that this email message has been swept for the presence of computer viruses. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Jakarta stats
Noel, Happy new year, Inactive as a commiter, which I took to be the definition Henri used. As a member I can (and will) still actively monitor and interfere in Jakatra PMC business, and I lurk with occasional posts on a few project lists, I'm no shrinking violet and in theory I can get all the karma I want (mua-ha-ha) but in practice I don't have anything very tangible to contribute to Jakarta anymore and much less time in which to contribute it. What I wondered was whether or not my having a PMC "seat" as an emeritus commiter could be seen as in any way holding the project back. d. --- Danny Angus Lead Technical Consultant ICT Products Development 4W - Ext: 33257 Direct Dial: +44 (0) 141 243 3257 |-+> | | "Noel J. Bergman"| | | <[EMAIL PROTECTED]| | | >| | || | | 12/01/2006 05:53 | | | PM | | | Please respond to| | | "Jakarta General | | | List"| |-+> >-| | | | To: "Jakarta General List" | | cc: | | Subject: RE: Jakarta stats | >-| Danny Angus wrote: > I'm one of the "1) Inactive PMC members Define inactive. Inactive as a committer? Inactive as a PMC member providing oversight to Jakarta projects? I'm in the former category, as are many, but I still actively monitor several project lists, even if I only post when I have something specific to contribute. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] *** The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient (or responsible for delivery of the message to the intended recipient) please notify us immediately on 0141 306 2050 and delete the message from your computer. You may not copy or forward it or use or disclose its contents to any other person. As Internet communications are capable of data corruption Student Loans Company Limited does not accept any responsibility for changes made to this message after it was sent. For this reason it may be inappropriate to rely on advice or opinions contained in an e-mail without obtaining written confirmation of it. Neither Student Loans Company Limited or the sender accepts any liability or responsibility for viruses as it is your responsibility to scan attachments (if any). Opinions and views expressed in this e-mail are those of the sender and may not reflect the opinions and views of The Student Loans Company Limit ed. This footnote also confirms that this email message has been swept for the presence of computer viruses. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Notice of intent.... #2
Tim OBrien wrote: --- Stephen Colebourne <[EMAIL PROTECTED]> For example: - HttpComponents - WebComponents - LibraryComponents (narrowAPI-deep) - BaseComponents (broadAPI-shallow) Explain that narrowAPI-deep, braodAPI-shallow business. BroadAPI-Shallow The principal API of the component is broad. That is, it consists of lots of methods. Each of those methods is Shallow. That is, each method does relatively little processing. Typically, these will not have config files. Typically, these wil not have dependencies. For example, a static Utils class. For example, commons-lang, commons-io. NarrowAPI-Deep The principal API of the component is narrow. That is, there are relatively few methods in the whole javadoc that most users should call. Each of those 'external' methods is Deep. That is, each external method performs a lot of internal work to achieve its goal. Typically, these will have config files. Typically, these wil have dependencies. For example, commons-jxpath, oro. I sugest these as groupings as I believe there is a difference in skills in creating these two types of libraries. With NarrowDeep its all about the making that narrow API as simple to understand, yet powerful, as possible. With BroadShallow, there is a lot of work defining the method exactly and in naming. (Plus lots of overap in skills too...) Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
