[RESULT][VOTE] Apache Chukwa graduation as TLP
Graduation community vote passed with 7 +1 from , which from those 6 are binding : Jean-Baptiste Onofre Ant Elder Christian Grobmeier Jukka Zitting Luciano Resende Alan D. Cabrera Jie Huang (non-binding) I'll check the status of the resolution and continue the process on the IPMC. Thanks regards, Eric On Tue, Sep 24, 2013 at 6:47 AM, Alan D. Cabrera l...@toolazydogs.comwrote: +1 - binding Regards, Alan On Sep 20, 2013, at 10:52 AM, Eric Yang ey...@apache.org wrote: [ ] +1 Graduate Chukwa podling from Incubator [ ] +0 Indifferent to graduation status of Chukwa [ ] -1 Reject graduation of Chukwa podling from Incubator because ...
Re: [VOTE] Apache Chukwa graduation
Thanks. We will request trademarks to look into it. regards, Eric On Mon, Sep 23, 2013 at 5:59 AM, Christian Grobmeier grobme...@gmail.comwrote: On 22 Sep 2013, at 22:59, Eric Yang wrote: We did the name search in 2009, 2010, and 2012 via different Apache processes while we were a sub-project of Hadoop, and repeat the name search process for incubator. The podling name search has been updated in https://issues.apache.org/**jira/browse/PODLINGNAMESEARCH-**19https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-19. I think trademark should not be an issue, Apache Chukwa (TM) has been listed on hadoop.apache.org for years. Hope this addresses the concerns. As the docs say, you can only work with the trademark when Trademark VP has resolved the mentioned issue. Since the issue is open for pretty long time, I will try to urge it on trademarks regards, Eric On Sun, Sep 22, 2013 at 6:38 AM, Christian Grobmeier grobme...@gmail.com wrote: -1 (binding) I have not seen a successful resolution of this process: http://www.apache.org/foundation/marks/naming.htmlhttp://www.apache.org/**foundation/marks/naming.html h**ttp://www.apache.org/**foundation/marks/naming.htmlhttp://www.apache.org/foundation/marks/naming.html I have seen some effort have been made in 2010: http://incubator.apache.org/projects/chukwa.htmlhttp://incubator.apache.org/**projects/chukwa.html http://**incubator.apache.org/projects/**chukwa.htmlhttp://incubator.apache.org/projects/chukwa.html The process has changed meanwhile and needs to be documented. The process has been discussed at general@incubator and should be known. Maybe I missed the issue (Jira being slow today for me). Please send me a successfully resolved issue number and I will turn into +1. Thanks! On Fri, Sep 20, 2013 at 6:52 PM, Eric Yang ey...@apache.org wrote: The Apache Chukwa project entered incubator in July of 2010. Since then it has grown the community in users, committers and PPMC members, made significant improvements to the project codebase and completed many releases following ASF policies and guidelines. The Apache Chukwa community has voted to proceed with graduation [1] and the result can be found at [2]. Discussion about the proposed resolution is also available at [3]. Please cast your votes: [ ] +1 Graduate Chukwa podling from Incubator [ ] +0 Indifferent to graduation status of Chukwa [ ] -1 Reject graduation of Chukwa podling from Incubator because ... Please find the proposed board resolution below. [1] http://s.apache.org/chukwa-graduation-votehttp://s.apache.org/chukwa-**graduation-vote http://s.**apache.org/chukwa-graduation-**votehttp://s.apache.org/chukwa-graduation-vote [2] http://s.apache.org/chukwa-graduation-resulthttp://s.apache.org/chukwa-**graduation-result http://s.**apache.org/chukwa-graduation-**resulthttp://s.apache.org/chukwa-graduation-result [3] http://s.apache.org/chukwa-graduation-Resolutionhttp://s.apache.org/chukwa-**graduation-Resolution http://**s.apache.org/chukwa-**graduation-Resolutionhttp://s.apache.org/chukwa-graduation-Resolution Resolution: X.Establish the Apache Chukwa Project 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 data streaming and visualization for Hadoop services. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Chukwa Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Chukwa Project be and hereby is responsible for the creation and maintenance of a software project related to data streaming, monitoring and visualization for Hadoop services; and be it further RESOLVED, that the office of Vice President, Apache Chukwa 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 Chukwa Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Chukwa 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 Chukwa Project: * Ahmed Fathalla (afathalla) * Alan D. Cabrera (adc) * Ant Elder (antelder) * Ariel Rabkin (asrabkin) * Bill Graham (billgraham) * Eric Yang (eyang) * Grace Huang (grace.huang) * Ivy Tang (ivytang) * Jerome Boulon (jboulon) * Jiaqi Tan (tanjiaqi) * Shreyas Subramanya (shreyas) * Sourygna Luangsay (sluangsay) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Eric Yang, be appointed to the office of Vice President, Apache Chukwa
Re: [VOTE] Apache Chukwa graduation
We did the name search in 2009, 2010, and 2012 via different Apache processes while we were a sub-project of Hadoop, and repeat the name search process for incubator. The podling name search has been updated in https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-19. I think trademark should not be an issue, Apache Chukwa (TM) has been listed on hadoop.apache.org for years. Hope this addresses the concerns. regards, Eric On Sun, Sep 22, 2013 at 6:38 AM, Christian Grobmeier grobme...@gmail.comwrote: -1 (binding) I have not seen a successful resolution of this process: http://www.apache.org/**foundation/marks/naming.htmlhttp://www.apache.org/foundation/marks/naming.html I have seen some effort have been made in 2010: http://incubator.apache.org/**projects/chukwa.htmlhttp://incubator.apache.org/projects/chukwa.html The process has changed meanwhile and needs to be documented. The process has been discussed at general@incubator and should be known. Maybe I missed the issue (Jira being slow today for me). Please send me a successfully resolved issue number and I will turn into +1. Thanks! On Fri, Sep 20, 2013 at 6:52 PM, Eric Yang ey...@apache.org wrote: The Apache Chukwa project entered incubator in July of 2010. Since then it has grown the community in users, committers and PPMC members, made significant improvements to the project codebase and completed many releases following ASF policies and guidelines. The Apache Chukwa community has voted to proceed with graduation [1] and the result can be found at [2]. Discussion about the proposed resolution is also available at [3]. Please cast your votes: [ ] +1 Graduate Chukwa podling from Incubator [ ] +0 Indifferent to graduation status of Chukwa [ ] -1 Reject graduation of Chukwa podling from Incubator because ... Please find the proposed board resolution below. [1] http://s.apache.org/chukwa-**graduation-votehttp://s.apache.org/chukwa-graduation-vote [2] http://s.apache.org/chukwa-**graduation-resulthttp://s.apache.org/chukwa-graduation-result [3] http://s.apache.org/chukwa-**graduation-Resolutionhttp://s.apache.org/chukwa-graduation-Resolution Resolution: X.Establish the Apache Chukwa Project 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 data streaming and visualization for Hadoop services. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Chukwa Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Chukwa Project be and hereby is responsible for the creation and maintenance of a software project related to data streaming, monitoring and visualization for Hadoop services; and be it further RESOLVED, that the office of Vice President, Apache Chukwa 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 Chukwa Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Chukwa 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 Chukwa Project: * Ahmed Fathalla (afathalla) * Alan D. Cabrera (adc) * Ant Elder (antelder) * Ariel Rabkin (asrabkin) * Bill Graham (billgraham) * Eric Yang (eyang) * Grace Huang (grace.huang) * Ivy Tang (ivytang) * Jerome Boulon (jboulon) * Jiaqi Tan (tanjiaqi) * Shreyas Subramanya (shreyas) * Sourygna Luangsay (sluangsay) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Eric Yang, be appointed to the office of Vice President, Apache Chukwa, 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 initial Apache Chukwa Project PMC be hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Chukwa Project; and be it further RESOLVED, that the initial Apache Chukwa Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Chukwa podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Chukwa podling encumbered upon the Apache Incubator PMC are hereafter discharged. Regards Eric --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org
[VOTE] Apache Chukwa graduation
The Apache Chukwa project entered incubator in July of 2010. Since then it has grown the community in users, committers and PPMC members, made significant improvements to the project codebase and completed many releases following ASF policies and guidelines. The Apache Chukwa community has voted to proceed with graduation [1] and the result can be found at [2]. Discussion about the proposed resolution is also available at [3]. Please cast your votes: [ ] +1 Graduate Chukwa podling from Incubator [ ] +0 Indifferent to graduation status of Chukwa [ ] -1 Reject graduation of Chukwa podling from Incubator because ... Please find the proposed board resolution below. [1] http://s.apache.org/chukwa-graduation-vote [2] http://s.apache.org/chukwa-graduation-result [3] http://s.apache.org/chukwa-graduation-Resolution Resolution: X.Establish the Apache Chukwa Project 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 data streaming and visualization for Hadoop services. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Chukwa Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Chukwa Project be and hereby is responsible for the creation and maintenance of a software project related to data streaming, monitoring and visualization for Hadoop services; and be it further RESOLVED, that the office of Vice President, Apache Chukwa 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 Chukwa Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Chukwa 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 Chukwa Project: * Ahmed Fathalla (afathalla) * Alan D. Cabrera (adc) * Ant Elder (antelder) * Ariel Rabkin (asrabkin) * Bill Graham (billgraham) * Eric Yang (eyang) * Grace Huang (grace.huang) * Ivy Tang (ivytang) * Jerome Boulon (jboulon) * Jiaqi Tan (tanjiaqi) * Shreyas Subramanya (shreyas) * Sourygna Luangsay (sluangsay) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Eric Yang, be appointed to the office of Vice President, Apache Chukwa, 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 initial Apache Chukwa Project PMC be hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Chukwa Project; and be it further RESOLVED, that the initial Apache Chukwa Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Chukwa podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Chukwa podling encumbered upon the Apache Incubator PMC are hereafter discharged. Regards Eric
Re: binary release artifacts
Thank you Elder for filing the LEGAL-178. Tim, the link provided is for source file headers and reference to Apache distribution of source code tarball. We will wait for LEGAL-178 to be resolved to react. This implies that Apache OpenOffice is also not doing the right thing. OpenOffice has its license translated to multiple languages, hence LICENSE and NOTICE files are not at top level. We should plan to make the system scale and improve upon. We can plan to make course correction for future release. The existing artifacts have been released for years, and it may not be the best interest of Apache Foundation to recall those artifacts. There could be users who depends on them. Binary artifacts did not violate any license terms. We appreciate your understanding on the subject at hand. regards, Eric On Mon, Sep 16, 2013 at 1:44 AM, ant elder ant.el...@gmail.com wrote: Perhaps, but AFAICT the existing documentation is either incorrect, lacking, or ambiguous so i've raised LEGAL-178 to clarify. ...ant On Mon, Sep 16, 2013 at 12:56 AM, sebb seb...@gmail.com wrote: On 15 September 2013 14:16, Tim Williams william...@gmail.com wrote: On Sun, Sep 15, 2013 at 5:19 AM, ant elder ant.el...@gmail.com wrote: Tim, one of the things we're trying to teach podlings is how to handle disputes and resolve problems in a happy respectful manner. You've out of the blue come on to their dev list without introducing yourself demanding that something that happened nearly two years ago be undone. My mail on their list wasn't intended to be 'demanding' or rude - my apologies if it came across that way. I honestly went in thinking it was a mistake - a simple misunderstanding. Its a testament to Chukwa that they've engaged in discussing the matter with you promptly and politely, never the less in under 48 hours of starting the discussion you've escalated this to general@ with a fairly negative email. I agree, Eric was prompt and polite. I escalated this for two reasons: 1) It became apparent that it wasn't a misunderstanding - it's a question of policy and it doesn't seem fair to hash that out on their dev list. It wasn't so much escalation as taking policy discussions to the right audience - if there were a mentor@ list, I would have aimed there. 2) This PMC has a release artifact published that was never voted upon. That was news to me and, I felt, worthy of sunlight - especially after the [prompt/polite] defensive reaction received. Sorry for the negativity, it was borne of frustration. It's frustrating to ask podlings to work hard dotting I's and crossing T's only to look around and see other podling's lackadaisical approach. Lets take your LICENSE/NOTICE file issue, you initially said the binary artifact didn't have any, it was then pointed out that in fact it did have them just not where you were looking, you then asserted that is not acceptable and they must only be right at the top directory, it was then pointed out other types of binary distributions like jars also don't have them at the top either, but you have ignored that and instead come here to general@. I guess I viewed that as a frustrating rationalization. Their distro is a standard tarball - where those files are well expected to be in the standard place by both policy and social norm - not some other artifact type where an difference is obvious. Anyway, moving it here was less about that and more about the fact that they released an artifact without voting. Though, since you bring it up I'd appreciate that if there's going to be no accountability for podlings to locate those source files in the right place[1], then yeah, I think we should change the policy to state that anywhere in the artifact is acceptable. I think the only proper places are at the top level for tarballs with the option of the META-INF directory for jars. --tim [1] - http://apache.org/legal/src-headers.html#notice I have no doubt that Chukwa will be happy to help resolve this in whatever way is necessary to satisfy all the ASF policy's, but we don't need a big general@ flame thread to do that. ...ant On Sun, Sep 15, 2013 at 3:46 AM, Tim Williams william...@gmail.com wrote: Moving this[1] to general@ On Sat, Sep 14, 2013 at 2:55 AM, ant elder ant.el...@gmail.com wrote: On Saturday, September 14, 2013, Tim Williams william...@gmail.com wrote: Hi Eric, I've included references inline for your convenience. I'll once again [strongly] suggest you guys remove that artifact. Thanks, --tim On Fri, Sep 13, 2013 at 6:53 PM, Eric Yang eric...@gmail.com wrote: Hi Tim, There is LICENSE.txt and NOTICES.txt in both source and binary package. In the binary package, the files are located in $PREFIX/share/doc/chukwa to match what standard Linux file system layout. We voted for source release
Re: Retirement decision making
+1 on active PMC duties would be fine to ensure continuation of the project. regards, Eric On Fri, Nov 30, 2012 at 1:27 AM, Ross Gardler rgard...@opendirective.comwrote: On 30 November 2012 00:52, Benson Margulies bimargul...@gmail.com wrote: Hard cases make bad law. The rough parameters of the recent 'small graduates' was that they had around 5 initial PMC members, and some detectable evidence that all of them were in the reasonably regular habit of contributing code, let alone voting for releases. If we insist on testing the absolute lower limit of viability, we're may bump into the absurd. +1 (where reasonably regular habit of contributing code should be reasonably regular habit of contributing in some way - that is only being active in PMC duties would be fine, need not be active committer, as long as it is responsible activity (i.e. voting from an informed position) Ross On Thu, Nov 29, 2012 at 4:45 PM, Andy Seaborne a...@apache.org wrote: On 29/11/12 14:53, Bertrand Delacretaz wrote: On Thu, Nov 29, 2012 at 3:18 PM, Alan Cabrera l...@toolazydogs.com wrote: ... Would you also add the three or more active PMC members requirement? What constitutes active?... IMO the bare minimum is being able to find three PMC members to vote on things when needed. Once a project gets below this limit it's in trouble and usually headed for the attic, but that's not the only possibility - see Resolution to reboot the Apache Xalan PMC at http://www.apache.org/foundation/records/minutes/2011/board_minutes_2011_07_20.txt for example. I think we need to be a bit careful about graduating a podling that is a minimum viable project. That's not say it shouldn't be done but if it's minimal, and looks ropey, then we're aren't doing us or them any favours if the project looks likely to get into problems quite soon. After all, graduation itself requires project resource. Andy -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com
Re: [DISCUSSION] Retire Chukwa from incubation
Hi Alexei, Chukwa started before Flume and Kafka started. Flume community has flourish with Cloudera behind it. In my experience Flume has been more fluid, and Chukwa has been more solid. Chukwa can't swim in flume 1.2 branch because flume is becoming more like Chukwa. Unfortunately, most of Chukwa community don't get used to Flume syntax and centralized configuration via ZooKeeper. Kafka is a much younger project in comparison to Chukwa or Flume. I don't know much about scala but providing solid scalable Java API on scala seems like a project of it's own right that neither Kafka nor Chukwa community would be interested. Chris has done the research in Apache, and did not find any possible projects that would be a good fit to shelter Chukwa. regards, Eric On Wed, Nov 28, 2012 at 5:46 AM, Alexei Fedotov alexei.fedo...@gmail.comwrote: Let me rephrase the question. Could the actual reason behind Chukwa retirement be related to the fact, that there exist Flume and Kafka which gives users same opportunites to manage distributed systems? I better understand this before trying to spread the word about joinging Chukwa community. If this is the case, could it be that there are ways to mergre projects somehow, e.g. provide Chukwa API on the top of Flume or Kafka? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Tue, Nov 27, 2012 at 6:23 PM, Alexei Fedotov alexei.fedo...@gmail.com wrote: Hello guys, I want to understand Chukwa community building strategy better. Are there any insights why companies which use Hadoop (in Moscow those include Deutche Bank, Yandex, Rambler and Microsoft) do not crowd around or stay in line to get a chance to use Chukwa? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Tue, Nov 27, 2012 at 3:55 PM, ant elder ant.el...@gmail.com wrote: On Tue, Nov 27, 2012 at 11:48 AM, Benson Margulies bimargul...@gmail.comwrote: One interesting point about consensus decision-making process is the need to define the starting point. The process assumes that there is a clear 'status quo', and that a consensus is required to change it. This may not always be the appropriate way to think about retiring a podling, but it's clearly the way we're thinking about this one. Does anyone else feel that this could have benefitted from a [DISCUSS] before the [VOTE]. At the bottom line, if there are new mentors to be fully responsible, I think it's reasonable to continue; however, I don't want to have exactly the same conversation in N months. Would the new mentors like to propose a time limit, and is the group willing to subscribe to the notion that, if after that time, the new mentors have the same report as the old mentors, we're at the end? Could we maybe include a time limit next month with the credible plan to give new mentors a little time to get up to speed with the project? ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: What constitute a successful project?
Apache is a non-profit organization. If we restrict our thinking model to metrics of how many developers, and how many patches are committed in pre-defeined time limit. There is no software that is gong to succeed in this evaluation other than commercial software. Paid developers are contributing to the software that meeting cooperate interests at rapid pace, and smaller companies will work together until cooperate interests tear apart the software, or the funding eventually dry up and the software cease to exist, and the community will eventually fall apart. Good software usually comes down to a few individuals who work hard to enable the community to flourish. Many of the good software takes decades to develop from hobby projects. I will accept the voting result from IPMC, and I wish IPMC would use better human sense to enable future project to flourish. Chris Douglas resigned from mentor position, therefore, Chukwa will need a new mentor, and one of Chukwa contributor Sourygna Luangsay volunteer to be the motivator for Chukwa development if Chukwa is voted to stay for another 6 months. regards, Eric On Mon, Nov 26, 2012 at 10:20 PM, Bernd Fondermann bernd.fonderm...@gmail.com wrote: On Tue, Nov 27, 2012 at 1:25 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Mon, Nov 26, 2012 at 10:53 PM, Alan Cabrera l...@toolazydogs.com wrote: As I mentioned in an earlier email, we did have this conversation seven months ago. We came to a consensus to give it another try. We even added a few committers a bit early with the hopes that they would infuse the project with more energy. That doesn't take away the fact that there are still people who are clearly interested in continuing work on the project. Instead of telling the community to pick up their toys and leave, I'd much rather ask them to come up with a credible alternative. The failure of past attempts to grow the community does not necessarily mean that future attempts will also fail, so I'd give the community the benefit of doubt as long as there are new ideas and people willing to try them. If I understand correctly the problems in Chukwa are two-fold: 1) the community isn't diverse, i.e. there are only few people involved, and 2) the community isn't active, in that even the involved people don't have too many cycles to spend on the project. Thus I'd raise the following questions to Eric and others who want to keep Chukwa alive at the ASF: a) Is it reasonable to expect existing community members to become more active in near future? If yes, will such increased activity be sustainable over a longer period of time? Why? IIUC there was some recent legal progress that might help here. What would be the best way to measure the expected increase in activity? b) How do you expect to get more people involved in the project? What concrete actions will be taken to increase the chances of new contributors showing up? Why do you believe these things will work better than the mentioned earlier attempts at growing the community? Good ideas of concrete actions are for example cutting new releases, improving project documentation, presenting the project at various venues, simplifying the project build and initial setup, and giving more timely answers and feedback to new users and contributors (see also my observation from October [1]). How can we best tell whether such efforts are working? Coming up with good answers to such questions is not necessarily easy (and it's fine if not all of them can yet be answered), but going through that effort should give us a good reason to continue the incubation of Chukwa at least for a few more months until we should start seeing some concrete and sustainable improvements in community activity and diversity. This is exactly what we did for the last months (years, actually). Give it yet more time. Honestly, I don't understand why we should continue in this mode for another few months when it failed for the past years. Is this the extra-bonus IPMC time? The legal issues only made it more clear to me that and why this Incubation failed. The much I'd love to see Chukwa fly, this is getting ridiculous. Bernd - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: What constitute a successful project?
Hi Alan, In Wink, you voted +1, and in Chukwa, you voted -1. While the status are similar between Chukwa and Wink, but what is the logic behind your votes? In addition, Chukwa and Kafka are similar, and some Kafka design are borrowed from Chukwa. Does your relationship with Kafka influence your judgement being bias toward Chukwa? You called me a lone developer, while the jira list showed there are several others contributing as well. There are people submitting patches and open jira for discussions. You volunteered to work as mentor for Chukwa, but we only hear from you 4 times while being Chukwa mentor: 1. March 23, we welcome you to become Chukwa mentor. On the same day, you ask Chukwa to be retired. 2. June Report, Chris reviewed report, you gave a +1. 3. September 9, you said thank you to Bernd for follow up on granting new committers access. 4. Nov 16, you start on the private list on the same thread about retiring Chukwa. I am sorry, but I may be blunt. I think your action is harmful to Chukwa community rather than helping the community. In the Chukwa private mailing list, I also expressed my limitation to be contributing to Chukwa while I am working through logistics with my employer to get approval. While I did not write new code for Chukwa for the past half year, Chukwa continue to receive patches from the following individuals: Noel Duffy Jie Huang Sourygna Luangsay Abhijit Dhar Saisai Shao Ivy Tang Prakhar Srivastava Eric Speck Some patches are committed by Ari Rabkin. Contributions after 0.5 release can be tracked in CHANGES.txt. Chukwa is truly running as an open Apache project where patches are reviewed and discussed. Chukwa is used by Netflix, IBM, Intel, and several companies. If you search on LinkedIn, number of people that has Chukwa on their resume grown from 30 people in January to 55 now. The information are the same information that I provided on chukwa-private mailing list. Here is the quote from Chris: Eric, you recommend graduating Chukwa to be a TLP based on its activity relative to other incubator projects, engagement from independent contributors, adoption and investment in commercial offerings, and indirect measures of a growing interest in the project. Is that a fair summary? While Chukwa community is low key on participate political votes because the same rehash of closing the community has been on the focus since the original incubation proposal was written. If we are going to move forward, more time in incubation is not a realistic option. The only way is vote for graduation and avoid the vicious cycle of closing the project review. regards, Eric On Tue, Nov 27, 2012 at 7:32 AM, Alan Cabrera l...@toolazydogs.com wrote: On Nov 27, 2012, at 7:16 AM, ant elder wrote: Unless there are compelling reason to stop, i.e continuing breaches of basic ASF polices and principles, then where possible letting a poddling continue incubation or just graduate seems better to me than making them go elsewhere. Its not like a small slow problem is chewing up ASF resources, but i understand not everyone here agrees with my views on that. Wink is an example of poddling in similar circumstances and there we are about to have decided that graduation is better than retirement. Perhaps thats a better approach. I don't recall a graduation recommendation request from the Incubator has ever been rejected by the board so perhaps the Incubator is too conservative with graduation recommendations. Its interesting comparing Wink and Chukwa. From many perspectives Chukwa is much more active than Wink but we're about to graduate Wink and talking about retiring this one. I've not yet had a chance to go through all the Chukwa archives but unless i'm misunderstanding something Chukwa isn't just a lone coder, there have been several committers in the last months and while one is doing the majority of the commits many of those are actually applying patches from other people, so it looks like there are a bunch of people out there working on the project and we need to find ways of better integrating them into the poddling community. This is an interesting line of reasoning worth pursuing, IMO. If Chukwa and Wink are actually on a par with each other we should see if it make sense to apply the same reasoning about Wink to Chukwa. Are we implicitly having a policy change with podlings, if so, should we make it explicit? Regards, Alan
Re: What constitute a successful project?
Hi Suresh, Anymore time spend in incubator is not productive. Developers would feel threaten by the fact that the project is coming to the end and stop contributing. I think the only way forward is to vote for graduation or setup shop on github. IPMC can make good decisions when they are well informed, and collective wisdom can decide the proper votes base on facts. This will save IPMC and Chukwa PMC time and energy to make best possible decisions for Chukwa community and let Chukwa community focus on the goal of it's charter. regards, Eric On Tue, Nov 27, 2012 at 4:36 AM, Suresh Marru sma...@apache.org wrote: On Nov 27, 2012, at 3:08 AM, Eric Yang eric...@gmail.com wrote: Apache is a non-profit organization. If we restrict our thinking model to metrics of how many developers, and how many patches are committed in pre-defeined time limit. There is no software that is gong to succeed in this evaluation other than commercial software. Paid developers are contributing to the software that meeting cooperate interests at rapid pace, and smaller companies will work together until cooperate interests tear apart the software, or the funding eventually dry up and the software cease to exist, and the community will eventually fall apart. Good software usually comes down to a few individuals who work hard to enable the community to flourish. Many of the good software takes decades to develop from hobby projects. I will accept the voting result from IPMC, and I wish IPMC would use better human sense to enable future project to flourish. Hi Eric, Its good to see Jukka and Ant stepping up as mentors, may be that will give you Chukwa one more chance. From browsing through the private list and the general list, I see lots of philosophical arguments and how you will bring in your patches now that legal review at your employer is over. Ofcourse you mention new volunteers too. But so far I haven't seen an answer from you or other Chukwa PPMC what have you done previously to grow the community, what did not work and what is the change in plan now? I see multiple variants of this question has been asked quite a few times in the last couple of days and I am eager to see an answer from the Chukwa PPMC. Suresh Chris Douglas resigned from mentor position, therefore, Chukwa will need a new mentor, and one of Chukwa contributor Sourygna Luangsay volunteer to be the motivator for Chukwa development if Chukwa is voted to stay for another 6 months. regards, Eric On Mon, Nov 26, 2012 at 10:20 PM, Bernd Fondermann bernd.fonderm...@gmail.com wrote: On Tue, Nov 27, 2012 at 1:25 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Mon, Nov 26, 2012 at 10:53 PM, Alan Cabrera l...@toolazydogs.com wrote: As I mentioned in an earlier email, we did have this conversation seven months ago. We came to a consensus to give it another try. We even added a few committers a bit early with the hopes that they would infuse the project with more energy. That doesn't take away the fact that there are still people who are clearly interested in continuing work on the project. Instead of telling the community to pick up their toys and leave, I'd much rather ask them to come up with a credible alternative. The failure of past attempts to grow the community does not necessarily mean that future attempts will also fail, so I'd give the community the benefit of doubt as long as there are new ideas and people willing to try them. If I understand correctly the problems in Chukwa are two-fold: 1) the community isn't diverse, i.e. there are only few people involved, and 2) the community isn't active, in that even the involved people don't have too many cycles to spend on the project. Thus I'd raise the following questions to Eric and others who want to keep Chukwa alive at the ASF: a) Is it reasonable to expect existing community members to become more active in near future? If yes, will such increased activity be sustainable over a longer period of time? Why? IIUC there was some recent legal progress that might help here. What would be the best way to measure the expected increase in activity? b) How do you expect to get more people involved in the project? What concrete actions will be taken to increase the chances of new contributors showing up? Why do you believe these things will work better than the mentioned earlier attempts at growing the community? Good ideas of concrete actions are for example cutting new releases, improving project documentation, presenting the project at various venues, simplifying the project build and initial setup, and giving more timely answers and feedback to new users and contributors (see also my observation from October [1]). How can we best tell whether such efforts are working? Coming up with good answers to such questions is not necessarily
Re: What constitute a successful project?
Continue the retirement vote, and see if it passes in IPMC. If it does, I will gladly setup shop in github. If it doesn't, Chukwa community should prepare for Chukwa 0.6.0 release, and start voting on Chukwa 0.6.0 release, and follow by vote for graduation. Content in Chukwa trunk contains a number of good features and fixes generated by the community. I really appreciate the support by Incubator community to make this possible. Does this sound like a plan? regards, Eric On Tue, Nov 27, 2012 at 10:00 PM, Alan Cabrera l...@toolazydogs.com wrote: On Nov 27, 2012, at 9:41 PM, Eric Yang wrote: snip/ The various comparisons are distractions. Let's focus on Chukwa and what can be done. If we are going to move forward, more time in incubation is not a realistic option. The only way is vote for graduation and avoid the vicious cycle of closing the project review. If there's an Incubator policy change that I don't know about I'm happy to hear it and reconsider my personal opinion. If someone wants to change Incubator policy I'm happy to discuss it. Can you not see by my message below that I am not intransigent but am willing to discuss all manner of things? I would focus more on the Chukwa project and not spend so much time on comparing it to other projects nor making ugly innuendoes. Look around you. You are surrounded by a community who wants to help. Regards, Alan On Tue, Nov 27, 2012 at 7:32 AM, Alan Cabrera l...@toolazydogs.com wrote: On Nov 27, 2012, at 7:16 AM, ant elder wrote: Unless there are compelling reason to stop, i.e continuing breaches of basic ASF polices and principles, then where possible letting a poddling continue incubation or just graduate seems better to me than making them go elsewhere. Its not like a small slow problem is chewing up ASF resources, but i understand not everyone here agrees with my views on that. Wink is an example of poddling in similar circumstances and there we are about to have decided that graduation is better than retirement. Perhaps thats a better approach. I don't recall a graduation recommendation request from the Incubator has ever been rejected by the board so perhaps the Incubator is too conservative with graduation recommendations. Its interesting comparing Wink and Chukwa. From many perspectives Chukwa is much more active than Wink but we're about to graduate Wink and talking about retiring this one. I've not yet had a chance to go through all the Chukwa archives but unless i'm misunderstanding something Chukwa isn't just a lone coder, there have been several committers in the last months and while one is doing the majority of the commits many of those are actually applying patches from other people, so it looks like there are a bunch of people out there working on the project and we need to find ways of better integrating them into the poddling community. This is an interesting line of reasoning worth pursuing, IMO. If Chukwa and Wink are actually on a par with each other we should see if it make sense to apply the same reasoning about Wink to Chukwa. Are we implicitly having a policy change with podlings, if so, should we make it explicit? Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Chukwa status (Was: [Incubator Wiki] Update of April2012 by EricYang)
Hi Jukka, Chukwa has been used in various organization. For Chukwa 0.5.0 release, the majority of code has been contributed from single individual. There are questions raised that there should be more diversity of the contribution from the community from mentors. There are increased activities on user mailing list in the past month, but momentum and traction is still a concern. I plan to update the report per Bernd's recommendation. regards, Eric On Sat, Mar 31, 2012 at 1:46 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, Thanks for the early report, Chukwa! On Thu, Mar 29, 2012 at 6:07 AM, Apache Wiki wikidi...@apache.org wrote: + Chukwa is an open source data collection system for monitoring large distributed systems. Chukwa is built on top of the Hadoop Distributed File System (HDFS), HBase and Map/Reduce framework and inherits Hadoop’s scalability and robustness. Chukwa also includes a flexible and powerful toolkit for displaying, monitoring and analyzing results to make the best use of the collected data. I think the first sentence would be enough context for the report. Please also include a note of when Chukwa entered incubation. + - Chukwa 0.5.0 has been released + - New committer Ahmed Fathalla has been voted in and granted proper krama + - Mentor William A. Rowe Jr resigned + - Alan D. Cabrera volunteer to become new mentor Sounds good. What's your status regarding graduation, most notably in terms of community activity and diversity? BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: subversion committer access for podding project
Thanks Craig. :) regards, Eric On Tue, Feb 7, 2012 at 11:44 PM, Craig L Russell craig.russ...@oracle.com wrote: Hi Eric, This request was completed on January 20 based on your request. Craig On Feb 7, 2012, at 9:59 PM, Eric Yang wrote: Hi Richard, The result thread was sent to private@incubator.a.o on Jan 17. I am not sure how to reference to private mailing thread, but I will send you a copy. Thank you for your help. regards, Eric On Tue, Feb 7, 2012 at 1:26 PM, Richard Frovarp rfrov...@apache.org wrote: On 02/07/2012 03:19 PM, Eric Yang wrote: Hi ipmc, Chukwa community has recently voted in a new committer. ICLA has been filed for the user, and the user has received unix account on people.a.o. However, none of Chukwa mentor or ppmc have krama to grant subversion access to the new committer. INFRA says it is responsibility of pmc chair to grant access. How should we proceed from here? Thanks regards, Eric Any PMC chair can grant access, and there are many on this list (including myself). However, we're going to need the result thread from the IPMC vote, and the user name before we make the change. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Secretary, Apache Software Foundation c...@apache.org http://db.apache.org/jdo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: subversion committer access for podding project
Hi Richard, The result thread was sent to private@incubator.a.o on Jan 17. I am not sure how to reference to private mailing thread, but I will send you a copy. Thank you for your help. regards, Eric On Tue, Feb 7, 2012 at 1:26 PM, Richard Frovarp rfrov...@apache.org wrote: On 02/07/2012 03:19 PM, Eric Yang wrote: Hi ipmc, Chukwa community has recently voted in a new committer. ICLA has been filed for the user, and the user has received unix account on people.a.o. However, none of Chukwa mentor or ppmc have krama to grant subversion access to the new committer. INFRA says it is responsibility of pmc chair to grant access. How should we proceed from here? Thanks regards, Eric Any PMC chair can grant access, and there are many on this list (including myself). However, we're going to need the result thread from the IPMC vote, and the user name before we make the change. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Chukwa 0.5.0 Release Candidate 3
Mentor could lose interests in a project over time due to various kind of reasons. Perhaps, It is time to deconstruct mentor idea and promote ppmc to ipmc after making incubating release(s) and only allow incubator project to graduate after promoted ppmc has mentored another project to make incubator release. This will enable promoted ppmc to execrise what has been learn and apply to other projects. Promoted ppmc can choose to stay as ipmc or resign ipmc after project graduation. The only drawback is someone on ipmc would need to promote ppmc regularly. It is more work for infrastructure to add and remove people from ipmc. Sent from my iPhone On Jan 26, 2012, at 6:46 PM, Ralph Goers ralph.go...@dslextreme.com wrote: On Jan 26, 2012, at 4:38 PM, Marvin Humphrey wrote: On Thu, Jan 26, 2012 at 06:57:08AM -0500, Ralph Goers wrote: This podling has 4 mentors listed. Only 1 voted on the release. Situations like this seem to be common. My worry isn't about the PPMC or committers but about whether this podling has sufficient mentors. Perhaps the podling has an especially conscientious PPMC member or two who should be evaluated for IPMC membership, as discussed recently? http://s.apache.org/Y4B Mind you, I don't follow chuckwa-dev so perhaps my perception is incorrect, but a podling should normally be able to get 3 IPMC votes just from its mentors. If we can't scare up enough IPMC votes for a release, why not get them from people who are... * familiar with the podling's ongoing development * going to be entrusted with binding votes the instant the project graduates ... as soon as they demonstrate proper diligence and understanding of ASF procedures? i'd agree, but this was the podling's first release. The point have having mentors is to get them up to speed. Ralph - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Chukwa 0.5.0 Release Candidate 3
The voting period is now closed. Thanks to everyone who took the time to review the release. Result Summary for this List: +1 [1] 0[1] -1[0] With the one IPMC member vote from mentors on the dev list and two +1 from general@incubator, the vote succeeds. IPMC member voting record: Chris Douglas:+1 Ralph Goers: +1 Ant Elder: +1 regards, Eric On Mon, Jan 23, 2012 at 12:55 AM, ant elder ant.el...@gmail.com wrote: +1 Same comment on the NOTICE file as over here: http://apache.markmail.org/message/hlfebouyg3r5w27i ...ant On Fri, Jan 20, 2012 at 6:46 AM, Eric Yang eric...@gmail.com wrote: Still missing one IPMC vote. Could someone help out? regards, Eric On Tue, Jan 17, 2012 at 12:06 PM, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 1/15/2012 1:42 AM, Ralph Goers wrote: You know, you have 4 mentors all of whom are supposed to be IPMC members. Have they voted? Nope, traveling, and now back in project hell at one of my own homes. I did review the Chukwa monthly report and comment on several apparent issues on dev@. I don't expect to have time to review this specific candidate, owing to a backlog of work accumulated over this short vacation. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Chukwa 0.5.0 Release Candidate 3
My apology to all. I am sorry to send out the draft copy when I intented to save as draft to count the actual votes. Result Summary for voting Chukwa 0.5.0 RC 3 +1 [9] 0 [0] -1 [0] IPMC: +1 Chris Douglas +1 Ralph Goers +1 Ant Elder PPMC: +1 Bill Graham +1 Jerome Boulon +1 Ari Rabkin +1 Eric Yang Committer: +1 Ahmed Fathalla Contributor +1 Mohammad Tariq The vote is now closed. Thanks to everyone who took the time to review the release. regards, Eric On Wed, Jan 25, 2012 at 10:04 PM, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 1/25/2012 11:49 PM, Eric Yang wrote: The voting period is now closed. Thanks to everyone who took the time to review the release. Result Summary for this List: +1 [1] 0 [1] -1 [0] With the one IPMC member vote from mentors on the dev list and two +1 from general@incubator, the vote succeeds. IPMC member voting record: Chris Douglas: +1 Ralph Goers: +1 Ant Elder: +1 I am very confused by your tally above. you cite [1] in brackets and there are three votes +1 between PPMC and IPMC. I'm very worried that, sans mentors, this PPMC can't muster three votes for a candidate. I think it might be premature to release and is a very long way from graduation. Please don't summarize simply IPMC binding votes, but cover all categories, most especially chukwa-dev community votes. Repost with the correct totals, because we [Incubator PMC] need that to gauge the health of the project. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Chukwa 0.5.0 Release Candidate 3
Still missing one IPMC vote. Could someone help out? regards, Eric On Tue, Jan 17, 2012 at 12:06 PM, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 1/15/2012 1:42 AM, Ralph Goers wrote: You know, you have 4 mentors all of whom are supposed to be IPMC members. Have they voted? Nope, traveling, and now back in project hell at one of my own homes. I did review the Chukwa monthly report and comment on several apparent issues on dev@. I don't expect to have time to review this specific candidate, owing to a backlog of work accumulated over this short vacation. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Chukwa 0.5.0 Release Candidate 3
This is a reminder to vote Chukwa 0.5.0 release candidate 3. We are still missing 2 IPMC votes to close this vote. If someone could take a look, it would be greatly appreciated. regards, Eric On Wed, Jan 11, 2012 at 12:55 PM, Chris Douglas cdoug...@apache.org wrote: +1 (binding) Checksum and signature match, verifications from previous RCs hold b/c only NOTICE and LICENSE have changed. -C On Mon, Jan 9, 2012 at 10:09 PM, Eric Yang eric...@gmail.com wrote: Hi all, Chukwa 0.5.0 is ready for release. This will be the first incubator release for Chukwa. The source tarball artifact is available at: http://people.apache.org/~eyang/chukwa-0.5.0-rc3/ Documents are available at: http://people.apache.org/~eyang/chukwa-0.5.0-docs/ The SVN tag to be voted upon: https://svn.apache.org/repos/asf/incubator/chukwa/tags/chukwa-0.5.0-rc3/ Chukwa's KEYS file containing PGP keys we use to sign the release: http://people.apache.org/~eyang/chukwa-0.5.0-rc3/KEYS Please download, evaluate, and vote on general@incubator. The PPMC vote thread is in progress at the same time as general@incubator. Changes since rc2: - Updated LICENSE and NOTICE files to reflect changes base on Sebb's examples. The vote will close at 12:30pm PST on Saturday January 14, 2012. Thanks regards, Eric - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Chukwa 0.5.0 Release Candidate 3
+1 On Tue, Jan 10, 2012 at 5:07 AM, sebb seb...@gmail.com wrote: On 10 January 2012 06:09, Eric Yang eric...@gmail.com wrote: Hi all, Chukwa 0.5.0 is ready for release. This will be the first incubator release for Chukwa. The source tarball artifact is available at: http://people.apache.org/~eyang/chukwa-0.5.0-rc3/ Documents are available at: http://people.apache.org/~eyang/chukwa-0.5.0-docs/ The SVN tag to be voted upon: https://svn.apache.org/repos/asf/incubator/chukwa/tags/chukwa-0.5.0-rc3/ NL files look OK to me now; thanks for fixing them. Chukwa's KEYS file containing PGP keys we use to sign the release: http://people.apache.org/~eyang/chukwa-0.5.0-rc3/KEYS Please download, evaluate, and vote on general@incubator. The PPMC vote thread is in progress at the same time as general@incubator. Changes since rc2: - Updated LICENSE and NOTICE files to reflect changes base on Sebb's examples. The vote will close at 12:30pm PST on Saturday January 14, 2012. Thanks regards, Eric - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Chukwa 0.5.0 release candidate 1
On Fri, Jan 6, 2012 at 3:04 PM, sebb seb...@gmail.com wrote: There are quite a few files without any licenses at all, e.g. conf/aggregator.sql conf/database_create_tables.sql src/main/web/hicc/css/default.css The NOTICE file should only contain *required* notices. In particular, the following paragraph is not required: Chukwa incorporates a number of components, not copyright by the Apache Foundation, and under permissive licenses. The YUI license appears to require a notice, but there is none. There are probably other issues; did not check them all. The LICENSE file contains quite a few non-ASCII characters that don't display properly. There's no point repeating AL 2.0 for the components that use it; just state which components use the AL 2.0. Thanks for the audit. I have fixed the errors over the weekend and will start rc 2 vote shortly. regards, Eric - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Chukwa 0.5.0 release candidate 2
Hi all, Chukwa 0.5.0 is ready for release. This will be the first incubator release for Chukwa. The source tarball artifact is available at: http://people.apache.org/~eyang/chukwa-0.5.0-rc2/ Documents are available at: http://people.apache.org/~eyang/chukwa-0.5.0-docs/ The SVN tag to be voted upon: https://svn.apache.org/repos/asf/incubator/chukwa/tags/chukwa-0.5.0-rc2/ Chukwa's KEYS file containing PGP keys we use to sign the release: http://people.apache.org/~eyang/chukwa-0.5.0-rc2/KEYS Please download, evaluate, and vote on general@incubator. The PPMC vote thread is in progress at the same time as general@incubator. Changes since rc1: - Updated LICENSE and NOTICE files to reflect changes base on ipmc feedback. - Updated Hadoop dependency to Hadoop 1.0.0. The vote will close at 12:30pm PST on Thursday January 12, 2012. Thanks regards, Eric - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Chukwa 0.5.0 release candidate 2
Thank you for the multiple examples. I think I finally understand what you are saying, and the information on LEGAL-59, and LEGAL-62. I will re-spin rc3 with a new svn tag with required changes in NOTICE file. Thanks regards, Eric On Mon, Jan 9, 2012 at 5:33 PM, sebb seb...@gmail.com wrote: On 9 January 2012 19:40, Eric Yang eric...@gmail.com wrote: Hi all, Chukwa 0.5.0 is ready for release. This will be the first incubator release for Chukwa. The source tarball artifact is available at: http://people.apache.org/~eyang/chukwa-0.5.0-rc2/ Documents are available at: http://people.apache.org/~eyang/chukwa-0.5.0-docs/ The SVN tag to be voted upon: https://svn.apache.org/repos/asf/incubator/chukwa/tags/chukwa-0.5.0-rc2/ The Script.aculo.us license has the following copyright notice: Copyright (c) 2005-2008 Thomas Fuchs (http://script.aculo.us, http://mir.aculo.us) However, this does not appear in NOTICE.txt. I would expect to see something like the following 2 lines in NOTICE.txt: This product includes Script.aculo.us Copyright (c) 2005-2008 Thomas Fuchs (http://script.aculo.us, http://mir.aculo.us) Similarly for any other included products that have a notice requirement, i.e. This product includes YUI Copyright Yahoo inc, 2009 This product includes IUI Copyright (c) 2007-2009, iUI Project Members etc. for any other included products that have a notice requirement. The entries in the NOTICE file need to be the minimum required. Chukwa's KEYS file containing PGP keys we use to sign the release: http://people.apache.org/~eyang/chukwa-0.5.0-rc2/KEYS Please download, evaluate, and vote on general@incubator. The PPMC vote thread is in progress at the same time as general@incubator. Changes since rc1: - Updated LICENSE and NOTICE files to reflect changes base on ipmc feedback. - Updated Hadoop dependency to Hadoop 1.0.0. The vote will close at 12:30pm PST on Thursday January 12, 2012. Thanks regards, Eric - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Chukwa 0.5.0 Release Candidate 3
Hi all, Chukwa 0.5.0 is ready for release. This will be the first incubator release for Chukwa. The source tarball artifact is available at: http://people.apache.org/~eyang/chukwa-0.5.0-rc3/ Documents are available at: http://people.apache.org/~eyang/chukwa-0.5.0-docs/ The SVN tag to be voted upon: https://svn.apache.org/repos/asf/incubator/chukwa/tags/chukwa-0.5.0-rc3/ Chukwa's KEYS file containing PGP keys we use to sign the release: http://people.apache.org/~eyang/chukwa-0.5.0-rc3/KEYS Please download, evaluate, and vote on general@incubator. The PPMC vote thread is in progress at the same time as general@incubator. Changes since rc2: - Updated LICENSE and NOTICE files to reflect changes base on Sebb's examples. The vote will close at 12:30pm PST on Saturday January 14, 2012. Thanks regards, Eric - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Chukwa 0.5.0 release candidate 1
Hi all, Chukwa 0.5.0 is ready for release. This will be the first incubator release for Chukwa. The source tarball artifact is available at: http://people.apache.org/~eyang/chukwa-0.5.0-rc1/ Documents are available at: http://people.apache.org/~eyang/chukwa-0.5.0-docs/ The SVN tag to be voted upon: https://svn.apache.org/repos/asf/incubator/chukwa/tags/chukwa-0.5.0-rc1/ Chukwa's KEYS file containing PGP keys we use to sign the release: http://people.apache.org/~eyang/chukwa-0.5.0-rc0/KEYS Please download, evaluate, and vote on general@incubator. The same artifacts have been tested and voted on chukwa-dev mailing list. The PPMC vote thread is: http://www.mail-archive.com/chukwa-dev@incubator.apache.org/msg00827.html The vote will close at 12:30pm PST on Tuesday January 10, 2012. Thanks regards, Eric - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Chukwa 0.5.0 release candidate 0
Dear IPMC members, Chukwa 0.5.0 is ready for release. The artifacts are available at: http://people.apache.org/~eyang/chukwa-0.5.0-rc0/ Documents are available at: http://people.apache.org/~eyang/chukwa-0.5.0-docs/ The SVN tag to be voted upon: https://svn.apache.org/repos/asf/incubator/chukwa/tags/chukwa-0.5.0-rc0/ Chukwa's KEYS file containing PGP keys we use to sign the release: http://people.apache.org/~eyang/chukwa-0.5.0-rc0/KEYS Please download, evaluate, and vote on general@incubator. The same artifacts have been tested and voted on chukwa-dev mailing list. The PPMC vote thread is: http://www.mail-archive.com/chukwa-dev@incubator.apache.org/msg00814.html The vote will close at 12:30pm PST on Wednesday January 11, 2012. Thanks regards, Eric - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Chukwa 0.5.0 release candidate 0
On Wed, Jan 4, 2012 at 5:55 AM, sebb seb...@gmail.com wrote: The NOTCE and LICENSE files contain several strange characters, which don't render OK. I will correct the UTF8 characters into plain ASCII text in rc1. The NOTICE file also seems to contain references which are not required, e.g. The Prototype AJAX library license does not seem to require a notice. The NOTICE file is for *required* notices only. From: https://issues.apache.org/jira/browse/LEGAL-59, it looks like BSD license do not require additional notice in the NOTICE file. How about MIT license? regards, Eric - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release for Bigtop version 0.1.0-incubating RC2
-1 non-binding, the package generation spec file are currently producing package name without reference to bigtop. The resulting artifacts can potentially overlap with project produced artifacts. regards, Eric On Aug 22, 2011, at 11:07 AM, Andrew Bayer wrote: This is the first incubator release for Apache Bigtop, version 0.1.0-incubating. It fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317549styleName=HtmlprojectId=12311420 *** Please download, test, and vote by Thursday, August 24 (3 working days from now) Note that we are voting on the source (tag). Source tarball, checksums, signature: http://people.apache.org/~abayer/bigtop-0.1.0-incubating-candidate-2/http://people.apache.org/~abayer/bigtop-0.1.0-incubating-candidate-0/ The tag to be voted on: http://svn.apache.org/repos/asf/incubator/bigtop/tags/release-0.1.0-incubating-RC2 (svn rev. 1160352) Bigtop's KEYS file, containing the PGP keys used to sign the release: http://svn.apache.org/repos/asf/incubator/bigtop/dist/KEYS Note that the Incubator PMC needs to vote on the release after a successful PPMC vote before any release can be made official. Thanks! A. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[PROPOSAL] HMS Project for the Apache Incubator
Greetings All, We would like to propose HMS Project for inclusion in ASF Incubator as a new podling. HMS is monitoring, administration and lifecycle management project for Apache Hadoop clusters. The complete proposal can be found at: http://wiki.apache.org/incubator/HMSProposal The initial contents of this proposal are also pasted below for convenience. Thanks and Regards, Eric = HMS Proposal = == Abstract == HMS is monitoring, administration and lifecycle management project for Apache Hadoop clusters. == Proposal == HMS will simplify the process of deployment, configuration, management and monitoring of the collection of Hadoop services and applications that compose a Hadoop cluster. The collection of services (Hadoop Stack) will include at least HDFS, !MapReduce, HBase, Hive, HCatalog, Pig and Zookeeper. HMS will be easily configurable to add additional services and applications to the stack. Our plan is to support the Hadoop stack as a unit of deployment and configuration where only certain pre-tested versions of software components are supported to be part of Hadoop stack. Administrators can always enable/disable the individual software components from the Hadoop stack per their deployment needs. The main use cases that HMS is trying to address are the following: * Hadoop stack deployment and upgrades * Hadoop services configuration management * Administration of Hadoop services * Includes starting and stopping services * Hadoop system maintenance tasks, such as fsck, format, re-balance, and compaction * User access quota management on Hadoop clusters * Easily check and be alerted to failures in Hadoop servers * Automated discovery of new machines that become available * Expanding and contracting Hadoop clusters * Automatic resynchronization to ‘desired’ state (of Hadoop stack) to handle faulty nodes * Handle node burn-ins (stress test nodes using Hadoop before deploying them for production use) * Simple monitoring and management UI * Dynamic configuration - Hadoop configuration deduced from machine attributes (e.g., RAM, CPU, Disk) * Operational HBase-based (inspired by OpenTSDB) monitoring for Hadoop clusters * Make it possible for administrators to deploy other Hadoop related services and client applications HMS is targeted to administrators responsible for managing Hadoop clusters. HMS leverages existing data center management and monitoring infrastructure - Nagios, LDAP, Kerberos, etc. All HMS functionality and data will be accessible via RESTFUL APIs and command line tools to facilitate its integration with existing data center management suites. For the bare metal provisioning, the cluster admins continue to use their existing infrastructure. Provisioning a machine from scratch is not in the scope of the current roadmap. == Background == Hadoop’s ecosystem includes many projects (HDFS, !MapReduce, Pig, HBase, etc.). In many cases, users and operators typically want to deploy a combination of some projects as a stack. It takes a significant amount of time to get a properly configured Hadoop cluster up and running. HMS has been designed to solve that problem. HMS automates the whole process of deploying a stack. HMS is being developed by developers employed with Yahoo!, Hortonworks and IBM. Such a tool would have a large number of users and increase the adoption of Apache Hadoop’s ecosystem. We are therefore proposing to make HMS Apache open source. == Rationale == Hadoop clusters are complicated and difficult to deploy and manage. The HMS project aims to improve the usability of Apache Hadoop. Doing so will demoncratize Apache Hadoop, growing its community and increasing the places Hadoop can be used and the problems it can solve. By developing HMS in Apache we hope to gather a diverse community of contributors, helping to make sure that HMS is deployable in as many different situations as possible. members of the Hadoop development community will be able to influence HMS’s roadmap, and contribute to it. We believe having HMS as part of the Apache Hadoop ecosystem will be a great benefit to all of Hadoop's users. == Current Status == Prototype available, developed by the list of initial committers. === Meritocracy === Our intent with this incubator proposal is to start building a diverse developer community around HMS following the Apache meritocracy model. We have wanted to make the project open source and encourage contributors from multiple organizations from the start. We plan to provide plenty of support to new developers and to quickly recruit those who make solid contributions to committer status. === Community === We are happy to report that multiple organizations are already represented by initial team. We hope to extend the user and developer base further in the future and build a solid open source community around HMS. === Core Developers === HMS is currently being developed by four engineers from Hortonworks - Eric Yang, Owen
[jira] Created: (INCUBATOR-110) Need access to incubator group
Need access to incubator group -- Key: INCUBATOR-110 URL: https://issues.apache.org/jira/browse/INCUBATOR-110 Project: Incubator Issue Type: Wish Components: policy Reporter: Eric Yang Chukwa has been accepted into incubator, but my user account on people is not part of incubator group. I need this to move chukwa website to incubator. Thanks -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[Result][Vote] Move Chukwa to incubator
Original incubator proposal: http://wiki.apache.org/incubator/ChukwaProposal Vote put forward to incubator: 1. recommend TLP with guides to help the initial pmc, 2. accept incubating with tlp resource naming, but -incubating release naming 3. accept incubating requiring all incubator naming conventions, that might help the incubator simplify this decision. Result of the vote: Option 1) Ant Elder, Eric Yang, William A. Rowe Jr. Option 2) Ari Rabkin, Jerome Boulon, Chris Douglas, Greg Reddin Option 3) Bernd Fondermann Owen O'Malley +1 on proposal I am not sure about Chris Mattmann¹s position, but he raised the question about TLP. Is it ok to keep hadoop naming until we graduate to TLP, hence, we only rename once? ³-incubating² will be added to release artifacts. What is next? Regards, Eric - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Move Chukwa to incubator
+1 for 1. Regards, Eric On 6/24/10 12:21 PM, William A. Rowe Jr. wr...@apache.org wrote: On 6/23/2010 8:12 AM, Bernd Fondermann wrote: On Wed, Jun 23, 2010 at 14:45, ant elder ant.el...@gmail.com wrote: IMHO we should insist on using the incubator naming for the Chukwa website/svn/MLs because I think Chukwa should just go directly to a TLP and if they have to use the incubator naming it may help them decide that the direct to TLP route really is better ;-) I see you blinking here, so I guess this is not just for putting up a strawman ;-) Well folks, it's a fun debate and all, but it isn't helping bring this vote to a conclusion :) Is anyone in agreement with ant? Otherwise we should just move ahead and can hold a separate vote on allowing tlp resource creation at this time. If the proposers want (Eric?) a three choice vote, 1. recommend TLP with guides to help the initial pmc, 2. accept incubating with tlp resource naming, but -incubating release naming, or 3. accept incubating requiring all incubator naming conventions, that might help the incubator simplify this decision. At this point, I personally guess that 1. might be the most sensible in terms of resource creation and management; it would simply require the group to vote for an initial chair/VP. If they are unsure of their group yet, perhaps one of the other mentors would offer to serve as their chair for the first six months, if they rather would do that? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Move Chukwa to incubator
Besides DOAP file and the incubator nomenclature, I may need help identify the addition responsibilities for Apache PMC. One problem, Chukwa community did not have a vote for PMC Chair because we are not sure what is the right process for this. Meanwhile, I have been writing quarterly report like any other Apache project, only recipient of the report is different. Chukwa releases have been voted by Chukwa community which is similar to Hadoop releases, and managed incremental changes using patches and committers. Code audit has been performed by the committers to ensure we don't bring in license incompatible libraries into Chukwa. Owen O'Malley had trained us these procedures roughly two years ago, and we have been executing the same process ever since. Chukwa has a community of exist user base of 35 people. It would be nice to make Chukwa a special case to skip incubator nomenclature. This would ease the migration path for the existing Chukwa community. Regards, Eric On 6/22/10 7:11 AM, Greg Reddin gred...@gmail.com wrote: On Tue, Jun 22, 2010 at 3:40 AM, Bernd Fondermann bernd.fonderm...@googlemail.com wrote: IIUC, the only issue right now is that the committers are hesistant to go TLP because they've never been on a PMC before. The current proposal doesn't use the incubator naming for the mailing lists and svn location, from past discussions here it should really be using the incubator naming unless its a very special case. Is this a special case? Good catch. I think the Incubator nomenclature should apply to Chukwa as well. It seems to me that it would save everyone some work if they went straight with the TLP nomenclature. If they only need a short time in the Incubator to learn how to be a PMC, then maybe the Incubator nomenclature is not necessary and just creates more work for infra, PMC, and users when they graduate. Greg - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Move Chukwa to incubator
Please vote as to whether you think Chukwa should move to Apache incubator. The proposal is posted at: http://wiki.apache.org/incubator/ChukwaProposal Thanks Regards, Eric
