Re: [VOTE] Retire Corinthia
On Sun, Nov 15, 2015, at 10:01 PM, Marvin Humphrey wrote: > This is a vote of the IPMC to confirm the decision to retire the podling. > > [ ] +1 to retire Corinthia from the Incubator +1 (binding) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Apache Metrics, Not Apache Humans
On Sun, Nov 15, 2015, at 11:58 PM, Sergio Fernández wrote:
> Marko, the metrics approach has been discussed in the past, for instance
> http://markmail.org/message/ubx3utli3bnltv75 So far my feeling is that
> the ASF prefer to deliver of people to build an opinion of projects rather
> than based them on pure statistical metrics. But I'd be happy to see something
> like that.
Metrics can help people form opinions ("huh, there's been fewer than 5
emails per month on Project Y's dev list ... that sounds like we should
look more closely at that project") but "pure statistical metrics" are a
*horrible* way to decide whether a project is "healthy."
A project could have a very active set of mailing lists, lots of
commits, push out releases regularly - and still be unhealthy in any
number of ways. (e.g. - all of the work is coming from people paid by
one company, or that community is refusing to accept patches from anyone
employed by another company, or any number of other situations that
don't indicate a project that's "healthy" as we understand health.)
Conversely, a project may have minimal traffic, very few commits, and so
forth - but still be "healthy" because it's a mature project that needs
very little development to stay useful and relevant to its community.
Best,
jzb
--
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: Concerning Sentry: A disagreement over the Apache Way and graduation
Top-posting on purpose. This thread has veered from discussing specific concerns about Sentry to a discussion about the Maturity Model. It'd probably be good to fork the thread and continue the discussion separately in case other folks specifically interested in the discussion about Sentry are watching this thread. Best, jzb On Sun, Nov 15, 2015, at 01:56 PM, Pierre Smits wrote: > Justin, > > Why is it so that graduation can be vetoed? > > Best regards, > > Pierre Smits > > *OFBiz Extensions Marketplace* > http://oem.ofbizci.net/oci-2/ > > On Sun, Nov 15, 2015 at 4:13 PM, Justin Erenkrantz > <jus...@erenkrantz.com> > wrote: > > > On Saturday, November 14, 2015, Rich Bowen <rbo...@rcbowen.com> wrote: > > > > > No. I can use whatever criteria I like to justify my vote on a podlings > > > graduation, if it's in line with asf philosophy. This document is, and > > > accurately reflects the criteria I use when voting on a graduation. That > > > is, the document reflects me, not vice versa, as I said above. > > > > > > It's very akin to the docs that circulate around member election time. > > They > > > are useful guidelines but nobody is compelled to adhere to any particular > > > one of them. > > > > > > > The difference is that member elections are majority-based - graduation > > votes are essentially subject to veto. > > > > There's a huge difference there. If you are subjecting all of your votes > > to that checklist and will actively block podlings that do not meet your > > personal guidelines, you are making everyone else subject to it. -- justin > > Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
OFFLINE (mostly) 9 November - 14 November
Since the Sentry graduation discussion I started has been fairly active (though less so the last few days) I wanted to give the Incubator and Sentry folks a heads up of limited availability. I'm in Winnipeg today and tomorrow morning, then flying to Churchill for a photo tour on the tundra. (If anyone is itching for photos of polar bears, keep an eye on my blog...) I expect that my connectivity will be iffy while out on the tundra, and my interest in non-vacation related Internet activities to be very limited even when I do have a connection. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Concerning Sentry: A disagreement over the Apache Way and graduation
On 11/05/2015 01:34 AM, Joe Schaefer wrote: > Thanks Lenni. If Joe will permit me to put some words in his mouth, > he seems to be focused on how the project is solving coordination problems. > Coming to agreement on things like what to include in a release for > instance, which jiras get punted to which release schedules, etc, it's hard > to see > the rhyme or reason why these things are happening with the timing you are > using. Yes. This is accurate. > I'm perfectly personally satisfied with the manner in which tickets are > being resolved, > but am inclined to trust Joe's instincts that more prior discussion about > planning and > such should be taking place on-list. David has echoed these concerns as > well. Much appreciated. Thanks! Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Concerning Sentry: A disagreement over the Apache Way and graduation
On 11/05/2015 03:13 AM, Martijn Dashorst wrote: >> PMC membership has nothing to do with technical mastery of the codebase, >> which is why I cringe every time I see people talking about what "the bar" >> should be. It's about trust. If you trust someone to work the gears on a >> release, >> that has considerable impact on the well-being of a project, and personally >> meets my definition of "belongs on the PMC". > > We have a new PMC member who hasn't done much (if any) work on the actual > code base of Wicket, but runs an awesome twitter account [1] posting > new projects > and applications using our framework, posting job listings etc. We wanted him > to > continue to do so and acknowledged that he found sites and jobs we were not > doing, so it was only logical to ask him to become a PMC member and our true > social manager! > > We *trust* him to do good with the twitter account and wanted to give him the > official seal of trust by inviting him to the PMC. If and when he finds time > to > contribute in other ways, we will be welcoming. You have no idea how glad I am to hear that this sort of thing is happening. Having a deep technical understanding of the code base should *not* be a blocker for people to be recognized for their contributions to projects. ASF projects need help in a lot of ways besides code - glad you've found someone who is lending a hand there. (I checked out the twitter feed, they really are doing a great job.) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Private PPMC discussions and archives (was Re: Concerning Sentry: A disagreement over the Apache Way and graduation)
On 11/04/2015 03:55 PM, Sravya Tirukkovalur wrote: > One question on discussing candidature of a person for PPMC on private: > I know that private is only for PPMC, but I believe the new elected PPMC > can always get the digest for older messages (or not?). If that is the case > wouldn't it defeat the purpose of having these discussions on private? New PPMC/PMC members *can* access private list archives where their candidacy is discussed, absolutely. And yes, this means that when they're added to the PPMC (or PMC, or as an ASF Member) they can see where they've been discussed 'privately.' So, when discussing this sort of thing, assume that eventually the person you're discussing will be able to see it. If the purpose were simply to do this out of sight of the prospective PPMC member, then it would defeat the purpose. However, AIUI, it serves a few additional purposes: - It doesn't have an immediate impact on the project or person. Someone who is contributing well but not quite ready for PPMC duties, for example, may get immediately discouraged if they're discussed publicly and found wanting. - You don't wind up with a publicly searchable discussion of someone's suitability (or lack thereof) that might turn up when someone google's a person's name. So - it might hurt my feelings eventually to learn that someone -1'ed me for some reason, but it shouldn't impact my job prospects, etc. But I recommend assuming that when you discuss anyone for PPMC (etc) on a private list that the odds are they will eventually see it. I'm not a fan of this, because I suspect it inhibits fully candid discussion. On the flip side, I don't think PPMC folks should shy away from objectively discussing folks and being willing to say "this person may be a great PPMC member someday, but I don't think they are ready today. Here's where I feel they need to improve." One hopes that our PPMC, PMC, etc. folks can handle objective (if retroactive) feedback, and be happy that they've since addressed concerns. But if a person goes on a personal rant against someone who is later added to the PPMC, then... they can probably expect to be dropped from the new PPMC person's holiday card list. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Concerning Sentry: A disagreement over the Apache Way and graduation
On Wed, Nov 4, 2015, at 08:43 PM, John D. Ament wrote: > I don't think that's the question on the table. Typically, podlings make > committers == PPMC members. The reasoning being that the only thing a > PPMC member can do is vote on adding new members. Other votes are all > non-binding (unless you're an IPMC member). It also helps promote the > synergy needed to become a TLP, forming a strong PMC. I don't suppose we have stats on that, do we? My first project was CloudStack, and I was surprised to find other podlings *didn't* distinguish between committer and PPMC. While PPMC votes on members, being a committer does give privileges beyond just being an occasional contributor, so some folks may find it a useful step between "we have to review all of your patches" and "you're helping with governance/growth of the project." Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Concerning Sentry: A disagreement over the Apache Way and graduation
On Wed, Nov 4, 2015, at 08:26 PM, Lenni Kuff wrote: > I think there is some confusion here. The Sentry project has never > considered Committer == PMC. The recent website change was only to help > clarify the roles of each of the members of the project, it was not the > result of any decision being made. So... the discussion that prompted this was in March 2014, but the fix didn't make it to the site until August 2015. https://issues.apache.org/jira/browse/SENTRY-128 See also (for those with access: http://s.apache.org/chc) I remembered the exchange about this, but wasn't aware that it'd taken so long to fix. When it came up (and in this Jira) it's said "we say that all committers are PPMC members this is not as planned. Committers should be considered separate from PMC members." The incubation status page likewise does not distinguish PPMC. (Compare to CloudStack, which did: http://incubator.apache.org/projects/cloudstack.html) Where was it "planned"? I don't see any indicator in the Sentry proposal that there was a distinction - where was it documented? If it wasn't written down somewhere, how would anybody know it was "planned" that way? The most public reference would indicate to contributors that contributors == PPMC. If it was "wrong" I can't find the source to indicate that the podling felt differently. Mea culpa for not looking at this more carefully at the time, but the podling probably should have paused and had a public conversation about this when it was first caught. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Concerning Sentry: A disagreement over the Apache Way and graduation
On Wed, Nov 4, 2015, at 09:02 PM, Patrick Hunt wrote: > My experience on other projects is the same as Joe. afaik it's up to the > podling, and most I've been involved with decided to go with committer != > ppmc. Honestly I thought that was the default. And here I think I have to agree that it this kind of variance makes it difficult for podlings to really know what's what. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Concerning Sentry: A disagreement over the Apache Way and graduation
On Wed, Nov 4, 2015, at 11:26 AM, Patrick Hunt wrote: > So you are -1 then. That's fine. But it gets back to my original concern. > It's artificial. I can go back to the Sentry community and say "hey, you > need some PPMC members, vote some in" and they might do it. It was > already > mentioned earlier in this thread that one of the mentors feels that a > couple of committers are ready. If they come back in a week and say "hey, > we just voted in 3 new ppmc members, now we're ready right?" you'll be > fine > with that? This is why I highlighted it as artificial. FWIW I agree with you that it's "artificial" and for a podling that's motivated to graduate (which Sentry appears to be) it's not hard to paper that over and just say "OK, if we want to graduate, let's tick this checkbox." Not having new PPMC folks is a symptom of what concerns me about Sentry. I didn't see a focus on adding committers until prodded. I don't see a focus on growing committers to become PMC members minus mentor prodding. If a project cares about sustainability and growth, shouldn't it be having these discussions? Their absence concerns me greatly. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Concerning Sentry: A disagreement over the Apache Way and graduation
On Wed, Nov 4, 2015, at 10:27 AM, Joe Schaefer wrote: > Joe, has any of this conversation put your mind at ease about the > podling? I'm less concerned than I was, yes. I'm still not in +1 territory. I'm not entirely sure I'm out of -1 territory. Sentry has made progress in its time in the incubator, but I feel it's required a lot of prodding at each step of the way - to reporting on time, adding contributors*, making sure its incubation status page is filled out, etc. It's also had some problems with release process, but I don't hold that against any podling because our release process can be hard to get right. But I view the podling as one that's concerned with releasing software, not growing community. I keep seeing references to "actively preventing" contributions - but I don't think that's a very high bar to clear. I want to see a podling actively working to make it possible to join and contribute. I'll note that I may see Sentry differently because I am a non-developer. The Jira-focused process may be adequate for folks who are primarily only focused on the release of software. It is not a particularly inviting or transparent process to anybody who might like to participate in Sentry in non-development roles. And I hope we care about contributors who will add value to Apache projects in non-development roles (documentation, marketing, translation, etc.). At any rate - I've said my piece, and I'll just reiterate that I don't think additional time is the answer. The signal I get from Sentry is that the podling feels it's ready to graduate, and they've indicated that they don't feel my suggestions are a "valid ask" - so I don't see much value in holding back a DISCUSSION and VOTE. Note, as I understand it the board "is unlikely" to approve a podling where a mentor is voting -1. While I have concerns, I also don't want to filibuster the process and just keep Sentry in Limbo. I'd appreciate input from other IPMC folks on best decorum (e.g. abstaining from the vote, stepping down as mentor) in this situation. If other folks share my concerns, the vote wouldn't pass. If I'm wrong, I don't feel I should hold it up single-handedly. * I would invite folks with access to go to Sentry's private list and look over discussions about adding new contributors, and discussions about the project in general. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Concerning Sentry: A disagreement over the Apache Way and graduation
On Mon, Nov 2, 2015, at 06:04 PM, Arvind Prabhakar wrote: > On Mon, Nov 2, 2015 at 12:28 PM, Joe Brockmeier <j...@zonker.net> wrote: > > > > > ... the reply from > > Arvind which basically says he doesn't consider it an issue if the > > project is "following a roadmap the community does not have control > > over... that too is not an issue in my opinion at all." [2] > > > > > > Joe - I trust and respect you enough to feel that this is unintentional, > but I am being taken out of context. In this and previous emails you have > suggested that I admit and approve of an external entity controlling > Sentry. This is a gross misrepresentation. Please stop implying that for > your future responses as it was not what I said or meant. I don't think that's *quite* what I suggested, but per Upayavira's note that followed yours, I see I may have misread your message. Upayavira's reading suggests you meant "not an issue" to mean "this is not happening" rather than "I don't consider this a problem." That significantly changes the tone of the response as I understood it. If that was your meaning, I do apologize for misinterpreting what you said. I do appreciate you understanding that my response was based on an honest interpretation of what you wrote. Just to be clear - you're vouching that all of Sentry's development is happening in the open, and Sentry development decisions are not being taken offlist? Thanks much for clarifying! Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Concerning Sentry: A disagreement over the Apache Way and graduation
On Tue, Nov 3, 2015, at 04:42 PM, Patrick Hunt wrote: > On Tue, Nov 3, 2015 at 12:48 AM, Bertrand Delacretaz > <bdelacre...@apache.org > > wrote: > > > On Mon, Nov 2, 2015 at 11:11 PM, Joe Brockmeier <j...@zonker.net> wrote: > > > ...Sentry started with 24 committers/PPMC. It hasn't added any PPMC > > members > > > since its inception... > > > > If that's correct I'm -1 on graduating Sentry. > > > > and earlier he wrote: > > > ..The model that Sentry is pursing may work very well *for the existing > > > members of the podling.* In my opinion, its process is entirely too > > > opaque to allow for interested parties outside of the existing podling > > > and companies interested in Sentry development to become involved... > > > > Not having added any PPMC members seems to confirm that. > > > > > Bertrand, imo this is a reasonable concern. I remember some discussion a > while back on the sentry lists about it. Note that the community has > highlighted it in their status reports, so it should be nothing > new/surprising. iirc (and I'm summarizing here, please correct me if I > get it wrong) the new committers have had varying levels of activity. Some > more active than others, but none that had reached ppmc status. Perhaps the > team should be more aggressive promoting folks, but I don't believe it's out > of exclusion or lack of understanding the Apache way. We generally shy away from discussing individuals on open lists w/r/t "this person should/shouldn't be a PPMC member" type things, so I'm not sure it'd be right to specifically point to any Sentry contributors as an example. I will say I can think of at least two Sentry contributors added since Sentry entered incubation who seem just as active as other folks who came in with the podling. When you say "reached PPMC status" I'm not sure there's a clear signal to me that they're less worthy than the folks ushered in with the podling. You said it "sounds like" making more folks PPMC members is "in the pipeline" - do you mean if Sentry graduates, or is there some other discussion I've missed where that's being pondered? Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Concerning Sentry: A disagreement over the Apache Way and graduation
On Mon, Nov 2, 2015, at 06:15 PM, Upayavira wrote: > On Mon, Nov 2, 2015, at 08:28 PM, Joe Brockmeier wrote: > > On 11/02/2015 01:09 PM, Joe Schaefer wrote: > > > Joe, can we see some jira tickets that you find questionable? Hard to > > > tell > > > what the problem is just by scanning the email traffic. > > > > I'll (again) point to the previous conversation that came out of David's > > discussion with Sentry folks at ApacheCon [1] and then the reply from > > Arvind which basically says he doesn't consider it an issue if the > > project is "following a roadmap the community does not have control > > over... that too is not an issue in my opinion at all." [2] > > Joe, I'd encourage you to re-read what he says there under [2]. When he > says "following a roadmap the community doesn't control over" he seems > to be paraphrasing what has previously been stated, and when he says > "this is not an issue" it seems to me he is saying "this is not > happening" rather than "this doesn't bother me". It seems to me you are > misrepresenting him based upon this one email. Thanks much for pointing this out. I honestly took it to mean "this doesn't bother me," but I can see how it could have been "this is not happening," which is - you know - a lot less alarming. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Concerning Sentry: A disagreement over the Apache Way and graduation
On 11/02/2015 12:27 PM, Vinod Vavilapalli wrote: > Many of the active TLPs do tend to center all project discussions on JIRA as > opposed to mailing lists. OTOH, non-code discussions are usually best served > on mailing lists. > > Instead of making it a JIRA vs mailing list discussion, how about the podling > be advised about putting a cool-off period for JIRA resolutions - 24-36hrs > before they get closed. Again, this is something a bunch of active TLPs > practice in the interest of leaving enough time windows for everyone (many > times around the world in different time-zones) to pitch in. It's not merely a Jira vs. mailing list discussion - please re-read the original message. Discussions are happening out of sight, and - in Arvind's own words - "as if following a roadmap the community does not have control over... that too is not an issue in my opinion at all." (Note Arvind is also a mentor for the project.) This is not just "Jira vs. Mailing list" this is "where are discussions happening, and can the community outside the existing group effectively participate?" The answer is clearly *no*. It boggles my mind that anyone would argue for this as an Apache project, especially a mentor. But that's why I brought this to the Incubator list - as a sanity check.* As best I can tell, Sentry development is largely guided outside Apache infrastructure and that's not acceptable - at least as I understand what we are trying to achieve. * A sanity check on this specific issue. I'm not inviting the Incubator to comment on my sanity in general, I can guess the answer already. ;-) -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Concerning Sentry: A disagreement over the Apache Way and graduation
On 11/02/2015 01:09 PM, Joe Schaefer wrote: > Joe, can we see some jira tickets that you find questionable? Hard to tell > what the problem is just by scanning the email traffic. I'll (again) point to the previous conversation that came out of David's discussion with Sentry folks at ApacheCon [1] and then the reply from Arvind which basically says he doesn't consider it an issue if the project is "following a roadmap the community does not have control over... that too is not an issue in my opinion at all." [2] It's not specific tickets - it's (again) that there appears to be a lot of discussion and planning taking place off-list, out of sight. Take the 1.6.0 release discussion - no roadmap discussed for 1.6.0 at all, it just appeared [3] and then within 15 minutes there's an "I agree, and I'll be release manager!" [4] message and then several +1 / "I agree" messages, and then .. done. This looks a lot to me like planning and decisions happening off-list and then a cursory "discussion" for appearance's sake. How is a person who's not tapped into the Sentry development process already supposed to get involved? How is this building community? I see the Sentry podling creating code... just not much evidence of a community outside what Sentry came in with. [1] http://s.apache.org/611 [2] http://s.apache.org/bhQ [3] http://s.apache.org/ZRV [4] http://s.apache.org/g9v -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Concerning Sentry: A disagreement over the Apache Way and graduation
On 11/02/2015 03:57 PM, Patrick Hunt wrote: > I see this (the release discussion threads you linked) as a semi-mature > community that's well aligned. A number of folks responded to the request > for discussion and said they were in favor. It was done on the ML in the > open. What more do we want? I don't see anyone excluded and I'm sure if > there was a new person looking to get involved they would have been > welcomed into the discussion, no one is being turned away from what I can > see. No one is being turned away, that I've noticed, but I really don't see how anyone is supposed to follow along if they're not part of the team already. I will say that the only Jira I've seen from outside recently didn't exactly get a warm reception. [1] Not rejected, just radio silence. I'm also sad to see that being held up as a standard by other mentors. My understanding is that projects should be attempting to create a community that is open, and trying to self-perpetuate. Sure, you can't do that if you turn people away actively - but you also can't do that by having conversations offlist and having an opaque process that newcomers can't follow along with. I'll say again - maybe my standards are improperly calibrated. If so, and "not actively turning people away" is the standard we're going for... that's disappointing as all heck. [1] https://issues.apache.org/jira/browse/SENTRY-934 -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Concerning Sentry: A disagreement over the Apache Way and graduation
On 11/02/2015 04:41 PM, Sravya Tirukkovalur wrote: > I think it is a good sign that community is volunteering to do the release > work. I think the point I'm making is largely being ignored. I'm not seeing much room for volunteers, and a lot of indication that conversations/decisions are happening off list and being carried back rather than being done entirely openly. > Here is the formal release work starting email[1] and discussing details on > when to branch and when to release giving sufficient time for everyone who > want to get their favorite jiras in. Dapeng (RM for 1.6.0) also started a > jira[2] to track the release work in detail: We might disagree on what constitutes "sufficient time" here - it looks like one week notice for the 1.6.0 branch, and then one week (planned) to release from there. > ". I will say that the only Jira I've seen from outside recently > didn't exactly get a warm reception. [1] Not rejected, just radio silence." > > That is not true, this is just one off instance. It has only been a week > since that jira has been created and I am sure one of us will review it > soon . But there are numerous instances where community was very welcoming > for new contributors and users[3][4][5]. In fact I feel proud to say that > community enabled many folks who filed bugs to also contribute bug fix > patches. OK, fair. I'll assume that's a one-off then, and apologize for missing the other examples. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Concerning Sentry: A disagreement over the Apache Way and graduation
Hi all, I'm one of the mentors of Sentry, which has been in incubation for some time. The project has progressed in a number of ways, but my largest concern is that the podling is doing [in my opinion] too much development and discussion out-of-sight. I've raised issues about this, as has David Nalley. David had a conversation with members of Sentry at ApacheCon Big Data in September, and that discussion was brought back to the list. [1] Jiras are being filed, and swiftly acted on, in a way that strongly suggests that a lot of discussion and direction of the project are happening off-list and out-of-sight to the average participant. David and myself have suggested ways that the community can remedy this, but the most recent mail from Arvind indicates that he (and others in the podling) don't feel it is a "valid ask." At this point, I'm raising this to general@ because I'd like second (and third, etc.) opinions. Perhaps I'm deeply wrong, and others here feel Sentry is ready to graduate. My feeling is that the podling is not operating in "the Apache Way" and doesn't show a great deal of interest in doing so. [2] To quote Arvind: "I feel another issue being pointed out or which has been eluded to in the past is - who decides which Jiras should be fixed, what features to create etc, specially when they show up as Jira issues directly with patches that follow soon. It seems that in some ways the lack of using mailing lists directly for discussion is linked to this behavior of filing issues and fixing them rapidly, as if following a roadmap that the community does not have control over. Please pardon me if my interpretation/understanding of the issue is not right. But if it is right, then I do want to say that - that too is not an issue in my opinion at all. And here is why: When someone files a Jira, they are inviting the entire community to comment on it and provide feedback. If it is not in the interest of the project, I do believe that responsible members of the community will be quick to bring that out for discussion and even Veto it if necessary. If that is not happening, it is not an issue with lack of community participation, but rather it is an indicator of a project team that knows where the gaps are and understands how to go about filling them intuitively." The model that Sentry is pursing may work very well *for the existing members of the podling.* In my opinion, its process is entirely too opaque to allow for interested parties outside of the existing podling and companies interested in Sentry development to become involved. The podling is pressing to move to graduation, and I cannot in good conscience vote +1 or even +0 at this point. I'm strongly -1 as a mentor and don't feel the podling has any interest in working in "the Apache Way" as commonly understood. [3] However, I feel we've reached an impasse and there's little value in continuing to debate amongst the mentors / podling. They've stated their position(s) and I've stated mine. (I *think* David Nalley is in agreement with me, but I don't wish to speak for him.) I'm bringing this to the IPMC fully understanding that I might be totally wrong - maybe I'm holding to a too strict or outdated idea of how projects should operate. I'm happy to be told so if that's the case so I can improve as a mentor or decide to bow out from mentoring in the future, if it's the case that my idea of a project is out-of-line with the majority here. [1] http://s.apache.org/611 [2] http://s.apache.org/bhQ [3] http://theapacheway.com/ Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Brooklyn from incubator
On Tue, Sep 29, 2015, at 08:32 AM, Hadrian Zbarcea wrote: > In hindsight, the cc: to dev@brooklyn created more confusion. This is > the incubator vote. I think we should drop the cc: to dev@ (kept it for > this email, to make sure Joe sees it). D'oh. Thanks! > On 09/29/2015 07:49 AM, Joe Brockmeier wrote: > > On Mon, Sep 28, 2015, at 10:06 AM, Hadrian Zbarcea wrote: > >> This is the Incubator vote to decide if Apache Brooklyn should graduate > >> from the Incubator. Please see the proposed resolution below. > >> > >> See also discuss thread [1]. Mentors were invited to join the future TLP > >> PMC on request. Invitation is open until this vote is closed. > >> > >> This vote is open for at least 72 hours. > >> > >> [ ] +1 Graduate Apache Brooklyn from the Incubator. > >> [ ] +0 Don't care. > >> [ ] -1 Don't graduate Apache Brooklyn from the Incubator because ... > > > > +1 (binding) > > > > Best, > > > > jzb > > Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Evaluation the interest of EasyMock at Apache
On Wed, Sep 23, 2015, at 05:02 AM, Emmanuel Lécharny wrote: > Le 23/09/15 08:45, Bertrand Delacretaz a écrit : > > Hi, > > > > On Wed, Sep 23, 2015 at 1:18 AM, Henry Saputra <henry.sapu...@gmail.com> > > wrote: > >> ...you should not worry too much about having the project to be in > >> incubator forever... > > That's assuming the community grows. > > > > https://github.com/easymock/easymock/graphs/contributors shows a huge > > majority of commits by Henri with just a few "drive-by" contributions > > here and there. > > > > Turning that into a more diverse Apache-style community would be > > great, but for that you need people to show up and get involved. From > > this angle I think it makes absolute sense for Henri to gauge interest > > here first. > > That is one big problem for established code bases that aren't moving > too much, but are heavily used by many, many developpers. > > Not all the projects deserve to go through incubation, and not all the > projects (especially small ones) deserve to be TLP. > > We had some discussion lately about moving such projects to a place at > The ASF where they could gather more then 1 or 2 PMC member to vote a > new release, but still be visible. Apache commons could be such a place, > but it's really a group of java libraries. We might need a new TLP for > tools, whatever the languages they are written in (Java, C, Python, etc). > > But this might not be the best place to discuss that, maybe we can have > a get together meeting in Budapest Aren't the mailing lists the ideal place(s) to discuss this, not in-person meetings? Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Reform of Incubator {was; [DISCUSSION] Graduate Ignite from the Apache Incubator)
On Mon, Aug 3, 2015, at 07:06 PM, Arvind Prabhakar wrote: That said, I have personally been in positions where I have seen IPMC members ask - and even demand things at times - that I feel are unreasonable requests for the podling. The reason I do not challenge those is because I feel that their asks are rooted in good intentions, and that the IPMC in its current form encourages such involvement and authority. At the same time I also worry about the state of the podling and what this does to their way of thinking about Apache and the Incubator. Can you give an example (possibly abstracted to protect the guilty)? I'm very aware that I don't have as much experience as other folks mentoring, and would be grateful if podlings (politely) pushed back if I am in fact asking for / demanding anything that is not reasonable. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Reform of Incubator {was; [DISCUSSION] Graduate Ignite from the Apache Incubator)
On Mon, Aug 3, 2015, at 03:13 PM, Roman Shaposhnik wrote: On Mon, Aug 3, 2015 at 3:44 AM, Joe Brockmeier j...@zonker.net wrote: On Sun, Aug 2, 2015, at 10:05 PM, Roman Shaposhnik wrote: I've been waiting for a bout a week for other to chime in, but it seems that nobody has so I'll repeat my question as of a week ago: what would be the effective way to change the status quo around IPMC an make it more board like? Perhaps we can start from making the release policy actually make sense along the lines that Ross has outlined. I guess I can propose a change to the current policies (or to Ross' point just get it back from the wayback machine :-)). But seriously, who else thinks the movement towards empowering PPMCs and making IPMC very much like the board makes sense? I think the thread fizzled because there's not a lot of support for the idea. At least, on my end, I'm not in favor. Yup. I believe this to be an unfortunate (at least from my standpoint) but and extremely fair observation. As far as I'm concerned the issue of RRs of IPMC is in a state of a stalemate right now. We clearly have a everything's fine lets just add more policy constituency vs. IPMC should be small and more board like crowd. If I had to identify one problem that the IPMC/Incubator suffers from at the moment it would not be a need for a small and more board like structure. The biggest problem (and perhaps I view it this way because I'm suffering from it / am part of the problem) is a lack of time / attention from mentors. I'm really not sure that the proposal here solves that in any meaningful way. The good news is that we're all united on making sure that the foundation is growing by podlings making progress and graduating to TLPs. The bad news is that because of the current mentality I don't see the types of unfortunate threads that Ignite just went through going away anytime soon. What about the Ignite thread was unfortunate? That it was a bit heated at times, or just the fact that there was disagreement? I fear that there's too much bias towards +1'ing things even when folks have legitimate concerns. This is that proverbial political overhead that a lot of folks are accusing ASF of and cite as a reason of not going into the foundation. Which is grossly unfair at the board level, but unfortunately seems to be very true at IPMC level today. A lot of companies seem to view any friction (e.g. actually complying with policies that put community over code) as political overhead that makes joining the foundation undesirable. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Reform of Incubator {was; [DISCUSSION] Graduate Ignite from the Apache Incubator)
On Tue, Aug 4, 2015, at 12:23 PM, Ross Gardler wrote: It's hard to get the balance right between appropriate oversight and unwanted meddling. No argument there. I'm unconvinced that a restructuring of the IPMC/PPMC/Mentorship structure as it is today will solve that, though it might push it around a little. I do think negotiating/communicating with mentors is a skill that helps folks deal with building community and running a project - which is often new to folks coming to the Incubator. So if there's unwanted meddling I hope that folks are able to push back a little bit and resolve that without having to throw out (a potentially) reasonable structure just to get around it. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Reform of Incubator
On 08/04/2015 02:45 PM, Konstantin Boudnik wrote: Sorry if it rubs the wrong way. However, we just have seen through the Ignite discussion (most recent one) the examples where personal expectations were represented as graduation requirements. It is perhaps in good faith - I am not questioning the intention. I am saying that when requirements are unclear, people interpret them based on their own understanding of unwritten Apache ethos. As Brane called it earlier - confusing opinions and policies. You see where I am going with this, right? Perhaps I'm unclear on the proposal - but how would that be mitigated by this proposal? I understand that it might expose podlings to less of this when directed towards the full IPMC for graduation, but how would it prevent this if a mentor confuses personal expectations for graduation requirements? Isn't that still a potential issue? I may misunderstand or have lost track of how that's handled in all the discussion. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Reform of Incubator {was; [DISCUSSION] Graduate Ignite from the Apache Incubator)
On Sun, Aug 2, 2015, at 10:05 PM, Roman Shaposhnik wrote: I've been waiting for a bout a week for other to chime in, but it seems that nobody has so I'll repeat my question as of a week ago: what would be the effective way to change the status quo around IPMC an make it more board like? Perhaps we can start from making the release policy actually make sense along the lines that Ross has outlined. I guess I can propose a change to the current policies (or to Ross' point just get it back from the wayback machine :-)). But seriously, who else thinks the movement towards empowering PPMCs and making IPMC very much like the board makes sense? I think the thread fizzled because there's not a lot of support for the idea. At least, on my end, I'm not in favor. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Thu, Jul 23, 2015, at 03:19 AM, Branko Čibej wrote: Personally I'm not too happy with how this community tracks issues, but hey, if it works for them, why fix it? It'll be a fine day when the IPMC starts telling podlings how their development workflow should look like. Does works for them translate into people not currently in the community can follow how the existing community tracks issues, so they can contribute and become part of the community? If so, then maybe it's OK. If it's not transparent to folks not currently part of that community, it's hard to see how the community will sustain itself with new members as other folks inevitably move on to other projects. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Mysos into the Apache Incubator
It's ... rather presumptive to have gotten a Twitter account that includes apache given that the project hasn't been accepted into the incubator yet. On Sat, May 30, 2015, at 04:05 PM, P. Taylor Goetz wrote: It looks like the project already has a Twitter account and a logo [1]. One thing to keep in mind is how difficult it can be to re-brand something after a brand has been established. IMHO, it would be best to figure out a viable name as early as possible to avoid having to re-brand later in order to graduate. Based on this and other threads, it seems entirely possible that the board may not accept Mysos as a TLP name. -Taylor [1] https://twitter.com/apachemysos On May 30, 2015, at 11:21 AM, Chris Aniszczyk caniszc...@gmail.com wrote: Personally, I would let the project decide how to move forward with the name than a bunch of us who aren't trademark lawyers. If it was something obvious, than that would make sense, but I briefly consulted our legal team internally and the name was cleared for usage since there are no marks registered and there was no likelihood of confusion. On Sat, May 30, 2015 at 7:45 AM, Joe Brockmeier j...@zonker.net wrote: On Fri, May 29, 2015, at 12:00 PM, Jake Farrell wrote: Bringing back comments from a separate thread on board@ Sorry to see your vote of a -1 on the proposal due to the name. This was raised during the discussion phase and as stated in the discussion we are not against a name change, but saw it as something that was not a blocker to entering incubation. We did an initial name search on our own and there are no collisions on Mysos externally and we have two Mesos PMC members on the project that did not see any problems with the name, Dave and Vinod are both on the Mesos PMC. A note has been sent to the Mesos PMC private@ list regarding the Mysos proposal and the project name and asked that comments be brought back to here. I agree with Bertrand - might as well change the name *now* rather than dealing with it at a later date. AIUI, Mysos is a combination of MySQL and Mesos -- which also could mean potential TM headaches for the podling. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Cheers, Chris Aniszczyk http://aniszczyk.org +1 512 961 6719 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Mysos into the Apache Incubator
On Fri, May 29, 2015, at 12:00 PM, Jake Farrell wrote: Bringing back comments from a separate thread on board@ Sorry to see your vote of a -1 on the proposal due to the name. This was raised during the discussion phase and as stated in the discussion we are not against a name change, but saw it as something that was not a blocker to entering incubation. We did an initial name search on our own and there are no collisions on Mysos externally and we have two Mesos PMC members on the project that did not see any problems with the name, Dave and Vinod are both on the Mesos PMC. A note has been sent to the Mesos PMC private@ list regarding the Mysos proposal and the project name and asked that comments be brought back to here. I agree with Bertrand - might as well change the name *now* rather than dealing with it at a later date. AIUI, Mysos is a combination of MySQL and Mesos -- which also could mean potential TM headaches for the podling. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Blog policy for poddlings
On Thu, May 28, 2015, at 09:43 PM, Dave Lester wrote: My understanding is that only TLPs can publish to blogs.a.o. I guess that depends on whether you mean the top-level Apache blog there or starting a new blog. CloudStack started its blog on blogs.apache.org while we were a podling with (IIRC) Sally's blessing. Example here: https://blogs.apache.org/cloudstack/tags/4.0.1-incubating Whether that was aggregated/carried on the main site, I don't recall. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Do we need @ASFIncubator ?
On Tue, Mar 24, 2015, at 03:53 AM, Romain Manni-Bucau wrote: +1 to keep @TheASF, will avoid noise or misunderstanding when a project is graduated + for general announcements it is more consistent. CC'ing press@ If I am not mistaken, we don't promote incubator releases, etc. from @TheASF as they are not yet TLPs. (Just as we do not issue press releases for them or do official press / marketing services for podlings until they graduate.) So - @ASFIncubator may be a good way to promote those projects until they're official. (Though I note we did tweet about Groovy entering/being proposed to the Incubator here: https://twitter.com/TheASF/status/575747253190725632) Romain Manni-Bucau @rmannibucau https://twitter.com/rmannibucau | Blog http://rmannibucau.wordpress.com | Github https://github.com/rmannibucau | LinkedIn https://www.linkedin.com/in/rmannibucau | Tomitriber http://www.tomitribe.com 2015-03-24 8:51 GMT+01:00 Bertrand Delacretaz bdelacre...@apache.org: On Mon, Mar 23, 2015 at 10:05 PM, Roman Shaposhnik r...@apache.org wrote: ...should we leverage @TheASF for the incubator-level announcements or should we establish our own handle?... I would prefer using @TheASF and keeping Sally in the loop so the can keep the overview on those announcements. But if people want to create and maintain a specific handle, I'm not opposed. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Do we need @ASFIncubator ?
Just my 2 cents - asfincubator is preferable to apacheincubator in 1) clarity (apache alone is less clear) and 2) shorter, and saving characters on twitter is important. On Tue, Mar 24, 2015, at 10:47 AM, Ted Dunning wrote: Roman is the former vp. And I set up ASF Incubator yesterday and will set up ApacheIncubator today. Then we can hash out which we want to use and how. Sent from my iPhone On Mar 24, 2015, at 5:51, Shane Curcuru a...@shanecurcuru.org wrote: Roman, as VP, do you want to start setting this up? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Lens into the Apache Incubator (earlier called Grill)
On Mon, Oct 6, 2014, at 06:51 AM, Sharad Agarwal wrote: [ ] +1 accept Lens in the Incubator +1 (binding) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Committer Voting and Vetos
On Thu, Sep 25, 2014, at 10:59 PM, Alex Harui wrote: In a past discussion about by-laws, some folks were adamant that voting for new committer and PMC members be consensus votes so a single person can block the adding of a candidate. Do any projects use some form of majority voting for new committers? What are the reasons for allowing vetoes? Yes, some projects have lazy majority/no veto for committer votes. CouchDB for example: http://couchdb.apache.org/bylaws.html Some reasons I'd give in favor of the veto model: * Consensus on decisions around new committers/PMC members is pretty important. A majority vote that overrides concerns of one or more PMC members rather than working through those concerns may not be good for the community. * You can usually re-visit a discussion to vote on a new committer or PMC member, but once they're voted on it's more difficult to undo it. If the no voter(s) are saying not yet convinced, giving some additional time to work that out may be better for the community than forcing it and later regretting it. Reason *not* to have a veto: * It could be abused, or simply cause harm to a community because one or more PMC members are too conservative about adding new committers. Contributors lose interest and the community stagnates. [Other folks probably have different reasons they'd give in favor of or against vetoes, many of whom have been around much longer than I -- so I hope others will chime in as well.] Generally, I lean towards having a veto. If one member has a real concern, I'd prefer to see it worked through and achieve consensus rather than overriding someone. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Sentry incubating version 1.4.0 (rc0)
On 08/11/2014 01:48 PM, Tuong Tr. wrote: Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) * verified SHA/MD5 sums * verified signature * verified DISCLAIMER, LICENSE, NOTICE * ran tests, RAT check good +1 binding Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANNOUNCE] Jan Iversen joins the IPMC
On 08/15/2014 06:47 AM, jan i wrote: Hmmm, I presented myself on members a little while ago, so I will safe you having to read that again. Note that general@ is a public list with a number of folks who are not Apache Members, so it might be a repeat for some people on general@ but certainly not all. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
August 2014 Incubator Report Timeline
http://wiki.apache.org/incubator/August2014 Wed August 06 -- Podling reports due by end of day Sun August 10 -- Shepherd reviews due by end of day Sun August 10 -- Summary due by end of day Tue August 12 -- Mentor signoff due by end of day Wed August 13 -- Report submitted to Board Wed August 20 -- Board meeting Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANNOUNCE] Konstantin Boudnik joins the IPMC
On Sat, Jul 12, 2014, at 01:11 AM, Roman Shaposhnik wrote: Hi! The Apache Incubator PMC has VOTEd to add Konstantin Boudnik AKA Cos to our ranks. Welcome, Cos! Great to have you on board! Welcome, Konstantin! Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Draft Report July 2014 - please review
Hi Roman, On Tue, Jul 8, 2014, at 11:56 PM, Roman Shaposhnik wrote: The rest looks good to me. I'll do one final pass tomorrow before submitting to the board! I went ahead and made the changes on the wiki. Let me know if you need anything else or if anyone has spotted any other omissions/errors. Thanks! Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Draft Report July 2014 - please review
On Wed, Jul 9, 2014, at 10:23 AM, Robert Metzger wrote: Hi, it seems that Flink does not have a Shepherd assigned. It is also missing a review by them. But it looks like half of the projects are missing shepherd/mentor notes. Specifically, we're missing shepard/mentor notes from: Aurora Flink Kalumet MetaModel NPanday (also no signed-off-by) Optiq (also no signed-off-by) Parquet Ripple Samza Slider UserGrid VXQuery Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Draft Report July 2014 - please review
are currently being processed. Signed-off-by: [ ](brooklyn) Matt Hogstrom [ ](brooklyn) Alex Karasulu [ ](brooklyn) David Nalley [ ](brooklyn) Marcel Offermans [ ](brooklyn) Jean-Baptiste Onofré [ ](brooklyn) Olivier Lamy [X](brooklyn) Chip Childers [ ](brooklyn) Andrei Savu [ ](brooklyn) Joe Brockmeier [ ](brooklyn) Jim Jagielski Shepherd/Mentor notes: (cc) As the report notes, Brooklyn is slowly (but surely) converting over to the ASF infrastructure and processes. They are making good progress at this time. DataFu DataFu provides a collection of Hadoop MapReduce jobs and functions in higher level languages based on it to perform data analysis. It provides functions for common statistics tasks (e.g. quantiles, sampling), PageRank, stream sessionization, and set and bag operations. DataFu also provides Hadoop jobs for incremental data processing in MapReduce. DataFu has been incubating since 2014-01-05. Three most important issues to address in the move towards graduation: 1. Building an ASF-based community. 2. Release. 3. Decide on the future home of the project. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? Will Vaughan gave a talk on DataFu at ApacheCon in April, and Casey Stella gave a talk on Pig and DataFu at the Hadoop Summit in June. How has the project developed since the last report? Lots of JIRAs on bug fixes and new features, especially in April and May. Work slowed significantly in June, which probably means it's time for a release to mark our progress thus far. Date of last release: None. Six month of incubation. When were the last committers or PMC members elected? 2014-02-22 Signed-off-by: [ ](datafu) Ashutosh Chauhan [X](datafu) Roman Shaposhnik [ ](datafu) Ted Dunning Shepherd/Mentor notes: (jmclean) : Mentor active, no obvious issues. DeviceMap Apache DeviceMap is a data repository containing device information, images and other relevant information for all sorts of mobile devices, e.g. smartphones and tablets. While the focus is initially on that data, APIs will also be created to use and manage it. DeviceMap has been incubating since 2012-01-03. The report was not delivered on time from the project itself, as a mentor I (bdelacretaz) have sent the following challenges to the project's dev list to try and get the current somewhat active PPMC members to take over: 1. Challenge #1: provide regular reports 2. Challenge #2: make a release 3. Challenge #3: form a PMC with 4-5 members to graduate Those should really not be challenges but at this point that felt like an appropriate way of indicating the importance of those actions. There's already promising responses, we'll see if those translate into concrete actions. Apart from that there's been some good discussions in the last weeks, but no concrete results yet. Best is probably to evaluate the progress on the above challenges next month to make a decision about the future of the project. Date of last release: No releases yet When were the last committers or PMC members elected? May 2013 Signed-off-by: [x](devicemap) Bertrand Delacretaz [ ](devicemap) Kevan Miller [ ](devicemap) Andrew Savory Shepherd/Mentor notes: (rvs) The report is missing. This on-n-off seems to continue with the project. I know that some of the mentors are recommending giving it more time, but it seems like we need to establish some metrics to at least get the community in shape to do the basics (like reporting and releasing). Without any kind of forcing function I am not sure what the future for this project really is. (bdelacretaz) Agreed - I have now provided a mentor report above. Fleece Implementation of JSon Processing Java specification. Fleece has been incubating since 2014-06-09. Three most important issues to address in the move towards graduation: 1. Finish bootstrapping project, update clutch.xml and update incubator status page. 2. Expanding the community, increase user list activity and adding new committers. 3. Develop a set of testcases which prove correct parsing behaviour. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? * none How has the community developed since the last report? * First communication/discussions via mailing lists took place, first issues reported and fixed. How has the project developed since the last report? * Incubator status page, the mailing lists and the initial website have been setup. Initial code have been imported. Date of last release: * No releases as of yet When were the last committers or PMC members elected? * N/A Signed-off-by: [X](fleece) Justin Mclean [ ](fleece) Christian Grobmeier [ ](fleece) Daniel Kulp Shepherd/Mentor notes: (jmclean) : Everything set up, off
Question on report
So - one of the podlings did not file a report, but one of the mentors did fill it in. Am I correct in assuming this would still count as a missed report? Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
July 2014 Incubator Report Timeline
Hi all, July 2014 Incubator Report Timeline: http://wiki.apache.org/incubator/July2014 Wed July 02 -- Podling reports due by end of day Sun July 06 -- Shepherd reviews due by end of day Sun July 06 -- Summary due by end of day Tue July 08 -- Mentor signoff due by end of day Wed July 09 -- Report submitted to Board Wed July 16 -- Board meeting Best, jzb - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Call for July's Report Manager
On 06/25/2014 11:32 PM, Marvin Humphrey wrote: The first task was due today: sending out the report timeline email to general@incubator. Consult report_runbook.py for the generated content. If you don't get to it by tomorrow afternoon, I'll send it out. Apologies! Sent out just now. Thanks, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Call for July's Report Manager
On Tue, Jun 17, 2014, at 04:33 PM, Marvin Humphrey wrote: On Tue, Jun 17, 2014 at 7:44 AM, John D. Ament john.d.am...@gmail.com wrote: Roman, hope you don't mind me getting this started early... Anyone interested in being a report manager for next month (July)'s report? Happily, Joe Brockmeier has already volunteered: Just confirming, yes - I'm happy to take this on for July. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache Celix as TLP
On 06/13/2014 05:17 PM, Roman Shaposhnik wrote: Personally, I don't feel this is a big deal. The PMC size is appropriate given the overall project size. That said, I'd like to make two points: * in general, for a smaller project like Celix I'd like to encourage folks to consider PMC == committers That is the case with Celix, correct? Looking at the status page, I only see committers and no PMC list. I would note that the number of PMC members concerns me a bit since the most recent release process took more than a month b/c there weren't enough VOTEs. That is somewhat tempered by the fact that the project seems to have added two PMC/committers since 1.0.0. Also of mild concern is that Celix missed its April report (it did report in May). Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Retire the S4 podling
Hi all, Per recent discussions on general@[1] and s4-dev@ [2], I went ahead and called for a VOTE on the S4 dev@ mailing list [3] about retiring the podling. That VOTE has passed with no -1s and 4 (binding) +1s from the podling PMC/committers. (S4 only has committers, and doesn't distinguish between PPMC/committer.) We didn't get a weigh-in from all mentors/PPMC on the retirement VOTE, so I'm going ahead and asking for a vote here. This VOTE will be open for at least 72 hours. Please indicate (binding) or (non-binding) when casting your VOTE. +1 [ ] Yes, I am in favor of retiring S4 from the Apache Incubator. +0 [ ] -1 [ ] No, I am not in favor of retiring S4 because... Note that we have one IPMC vote from Patrick already. [1] http://s.apache.org/7Gz [2] http://s.apache.org/ig [3] http://s.apache.org/OAU -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request for mentor assessment
On 06/12/2014 07:56 PM, Roman Shaposhnik wrote: This is one of the questions, I'd like to explore in greater details: are we comfortable with having professional student projects in the incubator? In response to the general question, it seems that professional student podlings are inconsistent with the idea that the Incubator is a process that should result in graduation or termination. In the case of Wave, it really strikes me as odd that the community is not capable of even a single release in more than 3.5 years: http://incubator.apache.org/wave/downloads.html This suggests that ASF is being used as a GitHub of sorts. Are we comfortable with this? Speaking for myself, no. I'd be uncomfortable having a specific deadline for graduation, but a podling that's not making progress towards graduation (in general, not pointing a finger specifically at Wave here) should be terminated. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: DRAFT Board Report June 2014
to address in the move towards graduation: 1. increase adoption, expand user community, and increase user list activity 2. have at least one more incubator release Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? none How has the community developed since the last report? A new PMC member was elected, Moon Soo Lee. The company DataSayer and the project Zeppelin (zeppelin-project.org) are now using MRQL. How has the project developed since the last report? We have switched to Junit for query testing, instead of evaluating queries from files using plain Java code. New tests were introduced and some bugs were corrected based on these tests. Date of last release: 2013-10-31 When were the last committers or PMC members elected? 2014-04-17 Signed-off-by: [X](mrql) Alan Cabrera [ ](mrql) Anthony Elder [ ](mrql) Alex Karasulu [ ](mrql) Mohammad Nour El-Din Parquet Parquet is a columnar storage format for Hadoop. Parquet has been incubating since 2014-05-20 . Three most important issues - Finish bootstrapping project, IP clearance, initial website - Expanding the community and adding new committers - 1st release Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - None at this time How has the community developed since the last report? - All initial committers have submitted ICLAs and the accounts have been created. The mailing lists have been setup and we are starting to use them for communication. How has the project developed since the last report? - We have setup the incubator status page and are waiting on the final SGA to be sent in to start the code import (INFRA-7782) Date of last release - No releases as of yet. Working through initial IP clearance. When were the last committers or PMC members elected? - N/A, still bootstrapping the project. Signed-off-by: [ ](parquet) Todd Lipcon [X](parquet) Jake Farrell [ ](parquet) Chris Mattmann [X](parquet) Roman Shaposhnik [X](parquet) Tom White S4 S4 (Simple Scalable Streaming System) is a general-purpose, distributed, scalable, partially fault-tolerant, pluggable platform that allows programmers to easily develop applications for processing continuous, unbounded streams of data. S4 has been incubating since 2011-09-26. No report submitted this month. There have been discussions about retiring the podling from the Apache Incubator. Sentry Sentry is a highly modular system for providing fine grained role based authorization to both data and metadata stored on an Apache Hadoop cluster. Sentry has been incubating since 2013-08-08. Three most important issues to address in the move towards graduation: 1. Grow the Sentry community 2. Add new committers that diversify the project 3. Continue to release at regular intervals Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? The community is growing. A number of new members have started actively contributing to the project. How has the project developed since the last report? The project did its 2nd release from incubation. Thanks to lot of hard work from the release manage Karthik Ramchandran and other community members, version 1.3 was released earlier this month. The db backed policy store feature branch is merged into master. The community is working towards improving that functionality and stabilization. Date of last release: 2014-05-15 When were the last committers or PMC members elected? Vamsee Yarlagadda has been added as a committer as announced on Feb 28, 2014. No new PPMC members have been added since the project has entered the incubator. Signed-off-by: [X](sentry) Arvind Prabhakar [X](sentry) Joe Brockmeier [ ](sentry) David Nalley [ ](sentry) Olivier Lamy [ ](sentry) Patrick Hunt [X](sentry) Thomas White Slider Slider is a collection of tools and technologies to package, deploy, and manage long running applications on Apache Hadoop YARN clusters. Slider has been incubating since 2014-04-29. Three most important issues to address in the move towards graduation: 1. Podling name search 2. Growing user community 3. Growing and increasing diversity of developer community Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? We're only getting started, and do not have any diversity yet. Our first goal will be to get users, bug reporters and developers. The dev list is up and running -and we do not have any separate user list, so we hope to pull users into coding. The initial release will help to gain awareness, and should bring in users. How has the project developed since the last report? Our main activity has
Re: DRAFT Board Report June 2014
I'm going to put this up on the wiki, please let me know if there are
any issues.
On Tue, Jun 10, 2014, at 01:07 AM, Joe Brockmeier wrote:
On 06/09/2014 11:11 AM, John D. Ament wrote:
All,
Please find the draft board report which includes all podlings that
have submitted reports thus far below.
Revised draft with summary, release info, etc.
= Incubator PMC report for June 2014 =
=== Timeline ===
||Wed June 04 ||Podling reports due by end of day ||
||Sun June 08 ||Shepherd reviews due by end of day ||
||Sun June 08 ||Summary due by end of day ||
||Tue June 10 ||Mentor signoff due by end of day ||
||Wed June 11 ||Report submitted to Board ||
||Wed June 18 ||Board meeting ||
=== Shepherd Assignments ===
||Alan D. Cabrera ||Brooklyn ||
||Andrei Savu ||Slider ||
||Andrei Savu ||Streams ||
||Dave Fisher ||S4 ||
||John Ament ||Storm ||
||Justin Mclean ||Kalumet ||
||Matthew Franklin ||Falcon ||
||Konstantin Boudnik ||Flink ||
||Matthew Franklin ||MRQL ||
||Raphael Bircher ||Wave ||
||Konstantin Boudnik ||Drill ||
||Ross Gardler ||DeviceMap ||
||Suresh Marru ||Sentry ||
||Suresh Marru ||log4cxx2 ||
=== Report content ===
{{{
Incubator PMC report for June 2014
The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.
There are currently 35 podlings under incubation. Two new podlings joined
the Apache Incubator in May, two podlings graduated.
* Community
New IPMC members:
John D. Ament
People who left the IPMC:
(none)
* New Podlings
Optiq
Parquet
* Graduations
Phoenix
Stratos
The board has motions for the following:
(none)
* Releases
The following releases were made since the last Incubator report:
metamodel-4.1.0-RC1-incubating
odftoolkit-0.6.1-incubating
sentry-1.3.0-incubating
slider-0.30-incubating
spark-0.8.1-incubating
* IP Clearance
Cray donated a set of libraries called Hadoop RDF Tools, and a VOTE
to accept the tools was called by Rob Vesse. The vote passed by lazy
consensus after 72 hours. No objections or points of discussion were
raised during the VOTE.
* Legal / Trademarks
New name for Stratosphere, now Flink.
* Infrastructure
Apache Podlings affected by ASF mail outage from May 7th through
May 10th, and extended recovery period to deliver backlog.
* Miscellaneous
S4 failed to report this month, and has been generally inactive. It
is likely that S4 will be retired, though the PPMC has not voted yet
to do so.
Summary of podling reports
* Still getting started at the Incubator
Brooklyn
* Not yet ready to graduate
No release:
NPanday
Samza
Wave
Community growth:
* Ready to graduate
The Board has motions for the following:
* Did not report, expected next month
Kalumet
S4
--
Table of Contents
Brooklyn
DeviceMap
Drill
Falcon
Flink (formerly Stratosphere)
Kalumet
log4cxx2
MRQL
Parquet
S4
Sentry
Slider
Storm
Streams
Wave
--
Brooklyn
Brooklyn is a framework for modeling, monitoring, and managing
applications
through autonomic blueprints.
Brooklyn has been incubating since 2014-05-01.
Three most important issues to address in the move towards graduation:
1. Migrating fully to Apache infrastructure (mainly concerning open
pull requests and issue tracker)
2. Forming a diverse community and PPMC
3. Learning and following the Apache way
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No.
How has the community developed since the last report?
This is our first report; our community remains very similar to the
point where we joined the Incubator.
How has the project developed since the last report?
This is our first report; our community remains very similar to the
point where we joined the Incubator.
Date of last release:
No releases yet under the Incubator.
When were the last committers or PMC members elected?
No new committers since we joined the Incubator.
DeviceMap
Apache DeviceMap is a data repository containing device information,
images
and other relevant information for all sorts of mobile devices, e.g.
smartphones and tablets. While the focus is initially on that data, APIs
will also be created to use and manage it.
DeviceMap has been incubating since 2012-01-03.
Three most important issues to address in the move towards graduation:
1. Grow community.
2. Generate a release.
3. Explore options to allow contributions through a Web based
interface/API to add new
Re: DRAFT Board Report June 2014
On Tue, Jun 10, 2014, at 11:40 AM, John D. Ament wrote: The only thing I've noticed is that the dates of the releases are missing. I'm not sure that's a big requirement though. You mean the final release date, or the length of the vote? Marvin had said that was optional (length of vote) and I don't see release dates in previous reports from April/May. However, I can add dates tonight if that's OK with everyone - I don't think that piece is substantial enough to prevent a review prior to sending to the board. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Call for Report Manager for June
On 06/09/2014 07:48 PM, John D. Ament wrote: Just wanted to point out, the report's due to the board on Wednesday and the VP should review prior to submission in case there are any edits. If you need help getting any of this together, let me know I can lend a hand. Working on this tonight, will let you know tomorrow morning if I run into any snags. (Or, alternately, it'll be done!) (Apologies for delay - travelling yesterday, at DockerCon today.) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding Summary - June 2014
On Sun, Jun 8, 2014, at 07:43 PM, John D. Ament wrote: Please be advised that the following podlings have not reported yet, and will be moved to monthly: Brooklyn Just entered incubation on May 1, will make sure there's a report for June next month. S4 Per last months' discussion, this podling is probably going to retire but not much movement to make that happen. I'm going to start a vote on that dev list to see if we can move this forward. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Call for Report Manager for June
On 06/01/2014 01:31 PM, Marvin Humphrey wrote: Joe Brockmeier wrote: I'd be interested in helping this month, with an eye to doing the report manager work for July and perhaps onwards from there. Wow, what a recruit -- thanks for stepping up, Joe! With your background in tech journalism, you're extremely overqualified for the Report Manager's editorial aspects. I look forward to supporting you this month and in July as well. As far as ongoing, let's revisit after the July report. The report is a pretty big production, and we've been working towards building a pool of people who can rotate in so that no one person burns out. John D. Ament replied to Joe: Great to hear! Do you want to do the report manager piece or the shepherd manager piece? John, I'm not totally clear on how you envision divvying up responsibility. Here's how we've done things before: mechanical -- Send report timeline email. mechanical -- Assign podlings which do not report to monthly. editorial -- Assemble list of releases. editorial -- Create podling summary. editorial -- Write narrative, misc, legal, infrastructure, etc. sections. mechanical -- Normalize report formatting mechanical -- Send shepherding email. Chair -- Deliver report to Board. mechanical -- Prepare next month's report template. It seems to me that your shepherd manager partially overlaps the mechanical responsibilities laid out here. Joe, what would you like to take on? Out of this list, I can take on: editorial -- Assemble list of releases. editorial -- Create podling summary. editorial -- Write narrative, misc, legal, infrastructure, etc. sections. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Call for Report Manager for June
On Sun, Jun 1, 2014, at 07:31 AM, John D. Ament wrote: All, I'd like to up the ante on Roman's proposal. After doing this job last month, I'd like to propose to split the responsibilities with someone for this month: - Report Manager is responsible for getting the incubator stuff together. Legal, releases, new members, etc. - Shepherd Manager is responsible for keeping all the shepherds together and formatting any of their reports. Either side, and probably both, would need to help any podlings with getting their reports together. If anyone's interested in taking on some of the work, let us know. I'd be interested in helping this month, with an eye to doing the report manager work for July and perhaps onwards from there. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANNOUNCE] John D. Ament joins the IPMC
On Sat, May 31, 2014, at 09:36 AM, Roman Shaposhnik wrote: Welcome, John! Great to have you on board! Welcome, John! Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT][VOTE] Accept Brooklyn into the Incubator
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/01/2014 01:34 PM, Chip Childers wrote: With 21 +1 votes (plenty binding), and no other votes, the vote passes. Welcome to the incubator Brooklyn! Congrats! Looking forward to it. Best, jzb - -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTY7n1AAoJEKbW5zOgIHzUcPEIANfrVR8ZCKeY1s+7cru1Cx1P ons/yFmIldg4ANj6XqtUPoB3I8aULiX4pB6x95Ptar7g0tXZ0HkVwoVhRi0s/kCv NVZ1/IVtXfNL4jk1aeYKqTQagk14xlsYNSAYzuoUDK8nn9jYep5ABcFqMAOhvdwD G9Tzjs0DYU3Xu4l02b/AYP9b/VjtmQbWJy7Hnu1aDfLLdD1azmaSqQRj4rauQQd8 02Ly8C5Ft1R1dZpoN31hgMSlhWnazW/QpYRUOuYkn5b3gjoXsk8ddAhaop9Awfon 5FbJIKjPFs1KTolUySfgYOnH3vMLg58emR2J50yJbh/lx8KluF413SucPMnK4O4= =eIjO -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Brooklyn into the Incubator
On Mon, Apr 28, 2014, at 08:49 AM, Chip Childers wrote: Based on the previous discussion of accepting Brooklyn into the Apache Incubator as a podling, I'd like to call a vote for this now. [X] +1 Accept Brooklyn into the Incubator (binding) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Brooklyn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/23/2014 09:28 AM, Chip Childers wrote: We would also like to solicit contributions from additional IPMC members willing to mentor the potential podling. Anyone interested? I'd be interested in signing on as a mentor. Best, jzb - -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTWeQkAAoJEKbW5zOgIHzUatcIAJwquckEzeV0fHd3bSZh8XrG zsLelrRGR2Qw+SWe1BSn+dpgUahfzMjhfm92AsWbX309SL/e0J/kBg8aRtaY7ioq L8lnhUu/1kAOB5wGfAfTaB9SmB7rlMMngb5125Zg9AHN4pZ3MaXV5Sy/h47qjKWF 009miJ0ojqs3gBF+B5za5aqPKY5uSIJoFLpEnm+HXz3FHPVrFxCwSoNHBbEhzpgn czas9+PxF6ChtsMhyy0B7dxacEmER75kC5MqNSVWW7kHvmlfdU8eArRXDQrxWJvx Y0yeMHIleCeYY0HCcT1dZUXIG2Dd8JWfYZKGgBxs4YB+FXhvmnEDRVOsEPK6as4= =rzMC -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Storm into the Incubator
On Thu, Sep 12, 2013, at 02:19 PM, Doug Cutting wrote: Discussion about the Storm proposal has subsided, issues raised now seemingly resolved. I'd like to call a vote to accept Storm as a new Incubator podling. The proposal is included below and is also at: https://wiki.apache.org/incubator/StormProposal Let's keep the vote open for four working days, until 18 September. [ ] +1 Accept Storm into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Storm because... +1 (binding) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE]: Accept Sentry in Apache Incubator
On Mon, Aug 5, 2013, at 08:23 AM, Shreepadma Venugopalan wrote: Following the discussions last week, I'm calling a vote to accept Sentry as a new project in the Apache Incubator. The proposal draft is available at: https://wiki.apache.org/incubator/SentryProposal and is also pasted to the bottom of this email. It is identical to what was proposed except for a) addition of two new mentors, and b) removal of the user list for now, per Marvin's suggestion. The proposal thread is available at: http://goo.gl/bvvJPh [ ] +1 Accept Sentry in the Incubator [ ] +/-0 Don't care [ ] -1 Don't accept Sentry in the Incubator because... +1 (binding) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Curator 2.1.0-incubating
On Wed, Jun 26, 2013, at 10:12 PM, Jordan Zimmerman wrote: Hello, This is a vote for the release of Apache Curator, version 2.1.0-incubating. ... [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) +1 (binding) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Provisionr version 0.4.0-incubating, RC0
On Thu, Jun 27, 2013, at 04:10 PM, Andrei Savu wrote: On Thu, Jun 27, 2013 at 7:59 PM, Dave Fisher dave2w...@comcast.net wrote: This link doesn't help determine who has voted from the PPMC nor does it provide a count of how many votes and by whom. Have you had any IPMC/binding votes? My bad. I was a bit lazy. We had 3 +1's from the PPMC and one +1 from Rahul Sharma (as contributor). No binding votes on the project mailing list. Generally, it's best practice to: 1) Supply a list of binding votes from your PPMC in the summary email to this list, like so: http://markmail.org/thread/wu4lpcdk6uk6lben 2) Supply a link to your [RESULT][VOTE] message that summarizes the vote, at the tail end of the VOTE thread. See, for example: http://markmail.org/message/dg6mquboi65t2nho Having to go through the list + comb through the names match them with PPMC is time-consuming. I looked it over, built it, etc. Looks good to me. +1 (binding) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Wave 0.4 based on RC3
Hi Ali, On Wed, Jun 19, 2013, at 03:06 PM, Ali Lown wrote: The voting period has now passed, and we have received no votes from anyone here :( Sorry, folks are too busy debating the problems of the Incubator to take time to review Incubator releases. ;-) I'll try to take a look tonight and nudge a few other IPMC folks do to the same. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Wave 0.4 based on RC3
Hi Ali, Comments inline. On Sat, Jun 15, 2013, at 05:24 PM, Ali Lown wrote: The result from the wave-dev vote can be found at: https://mail-archives.apache.org/mod_mbox/incubator-wave-dev/201306.mbox/%3CCABRGrVfPOwN3E8N-uScruYbxdezpfZzAJHMp8dN%2BUfpF6s%2BDGw%40mail.gmail.com%3E I find this slightly confusing as I expected at least 3 PPMC votes, but I guess Wave has opted for the committer == PPMC model? Wave 0.4 RC3 artefacts are available at: https://people.apache.org/~al/wave_rc/0.4-rc3/ Note: The checksums are SHA-512's A couple of things: - Preferably, you'd only include *one* set of artifacts to vote on. Am I voting on the zip, the bz2? I'm uncomfortable voting without checking out all the source releases as I have no way of knowing that the zip == the bz2 release without inspecting both. - Preferably, there'd be no binary release in the artifacts you're asking to have voted on. Convenience binaries are fine, but they're not an official release, so it'd be better not to include them with the files we're meant to be voting on. - I have to -1 this as there are several binary (.jar) files included in the release that don't belong in a source release. (under third_party/codegen/*) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Wave 0.4 based on RC3
I should have added: please do address the problems here and re-roll and I will be sure to examine that release in a timely fashion. Don't let a -1 discourage you, as most incubating projects have to go through a learning curve. On Thu, Jun 20, 2013, at 06:59 PM, Joe Brockmeier wrote: Hi Ali, Comments inline. On Sat, Jun 15, 2013, at 05:24 PM, Ali Lown wrote: The result from the wave-dev vote can be found at: https://mail-archives.apache.org/mod_mbox/incubator-wave-dev/201306.mbox/%3CCABRGrVfPOwN3E8N-uScruYbxdezpfZzAJHMp8dN%2BUfpF6s%2BDGw%40mail.gmail.com%3E I find this slightly confusing as I expected at least 3 PPMC votes, but I guess Wave has opted for the committer == PPMC model? Wave 0.4 RC3 artefacts are available at: https://people.apache.org/~al/wave_rc/0.4-rc3/ Note: The checksums are SHA-512's A couple of things: - Preferably, you'd only include *one* set of artifacts to vote on. Am I voting on the zip, the bz2? I'm uncomfortable voting without checking out all the source releases as I have no way of knowing that the zip == the bz2 release without inspecting both. - Preferably, there'd be no binary release in the artifacts you're asking to have voted on. Convenience binaries are fine, but they're not an official release, so it'd be better not to include them with the files we're meant to be voting on. - I have to -1 this as there are several binary (.jar) files included in the release that don't belong in a source release. (under third_party/codegen/*) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ODF Toolkit 0.6-incubating(RC6)
On Mon, Jun 17, 2013, at 12:12 AM, Florian Hopf wrote: the voting period has passed but we had another IPMC +1 from our mentor Nick Burch on odf-dev. Our other mentor Yegor seems to be pretty busy currently so it would be great if somebody else could have a look at the release candidate. Took a second look at this today, thanks for addressing the concerns I raised the first time around. +1 (binding) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Mandatory podling exit interviews
On Sat, Jun 15, 2013, at 12:18 PM, Ross Gardler wrote: I'm not keen on this one. I don't like surveys and I don't like mandatory activities for volunteers. Yet, Apache does have mandatory reporting for podlings and TLPs. It's not like this is particularly onerous. (Note, I read the proposal as an exit interview for the project/podling, not each and every individual committer/PPMC member.) But if the mandatory thing is too much for people, I think strongly encouraged exit interviews are a good idea. I am curious how the reports would be scrubbed, though - given that the timing of an exit interview would strongly indicate which project had graduated, and there's usually a fairly small number of mentors and project participants to provide feedback. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Stratos proposal as an incubating project
On Fri, Jun 14, 2013, at 04:49 PM, Ross Gardler wrote: I would like to invite the IPMC vote to accept the Stratos proposal [1]. I want to clarify that this vote is for the Stratos project to enter the incubator as a standard podling under the existing incubation policy. The acceptance or otherwise of the probationary TLP idea is a separate issue that will be explored during the first month of incubation, potentially resulting in a further IPMC vote. This vote is *only* for accepting the Stratos project as a podling. [ ] +1 Accept the Stratos project as an incubating project [ ] +0 [ ] -1 Do not accept the Stratos project as an incubating project because... (provide reason) +1 (binding) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
On Thu, Jun 13, 2013, at 08:58 AM, Chip Childers wrote: Alternatively, if WS02 wanted to keep using the Stratos term, the podling (to be) could re-brand the project itself to something other than Stratos. I think this would be a better way to go, honestly. If there was one thing I could do over again about CloudStack, it would have been to have let Citrix keep the name for their commercial offering and choose a different name for the Apache project. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Apache HotdoG into the Incubator
On Wed, Jun 12, 2013, at 01:22 PM, Ramirez, Paul M (398J) wrote: I'd like to call a VOTE for the acceptance of Apache HotdoG into the Incubator. I'll leave the VOTE open for the rest of the week and close it out Monday, June 17th early am PT. [ ] +1 Accept Apache HotdoG into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Apache HotdoG because... Full Proposal is pasted at the end of this email. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. +1 (binding) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Mesos
Have you updated your Incubator status page prior to this? I think there must be quite a few committers added since the proposal that are missing there. On Wed, Jun 12, 2013, at 03:03 PM, Mattmann, Chris A (398J) wrote: Hi All, The Apache Mesos community is ready to graduate. They have added committers and PPMC members while in the Incubator; have made a few releases; are discussing their issues on list and in the Apache way, and are inclusive and representative of Apache's goals as a Foundation. I'm extremely happy to put them up for Incubator graduation. We've VOTEd as a community to move forward with this: DISCUSS thread here: http://s.apache.org/XAu VOTE thread here: http://s.apache.org/K8C VOTE RESULT: Message-ID: cdde1f13.d6ea1%chris.a.mattm...@jpl.nasa.gov Project Incubator status page here: http://incubator.apache.org/projects/mesos.html Board resolution pasted at bottom of email. Existing tallies from the community VOTE: +1 Chris Mattmann* Vinod Kone Benjamin Hindman Benjamin Mahler Yan Xiu Deepal Jayasinghe Brenden Matthews Matei Zaharia Ant Elder* Konstantin Boudnik * - indicates IPMC Please VOTE to graduate Apache Mesos from the Incubator. Though only Incubator PMC member VOTEs are binding, all are welcome to voice your opinion. I'll leave the VOTE open for at least 72 hours, and hopefully can get enough VOTEs in time to close it by Saturday or Sunday in time for the board meeting on 6/19. [ ] +1 Graduate Apache Mesos from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Mesos from the Incubator because.. Thanks everyone! Cheers, Chris ---board resolution WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to efficient cluster management, resource isolation and sharing across distributed applications. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Mesos Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Mesos Project be and hereby is responsible for the creation and maintenance of software related to efficient cluster management, resource isolation and sharing across distributed applications; and be it further RESOLVED, that the office of Vice President, Apache Mesos be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Mesos Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Mesos Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Mesos Project: * Ali Ghodsi a...@apache.org * Andy Konwinski and...@apache.org * Benjamin Hindhman b...@apache.org * Benjamin Mahler bmah...@apache.org * Brian McCalister bri...@apache.org * Ian Holsman i...@apache.org * Matei Alexandru Zahari ma...@apache.org * Chris Mattmann mattm...@apache.org * Tom White tomwh...@apache.org * Vinod Kone vinodk...@apache.org * Brenden Matthews bren...@apache.org * Thomas Marshall tmarsh...@apache.org * Charles Reiss wog...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Benjamin Hindman be appointed to the office of Vice President, Apache Mesos, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Mesos Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Mesos podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Mesos podling encumbered upon the Apache Incubator Project are hereafter discharged. ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Best, jzb -- Joe
Re: [VOTE] Apache Spark for the Incubator
On Sat, Jun 8, 2013, at 12:34 AM, Mattmann, Chris A (398J) wrote: [ ] +1 Accept Spark into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept Spark into the Apache Incubator because.. +1 (binding) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Apache MetaModel into the Apache incubator
On Thu, Jun 6, 2013, at 05:30 PM, Henry Saputra wrote: [] +1 Accept MetaModel into the Apache incubator [] +0 Don't care. [] -1 Don't accept MetaModel into the incubator because... +1 (binding) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator
On Wed, Jun 5, 2013, at 10:00 AM, Ramirez, Paul M (398J) wrote: You are too fast for me. I'm moving forwarding with canceling for now, securing a mentor, and then resubmitting the vote. I would move to pull in the +1s during the next vote; noting that a retraction could be made if the person wished. I believe we can secure a mentor in short order but see no reason to buck the trend of a successful model and would prefer to start off on a good foot with as many people helping this along as possible. I'm willing to help here, you can count me in as a mentor. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Apache BeanShell in the Incubator
On Fri, May 24, 2013, at 02:23 AM, Simone Tripodi wrote: Dear ASF members, We would like to propose BeanShell for the incubator. The proposal draft is available at: https://wiki.apache.org/incubator/BeanShellProposal, follows below the proposal Open is open for at least 72h and closes approximately on May 27th at 8:20am GMT [ ] +1 accept BeanShell in the Incubator [ ] +/-0 [ ] -1 because (provide a reason) +1 (binding) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ODF Toolkit 0.6-incubating(RC5)
On Tue, May 21, 2013, at 12:56 AM, Florian Hopf wrote: Thanks, so far I got the impression that the most important place to put my key is at https://people.apache.org/keys/committer/ I am not sure yet how to upload files to the dist folder but I'll figure that out. You should have SVN access there. If you're still having trouble, let us know. As those changes don't require any changes to the source tree I think we don't need to vote on the dev-list again but only on the incubator list? Not sure there's a hard and fast rule there. I would probably re-start the vote, but that's me. I don't think it's absolutely necessary. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ODF Toolkit 0.6-incubating(RC5)
Hi Florian, On Sun, May 12, 2013, at 09:17 AM, Florian Hopf wrote: RC 5 of the ODF Toolkit 0.6-incubating is ready for release. This release candidate addresses missing licenses and the disclaimer that have been identified during the last IPMC vote. Which of the artifacts are we meant to be voting on? We have three source choices (tar.bz2, tar.gz, zip) - and ideally we'd be testing *all* of these to verify that they're the same. Why not distribute just one tarball? I'm OK with convenience binaries, but I really don't think it's a good idea to put them in the same directory as the source artifacts you want voted on. Also, I can't +1 this because the signature of the distributed artifact does not match the KEYS file in your dist directory. Your dist directory has this KEYS file: http://www.apache.org/dist/incubator/odftoolkit/KEYS Which only has Devin Han's key. You're distributing a KEYS file with your own key, but obviously we're not going to trust a KEYS file that is distributed with the source tarball itself. You need to upload your new KEYS file and point to it in your email asking for votes. Could you please re-roll this and start a new VOTE? Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Creating announce@ lists by default
On Tue, Mar 26, 2013, at 12:21 PM, Luciano Resende wrote: If I was the press/analyst folks or security/sysadmin folks, I'd probably prefer to receive all these announcements over one list, then having to figure out every announcement list for each apache project in use in my infrastructure or that I'm interested in. /me puts on my former press hat It depends a lot on whether I cover all open source or a specific project. If I care only about one or two Apache projects, I probably don't want to get all Apache announcements. Folks who care/write about OpenOffice, for instance, aren't going to necessarily want announcements about Whirr or Hadoop. AFAIC, having project-specific announce lists is good practice. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Apache CloudStack 4.0.1-incubating
After 72 hours, the vote for CloudStack 4.0.1-incubating *passes* with 3 IPMC +1 vote: +1 (binding) * Jim Jagielski * Olivier Lamy * Alex Karasulu There were no -1 or +0 votes cast. Jim, Olivier, and Alex voted on the cloudstack-...@incubator.apache.org vote thread [1]. I will be publishing the release today, and the project's community will put out its release announcement next week (after the mirrors have caught up). Thanks to everyone for participating! Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Apache CloudStack 4.0.1-incubating
Hi all, I'd like to call a vote for Apache CloudStack (Incubating) release, 4.0.1-incubating. This has been voted through on the cloudstack-...@incubator.apache.org mailing list (vote thread [1], and results [2]), and now requires a vote on general@incubator.apache.org. 3 IPMC votes have already been cast on the vote held on cloudstack-dev: +1 (PPMC / binding) * Jim Jagielski (mentor) * Olivier Lamy (mentor) * Alex Karasulu (mentor) There were no -1 or +0 votes cast. Instructions for validating and testing the artifacts can be found here: https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure If you have any trouble setting up a test environment using the procedure on the CloudStack wiki, please ask on the cloudstack-...@incubator.apache.org list. Someone will be sure to help, and we'll be sure to improve the test procedure documentation as well. The following artifacts are up for vote: Git Branch and Commit SH: https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=shortlog;h=refs/heads/4.0 Commit: cd83b49ee5107f11a754679b376b8631e3535878 List of changes: https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0 Source release (checksums and signatures are available here as well): https://dist.apache.org/repos/dist/dev/incubator/cloudstack/candidates/4.0.1-incubating/ PGP release keys (signed using A0207CD4) https://dist.apache.org/repos/dist/release/incubator/cloudstack/KEYS The vote will be open for 72 hours. For sanity in tallying the vote, can PPMC and IPMC members please be sure to indicate (binding) with their vote? [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks! [1] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3C20130128212642.GA3954@localhost.localdomain%3E [2] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C1359976565.32074.140661186536781.17F27A4D%40webmail.messagingengine.com%3E Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Wiki write access
Hi all, I need to request write access to the incubator wiki: Wiki username: JoeBrockmeier Apache username: jzb Please let me know if you need any additional information. Thanks! Joe -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
