Re: Retired podlings not being cleaned up
On Fri, Nov 17, 2023, at 10:44, sebb wrote: > Still no action as far as I can tell. They are not on the website anymore so I guess only a few of the required steps were done. Not sure if I manage this weekend, but if notify else picks it up, I will check > > On Mon, 30 Oct 2023 at 14:53, sebb wrote: >> >> Tuweni and Datalab retired some while ago, but nothing much seems to >> have been done to close them down. >> >> Sebb > > - > 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] Accept ResilientDB Into The Apache Incubator
Hello Mohammad, funny you ask right now, because I just updated some files before you sent your message. Your mentors, including me, will set up the project files. I added yours to the repo. You are visible here already (on the bottom): https://incubator.apache.org/ but the link doesn't work. I am currently trying to see why not. However, the next steps would be our mentors setup up the project and give you access to the resources. As mentioned, I just started with it. Also, later in time, I would like your team and everybody involved to have a (video) chat on slack (or similar) to get some questions clarified that you might have. This is not part of the standard procedure, but I would like to try it. Please let me know if you have further questions. Kind regards, Christian On Mon, Oct 23, 2023, at 23:55, Mohammad Sadoghi wrote: > Dear all, > > What would be our next step after the VOTE Result message? > > Our team is on standby to get the Podling procedure started. > > --- > Best Regards, > Mohammad Sadoghi, PhD > Associate Professor > Exploratory Systems Lab (ExpoLab) > Department of Computer Science > University of California, Davis > > ExpoLab: https://expolab.org/ > ResilientDB: https://resilientdb.com/ > Phone: 914-319-7937 > > > On Sat, Oct 21, 2023 at 7:43 AM Craig Russell wrote: > >> Hi Atri, >> >> > On Oct 21, 2023, at 06:31, Atri Sharma wrote: >> > >> > This vote is now closed with 10 +1s and no opposing votes. >> > >> > The vote has passed. >> >> Please be sure to close the vote with a VOTE RESULT message to the >> incubator. >> >> Warm regards, >> Craig >> > >> > I will start the further procedures now. >> > >> > On Mon, 16 Oct 2023 at 3:40 PM, Atri Sharma wrote: >> > >> >> Following up the [DISCUSS] thread on ResilientDB, I would like to call >> a >> >> VOTE to accept into the Apache Incubator. >> >> >> >> Please cast your vote: >> >> >> >> [ ] +1, bring into the Incubator >> >> [ ] +0, I don't care either way >> >> [ ] -1, do not bring ResilientDB into the Incubator, because... >> >> >> >> The vote will open at least for 72 hours and only votes from the >> >> Incubator PMC are binding, but votes from everyone are welcome. >> >> >> >> Please check out the ResilientDB Proposal from the incubator wiki[1]. >> >> >> >> [1] >> >> >> https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal >> >> >> >> Regards, >> >> >> >> Atri >> >> >> >> Craig L Russell >> c...@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] Accept ResilientDB Into The Apache Incubator
I think it’s safe to close the vote, if you find the time On Mon, Oct 16, 2023, at 12:10, Atri Sharma wrote: > Following up the [DISCUSS] thread on ResilientDB, I would like to call a > VOTE to accept into the Apache Incubator. > > Please cast your vote: > > [ ] +1, bring into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring ResilientDB into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > Please check out the ResilientDB Proposal from the incubator wiki[1]. > > [1]https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > Regards, > > Atri > > - > 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] Accept ResilientDB Into The Apache Incubator
-- Grobmeier Solutions GmbH https://grobmeier.solutions https://www.timeandbill.de On Mon, Oct 16, 2023, at 12:10, Atri Sharma wrote: > Following up the [DISCUSS] thread on ResilientDB, I would like to call a > VOTE to accept into the Apache Incubator. > > Please cast your vote: > > [ ] +1, bring into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring ResilientDB into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > Please check out the ResilientDB Proposal from the incubator wiki[1]. > > [1]https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > Regards, > > Atri > > - > 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] Accept ResilientDB Into The Apache Incubator
+1 (binding) On Mon, Oct 16, 2023, at 12:10, Atri Sharma wrote: > Following up the [DISCUSS] thread on ResilientDB, I would like to call a > VOTE to accept into the Apache Incubator. > > Please cast your vote: > > [ ] +1, bring into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring ResilientDB into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > Please check out the ResilientDB Proposal from the incubator wiki[1]. > > [1]https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > Regards, > > Atri > > - > 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: [DISCUSS] Incubating Proposal of ResilientDB
Hello, I removed the "broader contributing members" as suggested: https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal Let's move ahead with the [vote] thread. Kind regards, Christian On Sat, Oct 14, 2023, at 12:37, Christian Grobmeier wrote: > On Fri, Oct 13, 2023, at 20:22, Atri Sharma wrote: >> Unfortunately , I am locked out of my Apache account. While I reset that, I >> would request one of the mentors to make the changes. >> >> Post that, I will start the vote thread > > If not another mentor is faster than me, I am going to look at it later today > >> >> On Fri, 13 Oct 2023 at 10:47 PM, Mohammad Sadoghi >> wrote: >> >>> Dear all, >>> >>> Could we move the [VOTE] phase after removing the broad contributors (as it >>> was suggested)? >>> >>> The last [Discuss] thread was sent 10 days ago with +8(binding). >>> >>> --- >>> Best Regards, >>> Mohammad Sadoghi, PhD >>> Associate Professor >>> Exploratory Systems Lab (ExpoLab) >>> Department of Computer Science >>> University of California, Davis >>> >>> ExpoLab: https://expolab.org/ >>> ResilientDB: https://resilientdb.com/ >>> Phone: 914-319-7937 >>> >>> >>> On Thu, Oct 12, 2023 at 12:03 AM Mohammad Sadoghi >>> wrote: >>> >>> > Sure, please remove them [I do not have write access to the wiki]. Thank >>> > you kindly. >>> > >>> > --- >>> > Best Regards, >>> > Mohammad Sadoghi, PhD >>> > Associate Professor >>> > Exploratory Systems Lab (ExpoLab) >>> > Department of Computer Science >>> > University of California, Davis >>> > >>> > ExpoLab: https://expolab.org/ >>> > ResilientDB: https://resilientdb.com/ >>> > Phone: 914-319-7937 >>> > >>> > >>> > On Thu, Oct 12, 2023 at 12:02 AM Atri Sharma wrote: >>> > >>> >> I suggest removing them since it is leading to confusion. >>> >> >>> >> On Thu, Oct 12, 2023 at 12:27 PM Mohammad Sadoghi >>> >> wrote: >>> >> > >>> >> > Dear all, >>> >> > >>> >> > As for the question of the “Broader Contributing Members”, they do not >>> >> > qualify as initial committers as they have provided feedback / >>> >> contributed >>> >> > on the broader scope of ResilientDB, so we suggest either removing >>> them >>> >> or >>> >> > keeping them in a separate category. I prefer keeping them as a >>> separate >>> >> > category, but of course, we will follow the ASF recommendation.We are >>> in >>> >> > the process of improving and upgrading our website, and we will add >>> all >>> >> the >>> >> > initial committers to the website. Currently, from our website, we >>> have >>> >> > also linked to our Apache proposal, which includes the complete list >>> of >>> >> > initial committers.With regards to the question of forked repo vs. >>> >> branch, >>> >> > we are fine with either option. We have made our development public >>> (no >>> >> > longer private), and we can work on the either public repo (main vs. >>> >> > forked), whichever mode is preferred by ASF.With regards to PR, moving >>> >> > forward, we will ensure PR reviews and issue discussions are all done >>> on >>> >> > the public repo with complete visibility. >>> >> > >>> >> > --- >>> >> > Best Regards, >>> >> > Mohammad Sadoghi, PhD >>> >> > Associate Professor >>> >> > Exploratory Systems Lab (ExpoLab) >>> >> > Department of Computer Science >>> >> > University of California, Davis >>> >> > >>> >> > ExpoLab: https://expolab.org/ >>> >> > ResilientDB: https://resilientdb.com/ >>> >> > Phone: 914-319-7937 >>> >> > >>> >> > >>> >> > On Wed, Oct 11, 2023 at 7:49 PM Willem Jiang >>> >> wrote: >>> >> > >>> >> > > Unlike the Linux kernel, we use the dev or main branch from the >>> >> > > official upstream repo to accept the PRs from the develop
Re: [DISCUSS] Incubating Proposal of ResilientDB
n incubation you will need to create a website and you >> can >> >> > > discuss >> >> > > > > the history of the project and if they agree those contributors >> >> you >> >> > > wish to >> >> > > > > honor. >> >> > > > > >> >> > > > > Best wishes, >> >> > > > > Dave >> >> > > > > >> >> > > > > > >> >> > > > > > >> >> > > > > >> On Sun, Oct 8, 2023 at 9:47 AM Mohammad Sadoghi < >> >> > > mo.sado...@expolab.org >> >> > > > > > >> >> > > > > >> wrote: >> >> > > > > >> >> >> > > > > >> Everything we have done including research/papers and outcome >> >> of >> >> > > > > >> development have been open for years. We simply wanted to >> keep >> >> the >> >> > > > > public >> >> > > > > >> repo cleaner and we only released when we were certain that >> >> the new >> >> > > > > feature >> >> > > > > >> is well tested and stable. >> >> > > > > >> >> >> > > > > >> We will switch our development completely to our public repo >> >> > > effective >> >> > > > > >> immediately. That is not issue at all. >> >> > > > > >> >> >> > > > > >> Best Regards, >> >> > > > > >> Mohammad Sadoghi, PhD >> >> > > > > >> Associate Professor >> >> > > > > >> Exploratory Systems Lab (ExpoLab) >> >> > > > > >> Department of Computer Science >> >> > > > > >> University of California, Davis >> >> > > > > >> >> >> > > > > >> >> >> > > > > >> On Sun, Oct 8, 2023 at 3:08 AM Willem Jiang < >> >> willem.ji...@gmail.com >> >> > > > >> >> > > > > >> wrote: >> >> > > > > >> >> >> > > > > >>> I just checked the GitHub issue and PRs of ResilientDB. >> There >> >> is >> >> > > > > >>> little discussion on the GitHub issue and review comments on >> >> GitHub >> >> > > > > >>> PRs. >> >> > > > > >>> Please keep Open Communications[1] in mind. We value >> >> transparency >> >> > > in >> >> > > > > >>> the ASF way. Internal development could block the >> >> contributions >> >> > > > > >>> outside of the organization and cause us some trouble in >> >> building >> >> > > the >> >> > > > > >>> community. >> >> > > > > >>> >> >> > > > > >>> Once the development switches to the public repo, the >> project >> >> > > could be >> >> > > > > >>> ready to enter the incubation process. >> >> > > > > >>> >> >> > > > > >>> [1] >> >> > > > > >>> >> >> > > > > >> >> >> > > > > >> >> > > >> >> >> https://www.apache.org/theapacheway/#what-makes-the-apache-way-so-hard-to-define >> >> > > > > >>> >> >> > > > > >>> >> >> > > > > >>> Willem Jiang >> >> > > > > >>> >> >> > > > > >>> Twitter: willemjiang >> >> > > > > >>> Weibo: 姜宁willem >> >> > > > > >>> >> >> > > > > >>> On Sun, Oct 8, 2023 at 3:33 PM Mohammad Sadoghi < >> >> > > > > mo.sado...@expolab.org> >> >> > > > > >>> wrote: >> >> > > > > >>>> >> >> > > > > >>>> Thank you for your question. >> >> > > > > >>>> >> &
Re: [DISCUSS] Incubating Proposal of ResilientDB
On Tue, Oct 10, 2023, at 20:49, Atri Sharma wrote: > If no further concerns, I wish to start the vote thread tomorrow. > Awesome. Since you have allowed plenty of "complain time," it's safe to go by tomorrow. Thanks for taking care of this! > On Wed, 11 Oct 2023 at 12:16 AM, Christian Grobmeier > wrote: > >> I agree too. >> >> However, I am also concerned the titel is [DISCUSS] - shouldn't this be a >> vote already? >> >> >> On Tue, Oct 10, 2023, at 13:42, 俊平堵 wrote: >> > Agree with Roman and Dave that we can keep the original list. >> > I think Willem is just curious on the mismatch between commits and >> > committers, and the explanation here make sense to me. >> > >> > Thanks, >> > >> > JP >> > >> > Mohammad Sadoghi 于2023年10月10日周二 11:50写道： >> > >> >> Dear all, >> >> >> >> *Question on Initial Committers:* >> >> As was mentioned earlier. The criteria that I used was to credit anyone >> who >> >> has worked on the ResilientDB project since 2018, acknowledging their >> >> contributions. Below is the detailed breakdown of our contributors. So >> we >> >> can reduce the list as needed in accordance with ASF guidelines. As for >> the >> >> broader contributors, these are the folks who have supported >> ResilientDB, >> >> e.g., formalization of the research ideas, discussion of how to tackle a >> >> particular algorithm or its implementation, testing, and analysis. >> However, >> >> these broader members have not contributed to the codebase. So this is >> why >> >> they were tagged differently.*ResilientDB Core *[all have signed ICLA] >> >> Mohammad Sadoghi >> >> Junchao Chen >> >> Dakai Kang >> >> Suyash Gupta [Now at UC Berkeley] >> >> Sajjad Rahnama [Now at Oracle] >> >> Wayne Wang [Now at Hesai Technology] >> >> Julieta Duarte >> >> Glenn Chen >> >> *Tooling/SDK/Wallet/Applications *[all have signed ICLA] >> >> Thamir Qadah [Umm Al-Qura University] >> >> Jinxiao Yu [Now at Amazon AWS] >> >> Arindaam Roy [Now at Square] >> >> Divjeet Singh Jas >> >> Apratim Shukla >> >> Priyal Soni [Now at Amazon AWS] >> >> Rohan Sogani [Now at Oracle] >> >> Kaustubh Shete >> >> Gopal Nambiar >> >> Saipranav Kotamreddy >> >> Haskell Lark Macaraig >> >> >> >> *Deprecated/Obsolete Features *[have been rewritten or removed] >> >> Jelle Hellings [Now at McMaster >> University] >> >> Shesha Vishnu Prasad [Now at Path] >> >> Dhruv Krishnan [Now at Amazon AWS] >> >> Shubham Pandey [Now at Cisco] >> >> Steve Chen >> >> Priya Holani [Now at Amazon AWS] >> >> Haojun (Howard) Zhu >> >> Robert HE [Now at Amazon AWS] >> >> Shreenath Iyer [Now at Amazon AWS] >> >> Domenic Cianfichi [Now at Amazon AWS] >> >> Erik Linsenmayer [Now at General >> >> Atomics] >> >> Shreyan Mohanty [Now at General Atomics] >> >> Xinyuan Sun [Now at CertiK] >> >> Patrick Liao [Now at Juniper Networks] >> >> Tim Huang >> >> Jared Givens >> >> Aditya Bej >> >> Seongwoo Choi >> >> >> >> *Question on Private Development:* >> >> As per request, we have transitioned away from local/private >> development. >> >> We have forked our public ResilientDB, and we began the process of >> moving >> >> all experimental features into this repo. All these ongoing features are >> >> available in this repo but are still under development and not yet >> ready to >> >> be released to the main repository.*Our New Development Repo: * >> >> https://github.com/msadoghi/resilientdb/*Notable Branches (Active >> >> Projects)* >> >> Speculative Consensus: https://github.com/msadoghi/resilientdb/tree/poe >> >> Rotating Leader (lightweight recovery): >> >> https://github.com/msadoghi/resilientdb/tree/hs >> >> Queue-Oriented Concurrency Control (concurrent execution): >> >> https://github.com/msadoghi/resilientdb/tree/QueccBranch >> >> Smart Contract Concurrency: >> >> https://github.com/msadoghi/resilientdb/tree/smartcontract_cc >> >> >> >> --- >> >> Best Regards, >&g
Re: [DISCUSS] Incubating Proposal of ResilientDB
t;> > >>>>> I have a quick question about the initial committers. >> > >>>>> There are about 40+ initial committers, but I can only find about >> 20 >> > >>>>> contributors in the GitHub group[1] contributor list. >> > >>>>> Could you explain the initial committer criteria? >> > >>>>> There is a section of "Broader Contributing Members" in the >> > >>>>> proposal[2] after the initial committer, if we treat them as >> initial >> > >>>>> committers, why do we need to separate them with the initial >> > >>>>> committer? >> > >>>>> >> > >>>>> Thanks, >> > >>>>> >> > >>>>> [1]https://github.com/resilientdb >> > >>>>> [2] >> > >>>>> >> > >>> >> > >> >> > >> https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal >> > >>>>> >> > >>>>> Willem Jiang >> > >>>>> >> > >>>>> Twitter: willemjiang >> > >>>>> Weibo: 姜宁willem >> > >>>>> >> > >>>>> On Sun, Oct 8, 2023 at 1:38 PM 俊平堵 wrote: >> > >>>>>> >> > >>>>>> +1. >> > >>>>>> btw, I assume we will have an official vote thread (start with >> > >>> [VOTE]) >> > >>>>>> later? >> > >>>>>> >> > >>>>>> Thanks, >> > >>>>>> >> > >>>>>> JP >> > >>>>>> >> > >>>>>> Atri Sharma 于2023年10月3日周二 19:24写道： >> > >>>>>> >> > >>>>>>> We want to propose ResilientDB as a new Apache Incubator project. >> > >>>>>>> >> > >>>>>>> ResilientDB[1] is a distributed blockchain framework that is >> > >>> written >> > >>>>>>> in C++ and integrates with Byzantine Fault-Tolerant (BFT) and >> > >> Crash >> > >>>>>>> Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. >> > >>>>>>> >> > >>>>>>> Key features: >> > >>>>>>> >> > >>>>>>> Provides a scalable client-server architecture. Each developer >> > >> can >> > >>> use >> > >>>>>>> the ResilientDB framework to deploy a replicated service acting >> > >> as >> > >>> a >> > >>>>>>> service. The developer can choose the desired number of replicas >> > >>> and >> > >>>>>>> the number of clients its system should tolerate. >> > >>>>>>> >> > >>>>>>> Provides native integration with PBFT consensus protocol – >> > >> arguably >> > >>>>>>> the most popular BFT consensus protocol. PBFT helps replicas >> > >> reach >> > >>> an >> > >>>>>>> agreement for ordering the client's requests. >> > >>>>>>> >> > >>>>>>> Provides a mechanism to simulate the failure of different >> > >> replicas >> > >>>>>>> (including the leader). >> > >>>>>>> >> > >>>>>>> Provides a correct implementation of the view-change protocol >> > >> that >> > >>>>>>> replaces a faulty (or malicious) leader and moves all replicas to >> > >>> the >> > >>>>>>> new view. >> > >>>>>>> >> > >>>>>>> Provides checkpoint and recovery protocols to facilitate garbage >> > >>>>>>> collection, recovery of failed replicas, and durably logging of >> > >> the >> > >>>>>>> blockchain state. >> > >>>>>>> >> > >>>>>>> Eases development and testing of newer and optimized BFT and CFT >> > >>>>>>> consensus protocols. >> > >>>>>>> Provides clients with support for three different application >> > >>>>> interfaces: >> > >>>>>>> >> > >>>>>>> Key-Value Stores - where client transactions include key-value >> > >>> pairs. >> > >>>>>>> >> > >>>>>>> Smart Contracts - where clients issue smart contracts in Solidity >> > >>> for >> > >>>>>>> processing. >> > >>>>>>> >> > >>>>>>> UTXO - where clients issue unspent transactions similar to ones >> > >> in >> > >>>>> Bitcoin. >> > >>>>>>> >> > >>>>>>> Facilitates benchmarking system/protocol performance with the >> > >> help >> > >>> of >> > >>>>>>> existing benchmarks, such as YCSB [SoCC’10] and Diablo >> > >>> [EuroSys’23]. >> > >>>>>>> >> > >>>>>>> Stores non-volatile ledger (blockchain) in memory and for further >> > >>>>>>> durability, provides APIs to store both client data and >> > >> blockchain >> > >>> in >> > >>>>>>> LevelDB and RocksDB. >> > >>>>>>> >> > >>>>>>> >> > >>>>>>> The serving mentors would be: >> > >>>>>>> >> > >>>>>>> Junping Du >> > >>>>>>> >> > >>>>>>> Calvin Kirs >> > >>>>>>> >> > >>>>>>> Kevin Ratnasekera >> > >>>>>>> >> > >>>>>>> Roman Shaposhnik >> > >>>>>>> >> > >>>>>>> Christian Grobmeier >> > >>>>>>> >> > >>>>>>> and I shall be serving as the Champion. >> > >>>>>>> >> > >>>>>>> We have not done a trademark check yet for the name but that can >> > >> be >> > >>>>>>> pursued independently. >> > >>>>>>> >> > >>>>>>> [1] >> > >>>>>>> >> > >>>>> >> > >>> >> > >> >> > >> https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal >> > >>>>>>> [2] https://github.com/resilientdb/resilientdb >> > >>>>>>> >> > >>>>>>> Atri >> > >>>>>>> >> > >>>>>>> >> > >>> - >> > >>>>>>> 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 >> > >>> >> > >>> >> > >> >> > > >> > > >> > > -- >> > > *- Regards* >> > > >> > > *Suyash Gupta, PhD * >> > > *SkyLab* >> > > *Dept. of Computer Science* >> > > *University of California Berkeley* >> > >> > - >> > 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: [DISCUSS] Incubating Proposal of ResilientDB
+1 (binding) The proposal looks solid -- The Apache Software Foundation V.P., Data Privacy On Tue, Oct 3, 2023, at 13:23, Atri Sharma wrote: > We want to propose ResilientDB as a new Apache Incubator project. > > ResilientDB[1] is a distributed blockchain framework that is written > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash > Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. > > Key features: > > Provides a scalable client-server architecture. Each developer can use > the ResilientDB framework to deploy a replicated service acting as a > service. The developer can choose the desired number of replicas and > the number of clients its system should tolerate. > > Provides native integration with PBFT consensus protocol – arguably > the most popular BFT consensus protocol. PBFT helps replicas reach an > agreement for ordering the client's requests. > > Provides a mechanism to simulate the failure of different replicas > (including the leader). > > Provides a correct implementation of the view-change protocol that > replaces a faulty (or malicious) leader and moves all replicas to the > new view. > > Provides checkpoint and recovery protocols to facilitate garbage > collection, recovery of failed replicas, and durably logging of the > blockchain state. > > Eases development and testing of newer and optimized BFT and CFT > consensus protocols. > Provides clients with support for three different application interfaces: > > Key-Value Stores - where client transactions include key-value pairs. > > Smart Contracts - where clients issue smart contracts in Solidity for > processing. > > UTXO - where clients issue unspent transactions similar to ones in Bitcoin. > > Facilitates benchmarking system/protocol performance with the help of > existing benchmarks, such as YCSB [SoCC’10] and Diablo [EuroSys’23]. > > Stores non-volatile ledger (blockchain) in memory and for further > durability, provides APIs to store both client data and blockchain in > LevelDB and RocksDB. > > > The serving mentors would be: > > Junping Du > > Calvin Kirs > > Kevin Ratnasekera > > Roman Shaposhnik > > Christian Grobmeier > > and I shall be serving as the Champion. > > We have not done a trademark check yet for the name but that can be > pursued independently. > > [1] https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > [2] https://github.com/resilientdb/resilientdb > > Atri > > - > 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] Accept Answer into the Apache Incubator
+1 (binding) Exciting project, good luck. Christian On Tue, Oct 3, 2023, at 02:17, Willem Jiang wrote: > Following up the [DISCUSS] thread on Answer [1] I would like to call a > VOTE to accept into the Apache Incubator. > > Answer is a question-and-answer (Q) platform software for teams at > any scale to build a help center, knowledge base, community forum, > etc. > > Please cast your vote: > > [ ] +1, bring into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring Answer into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > Please check out the Answer Proposal from the incubator wiki[2]. > > [1]https://lists.apache.org/thread/42tvz3rqfy4w5poqgslh71sm1o1td7zn > [2]https://cwiki.apache.org/confluence/display/INCUBATOR/Answer+Proposal > > Best Regards, > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > - > 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: Looking for a Champion / Mentors for ResilientDB Blockchain Platform
I have added myself. There are many committers, I assume one more helping hand does not hurt. On Sun, Oct 1, 2023, at 19:34, Mohammad Sadoghi wrote: > Dear Christian, > > It would be wonderful if you would officially be added as one of our mentors. > The proposal can be found here > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > Thank you kindly Atri. > > Best Regards, > Mohammad Sadoghi, PhD > Associate Professor > Exploratory Systems Lab (ExpoLab) > Department of Computer Science > University of California, Davis > > > On Sun, Oct 1, 2023 at 10:20 AM Atri Sharma wrote: >> Sorry, was crazily distracted. This will be done before Monday >> >> On Sun, 1 Oct 2023 at 6:09 PM, Christian Grobmeier >> wrote: >>> Hi, >>> >>> if any problems, please feel free to add me as a mentor. I am also willing >>> to champion and make this vote happen, if the current champion prefers to >>> re-delegate. >>> >>> Kind regards, >>> Christian >>> >>> On Sat, Sep 30, 2023, at 16:59, Ayush Saxena wrote: >>> > Ok, I'll take that back. Reading the document here: >>> > https://incubator.apache.org/guides/roles_and_responsibilities.html#candidate >>> > >>> > It reads >>> > `` >>> > A Champion (see below) may propose their candidate project for >>> > acceptance as an incubating Podling. Approval of a project is subject >>> > to a vote of the Sponsor >>> > `` >>> > So, you need to wait for your champion, and rest you have done your >>> > part, Atri already mentioned he will start a thread soon. >>> > >>> > Good Luck!! >>> > >>> > -Ayush >>> > >>> > On Sat, 30 Sept 2023 at 20:16, Ayush Saxena wrote: >>> >> >>> >> You can start a VOTE thread yourself as well, can do the same way as >>> >> here [1] >>> >> >>> >> Good Luck!!! >>> >> >>> >> -Ayush >>> >> >>> >> [1] https://lists.apache.org/thread/3v9g2nk734m2zplrq1fgozc7xt169bgt >>> >> >>> >> On Sat, 30 Sept 2023 at 09:43, Mohammad Sadoghi >>> >> wrote: >>> >> > >>> >> > Dear all, >>> >> > >>> >> > Could we move the project to the vote phase? Please let us know if >>> >> > anything >>> >> > is needed from our end. Thank you kindly. >>> >> > >>> >> > --- >>> >> > Best Regards, >>> >> > Mohammad Sadoghi, PhD >>> >> > Associate Professor >>> >> > Exploratory Systems Lab (ExpoLab) >>> >> > Department of Computer Science >>> >> > University of California, Davis >>> >> > >>> >> > ExpoLab: https://expolab.org/ >>> >> > ResilientDB: https://resilientdb.com/ >>> >> > Phone: 914-319-7937 >>> >> > >>> >> > >>> >> > On Fri, Sep 29, 2023 at 4:45 AM Roman Shaposhnik >>> >> > wrote: >>> >> > >>> >> > > On Thu, Sep 28, 2023 at 7:46 PM Atri Sharma wrote: >>> >> > > > >>> >> > > > Sorry was away due to medical reasons. >>> >> > > >>> >> > > And my time to apologise as well -- past few weeks were crazy, but >>> >> > > I'm >>> >> > > now fully available to help with the project. >>> >> > > >>> >> > > > I will start this tonight >>> >> > > >>> >> > > Looking forward to it! >>> >> > > >>> >> > > Thanks, >>> >> > > Roman. >>> >> > > >>> >> > > - >>> >> > > 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: Looking for a Champion / Mentors for ResilientDB Blockchain Platform
Hi, if any problems, please feel free to add me as a mentor. I am also willing to champion and make this vote happen, if the current champion prefers to re-delegate. Kind regards, Christian On Sat, Sep 30, 2023, at 16:59, Ayush Saxena wrote: > Ok, I'll take that back. Reading the document here: > https://incubator.apache.org/guides/roles_and_responsibilities.html#candidate > > It reads > `` > A Champion (see below) may propose their candidate project for > acceptance as an incubating Podling. Approval of a project is subject > to a vote of the Sponsor > `` > So, you need to wait for your champion, and rest you have done your > part, Atri already mentioned he will start a thread soon. > > Good Luck!! > > -Ayush > > On Sat, 30 Sept 2023 at 20:16, Ayush Saxena wrote: >> >> You can start a VOTE thread yourself as well, can do the same way as here [1] >> >> Good Luck!!! >> >> -Ayush >> >> [1] https://lists.apache.org/thread/3v9g2nk734m2zplrq1fgozc7xt169bgt >> >> On Sat, 30 Sept 2023 at 09:43, Mohammad Sadoghi >> wrote: >> > >> > Dear all, >> > >> > Could we move the project to the vote phase? Please let us know if anything >> > is needed from our end. Thank you kindly. >> > >> > --- >> > Best Regards, >> > Mohammad Sadoghi, PhD >> > Associate Professor >> > Exploratory Systems Lab (ExpoLab) >> > Department of Computer Science >> > University of California, Davis >> > >> > ExpoLab: https://expolab.org/ >> > ResilientDB: https://resilientdb.com/ >> > Phone: 914-319-7937 >> > >> > >> > On Fri, Sep 29, 2023 at 4:45 AM Roman Shaposhnik >> > wrote: >> > >> > > On Thu, Sep 28, 2023 at 7:46 PM Atri Sharma wrote: >> > > > >> > > > Sorry was away due to medical reasons. >> > > >> > > And my time to apologise as well -- past few weeks were crazy, but I'm >> > > now fully available to help with the project. >> > > >> > > > I will start this tonight >> > > >> > > Looking forward to it! >> > > >> > > Thanks, >> > > Roman. >> > > >> > > - >> > > 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
[Pagespeed] Pagespeed podling was retired
Details: https://issues.apache.org/jira/browse/INFRA-24494 Thanks! Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[Spot] Spot podling was retired
Details: https://issues.apache.org/jira/browse/INFRA-24487 Kind regards, Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] [VOTE] Retire the Spot podling
The IPMC voted to retire the Spot podling. The vote ended with 11 +1 from: Christian Grobmeier PJ Fanning Nate Smith Willem Jiang Leda G Lima Furkan Kamaci Calvin Kirs Dave Fisher Yu Xiao Uma Maheswara Rao Gangumalia Gonzalez Victor Thanks to all who voted. - Original message - From: Christian Grobmeier To: general@incubator.apache.org Cc: d...@spot.apache.org, priv...@spot.apache.org Subject: [VOTE] Retire the Spot podling Date: Monday, March 13, 2023 21:42 Hello, as recently discussed, I think the Spot podling is ready for retirement. Several roll calls were made, like this one: https://lists.apache.org/list?priv...@spot.apache.org:2022-10 There has been no activity for a while; there are no signs of change soon. Please vote: [ ] +1, retire [ ] -1 don't retire, because... Please don't hesitate to vote -1 if you feel this podling should remain. This vote will be kept open for at least the usual 72 hours. Kind regards, Christian - 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] Retire the Spot podling
my own +1 On Mon, Mar 13, 2023, at 21:42, Christian Grobmeier wrote: > Hello, > > as recently discussed, I think the Spot podling is ready for retirement. > > Several roll calls were made, like this one: > https://lists.apache.org/list?priv...@spot.apache.org:2022-10 > > There has been no activity for a while; there are no signs of change soon. > > Please vote: > > [ ] +1, retire > [ ] -1 don't retire, because... > > Please don't hesitate to vote -1 if you feel this podling should remain. > > This vote will be kept open for at least the usual 72 hours. > > Kind regards, > Christian > > - > 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
[RESULT] [VOTE] Retire PageSpeed
The IPMC voted to retire the PageSpeed podling. The vote ended witih 9 +1 from: Christian Grobmeier Willem Jiang Otto van der Schaaf Calvin Kirs Dave Fisher PJ Fanning Yu Xiao Paul King Li Gang Thanks to all who voted. - Original message - From: Christian Grobmeier To: general@incubator.apache.org Cc: d...@pagespeed.apache.org, priv...@pagespeed.apache.org Subject: [VOTE] Retire PageSpeed Date: Monday, March 13, 2023 21:46 Hello, as recently discussed, I think the PageSpeed podling is ready for retirement. https://lists.apache.org/thread/jxw7mqmpcfxxp0mnnx28o0k78tym507b There has been no activity for a while; there are no signs of change soon. Please vote: [ ] +1, retire [ ] -1 don't retire, because... Please don't hesitate to vote -1 if you feel this podling should remain. This vote will be kept open for at least the usual 72 hours. Kind regards, Christian - 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] Retire PageSpeed
My own +1 On Mon, Mar 13, 2023, at 21:46, Christian Grobmeier wrote: > Hello, > > as recently discussed, I think the PageSpeed podling is ready for retirement. > > https://lists.apache.org/thread/jxw7mqmpcfxxp0mnnx28o0k78tym507b > > There has been no activity for a while; there are no signs of change soon. > > Please vote: > > [ ] +1, retire > [ ] -1 don't retire, because... > > Please don't hesitate to vote -1 if you feel this podling should remain. > > This vote will be kept open for at least the usual 72 hours. > > Kind regards, > Christian > > - > 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] Retire PageSpeed
Hello, as recently discussed, I think the PageSpeed podling is ready for retirement. https://lists.apache.org/thread/jxw7mqmpcfxxp0mnnx28o0k78tym507b There has been no activity for a while; there are no signs of change soon. Please vote: [ ] +1, retire [ ] -1 don't retire, because... Please don't hesitate to vote -1 if you feel this podling should remain. This vote will be kept open for at least the usual 72 hours. Kind regards, Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Retire the Spot podling
Hello, as recently discussed, I think the Spot podling is ready for retirement. Several roll calls were made, like this one: https://lists.apache.org/list?priv...@spot.apache.org:2022-10 There has been no activity for a while; there are no signs of change soon. Please vote: [ ] +1, retire [ ] -1 don't retire, because... Please don't hesitate to vote -1 if you feel this podling should remain. This vote will be kept open for at least the usual 72 hours. Kind regards, Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Paimon into the Apache Incubator
+1 (binding) This project might be a quick incubation, good luck! On Mon, Mar 6, 2023, at 08:59, Yu Li wrote: > Hi All, > > Following up on the [DISCUSS] thread on Paimon [1], I would like to call > a VOTE to accept Paimon into the Apache Incubator, please check out > the Paimon Proposal from the incubator wiki [2]. > > > Please cast your vote: > > > [ ] +1, bring Paimon into the Incubator > > [ ] +0, I don't care either way > > [ ] -1, do not bring Paimon into the Incubator, because... > > > The vote will open at least for 72 hours, and only votes from the Incubator > PMC are binding, but votes from everyone are welcome. > > Best Regards, > Yu > > [1] https://lists.apache.org/thread/hr3d7tpw02w6ybrnnlf3hcbhfxotwpvn > [2] https://cwiki.apache.org/confluence/display/INCUBATOR/PaimonProposal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[DISCUSS] Retire the Spot project?
Hello Spot team, cc/ general@ I am currently checking various podlings and have seen no activity in Spot for a long time. Several roll calls were made, like this one: https://lists.apache.org/list?priv...@spot.apache.org:2022-10 (private list) Although the contributor list is huge, nothing has changed since then. To me, it looks like nobody has the time to maintain the project. I want to bring up the idea of retirement again. It would mean Spot would no longer be in the incubator but could return to the incubator when there is a community. Retirement does not mean the code is locked up and archived forever. The Spot team can still work on it on platforms like Github. On the other hand, you don't need to report anymore; of course, you don't have strict ASF release rules. This makes it sometimes easier for teams to grow and become more active again. While retirement as a term sounds like an end, it is not, it can even offer a fresh start. What do you think about that? Kind regards, Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Retirement steps Heron: copyright question
Thanks Josh!
On Wed, Mar 1, 2023, at 16:12, Josh Fischer wrote:
> done:
> https://github.com/apache/incubator-heron/commit/1c5779dcdf19eed888412f3d87b31ebb4b00e07e
>
> On Wed, Mar 1, 2023 at 9:02 AM Josh Fischer wrote:
>
>> Sure, I'll get it done today.
>>
>> On Wed, Mar 1, 2023 at 8:49 AM Christian Grobmeier
>> wrote:
>>
>>> Josh,
>>>
>>> On Wed, Mar 1, 2023, at 14:38, Josh Fischer wrote:
>>> > Thanks for this, Christian. I was looking at this list [1] and had
>>> quite
>>> > a few questions. The list you sent seems to have more information.
>>> > 1.
>>> https://cwiki.apache.org/confluence/display/incubator/RetiringPodlings
>>>
>>> great you are still around - I could not complete this step here:
>>>
>>> "Create a file RETIRED.txt at the top-level of each podling source
>>> repository. This should contain something like the following:
>>>
>>> This podling has been retired, please see:
>>> http://incubator.apache.org/projects/index.html##{podling-name};
>>>
>>> As I have not write access to the repos. If I am not asking too much,
>>> could you take care of this?
>>>
>>> I will add a note to the Confluence page to point to the Incubator page.
>>> Thanks for bringing it up, I didn't know the wikipage
>>>
>>> Kind regards,
>>> Christian
>>>
>>>
>>> >
>>> > On Wed, Mar 1, 2023 at 3:58 AM Christian Grobmeier <
>>> grobme...@apache.org>
>>> > wrote:
>>> >
>>> >> Hi,
>>> >>
>>> >> I completed most of the retirement actions described here:
>>> >> https://incubator.apache.org/guides/retirement.html
>>> >>
>>> >> The copyright item is not checked. Do we have any tooling to check
>>> whether
>>> >> we remove the source code?
>>> >>
>>> >> It was also hard to dig out all the requested resources. If anybody
>>> knows
>>> >> any more, please add them here:
>>> >> https://issues.apache.org/jira/browse/INFRA-24277
>>> >>
>>> >> Kind regards,
>>> >> Christian
>>> >>
>>> >> -
>>> >> 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: Retirement steps Heron: copyright question
Josh,
On Wed, Mar 1, 2023, at 14:38, Josh Fischer wrote:
> Thanks for this, Christian. I was looking at this list [1] and had quite
> a few questions. The list you sent seems to have more information.
> 1. https://cwiki.apache.org/confluence/display/incubator/RetiringPodlings
great you are still around - I could not complete this step here:
"Create a file RETIRED.txt at the top-level of each podling source repository.
This should contain something like the following:
This podling has been retired, please see:
http://incubator.apache.org/projects/index.html##{podling-name};
As I have not write access to the repos. If I am not asking too much, could you
take care of this?
I will add a note to the Confluence page to point to the Incubator page. Thanks
for bringing it up, I didn't know the wikipage
Kind regards,
Christian
>
> On Wed, Mar 1, 2023 at 3:58 AM Christian Grobmeier
> wrote:
>
>> Hi,
>>
>> I completed most of the retirement actions described here:
>> https://incubator.apache.org/guides/retirement.html
>>
>> The copyright item is not checked. Do we have any tooling to check whether
>> we remove the source code?
>>
>> It was also hard to dig out all the requested resources. If anybody knows
>> any more, please add them here:
>> https://issues.apache.org/jira/browse/INFRA-24277
>>
>> Kind regards,
>> Christian
>>
>> -
>> 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
Retirement steps Heron: copyright question
Hi, I completed most of the retirement actions described here: https://incubator.apache.org/guides/retirement.html The copyright item is not checked. Do we have any tooling to check whether we remove the source code? It was also hard to dig out all the requested resources. If anybody knows any more, please add them here: https://issues.apache.org/jira/browse/INFRA-24277 Kind regards, Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[DISCUSS] Status of modpagespeed
Hello, PageSpeed has been in the Incubator since 2017: https://incubator.apache.org/projects/pagespeed.html It has little activity: https://github.com/apache/incubator-pagespeed-mod The last release was in 2020: https://www.modpagespeed.com/doc/download No matter where I look in the email archives, there is nothing except GitHub noise: https://lists.apache.org/list?d...@pagespeed.apache.org Only one committer has been active since 2020. Releases will also be impossible. The last report also indicates retirement: https://whimsy.apache.org/board/minutes/PageSpeed.html Another issue is the domain modpagespeed.com is still not controlled/owned by the ASF, but it's used. It's not listed in the ASF privacy policy as well, which could be a problem. The general overview page here looks unmaintained. https://incubator.apache.org/projects/pagespeed.html As it is now I don't see a chance to graduate this podling. I would +1 to retirment. Maybe the remaining people on dev@modpagespeed can comment (in CC). Wdyt? Kind regards, Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Looking for a champion: resurrect log4j 1.x
Hello, I just came across this thread - same as Ralph, I currently don't mentor any podlings. However, I am still on the Logging PMC. On Thu, Dec 23, 2021, at 07:05, Vladimir Sitnikov wrote: > Ralph>I was busy > > The world is on fire with log4j, so if you have no time left for 1.x, then, > please, just let others do the maintenance. You have been constantly treating others with disrespect. Nobody of us committed any time for log4j1 since 2012, and since 2015 it is EOL. Nobody of us even thought about giving any time to log4j1 until you came up on this list. I think it is fair to say the world is on fire with log4j2 BUT NOT with log4j1. There is no new security issues with log4j1. Instead we retired log4j1 for many reasons, including some multithreading issues which require heavy architectural changes - which we then fixed with log4j2. Nobody was able to fix it back then. Maybe I have missed something, but we never accepted a single podling for just one release, with one committer, with the original PMC opposing this step. And this for two security issues which are 10 years old which are not comparable to the ones we found in log4j2. I recommend looking at the Logging Chairs statement for details if interested which will be sent soon. Also, I don't think Cobol and Log4j 1 match up. That being said, the PMCs job - especially those people dealing with this issue - has been excellent so far, and this email thread looks like some of us were blocking all the time. That's not true and is a wrong impression. We just haven't heard good arguments for resurrecting log4j1. Cheers Christian > > Ralph>My recollection was me saying if I had the code in a git repo getting > it into a GitHub repo would be easy. > > I do not want to dilute "svn -> git" question any further, so, if you have > time (apparently, you do respond on logging and here), > consider answering at https://issues.apache.org/jira/browse/LOG4J2-3272 > > --- > > Ralph, my response was > https://lists.apache.org/thread/jzym3z270jqr84m8o4m7pxlmpk8frr4z > Literally, you have **nothing** to do except blessing the migration in > order to get Git and GitHub open for log4j 1.x . > > You even ignored "[VOTE] Move log4j 1.x from SVN to Git..." > https://lists.apache.org/thread/ssbdg44gy7txzl16xxd097t7orco52g2 > > You still keep asking "if git repo exists or not". Who cares if git repo > exists? > I offer you help with getting the things done, yet you ask questions as if > I ask you to do the work. > > Vladimir - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Retire Ripple
+1 (binding, Ripple mentor since it arrived) On Tue, Dec 1, 2015, at 05:54, Marvin Humphrey wrote: > Greetings, > > The Ripple community has been discussing retirement on their dev list. > > http://s.apache.org/LjX > > It would be more clear cut if there had been a VOTE thread, but since the > discussion took place on the podling dev list (rather than the private > list or > some other non-central channel), since traffic is low and thus the thread > is > very prominent, and since the subject line contains the word "retire", > hopefully all potential contributors have received sufficient notice. > > This is a vote of the IPMC to retire the podling. > > [ ] +1 to retire Ripple from the Incubator > [ ] -1 to keep Ripple in the Incubator > > This vote will be held open for at least 72 hours. > > Should this vote pass, I have volunteered to assist Ripple with > retirement, > as I have been assisting Droids, Kalumet and Corinthia. > > Marvin Humphrey > > - > 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: Question about proposal champions
Hi Greg, from my experience it has proven to be very hard to start single-man-shows here. The Incubator works best if there is an active community already. If you are a sole person, you might also consider labs.apache.org. Some people say, Labs is for experiments, and when there is a community, go to the Incubator. Personally, if you have no plan how to get new people on-board, or if nobody else here is interested in becoming a committer, or if your project is not Hadoop related :-), then you should first start building a community. If you don't have at least three committers, you will als not be be able to cut a release. Cheers, Christian On Thu, Nov 5, 2015, at 14:53, Greg Brown wrote: > Hi all, > > I've been out of the Apache loop for a while, but I have a new project > I'd like to propose for incubation. I know new Incubator projects require > a champion. As an ASF member myself, can I act as my own champion, or > does another member need to act as champion on my behalf? > > It certainly wouldn't hurt to have another champion for the project > since, to date, I've been the only committer. Just wanted to ask the > question before I got started on the actual proposal. > > Thanks, > 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
Re: Wave community may need our help
Agreed. First speak to wave-dev. We have had that kind of discussion several times. It did not change to date, so we should pick it up again. On Sat, Mar 14, 2015, at 21:44, Upayavira wrote: Although, I should also make this point directly on wave-dev. I have long been quiet there, and it would be unfair for this to arise without their prior warning. Upayavira On Sat, Mar 14, 2015, at 08:42 PM, Upayavira wrote: Please do. On Sat, Mar 14, 2015, at 06:54 PM, Ted Dunning wrote: Right. Brain not functioning apparently. Yes. Adding this to the incubator report is what I mean. On Sat, Mar 14, 2015 at 11:01 AM, Marvin Humphrey mar...@rectangular.com wrote: On Sat, Mar 14, 2015 at 10:43 AM, Ted Dunning ted.dunn...@gmail.com wrote: Upayavira, Mind if I add your comment to the wave report? The report for March has been filed already. I've initialized the wiki template for our April report. http://wiki.apache.org/incubator/April2015 Wave is not assigned to file a report for April, but this is the sort of discussion that would be appropriate to summarize in the narrative section at the top of the report. I suggest adding some sort of rough note now and then refining it later. Marvin Humphrey - 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: Wave community may need our help
Hi Roman, you might have noticed, that one of the mentors (me) were actively asking for this report. I simply forgot to sign it, which does not happen often to me. In example, the last report was signed (Dec). More mentors are always welcome; but its not this podling is out on his own. From mentoring activities, I even joined a Google Hangout to clarify questions, and releases were reviewed. When it comes to the situation of this podling, it hasn't changed much. I wonder why you think Wave would turn the corner. From time to time I start the retirement discussion at the podling as I don't think Wave will get enough momentum. There is a small community, but they cannot dedicate enough time. My personal opinion is that it will not make graduation at any time, and i told that before. I am happy if the project turns out otherwise. That being said, I am still on mailing lists, i am still helping out, I just wasn't there in the past 10 days for personal reasons. Again, I wrote this response to help giving the right impression on the podling, not to put your good intentions down to help. I am really happy if somebody else would help as mentor, as well as with log4cxx and ripple. Thanks, Christian -- Christian Grobmeier grobme...@gmail.com On Fri, Mar 13, 2015, at 00:48, Roman Shaposhnik wrote: Hi! all throughout my tenure I was keeping an eye on Wave trying to figure out how we can help that community. The poddling has been incubating close to 5 years and for a long time they've struggled with the basics of producing the release and growing the community beyond its core. I was extremely excited to see that this reporting cycle they seem to be finally turning the corner. Unfortunately, next thing I saw was that the report wasn't signed off by mentors. I totally understand that we all get busy (hey -- I was supposed to submit the final report yesterday -- totally didn't happen). It is just that if the community is really on the verge of turning the corner I think it really behoves us to help them as much as we can. Thoughts on how we can revitalize mentoring around Wave? Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[NOTICE] added Ripple committer to incubator group
Hi, according to: http://incubator.apache.org/guides/pmc.html I added the newly elected committer axemclion to the incubator group. He was already committer, so he couldn't be added to the group by infra. Thanks, Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: log4cxx2 - report reminders
On Mon, Dec 8, 2014, at 00:12, Roman Shaposhnik wrote: On Fri, Dec 5, 2014 at 6:04 PM, John D. Ament johndam...@apache.org wrote: All, It looks like log4cxx2 didn't receive report reminders. The one issue I noticed is that the email address for dev@ is log4cxx-dev@logging.a.o This strikes me as extremely odd. Does anybody know the history behind this kind of ML name? Yes. This podling was actually a mature project of logging.apache.org. Then we discussed the attic, because noone of the old committers were around. But objections were raised by the community. I discussed this issue with Logging PMC and IPMC and it seemed the best idea was to move log4cxx back to the incubator with new people from the mailing lists. As there are no IP concerns and we wanted to avoid wasting infra time, we have kept the old mailing lists. Btw, it is named log4cxx2 and not just log4cxx because before ages the project has already incubated with different people. From that point of view, I think it is only important for this podling to prove there are a few people and they understand the ASF principles and release requirements. I say few people, because the Logging PMC is active and able to help to pass votes. In this special case I think this podling could even graduate with one or two active persons. Hope that helps! Christian Thanks, Roman. - 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: [DRAFT] Board Report for December 2014 - please review
PLease note there is a Ripple report in preparation.
Log4cxx should be possible to craft a report.
in both cases I am a mentor, but my current personal situation prevents
me from being as active as I wouldl ike to be.
Other people joining as mentors would be welcome (Ripple already got
Ross)
--
Christian Grobmeier
http://www.grobmeier.de
http://www.timeandbill.de
On Mon, Dec 8, 2014, at 16:28, John D. Ament wrote:
Roman,
So here's what I'm seeing for some of why the reports are missing.
- log4cxx2 - Likely stuck in moderation limbo.
- Argus/Ranger - confused about monthly reporting vs quarterly reporting.
- Kalumet - seems like there's only one active member. He brought up the
topic of retirement.
- NPanday and Ripple are repeat offenders.
John
On Sun, Dec 7, 2014 at 7:46 PM, Roman Shaposhnik ro...@shaposhnik.org
wrote:
John, as usual thanks a ton for all of your hard work.
I'll add few of my comments directly to the wiki, but all
in all it looks good and ready to be submitted.
One thing that I'm really concerned about is, to your
point, the # of missing reports. In some cases, I'm
sure this is just a function of an oversight, but in
cases like NPanday I think we need to get to
some kind of a closure of what to do with
poddling.
I'll restart a few threads.
Thanks,
Roman.
On Sun, Dec 7, 2014 at 4:27 PM, John D. Ament johndam...@apache.org
wrote:
All,
Please find below the draft board report for December 2014. If anyone
has
any comments for the miscellaneous section please let me know. I still
have to address line lengths, but the report's all here.
Please feel free to edit the wiki with any proposed changes.
= Incubator PMC report for December 2014 =
=== Timeline ===
||Wed December 03 ||Podling reports due by end of day ||
||Sun December 07 ||Shepherd reviews due by end of day ||
||Sun December 07 ||Summary due by end of day ||
||Tue December 09 ||Mentor signoff due by end of day ||
||Wed December 10 ||Report submitted to Board ||
||Wed December 17 ||Board meeting ||
=== Shepherd Assignments ===
||Alan D. Cabrera ||Ignite ||
||Andrei Savu ||Drill ||
||Andrei Savu ||Johnzon ||
||Dave Fisher ||NPanday ||
||John Ament ||MRQL ||
||John Ament ||log4cxx2 ||
||Justin Mclean ||Tamaya ||
||Konstantin Boudnik ||Argus ||
||Matthew Franklin ||Brooklyn ||
||Raphael Bircher ||Kalumet ||
||Raphael Bircher ||Streams ||
||Roman Shaposhnik ||Sentry ||
||Ross Gardler ||Wave ||
||Suresh Marru ||Falcon ||
||Suresh Marru ||Lens ||
||Timothy Chen ||Ripple ||
||Timothy Chen ||Taverna ||
=== Report content ===
{{{
Incubator PMC report for December 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 36 podlings undergoing incubation. Two podlings
joined
us this month, NiFi and Tamaya. Three new IPMC members and two new
Shepherds joined our ranks as well.
* Community
New IPMC members:
Andrew L. Farris
Thejas Nair
Brock Noland
New Incubator Shepherds:
Timothy Chen
Andrew L. Farris
People who left the IPMC:
None
* New Podlings
Nifi
Tamaya
* Graduations
The board has motions for the following:
* Releases
The following releases were made since the last Incubator report:
apache-calcite-0.9.2-incubating
apache-twill-0.4.0-incubating
apache-parquet-format-2.2.0-incubating
apache-johnzon-0.2-incubating
apache-slider-0.60.0-incubating
metamodel-4.3.0-incubating
apache-aurora-0.6.0-incubating
* IP Clearance
Sling Sightly and XSS modules
* Legal / Trademarks
There are many on going Podling Name Search requests, with few being
closed.
Droids still has an open name search.
Falcon is procesing a name search currently.
Tamaya successfully cleared Podling Name Search.
* Infrastructure
SVN outage caused minor inconvenience to some podlings.
Argus/Ranger is facing some struggles with their rename.
* Miscellaneous
Summary of podling reports
* Still getting started at the Incubator
Ignite
Lens
Nifi
Tamaya
Taverna
* Not yet ready to graduate
No release:
Brooklyn
Wave
Community growth:
Falcon
Johnzon
Sentry
Streams
* Ready to graduate
The Board has motions for the following:
* Did not report, expected next month
Ranger (formerly Argus)
Kalumet
log4cxx2
NPanday
Ripple
* Not signed off by mentors
Brooklyn
Falcon
MRQL
Streams
Re: log4cxx2 - report reminders
On Mon, Dec 8, 2014, at 00:12, Roman Shaposhnik wrote: On Fri, Dec 5, 2014 at 6:04 PM, John D. Ament johndam...@apache.org wrote: All, It looks like log4cxx2 didn't receive report reminders. The one issue I noticed is that the email address for dev@ is log4cxx-dev@logging.a.o This strikes me as extremely odd. Does anybody know the history behind this kind of ML name? Yes. This podling was actually a mature project of logging.apache.org. Then we discussed the attic, because noone of the old committers were around. But objections were raised by the community. I discussed this issue with Logging PMC and IPMC and it seemed the best idea was to move log4cxx back to the incubator with new people from the mailing lists. As there are no IP concerns and we wanted to avoid wasting infra time, we have kept the old mailing lists. Btw, it is named log4cxx2 and not just log4cxx because before ages the project has already incubated with different people. From that point of view, I think it is only important for this podling to prove there are a few people and they understand the ASF principles and release requirements. I say few people, because the Logging PMC is active and able to help to pass votes. In this special case I think this podling could even graduate with one or two active persons. Hope that helps! Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DRAFT] Board Report for December 2014 - please review
I signed the ripple report brought in today and wrote a small log4cxx
report myself. I consider this valid as consider myself part of the
log4cxx community.
I hope this is acceptable, since the podling deadline was before a few
days. Please let me know if not and I will revert
Thanks!
--
Christian Grobmeier
grobme...@gmail.com
On Mon, Dec 8, 2014, at 16:49, Christian Grobmeier wrote:
PLease note there is a Ripple report in preparation.
Log4cxx should be possible to craft a report.
in both cases I am a mentor, but my current personal situation prevents
me from being as active as I wouldl ike to be.
Other people joining as mentors would be welcome (Ripple already got
Ross)
--
Christian Grobmeier
http://www.grobmeier.de
http://www.timeandbill.de
On Mon, Dec 8, 2014, at 16:28, John D. Ament wrote:
Roman,
So here's what I'm seeing for some of why the reports are missing.
- log4cxx2 - Likely stuck in moderation limbo.
- Argus/Ranger - confused about monthly reporting vs quarterly reporting.
- Kalumet - seems like there's only one active member. He brought up the
topic of retirement.
- NPanday and Ripple are repeat offenders.
John
On Sun, Dec 7, 2014 at 7:46 PM, Roman Shaposhnik ro...@shaposhnik.org
wrote:
John, as usual thanks a ton for all of your hard work.
I'll add few of my comments directly to the wiki, but all
in all it looks good and ready to be submitted.
One thing that I'm really concerned about is, to your
point, the # of missing reports. In some cases, I'm
sure this is just a function of an oversight, but in
cases like NPanday I think we need to get to
some kind of a closure of what to do with
poddling.
I'll restart a few threads.
Thanks,
Roman.
On Sun, Dec 7, 2014 at 4:27 PM, John D. Ament johndam...@apache.org
wrote:
All,
Please find below the draft board report for December 2014. If anyone
has
any comments for the miscellaneous section please let me know. I still
have to address line lengths, but the report's all here.
Please feel free to edit the wiki with any proposed changes.
= Incubator PMC report for December 2014 =
=== Timeline ===
||Wed December 03 ||Podling reports due by end of day ||
||Sun December 07 ||Shepherd reviews due by end of day ||
||Sun December 07 ||Summary due by end of day ||
||Tue December 09 ||Mentor signoff due by end of day ||
||Wed December 10 ||Report submitted to Board ||
||Wed December 17 ||Board meeting ||
=== Shepherd Assignments ===
||Alan D. Cabrera ||Ignite ||
||Andrei Savu ||Drill ||
||Andrei Savu ||Johnzon ||
||Dave Fisher ||NPanday ||
||John Ament ||MRQL ||
||John Ament ||log4cxx2 ||
||Justin Mclean ||Tamaya ||
||Konstantin Boudnik ||Argus ||
||Matthew Franklin ||Brooklyn ||
||Raphael Bircher ||Kalumet ||
||Raphael Bircher ||Streams ||
||Roman Shaposhnik ||Sentry ||
||Ross Gardler ||Wave ||
||Suresh Marru ||Falcon ||
||Suresh Marru ||Lens ||
||Timothy Chen ||Ripple ||
||Timothy Chen ||Taverna ||
=== Report content ===
{{{
Incubator PMC report for December 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 36 podlings undergoing incubation. Two podlings
joined
us this month, NiFi and Tamaya. Three new IPMC members and two new
Shepherds joined our ranks as well.
* Community
New IPMC members:
Andrew L. Farris
Thejas Nair
Brock Noland
New Incubator Shepherds:
Timothy Chen
Andrew L. Farris
People who left the IPMC:
None
* New Podlings
Nifi
Tamaya
* Graduations
The board has motions for the following:
* Releases
The following releases were made since the last Incubator report:
apache-calcite-0.9.2-incubating
apache-twill-0.4.0-incubating
apache-parquet-format-2.2.0-incubating
apache-johnzon-0.2-incubating
apache-slider-0.60.0-incubating
metamodel-4.3.0-incubating
apache-aurora-0.6.0-incubating
* IP Clearance
Sling Sightly and XSS modules
* Legal / Trademarks
There are many on going Podling Name Search requests, with few being
closed.
Droids still has an open name search.
Falcon is procesing a name search currently.
Tamaya successfully cleared Podling Name Search.
* Infrastructure
SVN outage caused minor inconvenience to some podlings.
Argus/Ranger is facing some struggles with their rename.
* Miscellaneous
Summary of podling reports
* Still getting started at the Incubator
Re: [PROPOSAL] Silk as new Incubator project
Not saying anything on the proposal itself, I would be concerned because of the name Silk. There is this: http://lucidworks.com/product/integrations/silk/ which is related to Apache Solr and Lucene and also gets some attention. While it may not solve the same thing, I wouldn't use the name Silk at least because it somehow works with other Apache products. It could lead to confusion. If the podling is accepted, I suggest to consider this before resources are created -- Christian Grobmeier grobme...@gmail.com On Fri, Sep 19, 2014, at 07:21, Henry Saputra wrote: Hi Cos, Looks like a good start of the proposal. How would this project relate to compare to existing ones like Apache Spark, Storm, or Samza? Would love to have comparisons to existing ASF projects section to the proposal. Also, would you guys mind adding or soliciting more mentors? Seemed like most of initial committers have not been involved in ASF yet so may need some help to adjust to Apache way. - Henry On Thu, Sep 18, 2014 at 9:40 PM, Konstantin Boudnik c...@apache.org wrote: I would like to propose Silk as an Apache Incubator project. The new proposal is added to https://wiki.apache.org/incubator/SilkProposal and is duplicated below. -- Regards, Cos = Silk Apache Incubator Proposal = == Abstract == Apache Silk will be a unified In-Memory Data Fabric providing high-performance, distributed in-memory data management software layer between various data sources and user applications. == Proposal == Apache Silk is written mostly in Java and Scala with small amount of C++ code and will initially combine the following technologies under one unified umbrella: * In-Memory Data Grid * In-Memory Compute Grid * In-Memory Streaming Processing This unified in-memory fabric will provide high-performance, distributed in-memory software layer that sits in between various data sources and user applica tions. Data sources can include SQL RDBMS, NoSQL, or HDFS. Applications APIs will be available for Java (and Java-based scripting languages), Scala, C++ and .NET (C#). GridGain Systems, Inc. submits this proposal to donate its Apache 2.0-licensed open source project generally known as “GridGain In-Memory Computing Platform”, its source code, documentation, and websites to the Apache Software Foundation (“ASF”) with the goal of extending the vibrant open source community around this technology ultimately governed by “Apache Way”. Proposed Naming We have been advised by the ASF mentors that the name “Silk” may not be ideal because the name may be too generic and may not pass ASF legal check. Here are the alternatives that we have come up with and any of those will be acceptable for the project pending the ASF legal green light: * Apache Silk (preferable name) * Apache Sylk * Apache Memstor * Apache Ignite == Background Rationale == In-Memory Data Fabric is a natural and evolutionary consolidation of various “in-memory technologies” from the last decade. From simple local caching (JSR-107), to distributed caching, to data grids and databases, to streaming and plug-n-play acceleration - the in-memory space has grown quite dramatically. With rapid advances in NVRAM and significant price reduction of traditional DRAM on one hand, and growing sophistication and demand for faster data processing on another - many users of these silo-ed technologies and products started to look for a “strategic approach” to in-memory - an in-memory data fabric - that would provide suitable APIs for different types of payloads: from data caching, to data grids, to in-memory SQL data stores, to HPC, to streaming processing. With expensive and proprietary in-memory computing products from companies like Oracle, SAP, Microsoft, and IBM - the developers worldwide need an unhindered access to advanced open source in-memory software technology, the technology they can trust to develop with and deploy for critical applications. Current Status Apache Silk will be based on the technology that is currently developed by GridGain Systems and available under Apache 2.0 license (http://www.gridgain.org). The software has been in development since 2007 and in production since 2009. It is currently used by over 500 production deployments with over 1,000,000 downloads to date, and with over 20,000,000 GridGain nodes started in the last 5 years. == Initial Goals == The number one goal during ASF incubation will coalesce around building a true active and vibrant community governed by the “Apache Way”. The initial development goals for Silk primarily revolve around migrating the existing code base, documentation, and refactoring of the existing internal build, test release processes. We believe these initial goals are sufficiently difficult
Re: [DISCUSS] Incubator exit criteria
On 11 Aug 2014, at 10:14, Bertrand Delacretaz wrote: With this in mind, I would remove almost everything from the What is retirement section and keep just A retired project is a project which has been closed down for various reasons, instead of graduating as an Apache project. It is no longer developed in the Apache Incubator and does not have any other duties. The project's code might stay available on Apache servers, if all the required IP clearance requirements have been met. Retirement is a decision of the Incubator PMC, which usually delegates it to the incubating project's mentors. The opinion of the incubating project's community should of course be taken into account, but in the end it's the Incubator PMC which makes the decision. Interesting and I think this is really good (writes a guy who discussed the rules a lot). The problem we wanted to solve (i think) was: how can we keep our incubator list clean and be pro-active when it comes to housekeeping? If the IPMC would look at the reporting podlings each month and check if retirement is needed, then the above phrase might make perfect sense. Some might consider it unfair to be retired. In example, some projects as Wave look inactive but there is some life left. Retire or not? It's subjective. There is a good chance we keep some long-term running projects, but on the other hand... what would it matter? That being said, I would love if the other docs would get such an haircut as well. Cheers, Christian And also keep the steps to retirement section. -Bertrand [1] http://incubator.apache.org/guides/retirement.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de The Zen Programmer: http://bit.ly/12lC6DL @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubator exit criteria
On 12 Jul 2014, at 8:05, Roman Shaposhnik wrote: On Fri, Jul 11, 2014 at 1:18 AM, ant elder ant.el...@gmail.com wrote: As i've said i don't think thats a very good rule and doesn't seem like its really been thought through properly. For example, its kept saying that the podling would go to the ASF Attic but the Attic is only for TLPs so retired podlings don't go there. That's actually the part of the thread that I have a lot of interest in. Is there any reason not to use attic for hibernated podlings? I am not sure if there is a real reason, but maybe its because the attic currently contains only real ASF projects where all legal things were sorted out. With a podling coming in this might not be the case. We would need to check back with the Attic people if they can handle this. Otherwise I don't see a reason why we shouldn't use the attic, imho its the reason why its there. How about before adding a new rule to the policy page we just try it with a few of the old podlings first to see what happens and from that find what sort of rule might work? That would be fine too. Roman, would you mind to create an update patch and send it around here for some kind of discussing/voting? Then we would see how people feel. I think this thread is already to big to get the right attention. Thanks! Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de The Zen Programmer: http://bit.ly/12lC6DL @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubator exit criteria
On 24 Jun 2014, at 21:27, Rob Weir wrote: On Tue, Jun 24, 2014 at 9:57 AM, Upayavira u...@odoko.co.uk wrote: On Tue, Jun 24, 2014, at 12:02 PM, Christian Grobmeier wrote: On 24 Jun 2014, at 7:24, Roman Shaposhnik wrote: That said, reminding people of the release often and early thing is good to do, but also have in mind that incubator releases are very difficult to make. Unlike Christian (another Wave mentor :-) ), I am generally in support of this proposal. If a project cannot get a release out, then it suggests insufficient weight behind it. Releasing software is what the ASF is about. It is acceptable that a mature ASF project, one that is code-complete, doesn't release regularly, but an incubator project would not fall into that camp, therefore being able to say we can muster the resources to make a 'legally valid release' within a year seems eminently reasonable to me. https://blogs.apache.org/OOo/entry/an_apache_openoffice_timeline In total, from entering incubation to first release was 11 months and a week. So this confirms that a year, for most projects should be sufficient. But there could be exceptions, due to factors similar to those I listed above. But such exceptions should be rare. Indeed the OOo was an impressive amount of work. Reading comments from Upayavira and Rob, I am willing to support the relaxed proposal of Roman. I would prefer mine, but we can always do modifications as we see fit. As it seems i was the only sceptic, we can try to formulate a patch for our policies. Thanks! Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubator exit criteria
On 25 Jun 2014, at 10:38, ant elder wrote: On Wed, Jun 25, 2014 at 9:04 AM, Christian Grobmeier grobme...@gmail.com wrote: On 24 Jun 2014, at 21:27, Rob Weir wrote: On Tue, Jun 24, 2014 at 9:57 AM, Upayavira u...@odoko.co.uk wrote: On Tue, Jun 24, 2014, at 12:02 PM, Christian Grobmeier wrote: On 24 Jun 2014, at 7:24, Roman Shaposhnik wrote: That said, reminding people of the release often and early thing is good to do, but also have in mind that incubator releases are very difficult to make. Unlike Christian (another Wave mentor :-) ), I am generally in support of this proposal. If a project cannot get a release out, then it suggests insufficient weight behind it. Releasing software is what the ASF is about. It is acceptable that a mature ASF project, one that is code-complete, doesn't release regularly, but an incubator project would not fall into that camp, therefore being able to say we can muster the resources to make a 'legally valid release' within a year seems eminently reasonable to me. https://blogs.apache.org/OOo/entry/an_apache_openoffice_timeline In total, from entering incubation to first release was 11 months and a week. So this confirms that a year, for most projects should be sufficient. But there could be exceptions, due to factors similar to those I listed above. But such exceptions should be rare. Indeed the OOo was an impressive amount of work. Reading comments from Upayavira and Rob, I am willing to support the relaxed proposal of Roman. I would prefer mine, but we can always do modifications as we see fit. As it seems i was the only sceptic, we can try to formulate a patch for our policies. You aren't the only sceptic, i'm not enthusiastic about having such specific policy about release time frames either. Some projects are just slow, having a deadline like that could just make them get a release out of low quality without much care just to tick the box. Looking at clutch these are the current podlings and age which are older than a year and have no release: Aurora 267 BatchEE 265 DeviceMap 904 Kalumet 1009 Ripple 617 Samza 330 Streams 582 Usergrid 265 Wave 1299 Maybe their mentors should just go have a conversation with them about it? I can speak for Ripple already: there is a problem and will need a solution soon (integration into Cordova, or moving out to GitHub). ...ant --- http://www.grobmeier.de The Zen Programmer: http://bit.ly/12lC6DL @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubator exit criteria
On 24 Jun 2014, at 7:24, Roman Shaposhnik wrote: On Thu, Jun 19, 2014 at 6:22 AM, Christian Grobmeier grobme...@gmail.com wrote: I think its not enough to just look at release / committer additions. In the case of Wave, there was a committer addition in the past year. Still no commits, nor a release. Looking closer you would find that committer was added because there was some excitement around at that time, with a lot of plans. But then people were facing simply too much work for a small team, and the motivation then stopped. A deadline wouldn't not help to get out a release. That being said, I would like to re-suggest my initial thought with one modification: - no new committer for a year - AND no release for a year - AND less than 20 emails in a month on dev@ - AND less than 10 commits/jira modifications in a month - AND no way to change this in the next three months (in example: hackathon on horizon) Here's my personal struggle with two of the items on this list: - AND less than 20 emails in a month on dev@ - AND less than 10 commits/jira modifications in a month I can't fathom how a community that is that active can't put itself to a task of making a release. Let's assume the Wave project would have more activity. Maybe lets say they are operating with around 20 commits a month. It would be still difficult to release the code base within one year, because its really complex and needs a full refactoring. If we do not weight activity in general in, we reduce the exit criteria to: how fast can you do a release? And: if you don't manage to make a release in the first year - no matter how your product looks like - you might be thrown out. At the ends of the day, the release of an incubating project is NOT a glorious exercise in putting the final coat of paint on a flawless product. It is rather a very mundane way sharing technology with its users community. And after all, growing the user community is as important as growing the contributing community. It is only fair that IPMC gently reminds PPMC of that. I agree, but sometimes it's simply not possible to release. Actually, Wave *could* have released something, but nobody wants it to look like that. Let's assume they would release it now, which would be possible in theory. Let's say they would get 3 +1 from the PMC, which will be hard already. Then you have a released project, but the community is almost inactive. Heck, our TLPs practice it (where expectations are arguably higher) let alone Incubating projects. Take Hadoop as an example -- in order to make Hadoop 2.x successful the community decided to put an early alpha releases of Hadoop 2.0.x out to share the technology with its users. It was exactly the right decisions and ultimately it resulted in a much smoother 2.x.y series. As to my knowledge, some Hadoop-devs get financial support from companies. Projects like Ripple, Wave or Log4cxx do not have that financial support. In most cases, people work on these codebases in their prime time. For that reason I don't want to compare company-backed projects with prime-time projects. In short -- you don't have to make your releases GA. Alpha releases are just fine. Still you have to demonstrate that you are capable of sharing your work with the user community and doing an alpha/beta/gamma/YNH release is the only way to do it. I know what you mean, but I doubt this alone is a factor we should weight for an exit. People might struggle with a release but be healthy otherwise. People might get a release done, but have no community otherwise. That said, reminding people of the release often and early thing is good to do, but also have in mind that incubator releases are very difficult to make. Regards, Christian Thanks, Roman. - 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: [DISCUSS] Incubator exit criteria
On 19 Jun 2014, at 14:54, Marvin Humphrey wrote: On Wed, Jun 18, 2014 at 11:14 PM, Roman Shaposhnik r...@apache.org wrote: To this end, I'd like to prose a very simplistic criteria for a potential retirement from the incubator: unless both of of the following applies project get put to a retirement IPMC vote: * there has been a release in the past 12 months * there has been a bona-fine change to a community structure in the past 12 months +1 I think this is highly constructive, and I think the simplified criteria are a strong improvement. For those who are raising objections, consider that the retirement vote **may not pass**. Deadlines are great motivators. Just knowing that a retirement vote is looming should get those releases in the pipeline and those PPMC members proposed. Having to make the case that the podling should continue is also an excellent exercise which should serve to focus the podling on the goals of the Incubator and help to educate as to what it means to be an Apache project. That is worthwhile even for podlings who may be extremely active like Drill, or those who take a while to ramp up like Celix. Email activity and commits are not enough on their own -- they may well get you the votes to get you through the vote, but only a release or a community change should buy an automatic extension. I think its not enough to just look at release / committer additions. In the case of Wave, there was a committer addition in the past year. Still no commits, nor a release. Looking closer you would find that committer was added because there was some excitement around at that time, with a lot of plans. But then people were facing simply too much work for a small team, and the motivation then stopped. A deadline wouldn't not help to get out a release. That being said, I would like to re-suggest my initial thought with one modification: - no new committer for a year - AND no release for a year - AND less than 20 emails in a month on dev@ - AND less than 10 commits/jira modifications in a month - AND no way to change this in the next three months (in example: hackathon on horizon) At least three of these requirements must be true to cause a retirement vote. Thanks, Christian One suggestion: Make the community criteria an addition to the PPMC. Adding a Mentor would count. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de The Zen Programmer: http://bit.ly/12lC6DL @grobmeier GPG: 0xA5CC90DB - 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 16 Jun 2014, at 21:56, Konstantin Boudnik wrote: On Thu, Jun 12, 2014 at 11:31PM, Joe Brockmeier wrote: On 06/12/2014 07:56 PM, Roman Shaposhnik wrote: This suggests that ASF is being used as a GitHub of sorts. Are we comfortable with this? It's not really like GitHub. There is a community, at least a few people. It's definitely not about the cool tools, otherwise they would have gone to GitHub. We asked them recently, they declined and wanted to stay as they feel the ASF is the right place (see dev@ for reference) 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. For what it worth, I think you're right: a permanent incubator project doesn't make sense. For once, there's a lot of people mechanics involved into podlings' mentoring, reporting, etc. And it doesn't feel exactly right to forever handhold something that doesn't have an intention to evolve. The have the intention, but not the man power. There were phases with some excitement. If the IPMC wants to shut down the podling, then I would like to see us formulating a few rules when we do that. We should not shut a podling down just because we feel like that. Instead let us define what it means to evolve or what the intention to evolve means. Like: - no new committer for a year - AND no release for a year - AND less than 20 emails in a month on dev@ - AND less than 10 commits in a month - AND no way to change this in the next three months (in example: hackathon on horizon) (according to this, Wave would go to attic) Cheers, Christian Cos - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de The Zen Programmer: http://bit.ly/12lC6DL @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] fleece as new incubator project
+1 On 6 Jun 2014, at 9:31, Romain Manni-Bucau wrote: Following the discussion earlier, I'm calling a vote to accept Fleece as a new Incubator project. The proposal draft is available at: https://wiki.apache.org/incubator/Fleece, and is also included below. Vote is open for at least 72h and closes at the earliest on 09 June 09:30 GMT. [ ] +1 accept Fleece in the Incubator [ ] +/-0 [ ] -1 because... Here's my +1. Apache Fleece Proposal Abstract Apache Fleece is an implementation of JSR-353 (JavaTM API for JSON Processing). Proposal Apache Fleece will consist of a number of modules. Mainly an implementation of JSR-353 but also a set of usefule modules to help with the usage of JSR-353 (surely a mapping module and a jaxrs provider module). Background JSon being more and more important JavaEE 7 specified an API to read and create JSon objects/arrays. Apache Fleece builds on this specification a potential base to do Json at Apache (hopefully it will be integrated with CXF for instance). Rationale There is not yet a Json related project at Apache but a lot of projects rely on some specific implementions (jettison, jackson, others...). Proposing a default would be great. The other point is a set of Apache projects related to JavaEE (CXF, TomEE, Geronimo, Axis2...) will need an implementation. Having one built at Apache is a really nice to have. Initial Goals The initial goal of the Apache Fleece project is to get a JSR-353 compliant implementation Current Status Initial codebase was developped on github but designed to be integrated in Apache. Meritocracy Initial community will be mainly composed of already Apache committers so meritocracy is already something well known. Community Initial community will be composed of TomEE community for sure, hopefully CXF and potentially all JSon users of Apache. Initial committers - Romain Manni-Bucau (individual, ASF) - Jean-Louis Monteiro (individual, ASF) - Mark Struberg (individual, ASF member) - Gerhard Petracek (individual, ASF member) - David Blevins (individual, ASF member) - Sagara Gunathunga (ASF) Alignment Several Apache project will need a JSR-353 implementation. Having a project which can be shared is better than having a sub project of a particular project. Moreover this project makes sense alone since users can integrate it without any other dependencies and use it to read/generate Json in their project so it makes sense to create a dedicated project. Known Risks Main risk is to get a not so active project since the specification is not that big. Documentation There is no documentation to import today but it will be created using standard ASF tools (ASF CMS mainly). Initial Source Initial sources are on this git repository: https://github.com/rmannibucau/json-impl.git Source and IP Submission Plan Initial sources are under Apache license v2. Side note: it was really developed to be integrated in this project (without waiting it to be created). Required Resources Mailing Lists - - d...@fleece.incubator.apache.org - comm...@fleece.incubator.apache.org - priv...@fleece.incubator.apache.org Version Control It is proposed that the source code for the Apache Fleece project be hosted in the Apache Git repository, under the following directory: - git.apache.org/incubator-fleece.git Issue Tracking The following JIRA project would be required to track issues for the Apache Fleece project: - FLEECE Initial Committers - Romain Manni-Bucau - Jean-Louis Monteiro - Mark Struberg - Gerhard Petracek - David Blevins Sponsors Champion - Mark Struberg Nominated Mentors - Justin Mclean - Christian Grobmeier - Daniel Kulp Project Name Seems *Fleece* is the name which satisfies most of people but we can still ask for a new name if we feel it needed before being graduated. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau --- http://www.grobmeier.de The Zen Programmer: http://bit.ly/12lC6DL @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] json as new incubator project
On 1 Jun 2014, at 0:31, Justin Mclean wrote: Hi, About the name any proposition is welcomed. I though to brace BTW. Apache Argonaut sounds good but I assume that name is in common use so perhaps Argus (the ship builder), or perhaps Fleece? I actually once wrote an article called Json and the golden fleece (just in german), so I would like this reference too. I was a little bit involved in that JSR (not very active to be honest) and developed a JSON component myself before the JSR was in the making, so I have an interest in it. Unfortunately I have very limited time to help actively. Anyway if there is trouble to finding an additional mentor, I will step up. On the proposal i see two sections called initial committers and one core developer. I would like to suggest to remove the section core developer and on of the initial committers blocks. I would like to also suggest to look into Noggit: http://svn.apache.org/repos/asf/labs/noggit/ which is more or less used in a later form in Solr. As sponsoring entity it might even make sense to look at Apache Commons, as the component will be small. It would also relax the naming problem, as it would most likely be named Apache Commons Json then. Cheers, Christian Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de The Zen Programmer: http://bit.ly/12lC6DL @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] json as new incubator project
Hi, commons might be an option. But we still would need to go through the incubator. Otoh Commons proved not to be very JSR friendly to be honest. We had this discussion for BVal etc, and recent JCS discussions where also not in favour for it. I'd be happy to host it over there though. there is no rush luckily. But you are right that Commons is not always the best option. And if we have a big community and maybe later other json stuff at hand, it makes sense to aim at tld. Christian, txs for bringing up noggit. Didn't even know it. How far is it away from the SOLR version? And to which degree does it cover JSON? Anyone who knows the SOLR code think we could split this out form SOLR if this version is better? here is the latest stable: https://github.com/yonik/noggit Looking at Solrs code here: https://svn.apache.org/repos/asf/lucene/dev/trunk/solr/core/src/java/org/apache/solr/handler/loader/JsonLoader.java it seems like it is using the latest stable (or one of them) - I concluded that by looking at the namespace. Noggits License is AL2.0, so it should be no problem to use some of the code. However i once digged through it, while i wrote my own small lib: https://github.com/grobmeier/jjson It turned out that it has a great approach, but wasn't that easy to hack. That's why I stopped merging the two code bases and mine stayed pretty dump. Romains code is pretty good already. But it uses antlr for parsing. Not sure how much this is a blocker when it comes to performance tuning and cutting down the size of the JAR yet. Actually I don't like antlr that much and would love to see it go. I totally enjoy json libs with zero dependencies. Cheers Christian LieGrue, strub On Sunday, 1 June 2014, 10:47, Christian Grobmeier grobme...@gmail.com wrote: On 1 Jun 2014, at 0:31, Justin Mclean wrote: Hi, About the name any proposition is welcomed. I though to brace BTW. Apache Argonaut sounds good but I assume that name is in common use so perhaps Argus (the ship builder), or perhaps Fleece? I actually once wrote an article called Json and the golden fleece (just in german), so I would like this reference too. I was a little bit involved in that JSR (not very active to be honest) and developed a JSON component myself before the JSR was in the making, so I have an interest in it. Unfortunately I have very limited time to help actively. Anyway if there is trouble to finding an additional mentor, I will step up. On the proposal i see two sections called initial committers and one core developer. I would like to suggest to remove the section core developer and on of the initial committers blocks. I would like to also suggest to look into Noggit: http://svn.apache.org/repos/asf/labs/noggit/ which is more or less used in a later form in Solr. As sponsoring entity it might even make sense to look at Apache Commons, as the component will be small. It would also relax the naming problem, as it would most likely be named Apache Commons Json then. Cheers, Christian Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de The Zen Programmer: http://bit.ly/12lC6DL @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de The Zen Programmer: http://bit.ly/12lC6DL @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] json as new incubator project
On 1 Jun 2014, at 12:21, Romain Manni-Bucau wrote: Hi Christian, updated the proposal page according to your comments (added you as mentor for now and merged initial/core dev parts). Will try to import noggit parser (actually I was in thr process of removing antlr which was mainly here to get started quickly so if noggit avoids me to rewrite a new state machine it will be very nice) I keep fingers crossed. Not sure if it will help you though, but it is really fast in what it does. Cheers Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-06-01 10:46 GMT+02:00 Christian Grobmeier grobme...@gmail.com: On 1 Jun 2014, at 0:31, Justin Mclean wrote: Hi, About the name any proposition is welcomed. I though to brace BTW. Apache Argonaut sounds good but I assume that name is in common use so perhaps Argus (the ship builder), or perhaps Fleece? I actually once wrote an article called Json and the golden fleece (just in german), so I would like this reference too. I was a little bit involved in that JSR (not very active to be honest) and developed a JSON component myself before the JSR was in the making, so I have an interest in it. Unfortunately I have very limited time to help actively. Anyway if there is trouble to finding an additional mentor, I will step up. On the proposal i see two sections called initial committers and one core developer. I would like to suggest to remove the section core developer and on of the initial committers blocks. I would like to also suggest to look into Noggit: http://svn.apache.org/repos/asf/labs/noggit/ which is more or less used in a later form in Solr. As sponsoring entity it might even make sense to look at Apache Commons, as the component will be small. It would also relax the naming problem, as it would most likely be named Apache Commons Json then. Cheers, Christian Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de The Zen Programmer: http://bit.ly/12lC6DL @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de The Zen Programmer: http://bit.ly/12lC6DL @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator PMC/Board report for Jun 2014 ([ppmc])
Thanks John Marvin! On 29 May 2014, at 19:31, Marvin Humphrey wrote: On Wed, May 28, 2014 at 5:51 PM, John D. Ament john.d.am...@gmail.com wrote: :-) Apologies on my part. I think I got the other podlings, though hopefully they will let us know. I've updated ripple at this point to be back in group 1. Looks good to me, John! Thanks again for all your help last month working through the challenges, and for taking the initiative to start this month's report as well. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de The Zen Programmer: http://bit.ly/12lC6DL @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Fwd: Incubator PMC/Board report for Jun 2014 ([ppmc])
FYI: Ripple reported in May: http://wiki.apache.org/incubator/May2014 We are also not included in the report-next-month section: http://incubator.apache.org/report-next-month.html#ripple This says next report is July: http://incubator.apache.org/report-groups.txt Any ideas what went wrong or what I could check? From: Marvin no-re...@apache.org To: d...@ripple.incubator.apache.org Subject: Incubator PMC/Board report for Jun 2014 ([ppmc]) Date: Wed, 28 May 2014 14:15:04 + (UTC) Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 18 June 2014, 10:30:30:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Jun 4th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/June2014 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Proposal] Add me as Mentor for ODF Toolkit Podling
On 20 May 2014, at 19:07, Rob Weir wrote: I looked around and did not see a process defined for adding a Mentor to a podling. I see how they are added at podling initiation, but not after. So apologies if I'm missing something. It appears that we have at present zero active Mentors, so even with the experimental release process we're unable to move forward, since that requires Mentor sign off on the release manifest/checklist. I haven't heard of a process defined. I did something similar in the past by notifying the list and asking the community if they would be fine with me joining, and that's it. As member of this PMC is think there should not be an formalities for you to help podlings who need it. Just make sure to add your name to the mentors list, since reporting templates will be generated from there. Kind regards, Christian I am able and willing to help here. Regards, -Rob - 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
Log4cxx project bootstrapped
Hello,
just a short message to let you know i moved the log4cxx tree to the
incubation tree and committed this auth:
Index: asf-authorization-template
===
--- asf-authorization-template (Revision 892487)
+++ asf-authorization-template (Arbeitskopie)
@@ -241,6 +241,7 @@
libcloud-pmc={reuse:pit-authorization:libcloud-pmc}
logging-pmc={reuse:pit-authorization:logging-pmc}
logging={ldap:cn=logging,ou=groups,dc=apache,dc=org}
+log4cxx=grobmeier,sdeboy,fseydoux,chand,nickwilliams,tschoening,rhys,joseph,alexz
lucene={ldap:cn=lucene,ou=groups,dc=apache,dc=org}
lucene-pmc={reuse:pit-authorization:lucene-pmc}
lucene-c=ehatcher,rooneg,pquerna
@@ -865,6 +866,9 @@
[/incubator/lcf]
@lucene-connectors = rw
+[/incubator/log4cxx]
+@log4cxx = rw
+
With that, the podling is ready to go
Cheers,
Christian
---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: Log4cxx project bootstrapped
On 2 Jan 2014, at 16:17, sebb wrote:
On 2 January 2014 10:28, Christian Grobmeier grobme...@gmail.com
wrote:
Hello,
just a short message to let you know i moved the log4cxx tree to the
incubation tree and committed this auth:
This has caused a problem for the projects.apache.org site.
Please update the location of the DOAP.
Thanks, as I already responded by PM, it has been fixed ealier today
Index: asf-authorization-template
===
--- asf-authorization-template (Revision 892487)
+++ asf-authorization-template (Arbeitskopie)
@@ -241,6 +241,7 @@
libcloud-pmc={reuse:pit-authorization:libcloud-pmc}
logging-pmc={reuse:pit-authorization:logging-pmc}
logging={ldap:cn=logging,ou=groups,dc=apache,dc=org}
+log4cxx=grobmeier,sdeboy,fseydoux,chand,nickwilliams,tschoening,rhys,joseph,alexz
lucene={ldap:cn=lucene,ou=groups,dc=apache,dc=org}
lucene-pmc={reuse:pit-authorization:lucene-pmc}
lucene-c=ehatcher,rooneg,pquerna
@@ -865,6 +866,9 @@
[/incubator/lcf]
@lucene-connectors = rw
+[/incubator/log4cxx]
+@log4cxx = rw
+
With that, the podling is ready to go
Cheers,
Christian
---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB
-
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
---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Enable Release Checklist Experiment
+1, good job. On 13 Dec 2013, at 21:59, Marvin Humphrey wrote: Greetings, As the next step in our ongoing efforts to reform the release voting process, I propose that we run an experiment allowing the PPMC members of select podlings to earn binding votes under limited circumstances by completing a release checklist. For participating podlings, the Incubator's release management guide... http://incubator.apache.org/guides/releasemanagement.html ... would be supplanted by the following documents: http://incubator.apache.org/guides/release_manifest.txt http://incubator.apache.org/guides/release.html The scope of this VOTE is limited to approving the following patch to our policy page: https://paste.apache.org/k4vJ Here is the patch content minus markup: 2013 Alternate Release Voting Process Select podlings pre-cleared by a majority vote of the IPMC MAY participate in an alternate release voting process: Should a Podling decide it wishes to perform a release, the Podling SHALL hold a vote on the Podling's dev list and create a permanently archived Release Manifest as described in the Experimental Release Guide. At least three +1 votes from PPMC members are required (see the Apache Voting Process page). If the majority of PPMC votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's general list and formally request the Incubator PMC approve such a release. Formal approval requires three binding +1 votes and more positive than negative votes. Votes cast by members of the Incubator PMC are always binding. For all releases after the first, votes cast by members of the PPMC are binding if a Mentor approves the Release Manifest. Please note that the proposed change is both incremental and reversible: * It is incremental because podlings must be opted in by vote of the IPMC to participate. * It is reversible because once the experiment has run its course the policy change can be reverted with zero impact through lazy consensus. Those who may have questions about the legitimacy of allowing binding votes from non-IPMC members should see this post from Roy Fielding: http://s.apache.org/v7 Please vote: [ ] +1 Yes, apply the patch enabling the experiment. [ ] -1 No, do not apply the patch enabling the experiment. This majority VOTE will run for 7 days and will close at 13:00 PST on Friday, December 20, 2013. Votes cast by members of the Incubator PMC are binding. Here is my own +1. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de The Zen Programmer: http://bit.ly/12lC6DL @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Log4cxx for Incubation
my own +1 On 4 Dec 2013, at 20:48, Christian Grobmeier wrote: Dear all, please cast your vote to accept Log4cxx for incation. The proposal is pasted below, but can be found here too: https://wiki.apache.org/incubator/Log4cxxProposal This vote will close in 72 hours. [ ] +1 Accept Log4cxx into the Incubator [ ] -1 Don't accept Log4cxx because... Thanks, Christian Log4cxx Proposal Apache log4cxx is a subproject of Apache Logging Services. It is a logging framework for C++ patterned after Apache log4j. Apache log4cxx uses Apache Portable Runtime for most platform-specific code and should be usable on any platform supported by APR. The current website is visible at: http://logging.apache.org/log4cxx/ The original developers of the project went inactive and the project was not maintained for quite a while. The Logging PMC thought about moving the project to the attic but a few users were objecting. This proposal is to create a new community around Log4cxx. Rationale Currently Log4cxx appears to be pretty stable without many competitors. It has a small but dedicated user base. Current Status Meritocracy Log4cxx was developed at the Apache Software Foundation. Its SVN history reaches back to 2003 but there was even previous development on CVS. While the interested developers were not involved in the past efforts there is consens that Apache Logging Services is the best place for the future development of Log4cxx. Alignment Goal of the incubation is to reboot the community around log4cxx. Known Risks Orphaned Products With six interested developers and one of them being a committer to Apache Logging Services the risk can be considered low. Inexperience with Open Source One of the committers is already committer to Apache Logging. The others were already subscribed to the mailing list and actively participating on the discussions. Homogeneous Developers The list of initial committers are geographically distributed across the world with no one company being associated with a majority of the developers. Reliance on Salaried Developers None of the initial committers is paid to develop code for this project. However it has been expressed that the framework is in use at the companies of the developers. CCLAs will be submitted were relevant. Relationships with Other Apache Products So far no other Apache products are known which use Log4cxx. Apache Log4j was the prototype for creating Log4cxx. An Excessive Fascination with the Apache Brand n/a. Log4cxx was developed at the ASF. Initial Source The initial source was developed at the ASF and has already a clean IP and is distributed with AL 2.0. Source and Intellectual Property Submission Plan The source code is available here: https://svn.apache.org/repos/asf/logging/log4cxx External Dependencies None. Cryptography The project does not handle cryptography in any way. Required Resources We would like to use the already existing mailinglists: http://logging.apache.org/log4cxx/mail-lists.html We would like to move the source code folder from: https://svn.apache.org/repos/asf/logging/log4cxx to: https://svn.apache.org/repos/asf/incubator/log4cxx Issue tracking: We would like to use: https://issues.apache.org/jira/browse/LOGCXX which already exists. We would like to move the current website to: http://incubator.apache.org/log4cxx/ As the main Logging site is created with the Apache CMS, we would like to establish a similar process for log4cxx. Initial Committers Names of initial committers - in alphabetical order - with current ASF status: Florian Seydoux florianseyd...@gmail.com (ICLA signed) chand priyankara ch...@engineering.com (ICLA signed) Nick Williams nickwilli...@apache.org (Apache Logging Committer) Thorsten Schöning tschoen...@am-soft.de Rhys Ulerich rhys.uler...@gmail.com (ICLA signed) Joseph Southwell jos...@southwell.org (ICLA signed) Alexandru Zbârcea zbarce...@gmail.com (ICLA signed) Sponsors Champion Christian Grobmeier grobmeier at apache dot org (Member) Nominated Mentors Christian Grobmeier grobmeier at apache dot org Scott Deboy sdeboy at apache dot org Sponsoring Entity Apache Logging PMC --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Accept Log4cxx for Incubation
This vote passes with 4 +1 from: * Chris Mattmann * Marvin Humphrey * Scott Deboy * Christian Grobmeier I am going to set up the new podling the next days. On 4 Dec 2013, at 20:48, Christian Grobmeier wrote: Dear all, please cast your vote to accept Log4cxx for incation. The proposal is pasted below, but can be found here too: https://wiki.apache.org/incubator/Log4cxxProposal This vote will close in 72 hours. [ ] +1 Accept Log4cxx into the Incubator [ ] -1 Don't accept Log4cxx because... Thanks, Christian Log4cxx Proposal Apache log4cxx is a subproject of Apache Logging Services. It is a logging framework for C++ patterned after Apache log4j. Apache log4cxx uses Apache Portable Runtime for most platform-specific code and should be usable on any platform supported by APR. The current website is visible at: http://logging.apache.org/log4cxx/ The original developers of the project went inactive and the project was not maintained for quite a while. The Logging PMC thought about moving the project to the attic but a few users were objecting. This proposal is to create a new community around Log4cxx. Rationale Currently Log4cxx appears to be pretty stable without many competitors. It has a small but dedicated user base. Current Status Meritocracy Log4cxx was developed at the Apache Software Foundation. Its SVN history reaches back to 2003 but there was even previous development on CVS. While the interested developers were not involved in the past efforts there is consens that Apache Logging Services is the best place for the future development of Log4cxx. Alignment Goal of the incubation is to reboot the community around log4cxx. Known Risks Orphaned Products With six interested developers and one of them being a committer to Apache Logging Services the risk can be considered low. Inexperience with Open Source One of the committers is already committer to Apache Logging. The others were already subscribed to the mailing list and actively participating on the discussions. Homogeneous Developers The list of initial committers are geographically distributed across the world with no one company being associated with a majority of the developers. Reliance on Salaried Developers None of the initial committers is paid to develop code for this project. However it has been expressed that the framework is in use at the companies of the developers. CCLAs will be submitted were relevant. Relationships with Other Apache Products So far no other Apache products are known which use Log4cxx. Apache Log4j was the prototype for creating Log4cxx. An Excessive Fascination with the Apache Brand n/a. Log4cxx was developed at the ASF. Initial Source The initial source was developed at the ASF and has already a clean IP and is distributed with AL 2.0. Source and Intellectual Property Submission Plan The source code is available here: https://svn.apache.org/repos/asf/logging/log4cxx External Dependencies None. Cryptography The project does not handle cryptography in any way. Required Resources We would like to use the already existing mailinglists: http://logging.apache.org/log4cxx/mail-lists.html We would like to move the source code folder from: https://svn.apache.org/repos/asf/logging/log4cxx to: https://svn.apache.org/repos/asf/incubator/log4cxx Issue tracking: We would like to use: https://issues.apache.org/jira/browse/LOGCXX which already exists. We would like to move the current website to: http://incubator.apache.org/log4cxx/ As the main Logging site is created with the Apache CMS, we would like to establish a similar process for log4cxx. Initial Committers Names of initial committers - in alphabetical order - with current ASF status: Florian Seydoux florianseyd...@gmail.com (ICLA signed) chand priyankara ch...@engineering.com (ICLA signed) Nick Williams nickwilli...@apache.org (Apache Logging Committer) Thorsten Schöning tschoen...@am-soft.de Rhys Ulerich rhys.uler...@gmail.com (ICLA signed) Joseph Southwell jos...@southwell.org (ICLA signed) Alexandru Zbârcea zbarce...@gmail.com (ICLA signed) Sponsors Champion Christian Grobmeier grobmeier at apache dot org (Member) Nominated Mentors Christian Grobmeier grobmeier at apache dot org Scott Deboy sdeboy at apache dot org Sponsoring Entity Apache Logging PMC --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache Sirona 0.1-incubating
On 9 Dec 2013, at 6:05, Marvin Humphrey wrote: On Sun, Dec 8, 2013 at 8:20 PM, Olivier Lamy ol...@apache.org wrote: So please instead of discussing again about procedures. Just discuss about the release :-) /me trying to rock the boat Sirona has FIVE Mentors, plus another committer who is on the IPMC. Only two of you have voted: you and Jean-Baptiste Onofré. The project just entered incubation two months ago. Where is everybody? When I joined as committer I mentioned that I am in time trouble at the moment. Currently I consider to step out as I am not able to follow as closely as I would wish. Cheers Christian Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Engaging Mentors
Taylor, your mentors should read the mailing lists. Why I would not expect to get answers when a question is hidden in a technical detail question, a subject line with [MENTOR] in it should draw attention. I expect mentors to read all subject lines. Other tags mentors should watch is [VOTE] or [DISCUSS] or anything on private@. However we have often the case that mentors are awol. If you are not able to get anything out from your mentors please hit general@ again with your question. Cheers, Christian On 5 Dec 2013, at 8:42, P. Taylor Goetz wrote: Now that Storm has gotten its final non-Apache release (0.9.0) out the door [1], we’re ready to dig in and focus entirely on migrating to Apache. Until now, we’ve not been all that focused on embracing the Apache process (we’ve been trying to get 0.9.0 out to a waiting community), and so haven’t needed much from our mentors (i.e. I’m not finding fault with our mentors at all.). No that that’s changed, what’s the best way to catch our mentors’ attention? Is it just an email to dev@ with a subject line prepended with “[MENTORS]”, or is there a better way? Just looking for a way to separate signal from noise for our mentors. - Taylor [1] http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201312.mbox/%3C820508E3-8377-4B70-A58B-A15E87F3B319%40gmail.com%3E --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Ripple reports
On 5 Dec 2013, at 6:41, David Crossley wrote: Marvin Humphrey wrote: Marvin Humphrey mar...@rectangular.com wrote: Christian Grobmeier grobme...@gmail.com wrote: i just added the ripple report for december (its the same as november). We were to late in november. however the report template generator didn't include us in generation. OK, I see what happened. Ripple received reminders on ripple-dev on November 22 and November 28 insisting that Ripple needed to file a December2013 report. This happened because at the time, Ripple still had the monthly tag in podlings.xml. Part of the Chair's workflow is to remove expired monthly attributes from podlings.xml. I didn't get to that until shortly after the November 28 reminders were sent out. In all of the documentation and tools, i have been trying to encourage the podlings to look after their own metadata. Sure, we do seem to need a backstop, but please can we continue to encourage them to look after their own stuff. Well it happens that a mentor (in this case me) did mess up something too. I take it on my own back that i have not educated Ripple to deal with podling.xmls or not worked with the data myself. Anyway, thanks Marvin for helping me identify the issue. Cheers -David https://svn.apache.org/viewvc/incubator/public/trunk/content/podlings.xml?r1=1545305r2=1546281 Probably the best way to prevent this from happening in the future is to move this Chair task (along with a few others like creating the wiki template) to just after filing the last report. I can do that by rejiggering the blocks in report_runbook.py. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Log4cxx incubation
Hi, I would appreciate comments if you believe my proceeding is OK. Since there are no other interested mentors: would you folks object if we start anyway? I feel a bit alone with my proposal. Given the size of the IPMC thats a bit sad. Thanks, Christian On 28 Nov 2013, at 10:50, Christian Grobmeier wrote: Dear Incubator people, I just added a new proposal for the incubation of log4cxx: https://wiki.apache.org/incubator/Log4cxxProposal This project was inactive for a good while at logging.apache.org. When we discussed the attic, a lot of people showed their interest and willingness to work on it. Due to the size of the new team I think it is to start a new incubation. Of course I am willing to step up as Champion and Mentor. Others here who have an interest in logging in C are invited to step up as a mentor too. The goal is to reboot this project and move it back to logging.a.o as soon as the team is ready. As resources are already there, I would like to simply reuse them and just move the svn repos to the incubator tree. Please let me know about your thoughts. Thanks, Christian --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Log4cxx incubation
Thanks a lot for your comments Marvin. They were very encouraging. Scott Deboy just pinged me that he joins the ranks of log4cxx mentors. He is also is involved in Apache Logging. I am going to call a vote! On 4 Dec 2013, at 20:12, Marvin Humphrey wrote: On Wed, Dec 4, 2013 at 12:30 AM, Christian Grobmeier grobme...@gmail.com wrote: Since there are no other interested mentors: would you folks object if we start anyway? Sounds like a throwback to the early days of the Incubator when I hear there was only one Mentor per podling. :) +1, go ahead! The podling will probably have a comparatively easy incubation, since several aspects are already taken care of. Not having to deal with IP clearance makes things much simpler. Depending on how quickly the new community masters the Apache Way, incubation could be over within a few months. I don't see any problem with what you've proposed as far as reusing existing resources. We might not make such exceptions every time, but they seem fine in this unusual case. It's nice that there is minimal impact on Infra. I feel a bit alone with my proposal. Given the size of the IPMC thats a bit sad. This seems like an excellent opportunity for people who are less experienced or perhaps not members of the IPMC yet to try their hand at mentoring. Given your expertise and dedication, someone with less experience could offer advice to the podling and feel confident that you would be there to back them up or provide subtle correction as necessary. Be sure to let private@incubator know if anybody shows up to help and deserves to be nominated for the IPMC. :) Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Accept Log4cxx for Incubation
Dear all, please cast your vote to accept Log4cxx for incation. The proposal is pasted below, but can be found here too: https://wiki.apache.org/incubator/Log4cxxProposal This vote will close in 72 hours. [ ] +1 Accept Log4cxx into the Incubator [ ] -1 Don't accept Log4cxx because... Thanks, Christian Log4cxx Proposal Apache log4cxx is a subproject of Apache Logging Services. It is a logging framework for C++ patterned after Apache log4j. Apache log4cxx uses Apache Portable Runtime for most platform-specific code and should be usable on any platform supported by APR. The current website is visible at: http://logging.apache.org/log4cxx/ The original developers of the project went inactive and the project was not maintained for quite a while. The Logging PMC thought about moving the project to the attic but a few users were objecting. This proposal is to create a new community around Log4cxx. Rationale Currently Log4cxx appears to be pretty stable without many competitors. It has a small but dedicated user base. Current Status Meritocracy Log4cxx was developed at the Apache Software Foundation. Its SVN history reaches back to 2003 but there was even previous development on CVS. While the interested developers were not involved in the past efforts there is consens that Apache Logging Services is the best place for the future development of Log4cxx. Alignment Goal of the incubation is to reboot the community around log4cxx. Known Risks Orphaned Products With six interested developers and one of them being a committer to Apache Logging Services the risk can be considered low. Inexperience with Open Source One of the committers is already committer to Apache Logging. The others were already subscribed to the mailing list and actively participating on the discussions. Homogeneous Developers The list of initial committers are geographically distributed across the world with no one company being associated with a majority of the developers. Reliance on Salaried Developers None of the initial committers is paid to develop code for this project. However it has been expressed that the framework is in use at the companies of the developers. CCLAs will be submitted were relevant. Relationships with Other Apache Products So far no other Apache products are known which use Log4cxx. Apache Log4j was the prototype for creating Log4cxx. An Excessive Fascination with the Apache Brand n/a. Log4cxx was developed at the ASF. Initial Source The initial source was developed at the ASF and has already a clean IP and is distributed with AL 2.0. Source and Intellectual Property Submission Plan The source code is available here: https://svn.apache.org/repos/asf/logging/log4cxx External Dependencies None. Cryptography The project does not handle cryptography in any way. Required Resources We would like to use the already existing mailinglists: http://logging.apache.org/log4cxx/mail-lists.html We would like to move the source code folder from: https://svn.apache.org/repos/asf/logging/log4cxx to: https://svn.apache.org/repos/asf/incubator/log4cxx Issue tracking: We would like to use: https://issues.apache.org/jira/browse/LOGCXX which already exists. We would like to move the current website to: http://incubator.apache.org/log4cxx/ As the main Logging site is created with the Apache CMS, we would like to establish a similar process for log4cxx. Initial Committers Names of initial committers - in alphabetical order - with current ASF status: Florian Seydoux florianseyd...@gmail.com (ICLA signed) chand priyankara ch...@engineering.com (ICLA signed) Nick Williams nickwilli...@apache.org (Apache Logging Committer) Thorsten Schöning tschoen...@am-soft.de Rhys Ulerich rhys.uler...@gmail.com (ICLA signed) Joseph Southwell jos...@southwell.org (ICLA signed) Alexandru Zbârcea zbarce...@gmail.com (ICLA signed) Sponsors Champion Christian Grobmeier grobmeier at apache dot org (Member) Nominated Mentors Christian Grobmeier grobmeier at apache dot org Scott Deboy sdeboy at apache dot org Sponsoring Entity Apache Logging PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Ripple reports
Hi, i just added the ripple report for december (its the same as november). We were to late in november. however the report template generator didn't include us in generation. can this be fixed for the next time or do we simply roll back to report in 2 months (no problem with that) Cheers --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Log4cxx incubation
Hi Justin, both - Scott and me - are ASF members and IPMC members. The policy has not changed. Cheers, Christian On 4 Dec 2013, at 22:10, Justin Mclean wrote: Hi, I thought you needed to be a IPMC member in order to be a mentor. [1] states that Mentors MUST be on the IPMC. If you're an ASF member you can ask to be on the IPMC [2]. So by people above I assume you mean ASF/IPMC members or has this changed? Thanks, Justin 1.http://incubator.apache.org/guides/mentor.html 2. http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29 --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Log4cxx incubation
zero feedback? :-) On 28 Nov 2013, at 10:50, Christian Grobmeier wrote: Dear Incubator people, I just added a new proposal for the incubation of log4cxx: https://wiki.apache.org/incubator/Log4cxxProposal This project was inactive for a good while at logging.apache.org. When we discussed the attic, a lot of people showed their interest and willingness to work on it. Due to the size of the new team I think it is to start a new incubation. Of course I am willing to step up as Champion and Mentor. Others here who have an interest in logging in C are invited to step up as a mentor too. The goal is to reboot this project and move it back to logging.a.o as soon as the team is ready. As resources are already there, I would like to simply reuse them and just move the svn repos to the incubator tree. Please let me know about your thoughts. Thanks, Christian --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: How long is too long in the incubator?
On 30 Nov 2013, at 2:16, Marvin Humphrey wrote: On Fri, Nov 29, 2013 at 2:25 PM, Upayavira u...@odoko.co.uk wrote: If a podling has been in the incubator for some years, but is struggling to reach critical mass, is there any reason not to just let the podling be? If the mentors stick to the project there is only little problem (I think). On the other hand we should avoid to become some kind of scm hoster. The incubator has a specific goal and if project enters I believe it should work to reach these goals. If the goals are not reached like in the case you might have in mind, i believe we need to ask: why? Are you on the right place? Sometimes such questions bring up a few problems, sometimes not. Just for the record, I have no problem this project stays longer. But I will continue asking if there is life in the podling if there is no progress in future. Hope my recent emails didn't read like that I absolutely want to throw them out. Its not like that. Thanks! Christian We talked this subject through in November 2011, under the heading Actively retiring projects: http://markmail.org/message/4cagxwofrsmkmsek The biggest change we made in the wake of that discussion was to graduate small but stable communities more aggressively. Isis was one[1]. VXQuery, with 4-5 active PPMC members, is likely to graduate under similar criteria. Another change which has happened gradually over the last few years is that we have cast aside the stigma associated with leaving the Incubator. Vestiges of a less tolerant mentality from the early days persist in our policy page[2]: http://incubator.apache.org/incubation/Incubation_Policy.html#Termination+of+a+Podling Termination of a Podling If you receive a recommendation for termination then you have a problem. I have always thought that shaming projects which don't complete incubation was unjust, bad policy, and unbecoming of a volunteer-driven public charity. Now that we have softened our attitudes, recognizing that all software products have a lifecycle and emphasizing retirement over termination, the Incubator has become more self-cleaning. Back in 2011, the Incubator had a significant problem with accumulating stalled podlings. Today, we have more room to consider podlings in difficult circumstances on a case-by-case basis. Marvin Humphrey [1] http://markmail.org/message/3aiwjgocoqeojeop [2] One of these days I'm going to call a VOTE on changing that language. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Log4cxx incubation
These are all people who are not known to Logging. And so far I don't see if anybody else at Logging has the time or knowledge to oversee incoming patches. I would like to treat it as a new incubation: new people, new community, new things to learn. I would like to give them write access directly, because I can't judge on the patches myself (zero c++ knowledge). Does it explain why I would like to mentor them in the community? On 30 Nov 2013, at 21:30, sebb wrote: I'm not sure why the Incubator needs to be involved at all here. On 30 November 2013 19:30, Christian Grobmeier grobme...@gmail.com wrote: zero feedback? :-) On 28 Nov 2013, at 10:50, Christian Grobmeier wrote: Dear Incubator people, I just added a new proposal for the incubation of log4cxx: https://wiki.apache.org/incubator/Log4cxxProposal This project was inactive for a good while at logging.apache.org. When we discussed the attic, a lot of people showed their interest and willingness to work on it. Due to the size of the new team I think it is to start a new incubation. Of course I am willing to step up as Champion and Mentor. Others here who have an interest in logging in C are invited to step up as a mentor too. The goal is to reboot this project and move it back to logging.a.o as soon as the team is ready. As resources are already there, I would like to simply reuse them and just move the svn repos to the incubator tree. Please let me know about your thoughts. Thanks, Christian --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB - 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 --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[PROPOSAL] Log4cxx incubation
Dear Incubator people, I just added a new proposal for the incubation of log4cxx: https://wiki.apache.org/incubator/Log4cxxProposal This project was inactive for a good while at logging.apache.org. When we discussed the attic, a lot of people showed their interest and willingness to work on it. Due to the size of the new team I think it is to start a new incubation. Of course I am willing to step up as Champion and Mentor. Others here who have an interest in logging in C are invited to step up as a mentor too. The goal is to reboot this project and move it back to logging.a.o as soon as the team is ready. As resources are already there, I would like to simply reuse them and just move the svn repos to the incubator tree. Please let me know about your thoughts. Thanks, Christian --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Project reboot proposals - any guidance?
Hey Nick I spoke with Tammo about this while we had a virtual coffee recently. However I don't know about similar cases so much. Basically I don't see lot of risk from a legal standpoint and would give my +1 quickly. But of course it would be interesting for me about the motivations. I mean, the project was almost dead and now a few people want it to be revived. Why? Was the problem in the previous project to less interest? Problems in the community? As I said, this would be interesting but personally I don't consider this information necessary. What I don't know: do the current resources need to move to an *.incubator.a.o space? I believe this is unnecessary overhead, but maybe other have an idea on that too. So far, I would +1 this proposal. Mentors good, Champion good and people come from the community. Legals are all done and almost no resources will be wasted to set this up. Cheers On 24 Oct 2013, at 17:26, Nick Burch wrote: Hi All I'm currently helping the XMLBeans community put together a proposal to reboot their project, which is otherwise destined for the attic. However, while I've helped a few new projects enter the incubator in the past, I've never tried helping with a reboot. As such, I'm not quite sure if the initial proposal is quite right or not. Do we have any guidance on what a reboot proposal should and shouldn't contain? If not, any chance people could cast any eye over the proposal, and either fix stuff if they can, or flag it for work if not? The proposal is at: https://wiki.apache.org/incubator/XMLBeansProposal Thanks Nick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Licensing question for new incubator project
Hi Jacob, On 10 Oct 2013, at 23:50, Jacob Beard wrote: I'm the author of an open source project which project grew out of an ASF-mentored Google Summer of Code project three years ago. This project has been in constant development ever since, and has grown into a mature code-base, used in production in several places. I am interested in contributing this project back to ASF, and it seems like the way to do that is by submitting it as an incubator project. cool! I have a question regarding licensing. I developed part of this project during my current employment, and my employer gave me permission to publish my work under an Apache 2 license on Github. I believe they will be supportive of my request to submit the project to ASF. However, I will be changing my employment soon (they are aware of this), and so I would like to resolve all the IP issues with them now, while I am still at the company. I would therefore like to verify that, in order to contribute the project to ASF, they will be required to sign a Corporate CLA, and a Software Grant Agreement. yes, the company will need to sign a software grant and imho should sign a corporate CLA. I would also like to check if there is any issue with having them sign these documents early in the process, before I submit the Incubator proposal? It definitely makes sense and I am not aware of an issues. In your situation I would do the same. There is of course a chance the incubator pmc rejects your proposal. Is there anything else I should be aware of at this stage? Please note, most project which are accepted have already a community. It reads as your project would have one. If you know a few people here I would also recommend you to recruit a Champion even before you submit the proposal. I would think your GSOC mentors might be able to help you. A Champion is very good to have with the first steps. You should wait a little bit if somebody else has another thing to add to my comments. Cheers Christian Thanks for your attention, and I look forward to receiving your comments. Jacob Beard --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Sirona as an incubated project
+1 On 9 Oct 2013, at 3:29, Olivier Lamy wrote: Hi, Since discussion about the Sirona seems done, I'd like to call a vote for Sirona to become an incubated project. The proposal is pasted below, and also available at: https://wiki.apache.org/incubator/SironaProposal Let's keep this vote open for three business days. [ ] +1 Accept Sirona into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Sirona because... ## page was renamed from MonitoringProposal = Apache Sirona = == Abstract == Apache Sirona aims to provide a simple but extensible monitoring solution for Java applications. Apache Sirona provides two kind of components : * Apache Sirona Core to provide a base framework for monitoring/recording a Java application. * Default based plugins * Apache Sirona base reporting web application (provide a basic reporting on recorded figures). == Background == Currently, Apache Sirona source is hosted in Apache Commons Sandbox scm. The development has begun few years ago but goes to dormant statut. == Rationale == Currently users who need some monitoring need to use some non Open Source solutions or GPL solutions. The goal is to provide a solution based on the Apache License. == Initial Goals == Apache Sirona doesn't have any release currently. The initial goal of this project will be to build community in the spirit of the Apache Way, and to address new features and bug-fixes of the first releases. === Current Status === Intent of the proposal is to build a diverse community of developers around Sirona. Sirona started in the Apache Commons Sandbox, driven in the spirit of open source and we would like to continue in this spirit by, for example, encouraging contributors from a variety of organizations. === Community === Apache Sirona stakeholders desire to expand the user and developer base of Apache Sirona further in the future == Known Risks == === Orphaned Products === Sirona is a new product. So without community adoption the risks of it being orphaned exist. === Inexperience with Open Source === The code has been developed in Apache Commons Sandbox mostly by Romain Manni-Bucau and Olivier Lamy who intimately familiar with the Apache model for open-source development and is experienced with working with new contributors. === Homogeneous Developers === The initial set of committers is from a small set of organizations. However, we expect that once approved for incubation, the project will attract new contributors from diverse organizations and will thus grow organically. The participation of developers from several different organizations in the mailing list is a strong indication for this assertion. === Reliance on Salaried Developers === It is expected that Apache Sirona will be developed on salaried and volunteer time. === Relationships with Other Apache Products === Apache Sirona depends upon other Apache Projects: Velocity and various Apache Commons components and build systems like Maven. === A Fascination with the Apache Brand === The reason for joining Apache is to foster a healthy community of contributors and consumers around the project. This is facilitated by ASF and that is the primary reason we would like Apache Sirona to become an Apache project. == Documentation == Docs: http://commons.apache.org/sandbox/commons-monitoring/ == Initial Source == https://svn.apache.org/repos/asf/commons/sandbox/monitoring/trunk == Source and Intellectual Property Submission Plan == The initial source is already Apache 2.0 licensed. == External Dependencies == The required external dependencies are all Apache License or compatible licenses. Following components with non-Apache licenses are enumerated : == Cryptography == Apache Sirona does not depend upon any cryptography tools or libraries. == Required Resources == === Mailing lists === * sirona-private (with moderated subscriptions) * sirona-dev * sirona-commits * sirona-user == Subversion Directory == https://svn.apache.org/repos/asf/incubator/sirona == Issue Tracking == JIRA Sirona (key: SIRONA) == Other Resources == The existing code already has unit and integration tests so we would like to use Jenkins instance to run them whenever a new patch is submitted. This can be added after project creation. == Initial Committer == * Romain Manni-Bucau (rmannibu...@apache.org) * Jean-Louis Monteiro (jlmonte...@apache.org) * Fred Zhang (no ASF account) * Fabrice Bacchella (no ASF account) * Christian Grobmeier (grobme...@apache.org) == Affiliations == * Olivier Lamy, Ecetera * Fred Zhang, Ecetera == Sponsors == === Champion === * Olivier Lamy (ol...@apache.org) === Nominated Mentors === * Olivier Lamy (ol...@apache.org) * Henri Gomez (hgo...@apache.org) * Jean-Baptiste Onofré (jbono...@apache.org) * Tammo van Lessen (va...@apache.org) * Mark Struberg (strub...@apache.org) Thanks
Re: Too many late reports
Ups! Due to tons of $realtime work recently I missed to push the Ripple report. I am going after that asap. Are you accepting it if it comes soonish? Btw, in almost all podling esp the smaller communities I have to remind the reports, even when there was Marvin. It feels as people would ignore marvin, because they know how to do it when I remind them. Thats just a non-representative observation. On 7 Oct 2013, at 6:19, Marvin Humphrey wrote: On Sun, Oct 6, 2013 at 11:29 AM, Dave Fisher dave2w...@comcast.net wrote: Dave Fisher DeviceMap Dave Fisher Spark Although there are no reports yet. On Sun, Oct 6, 2013 at 11:45 AM, Matt Franklin m.ben.frank...@gmail.com wrote: Missing the ODF Toolkit report for this month. Lots of late or missing reports this month! As of the due date last Wednesday, 8 podlings out of 16 had not reported: * Chukwa * DeviceMap * Helix * ODF Toolkit * Ripple * Samza * Spark * Stratos Since then, Chukwa and Helix filed their reports late Saturday; Spark filed a report today -- *after* Dave Fisher had filed his shepherding commentary, which concludes with the sentence I'm not sure why they have not reported yet. It's inconvenient to receive podling reports late. Mentors have less time to sign off and possibly comment; shepherds don't get to take the podling's own self-examination into account when conducting their reviews. Perhaps it would be better if we ask late podlings to file next month instead. That's what the Board asks TLPs to do when their reports show up too late. In the past, the Incubator PMC has not done a good job of following up when reports are missed entirely, arguably contributing to our losing track of low-activity podlings and delaying intervention. I've started doing it a bit, though I've missed at least one (NPanday did not file in August but there was no followup AFAIK). It might be nice to build a remedy into the reporting run book -- something like this: After filing the report, perform the following steps for each podling which did not report: * Edit podlings.xml to set the monthly reporting attribute for the podling. * Send a message to the podling's dev list requesting that they file an out-of-cycle report next month as a makeup. One possible contributing factor is that podlings are still not getting a full week's notice to file their reports. Sure, reporting isn't a huge task, but when you're new to creating reports it takes much longer. The argument that podlings ought to just know these dates and file on time rather than relying on reminders[1] simply isn't getting the job done. I think we'd get better results if we expect punctuality from podlings, set a good example by demonstrating punctuality ourselves, and express lenience by requesting that a podling report next month rather than by accepting a report too late to give it the attention it deserves. The problem is that at present the reminders have to be sent out manually[2], and despite the best of intentions, humans are not ideal replacements for cron jobs. It's time to ask again: what would it take to get those reminders firing with unerring reliability three weeks before the Board meeting? Is it realistic to attempt a patch eliminating the need for an svn password? Marvin Humphrey [1] http://s.apache.org/PIj [2] http://s.apache.org/dwM - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] [PROPOSAL] Apache Monitoring
Thanks a lot Olivier On 7 Oct 2013, at 1:26, Olivier Lamy wrote: Page renamed: https://wiki.apache.org/incubator/SironaProposal I will wait until tomorrow if no more objections then start the vote. On 7 October 2013 09:59, Tammo van Lessen tvanles...@gmail.com wrote: +1 for Sirona On Fri, Oct 4, 2013 at 4:44 PM, Ashish paliwalash...@gmail.com wrote: +1, sounds good On Wed, Oct 2, 2013 at 4:31 AM, Olivier Lamy ol...@apache.org wrote: So Apache Merlin sounds good to me. Any objections? On 25 September 2013 23:47, Christian Grobmeier grobme...@gmail.com wrote: Nechtan sounds cool also. Please note, in the german wikipedia its translated with The tremendousness. This is not noted on the english wikipedia. After reading wikipedia I am still not sure what Nechtan stands for. But I like its sound. I just found Sirona, goddess of healing. Because monitoring is identifying the sickness before its getting worse. However, Sirona is used by companies related to healing (aka dental works). What I found interesting is this page claims Merlin being a god: http://wicca.com/celtic/wicca/celtic.htm of protecting, counseling, crystal reading and so. A few projects use Merlin, but all are very small ant not related to monitoring. There is a project management software called marlin: http://www.projectwizards.net/de/merlin/ I believe we currently have: Apache Leitstand Apache Nechtan Apache Merlin Apache Sirona Apache Heimdall Apache Dagr Cheers On 25 Sep 2013, at 15:03, Stephen Connolly wrote: Why not try Celtic mythology I was thinking Apache Nechtan due to the association with access to knowledge and floods... but heck I am not good on my Irish mythology and the Norse ones always sounded way cooler On 25 September 2013 13:23, Christian Grobmeier grobme...@gmail.com wrote: I also see thor is being used by infra: status.apache.org (mentioning, because it has been proposed as name too). However, it's not so bad. I actually mixed up Baldur with Heimdall, who is the actual protector of Bifröst. Baldur was more known because he was able to return from Hel (sounds like a good name for a server ;-) A quick crosscheck told me Heimdall is not used that often. For those who were concerned about using nordic godnames: Heimdall was named as the father of all humans. He was also known for his horn Gjallarhorn which he blew when danger appeared. Most notable he blew that horn when Ragnarökr (the end of our time and the fall of the gods) starts. I imagine the sound of a horn when critical notification of the tool happens ;-) Another idea i just had was Dagr. It old norsk for Day. In old myths Dagr is the son of night and he rides his horse Skinfaxi through heaven. The crest of the horse lights the earth with golden shimmer. I imagine Apache Dagr to shed light on the dark corners of our applications. Heck, when I was young i read a lot about northern mythology. Its so poetic. I should spend some time to read again. On 25 Sep 2013, at 10:19, Daniel Gruno wrote: On 09/25/2013 09:21 AM, Tammo van Lessen wrote: Baldr is fine with me, my only concern is the similarity to Apache Buildr. Just a heads up from infra; baldr.apache.org is already very much a thing, and has been for more than five years. If it can be avoided, we'd really appreciate it if we can keep the name Baldr for our infrastructure. With regards, Daniel. Tammo Am 25.09.2013 01:18 schrieb Olivier Lamy ol...@apache.org: So what about Baldr? BTW we can start incubation using Monitoring then change the name for TLP? WDYT? On 21 September 2013 06:30, Christian Grobmeier grobme...@gmail.com wrote: I would like to throw in this document: http://www.apache.org/**foundation/marks/naming.html http://www.apache.org/foundation/marks/naming.html We should make a few tests already before we start the process officially. here is the current list, i felt so free to add a few comments already. - CoMon There is Common Software, a company. We might have a trademarks problem because of similarity. - Leitstand Not sure if I like the sound :-), but did not find any repositories at github. From the meaning, a Leitstand is usually something were you can adjust things (more power, less steam and so on). Monitoring would be only a part of it. But on the other hand, it expresses things well and it is a unused word so far. - Thor Great name, great god, but unfortunately a lot of people use that name for their code :-( - Balder / Baldur, also possible: Baldr I haven't see a lot with that name, but we need to check this more in detail. From that perspective, Leitstand would be the best catch from a unique point of view. I like Baldr very much from that meaning. Lets see if there are more names the next days. Romain Manni-Bucau schrieb: Why not CoMon? Remind commons monitoring, that's fun and closer to english so easier
Re: [DISCUSS] [PROPOSAL] Apache Monitoring
I also see thor is being used by infra: status.apache.org (mentioning, because it has been proposed as name too). However, it's not so bad. I actually mixed up Baldur with Heimdall, who is the actual protector of Bifröst. Baldur was more known because he was able to return from Hel (sounds like a good name for a server ;-) A quick crosscheck told me Heimdall is not used that often. For those who were concerned about using nordic godnames: Heimdall was named as the father of all humans. He was also known for his horn Gjallarhorn which he blew when danger appeared. Most notable he blew that horn when Ragnarökr (the end of our time and the fall of the gods) starts. I imagine the sound of a horn when critical notification of the tool happens ;-) Another idea i just had was Dagr. It old norsk for Day. In old myths Dagr is the son of night and he rides his horse Skinfaxi through heaven. The crest of the horse lights the earth with golden shimmer. I imagine Apache Dagr to shed light on the dark corners of our applications. Heck, when I was young i read a lot about northern mythology. Its so poetic. I should spend some time to read again. On 25 Sep 2013, at 10:19, Daniel Gruno wrote: On 09/25/2013 09:21 AM, Tammo van Lessen wrote: Baldr is fine with me, my only concern is the similarity to Apache Buildr. Just a heads up from infra; baldr.apache.org is already very much a thing, and has been for more than five years. If it can be avoided, we'd really appreciate it if we can keep the name Baldr for our infrastructure. With regards, Daniel. Tammo Am 25.09.2013 01:18 schrieb Olivier Lamy ol...@apache.org: So what about Baldr? BTW we can start incubation using Monitoring then change the name for TLP? WDYT? On 21 September 2013 06:30, Christian Grobmeier grobme...@gmail.com wrote: I would like to throw in this document: http://www.apache.org/foundation/marks/naming.html We should make a few tests already before we start the process officially. here is the current list, i felt so free to add a few comments already. - CoMon There is Common Software, a company. We might have a trademarks problem because of similarity. - Leitstand Not sure if I like the sound :-), but did not find any repositories at github. From the meaning, a Leitstand is usually something were you can adjust things (more power, less steam and so on). Monitoring would be only a part of it. But on the other hand, it expresses things well and it is a unused word so far. - Thor Great name, great god, but unfortunately a lot of people use that name for their code :-( - Balder / Baldur, also possible: Baldr I haven't see a lot with that name, but we need to check this more in detail. From that perspective, Leitstand would be the best catch from a unique point of view. I like Baldr very much from that meaning. Lets see if there are more names the next days. Romain Manni-Bucau schrieb: Why not CoMon? Remind commons monitoring, that's fun and closer to english so easier to propagate IMO. Le 20 sept. 2013 12:59, Jean-Baptiste Onofré j...@nanthrax.net a écrit : I like the Apache Leitstand name. Regards JB On 09/20/2013 09:51 AM, Tammo van Lessen wrote: So if German is en vogue already, I'd propose Apache Leitstand [1], which means control room. I think it would make also a nice name when pronounced in English. This of course only works if the GUI is an important piece of the project, which is the case if I understood correctly. Cheers, Tammo [1] http://de.wikipedia.org/wiki/**Leitstand http://de.wikipedia.org/wiki/Leitstand On Fri, Sep 20, 2013 at 3:23 AM, Olivier Lamy ol...@apache.org wrote: So It looks we have more interested folks. But before starting the vote I'd like to find an other name for the project. Someone proposed Baldur or Balder (note, It's a popular germanic god). So as a French guy this proposition looks to be rude for me :-). More seriously, this name doesn't hurt me. If any other propositions, it's time to speak. Cheers -- Olivier On 16 September 2013 08:25, Tammo van Lessen tvanles...@gmail.com wrote: Am 15.09.2013 15:35 schrieb Romain Manni-Bucau rmannibu...@gmail.com : Hi Angular is great but i hope well keep extensibility possible without js. In all case well get at least a thread on it to discuss about the stack we want and well use ;) Looking forward to that discussion ;) I'd prefer progressive enhancement over SPAs in this context as well. Or even http://roca-style.org. Tammo -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy --**--** - To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache. **orggeneral-h...@incubator.apache.org -- Jean-Baptiste Onofré jbono
Re: [VOTE] first milestone release of Apache Drill (incubating)
On 24 Sep 2013, at 0:11, Ted Dunning wrote: - moving trademarks@ to bcc to avoid mixing private and public lists *Christian*, Do you withdraw this -1 now that Shane has said that we don't have to wait for PODLINGNAMESEARCH-16 to close? I will edit the product status page to reflect current (non) progress. Yes, I withdraw my -1 and give a +1 (I did some more basic checks). Sorry for holding you up, but I felt it was necessary to apply the process and see if it is as we wanted it. Thanks also for your help and patience! On Sun, Sep 22, 2013 at 6:44 AM, Christian Grobmeier grobme...@gmail.comwrote: Hi, Could you please explain why the projects thinks a trademark process is not required? http://incubator.apache.org/**projects/drill.htmlhttp://incubator.apache.org/projects/drill.html For me it is required to clear the name before a product is published: http://www.apache.org/**foundation/marks/naming.htmlhttp://www.apache.org/foundation/marks/naming.html I don't see why Drill is an exception, but maybe I have missed something. Until I know more, I need to -1 this. Thanks! On Tue, Sep 17, 2013 at 03:29:46PM -0700, Ted Dunning wrote: We've held a vote on drill-dev to release the first milestone release. The vote thread can be found here: http://mail-archives.apache.**org/mod_mbox/incubator-drill-** dev/201309.mbox/%**3CCAKa9qDkMxJp-r8v+**ZwabM5E4b5osrypJyp+DuPvq2LR-** d70...@mail.gmail.com%3Ehttp://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201309.mbox/%3ccaka9qdkmxjp-r8v+zwabm5e4b5osrypjyp+dupvq2lr-d70...@mail.gmail.com%3E The vote passed with 4 x +1 binding votes 7 x +1 non-binding votes An additional non-binding +1 vote was received after the vote closed. A summary email can be found here: http://mail-archives.apache.**org/mod_mbox/incubator-drill-** dev/201309.mbox/%3CCAKa9qDn1+**TnKVP=p_=Lh==mOS=azctUz6_** Qvsm4U3Z4gdhHHgQ@mail.gmail.**com%3Ehttp://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201309.mbox/%3CCAKa9qDn1+TnKVP=p_=Lh==mOS=azctuz6_qvsm4u3z4gdhh...@mail.gmail.com%3E The source only release artifactscan be found together with signatures here: http://people.apache.org/~**jacques/apache-drill-1.0.0-m1.**rc4/http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc4/ Please vote on this release --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-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] Apache Chukwa graduation
Eric, we discussed a little on trademarks and it has been said it is recommended to wait for the name search issue to resolve, but not necessary required. The PMC needs to decide themselves to take the risk. If there is an infringement reported to trademarks, it may result in renaming. As concerned on the ASF trademarks, I think everybody should complete the process. However as an IPMC member I do not see much problems with this name. Therefore I withdraw my -1 and give it a +1. Good luck! On 24 Sep 2013, at 7:33, Eric Yang wrote: 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
Re: [VOTE] : Release Apache Sentry 1.2.0 incubating (rc0)
Hi Shreepadma, I am withdrawing my -1 as this has been resolved. Please note, I believe this name will ask for trouble, esp with getsentry.com. I also believe you should discuss this in your project if you really want to take on the risk of this name prior graduation. Thanks, Christian On 24 Sep 2013, at 0:30, Shreepadma Venugopalan wrote: Hi Christain, Name search JIRA for Sentry has been resolved. Are you OK with changing your vote? Cheers, Shreepadma On Sun, Sep 22, 2013 at 11:59 AM, Christian Grobmeier grobme...@gmail.comwrote: Shreepadma Venugopalan schrieb: On Sun, Sep 22, 2013 at 11:06 AM, Christian Grobmeier grobme...@gmail.comwrote: Shreepadma Venugopalan schrieb: Per this document: http://www.apache.org/foundation/marks/naming.html, its required to start the name search process before we release any packages. It doesn't mention the name has to be cleared before a release. OK, maybe it's no phrased well. But surely you understand why the name must be cleared before any package is released? Well, the way the rule reads today is the search process has to start before a release can happen. If the name has to be cleared before a release, it needs to be explicitly stated that way. On the end of the document one can read: The V.P. Branding will finally approve your request. Important: you must wait until your trademark has been approved. There is no lazy consensus. Once the name is approved, you can resolve the JIRA issue and work with your new trademark. Incubator Podlings: please don't forget to update your Incubator status page. It says, you can only work with your trademark when VP has approved the mark. For me this includes a release. You maybe can guess that it can cause trouble when you work with a brand with has not checked. Only recently we had to rename a subproject of project because the brand was not checked accordingly. We can either discuss about grammar or spelling issues, which this document surely has (they are mostly my fault). Or we can simply try to understand what problems it solves and act like that. For me trademarks clearance are as important as a clean IP. If I were you, I would keep this vote running, but make the outcome pending to the response. Now, as Jira is available to me again I can see there a couple of (software) projects using the name Sentry already. Like for example: getsentry.com Given the high number of other which use the name (346 search results on github) I have concerns we will run into a trademark conflict here and insist you wait until trademarks@ has approved your mark. + cc Trademarks Cheers Christain We have already started a name search JIRA for Apache Sentry. Here's the name search JIRA for Apache Sentry: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-38 OK, then lets wait until this has been closed. The project status page (http://incubator.apache.org/**projects/sentry.html http://incubator.apache.org/projects/sentry.html) has also been updated to reflect it. I can't see a note. Maybe its not yet published? I think the voting can continue on this RC. I disagree. First clear the name, then release. Anyway I will propose a change on the process document to make the intention more clear. Cheers Cheers. Shreepadma Thanks. Shreepadma On Sun, Sep 22, 2013 at 6:41 AM, Christian Grobmeier grobme...@gmail.comwrote: -1 (binding). As per this document: http://incubator.apache.org/**projects/sentry.html http://incubator.apache.org/projects/sentry.html the trademark process has not been resolved. It is required to clear the name before a product is published: http://www.apache.org/**foundation/marks/naming.html http://www.apache.org/foundation/marks/naming.html Thanks! On 22 Sep 2013, at 7:02, Shreepadma Venugopalan wrote: This is the first incubator release of Apache Sentry, version 1.2.0-incubating. It fixes the following issues: http://s.apache.org/VlU Source files : http://people.apache.org/~**shreepadma/sentry-1.2.0/ http://people.apache.org/~shreepadma/sentry-1.2.0/ Tag to be voted on (rc0): https://git-wip-us.apache.org/**repos/asf/incubator-sentry/** repo?p=incubator-sentry.git;a=**log;h=refs/tags/release-1.2.0-**rc0 https://git-wip-us.apache.org/repos/asf/incubator-sentry/repo?p=incubator-sentry.git;a=log;h=refs/tags/release-1.2.0-rc0 Sentry's KEYS containing the PGP key we used to sign the release: https://people.apache.org/**keys/group/sentry.asc https://people.apache.org/keys/group/sentry.asc Note that this is a source only release and we are voting on the source (tag). A vote on releasing this package has already passed in Apache Sentry PPMC[1] including +1 votes from our IPMC mentors (Patrick Hunt and Arvind Prabhakar). Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Shreepadma [1] - http://markmail.org/search/?q=**sentry%20vote%20release#query:** sentry
Re: [VOTE] Apache Chukwa graduation
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-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.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
Re: [VOTE] Apache Chukwa graduation
-1 (binding) I have not seen a successful resolution of this process: http://www.apache.org/foundation/marks/naming.html I have seen some effort have been made in 2010: http://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-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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] : Release Apache Sentry 1.2.0 incubating (rc0)
-1 (binding). As per this document: http://incubator.apache.org/projects/sentry.html the trademark process has not been resolved. It is required to clear the name before a product is published: http://www.apache.org/foundation/marks/naming.html Thanks! On 22 Sep 2013, at 7:02, Shreepadma Venugopalan wrote: This is the first incubator release of Apache Sentry, version 1.2.0-incubating. It fixes the following issues: http://s.apache.org/VlU Source files : http://people.apache.org/~shreepadma/sentry-1.2.0/ Tag to be voted on (rc0): https://git-wip-us.apache.org/repos/asf/incubator-sentry/repo?p=incubator-sentry.git;a=log;h=refs/tags/release-1.2.0-rc0 Sentry's KEYS containing the PGP key we used to sign the release: https://people.apache.org/keys/group/sentry.asc Note that this is a source only release and we are voting on the source (tag). A vote on releasing this package has already passed in Apache Sentry PPMC[1] including +1 votes from our IPMC mentors (Patrick Hunt and Arvind Prabhakar). Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Shreepadma [1] - http://markmail.org/search/?q=sentry%20vote%20release#query:sentry%20vote%20release+page:1+mid:sqrwevgsxakqatqk+state:results - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] first milestone release of Apache Drill (incubating)
Hi, Could you please explain why the projects thinks a trademark process is not required? http://incubator.apache.org/projects/drill.html For me it is required to clear the name before a product is published: http://www.apache.org/foundation/marks/naming.html I don't see why Drill is an exception, but maybe I have missed something. Until I know more, I need to -1 this. Thanks! On Tue, Sep 17, 2013 at 03:29:46PM -0700, Ted Dunning wrote: We've held a vote on drill-dev to release the first milestone release. The vote thread can be found here: http://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201309.mbox/%3ccaka9qdkmxjp-r8v+zwabm5e4b5osrypjyp+dupvq2lr-d70...@mail.gmail.com%3E The vote passed with 4 x +1 binding votes 7 x +1 non-binding votes An additional non-binding +1 vote was received after the vote closed. A summary email can be found here: http://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201309.mbox/%3CCAKa9qDn1+TnKVP=p_=Lh==mOS=azctuz6_qvsm4u3z4gdhh...@mail.gmail.com%3E The source only release artifactscan be found together with signatures here: http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc4/ Please vote on this release - 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] : Release Apache Sentry 1.2.0 incubating (rc0)
Shreepadma Venugopalan schrieb: Per this document: http://www.apache.org/foundation/marks/naming.html, its required to start the name search process before we release any packages. It doesn't mention the name has to be cleared before a release. OK, maybe it's no phrased well. But surely you understand why the name must be cleared before any package is released? We have already started a name search JIRA for Apache Sentry. Here's the name search JIRA for Apache Sentry: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-38 OK, then lets wait until this has been closed. The project status page (http://incubator.apache.org/**projects/sentry.htmlhttp://incubator.apache.org/projects/sentry.html) has also been updated to reflect it. I can't see a note. Maybe its not yet published? I think the voting can continue on this RC. I disagree. First clear the name, then release. Anyway I will propose a change on the process document to make the intention more clear. Cheers Thanks. Shreepadma On Sun, Sep 22, 2013 at 6:41 AM, Christian Grobmeier grobme...@gmail.comwrote: -1 (binding). As per this document: http://incubator.apache.org/**projects/sentry.htmlhttp://incubator.apache.org/projects/sentry.html the trademark process has not been resolved. It is required to clear the name before a product is published: http://www.apache.org/**foundation/marks/naming.htmlhttp://www.apache.org/foundation/marks/naming.html Thanks! On 22 Sep 2013, at 7:02, Shreepadma Venugopalan wrote: This is the first incubator release of Apache Sentry, version 1.2.0-incubating. It fixes the following issues: http://s.apache.org/VlU Source files : http://people.apache.org/~**shreepadma/sentry-1.2.0/http://people.apache.org/~shreepadma/sentry-1.2.0/ Tag to be voted on (rc0): https://git-wip-us.apache.org/**repos/asf/incubator-sentry/** repo?p=incubator-sentry.git;a=**log;h=refs/tags/release-1.2.0-**rc0https://git-wip-us.apache.org/repos/asf/incubator-sentry/repo?p=incubator-sentry.git;a=log;h=refs/tags/release-1.2.0-rc0 Sentry's KEYS containing the PGP key we used to sign the release: https://people.apache.org/**keys/group/sentry.aschttps://people.apache.org/keys/group/sentry.asc Note that this is a source only release and we are voting on the source (tag). A vote on releasing this package has already passed in Apache Sentry PPMC[1] including +1 votes from our IPMC mentors (Patrick Hunt and Arvind Prabhakar). Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Shreepadma [1] - http://markmail.org/search/?q=**sentry%20vote%20release#query:** sentry%20vote%20release+page:**1+mid:sqrwevgsxakqatqk+state:**resultshttp://markmail.org/search/?q=sentry%20vote%20release#query:sentry%20vote%20release+page:1+mid:sqrwevgsxakqatqk+state:results --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1525390 - /incubator/public/trunk/content/projects/sentry.xml
-1, please roll this back. THe VP must agree to this first, then you can mark this as done. See: http://www.apache.org/foundation/marks/naming.html The V.P. Branding will finally approve your request. Important: you must wait until your trademark has been approved. There is no lazy consensus. Once the name is approved, you can resolve the JIRA issue and work with your new trademark. Incubator Podlings: please don't forget to update your Incubator status page. Thanks shreepa...@apache.org schrieb: Author: shreepadma Date: Sun Sep 22 17:03:45 2013 New Revision: 1525390 URL: http://svn.apache.org/r1525390 Log: CMS commit to incubator by shreepadma Modified: incubator/public/trunk/content/projects/sentry.xml Modified: incubator/public/trunk/content/projects/sentry.xml URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/projects/sentry.xml?rev=1525390r1=1525389r2=1525390view=diff == --- incubator/public/trunk/content/projects/sentry.xml [utf-8] (original) +++ incubator/public/trunk/content/projects/sentry.xml [utf-8] Sun Sep 22 17:03:45 2013 @@ -263,7 +263,7 @@ thitem/th /tr tr - td-..-../td + td2013-09-19/td tdMake sure that the requested project name does not already exist. a href=http://www.apache.org/foundation/marks/naming.html;Please follow the guide to ensure a suitable project/product name./a/td /tr - To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org For additional commands, e-mail: cvs-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] : Release Apache Sentry 1.2.0 incubating (rc0)
Shreepadma Venugopalan schrieb: On Sun, Sep 22, 2013 at 11:06 AM, Christian Grobmeier grobme...@gmail.comwrote: Shreepadma Venugopalan schrieb: Per this document: http://www.apache.org/foundation/marks/naming.html, its required to start the name search process before we release any packages. It doesn't mention the name has to be cleared before a release. OK, maybe it's no phrased well. But surely you understand why the name must be cleared before any package is released? Well, the way the rule reads today is the search process has to start before a release can happen. If the name has to be cleared before a release, it needs to be explicitly stated that way. On the end of the document one can read: The V.P. Branding will finally approve your request. Important: you must wait until your trademark has been approved. There is no lazy consensus. Once the name is approved, you can resolve the JIRA issue and work with your new trademark. Incubator Podlings: please don't forget to update your Incubator status page. It says, you can only work with your trademark when VP has approved the mark. For me this includes a release. You maybe can guess that it can cause trouble when you work with a brand with has not checked. Only recently we had to rename a subproject of project because the brand was not checked accordingly. We can either discuss about grammar or spelling issues, which this document surely has (they are mostly my fault). Or we can simply try to understand what problems it solves and act like that. For me trademarks clearance are as important as a clean IP. If I were you, I would keep this vote running, but make the outcome pending to the response. Now, as Jira is available to me again I can see there a couple of (software) projects using the name Sentry already. Like for example: getsentry.com Given the high number of other which use the name (346 search results on github) I have concerns we will run into a trademark conflict here and insist you wait until trademarks@ has approved your mark. + cc Trademarks Cheers Christain We have already started a name search JIRA for Apache Sentry. Here's the name search JIRA for Apache Sentry: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-38 OK, then lets wait until this has been closed. The project status page (http://incubator.apache.org/**projects/sentry.html http://incubator.apache.org/projects/sentry.html) has also been updated to reflect it. I can't see a note. Maybe its not yet published? I think the voting can continue on this RC. I disagree. First clear the name, then release. Anyway I will propose a change on the process document to make the intention more clear. Cheers Cheers. Shreepadma Thanks. Shreepadma On Sun, Sep 22, 2013 at 6:41 AM, Christian Grobmeier grobme...@gmail.comwrote: -1 (binding). As per this document: http://incubator.apache.org/**projects/sentry.html http://incubator.apache.org/projects/sentry.html the trademark process has not been resolved. It is required to clear the name before a product is published: http://www.apache.org/**foundation/marks/naming.html http://www.apache.org/foundation/marks/naming.html Thanks! On 22 Sep 2013, at 7:02, Shreepadma Venugopalan wrote: This is the first incubator release of Apache Sentry, version 1.2.0-incubating. It fixes the following issues: http://s.apache.org/VlU Source files : http://people.apache.org/~**shreepadma/sentry-1.2.0/ http://people.apache.org/~shreepadma/sentry-1.2.0/ Tag to be voted on (rc0): https://git-wip-us.apache.org/**repos/asf/incubator-sentry/** repo?p=incubator-sentry.git;a=**log;h=refs/tags/release-1.2.0-**rc0 https://git-wip-us.apache.org/repos/asf/incubator-sentry/repo?p=incubator-sentry.git;a=log;h=refs/tags/release-1.2.0-rc0 Sentry's KEYS containing the PGP key we used to sign the release: https://people.apache.org/**keys/group/sentry.asc https://people.apache.org/keys/group/sentry.asc Note that this is a source only release and we are voting on the source (tag). A vote on releasing this package has already passed in Apache Sentry PPMC[1] including +1 votes from our IPMC mentors (Patrick Hunt and Arvind Prabhakar). Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Shreepadma [1] - http://markmail.org/search/?q=**sentry%20vote%20release#query:** sentry%20vote%20release+page:**1+mid:sqrwevgsxakqatqk+state:**results http://markmail.org/search/?q=sentry%20vote%20release#query:sentry%20vote%20release+page:1+mid:sqrwevgsxakqatqk+state:results --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**org general-h...@incubator.apache.org
Re: [DISCUSS] [PROPOSAL] Apache Monitoring
I would like to throw in this document: http://www.apache.org/foundation/marks/naming.html We should make a few tests already before we start the process officially. here is the current list, i felt so free to add a few comments already. - CoMon There is Common Software, a company. We might have a trademarks problem because of similarity. - Leitstand Not sure if I like the sound :-), but did not find any repositories at github. From the meaning, a Leitstand is usually something were you can adjust things (more power, less steam and so on). Monitoring would be only a part of it. But on the other hand, it expresses things well and it is a unused word so far. - Thor Great name, great god, but unfortunately a lot of people use that name for their code :-( - Balder / Baldur, also possible: Baldr I haven't see a lot with that name, but we need to check this more in detail. From that perspective, Leitstand would be the best catch from a unique point of view. I like Baldr very much from that meaning. Lets see if there are more names the next days. Romain Manni-Bucau schrieb: Why not CoMon? Remind commons monitoring, that's fun and closer to english so easier to propagate IMO. Le 20 sept. 2013 12:59, Jean-Baptiste Onofré j...@nanthrax.net a écrit : I like the Apache Leitstand name. Regards JB On 09/20/2013 09:51 AM, Tammo van Lessen wrote: So if German is en vogue already, I'd propose Apache Leitstand [1], which means control room. I think it would make also a nice name when pronounced in English. This of course only works if the GUI is an important piece of the project, which is the case if I understood correctly. Cheers, Tammo [1] http://de.wikipedia.org/wiki/**Leitstandhttp://de.wikipedia.org/wiki/Leitstand On Fri, Sep 20, 2013 at 3:23 AM, Olivier Lamy ol...@apache.org wrote: So It looks we have more interested folks. But before starting the vote I'd like to find an other name for the project. Someone proposed Baldur or Balder (note, It's a popular germanic god). So as a French guy this proposition looks to be rude for me :-). More seriously, this name doesn't hurt me. If any other propositions, it's time to speak. Cheers -- Olivier On 16 September 2013 08:25, Tammo van Lessen tvanles...@gmail.com wrote: Am 15.09.2013 15:35 schrieb Romain Manni-Bucau rmannibu...@gmail.com : Hi Angular is great but i hope well keep extensibility possible without js. In all case well get at least a thread on it to discuss about the stack we want and well use ;) Looking forward to that discussion ;) I'd prefer progressive enhancement over SPAs in this context as well. Or even http://roca-style.org. Tammo -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy --**--** - To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: perms on wiki
i just added you Am 17.09.13 09:51, schrieb Romain Manni-Bucau: Here is my account login: RomainMannibucau Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/9/17 Romain Manni-Bucau rmannibu...@gmail.com: Hmm, seems i'm blocked (i tested apache and jira accounts probably too much times). i would like rmannibucau but not sure it is created. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/9/17 David Crossley cross...@apache.org: Romain Manni-Bucau wrote: Hi, anyone can give me permissions to edit the wiki please? (i would like to create a proposal) Yes, but you do need to provide the crucial information: your wiki username. See the top-right of http://wiki.apache.org/incubator/ -David Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau - 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: [DISCUSS] [PROPOSAL] Apache Monitoring
Am 15.09.13 14:12, schrieb Tammo van Lessen: Thanks. Mentor would be fine with me, but I'm not sure if I'm eligible. I'm Apache Member but not IPMC member. As a member you can join by requesting IPMC membership. You should to that, if you would like to mentor On Sat, Sep 14, 2013 at 3:00 PM, Olivier Lamy ol...@apache.org wrote: Hi Tammo/Mark I have added you as mentor. Let us know if it's the role you want to have? On 14 September 2013 18:18, Mark Struberg strub...@yahoo.de wrote: I'm in. +1 LieGrue, strub - Original Message - From: Romain Manni-Bucau rmannibu...@gmail.com To: general@incubator.apache.org Cc: Sent: Friday, 13 September 2013, 21:29 Subject: Re: [DISCUSS] [PROPOSAL] Apache Monitoring Hi The gui is optional but a big added value for me. Rrd is on the radar (Olivier spoke about it first) Le 13 sept. 2013 20:43, Tammo van Lessen tvanles...@gmail.com a écrit : Hi Romain, cool, count me in. Though, I still have some questions: 1. linked to the GUI: does this mean, that it won't work without the GUI, i.e. it is not planned to provide reporters that push data to statsd, graphite, librato et al? Or does it just mean, that GUI is also in the focus? 2. Persistence sounds very cool, would that include a time-series-storage (similar to rrdtool) or just to keep the current values? Thanks, Tammo On Fri, Sep 13, 2013 at 6:04 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi basis are close to metrics but it has some few differences: 1) it is extensible by design and linked to the GUI 2) we will handle persistence of counters/gauges 3) we will handle aggregation and hopefully much more ;) Then I hope we will integrate it deeply with other Apache project (tomee, jbatch impl maybe) Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/9/13 Tammo van Lessen tvanles...@gmail.com: Sounds interesting. I'm curious how this is related to other metrics libraries, like Coda Hale's [1]. Does it have a similar scope? Thanks, Tammo [1] http://metrics.codahale.com/ On Fri, Sep 13, 2013 at 2:10 AM, Olivier Lamy ol...@apache.org wrote: Hi Folks, Below is a proposal for a new incubator project called Apache Monitoring. (the name will certainly change as I imagine few people won't be happy if we request to be able to use monitoring.a.o as website :-) ). https://wiki.apache.org/incubator/MonitoringProposal The source code is currently hosted at Commons Sandbox but as the code is larger than a simple component, the idea is to have a separate project. So let us know if you want to join (etc...) Cheers -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Tammo van Lessen - http://www.taval.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Tammo van Lessen - http://www.taval.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - 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: [DISCUSS] [PROPOSAL] Apache Monitoring
Great proposal. You have already enough mentors, otherwise I would step up as one. Am 13.09.13 21:29, schrieb Romain Manni-Bucau: The gui is optional but a big added value for me. Rrd is on the radar (Olivier spoke about it first) Not sure how much time I will have but I might join and help with the GUI stuff. I would like to see such a gui myself, preferrably build with AngularJS. If you don't mind about my yet unclear time situation, you can count me in as initial committer. Le 13 sept. 2013 20:43, Tammo van Lessen tvanles...@gmail.com a écrit : Hi Romain, cool, count me in. Though, I still have some questions: 1. linked to the GUI: does this mean, that it won't work without the GUI, i.e. it is not planned to provide reporters that push data to statsd, graphite, librato et al? Or does it just mean, that GUI is also in the focus? 2. Persistence sounds very cool, would that include a time-series-storage (similar to rrdtool) or just to keep the current values? Thanks, Tammo On Fri, Sep 13, 2013 at 6:04 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi basis are close to metrics but it has some few differences: 1) it is extensible by design and linked to the GUI 2) we will handle persistence of counters/gauges 3) we will handle aggregation and hopefully much more ;) Then I hope we will integrate it deeply with other Apache project (tomee, jbatch impl maybe) Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/9/13 Tammo van Lessen tvanles...@gmail.com: Sounds interesting. I'm curious how this is related to other metrics libraries, like Coda Hale's [1]. Does it have a similar scope? Thanks, Tammo [1] http://metrics.codahale.com/ On Fri, Sep 13, 2013 at 2:10 AM, Olivier Lamy ol...@apache.org wrote: Hi Folks, Below is a proposal for a new incubator project called Apache Monitoring. (the name will certainly change as I imagine few people won't be happy if we request to be able to use monitoring.a.o as website :-) ). https://wiki.apache.org/incubator/MonitoringProposal The source code is currently hosted at Commons Sandbox but as the code is larger than a simple component, the idea is to have a separate project. So let us know if you want to join (etc...) Cheers -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Tammo van Lessen - http://www.taval.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Tammo van Lessen - http://www.taval.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] [PROPOSAL] Apache Monitoring
Am 15.09.13 15:35, schrieb Romain Manni-Bucau: Hi Angular is great but i hope well keep extensibility possible without js. In all case well get at least a thread on it to discuss about the stack we want and well use ;) Without JS in 2013? There is definitely a need to discuss this! :-) Let's do so when there is a mailing list. Cheers! Le 15 sept. 2013 15:29, Christian Grobmeier grobme...@gmail.com a écrit : Great proposal. You have already enough mentors, otherwise I would step up as one. Am 13.09.13 21:29, schrieb Romain Manni-Bucau: The gui is optional but a big added value for me. Rrd is on the radar (Olivier spoke about it first) Not sure how much time I will have but I might join and help with the GUI stuff. I would like to see such a gui myself, preferrably build with AngularJS. If you don't mind about my yet unclear time situation, you can count me in as initial committer. Le 13 sept. 2013 20:43, Tammo van Lessen tvanles...@gmail.com a écrit : Hi Romain, cool, count me in. Though, I still have some questions: 1. linked to the GUI: does this mean, that it won't work without the GUI, i.e. it is not planned to provide reporters that push data to statsd, graphite, librato et al? Or does it just mean, that GUI is also in the focus? 2. Persistence sounds very cool, would that include a time-series-storage (similar to rrdtool) or just to keep the current values? Thanks, Tammo On Fri, Sep 13, 2013 at 6:04 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi basis are close to metrics but it has some few differences: 1) it is extensible by design and linked to the GUI 2) we will handle persistence of counters/gauges 3) we will handle aggregation and hopefully much more ;) Then I hope we will integrate it deeply with other Apache project (tomee, jbatch impl maybe) Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/9/13 Tammo van Lessen tvanles...@gmail.com: Sounds interesting. I'm curious how this is related to other metrics libraries, like Coda Hale's [1]. Does it have a similar scope? Thanks, Tammo [1] http://metrics.codahale.com/ On Fri, Sep 13, 2013 at 2:10 AM, Olivier Lamy ol...@apache.org wrote: Hi Folks, Below is a proposal for a new incubator project called Apache Monitoring. (the name will certainly change as I imagine few people won't be happy if we request to be able to use monitoring.a.o as website :-) ). https://wiki.apache.org/incubator/MonitoringProposal The source code is currently hosted at Commons Sandbox but as the code is larger than a simple component, the idea is to have a separate project. So let us know if you want to join (etc...) Cheers -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Tammo van Lessen - http://www.taval.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Tammo van Lessen - http://www.taval.de - 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: [DISCUSS] [PROPOSAL] Apache Monitoring
Am 15.09.13 15:56, schrieb Romain Manni-Bucau: Sure, keep in mind monitoring interfaces are used by robots (curl) too ;). they surely prefer something like JSON instead of raw html? But im not so extremist that i looked :p Good to hear :-) Le 15 sept. 2013 15:53, Christian Grobmeier grobme...@gmail.com a écrit : Am 15.09.13 15:35, schrieb Romain Manni-Bucau: Hi Angular is great but i hope well keep extensibility possible without js. In all case well get at least a thread on it to discuss about the stack we want and well use ;) Without JS in 2013? There is definitely a need to discuss this! :-) Let's do so when there is a mailing list. Cheers! Le 15 sept. 2013 15:29, Christian Grobmeier grobme...@gmail.com a écrit : Great proposal. You have already enough mentors, otherwise I would step up as one. Am 13.09.13 21:29, schrieb Romain Manni-Bucau: The gui is optional but a big added value for me. Rrd is on the radar (Olivier spoke about it first) Not sure how much time I will have but I might join and help with the GUI stuff. I would like to see such a gui myself, preferrably build with AngularJS. If you don't mind about my yet unclear time situation, you can count me in as initial committer. Le 13 sept. 2013 20:43, Tammo van Lessen tvanles...@gmail.com a écrit : Hi Romain, cool, count me in. Though, I still have some questions: 1. linked to the GUI: does this mean, that it won't work without the GUI, i.e. it is not planned to provide reporters that push data to statsd, graphite, librato et al? Or does it just mean, that GUI is also in the focus? 2. Persistence sounds very cool, would that include a time-series-storage (similar to rrdtool) or just to keep the current values? Thanks, Tammo On Fri, Sep 13, 2013 at 6:04 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi basis are close to metrics but it has some few differences: 1) it is extensible by design and linked to the GUI 2) we will handle persistence of counters/gauges 3) we will handle aggregation and hopefully much more ;) Then I hope we will integrate it deeply with other Apache project (tomee, jbatch impl maybe) Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/9/13 Tammo van Lessen tvanles...@gmail.com: Sounds interesting. I'm curious how this is related to other metrics libraries, like Coda Hale's [1]. Does it have a similar scope? Thanks, Tammo [1] http://metrics.codahale.com/ On Fri, Sep 13, 2013 at 2:10 AM, Olivier Lamy ol...@apache.org wrote: Hi Folks, Below is a proposal for a new incubator project called Apache Monitoring. (the name will certainly change as I imagine few people won't be happy if we request to be able to use monitoring.a.o as website :-) ). https://wiki.apache.org/incubator/MonitoringProposal The source code is currently hosted at Commons Sandbox but as the code is larger than a simple component, the idea is to have a separate project. So let us know if you want to join (etc...) Cheers -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Tammo van Lessen - http://www.taval.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Tammo van Lessen - http://www.taval.de - 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: [PROPOSAL] Castafiore framework proposal to incubator
Am 05.09.13 07:09, schrieb Kureem Rossaye: Thank you very much, I have not included the proposal to the Incubator wiki yet. How can I do that? Create an account here: http://wiki.apache.org/incubator/ Then mail your username to this list, askinf for access. You'll be granted then. Then you can add your proposal here: http://wiki.apache.org/incubator/ProjectProposals I assume you know this link already: http://incubator.apache.org/guides/proposal.html Please try to make the proposal look similar to the others on the wiki. Cheers! Christian Thanks Kureem On 5 September 2013 00:09, Christian Grobmeier grobme...@gmail.com wrote: Nice! Have you included your proposal to the Incubator wiki? I would like to forward it to the Struts team, some might be interested. I have no time to actually code, but I might help with incubation (mentoring or championing). Before deciding on that, I would like to hear if there is interest of others here. Am 04.09.13 15:04, schrieb Kureem Rossaye: *once could use Castafiore in conjunction with Struts. In other terms, Castafiore could be used as a Struts plugin which then calls Struts Actions and replaces Tiles, JSP whatever. Is that correct?* Correct! Actually I myself did not get the idea that it could be used like that. Yes it can be used like that. Actually, a castafiore application (which can be a simple table) can be included on a page using a simple javascript or a jsp tag. So why not a struts plugin. Actually I have tried it as an echo2 framework component. It works just nice. Thanks for your interest Ragards, Kureem On 4 September 2013 15:32, Christian Grobmeier grobme...@gmail.com wrote: Kureem, this sounds nice. As far as I understood it, once could use Castafiore in conjunction with Struts. In other terms, Castafiore could be used as a Struts plugin which then calls Struts Actions and replaces Tiles, JSP whatever. Is that correct? Cheers Am 04.09.13 10:01, schrieb Kureem Rossaye: Hi, Indeed, I have read the incubation proposal guide. The only thing I could not figure out is how to recruit a champion. However, after re-reading the guide, I missed something. I should have prefixed the subject of the mail with [PROPOSAL]. So I am resending the proposal with the proper subject. ** PROPOSAL Abstract Castafiore framework is a web frameworks, fully component oriented, ajax based, one page appplication. Although the framework can be viewed as a classical component oriented web framework like GWT, it has been designed and implemented with a particular goal in mind. It is to be able to make existing javascript libraries java-able. Meaning that the framework allows to easily take a javascript library like e.g jquery ui and use the components and features via java. The integration of the javascript libraries need to be easy and natural. Actually companies like ext js and smartgwt have made their components java-able using GWT. I wish to provide an alternative to gwt that is much easier, fast, lightweight, and much more productive. Proposal Castafiore framework has been designed and implemented with the following goals in mind 1. Fully object oriented 2. Simple API that is very close to html itself We wanted an API that is closer to html markup and javascripts event model. I believe that this would help web developers easily visualize the rendering when reading source code. 3. Write a full application with only java 4. No need for compiler to convert to javascript like gwt.Javascript is rendered at runtime. 5. The same API can be used to make an software that is server centric and or client centric. Meaning that the user can make part of his application server centric and part of his application client centric. He can of course choose to make the whole application client centric or server centric depending on the requirement. All of this using the same API. 6. Low memory footprint 7. Easy packaging of application. Everything can be packaged in a single jar. This includes images, css or javascript as well 8. Same API used to create custom components. No need to external set of API or specific programming technique to create custom components. Creating a custom components should be done only the same way as writing an application. 9. No need for javascript to create custom components. 10. Although there is no need for javascript to create an application, it should be easy to integrate external javascript libraries and use them in java codes itself. This should be done is a natural way just like we would do in an HTML page. This should be like this so that javascript library authors with some java skills find it natural and easy to provide a castafiore
Re: request for write access to incubator wiki
Am 05.09.13 12:07, schrieb Kureem Rossaye: Hi, Is it possible to grant me access to the wiki in order to submit a proposal. Regards, Just need your Wiki name :-) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: request for write access to incubator wiki
you are in! Am 05.09.13 12:59, schrieb Kureem Rossaye: oops sorry The wiki name : KureemRossaye On 5 September 2013 14:35, Christian Grobmeier grobme...@gmail.com wrote: [image: Boxbe] https://www.boxbe.com/overview This message is eligible for Automatic Cleanup! (grobme...@gmail.com) Add cleanup rulehttps://www.boxbe.com/popup?url=https%3A%2F%2Fwww.boxbe.com%2Fcleanup%3Ftoken%3DTZqENn0%252BHaUUFOEZTEnHbeL%252Fuc0xnHBLOfVOL2mB8dMQXHMVa1XQXyBM262D6Q%252F7TglblgGmy8lNYpBTo4iNQuj4tuTCY9ycoiJbcnT%252FUEiYRv6WrXDtsuNYndYSuoIHy8uE4%252FFFeRM%253D%26key%3DO31%252Bnk0s2hcnT2%252F1nR0NBuxALSmmhoLHHQFtTnZEzZs%253Dtc_serial=15055205087tc_rand=723775848utm_source=stfutm_medium=emailutm_campaign=ANNO_CLEANUP_ADDutm_content=001| More infohttp://blog.boxbe.com/general/boxbe-automatic-cleanup?tc_serial=15055205087tc_rand=723775848utm_source=stfutm_medium=emailutm_campaign=ANNO_CLEANUP_ADDutm_content=001 Am 05.09.13 12:07, schrieb Kureem Rossaye: Hi, Is it possible to grant me access to the wiki in order to submit a proposal. Regards, Just need your Wiki name :-) - 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: [PROPOSAL] Castafiore framework proposal to incubator
Perfect! I will now ask on the Struts list if there are some people interested Thanks! Am 05.09.13 14:42, schrieb Kureem Rossaye: Done! Kureem Am 05.09.13 07:09, schrieb Kureem Rossaye: Thank you very much, I have not included the proposal to the Incubator wiki yet. How can I do that? Create an account here: http://wiki.apache.org/incubator/ Then mail your username to this list, askinf for access. You'll be granted then. Then you can add your proposal here: http://wiki.apache.org/incubator/ProjectProposals I assume you know this link already: http://incubator.apache.org/guides/proposal.html Please try to make the proposal look similar to the others on the wiki. Cheers! On 5 September 2013 12:47, Christian Grobmeier grobme...@gmail.com wrote: Am 05.09.13 07:09, schrieb Kureem Rossaye: Thank you very much, I have not included the proposal to the Incubator wiki yet. How can I do that? Create an account here: http://wiki.apache.org/incubator/ Then mail your username to this list, askinf for access. You'll be granted then. Then you can add your proposal here: http://wiki.apache.org/incubator/ProjectProposals I assume you know this link already: http://incubator.apache.org/guides/proposal.html Please try to make the proposal look similar to the others on the wiki. Cheers! Christian Thanks Kureem On 5 September 2013 00:09, Christian Grobmeier grobme...@gmail.com wrote: Nice! Have you included your proposal to the Incubator wiki? I would like to forward it to the Struts team, some might be interested. I have no time to actually code, but I might help with incubation (mentoring or championing). Before deciding on that, I would like to hear if there is interest of others here. Am 04.09.13 15:04, schrieb Kureem Rossaye: *once could use Castafiore in conjunction with Struts. In other terms, Castafiore could be used as a Struts plugin which then calls Struts Actions and replaces Tiles, JSP whatever. Is that correct?* Correct! Actually I myself did not get the idea that it could be used like that. Yes it can be used like that. Actually, a castafiore application (which can be a simple table) can be included on a page using a simple javascript or a jsp tag. So why not a struts plugin. Actually I have tried it as an echo2 framework component. It works just nice. Thanks for your interest Ragards, Kureem On 4 September 2013 15:32, Christian Grobmeier grobme...@gmail.com wrote: Kureem, this sounds nice. As far as I understood it, once could use Castafiore in conjunction with Struts. In other terms, Castafiore could be used as a Struts plugin which then calls Struts Actions and replaces Tiles, JSP whatever. Is that correct? Cheers Am 04.09.13 10:01, schrieb Kureem Rossaye: Hi, Indeed, I have read the incubation proposal guide. The only thing I could not figure out is how to recruit a champion. However, after re-reading the guide, I missed something. I should have prefixed the subject of the mail with [PROPOSAL]. So I am resending the proposal with the proper subject. ** PROPOSAL Abstract Castafiore framework is a web frameworks, fully component oriented, ajax based, one page appplication. Although the framework can be viewed as a classical component oriented web framework like GWT, it has been designed and implemented with a particular goal in mind. It is to be able to make existing javascript libraries java-able. Meaning that the framework allows to easily take a javascript library like e.g jquery ui and use the components and features via java. The integration of the javascript libraries need to be easy and natural. Actually companies like ext js and smartgwt have made their components java-able using GWT. I wish to provide an alternative to gwt that is much easier, fast, lightweight, and much more productive. Proposal Castafiore framework has been designed and implemented with the following goals in mind 1. Fully object oriented 2. Simple API that is very close to html itself We wanted an API that is closer to html markup and javascripts event model. I believe that this would help web developers easily visualize the rendering when reading source code. 3. Write a full application with only java 4. No need for compiler to convert to javascript like gwt.Javascript is rendered at runtime. 5. The same API can be used to make an software that is server centric and or client centric. Meaning that the user can make part of his application server centric and part of his application client centric. He can of course choose to make the whole application client centric or server centric depending on the requirement. All of this using the same API. 6. Low memory footprint 7. Easy packaging of application. Everything can
Re: [PROPOSAL] Castafiore framework proposal to incubator
Kureem, this sounds nice. As far as I understood it, once could use Castafiore in conjunction with Struts. In other terms, Castafiore could be used as a Struts plugin which then calls Struts Actions and replaces Tiles, JSP whatever. Is that correct? Cheers Am 04.09.13 10:01, schrieb Kureem Rossaye: Hi, Indeed, I have read the incubation proposal guide. The only thing I could not figure out is how to recruit a champion. However, after re-reading the guide, I missed something. I should have prefixed the subject of the mail with [PROPOSAL]. So I am resending the proposal with the proper subject. ** PROPOSAL Abstract Castafiore framework is a web frameworks, fully component oriented, ajax based, one page appplication. Although the framework can be viewed as a classical component oriented web framework like GWT, it has been designed and implemented with a particular goal in mind. It is to be able to make existing javascript libraries java-able. Meaning that the framework allows to easily take a javascript library like e.g jquery ui and use the components and features via java. The integration of the javascript libraries need to be easy and natural. Actually companies like ext js and smartgwt have made their components java-able using GWT. I wish to provide an alternative to gwt that is much easier, fast, lightweight, and much more productive. Proposal Castafiore framework has been designed and implemented with the following goals in mind 1. Fully object oriented 2. Simple API that is very close to html itself We wanted an API that is closer to html markup and javascripts event model. I believe that this would help web developers easily visualize the rendering when reading source code. 3. Write a full application with only java 4. No need for compiler to convert to javascript like gwt.Javascript is rendered at runtime. 5. The same API can be used to make an software that is server centric and or client centric. Meaning that the user can make part of his application server centric and part of his application client centric. He can of course choose to make the whole application client centric or server centric depending on the requirement. All of this using the same API. 6. Low memory footprint 7. Easy packaging of application. Everything can be packaged in a single jar. This includes images, css or javascript as well 8. Same API used to create custom components. No need to external set of API or specific programming technique to create custom components. Creating a custom components should be done only the same way as writing an application. 9. No need for javascript to create custom components. 10. Although there is no need for javascript to create an application, it should be easy to integrate external javascript libraries and use them in java codes itself. This should be done is a natural way just like we would do in an HTML page. This should be like this so that javascript library authors with some java skills find it natural and easy to provide a castafiore component together with the library. e.g. The author of flexgrid should should find it easy to create a castafiore component thus making his library usable directly in java. *Actually, I wanted to create a java web framework for javascript programmers. They should find it easy and fun to integrate and distribute their js libraries as a castafiore component. They will be able to distribute their libraries as a single jar. This is very convenient for java developers to just download the jar, include in classpath, and using the library, components and feature right away in their web application in pure java. Furthermore the castafiore framework itself is very lightweight with just 2 libraries and 1 web.xml entry. Even if the java developer is not using castafiore in his project, he should find it easy to just drop the 2 libraries + web.xml entry in classpath and start using it right away. Very practical.* 1. Load external resources like css and javascript lazily and efficiently only when needed. 2. Loading of external resources can be done eagerly if the API user wish so. 3. The framework does not own the whole page. Meaning that an application created with the framework can be used in an already created page. This allows API developer to use the framework only for very specific purposes like for example a dynamic table, while at the same time using other web framework like struts for the other sections of the application. 4. Although a whole application can be created using pure java, the framework should be able to integrate templates. 5. By default, there should be 100% separation of logic and presentation.
Re: [PROPOSAL] Castafiore framework proposal to incubator
Nice! Have you included your proposal to the Incubator wiki? I would like to forward it to the Struts team, some might be interested. I have no time to actually code, but I might help with incubation (mentoring or championing). Before deciding on that, I would like to hear if there is interest of others here. Am 04.09.13 15:04, schrieb Kureem Rossaye: *once could use Castafiore in conjunction with Struts. In other terms, Castafiore could be used as a Struts plugin which then calls Struts Actions and replaces Tiles, JSP whatever. Is that correct?* Correct! Actually I myself did not get the idea that it could be used like that. Yes it can be used like that. Actually, a castafiore application (which can be a simple table) can be included on a page using a simple javascript or a jsp tag. So why not a struts plugin. Actually I have tried it as an echo2 framework component. It works just nice. Thanks for your interest Ragards, Kureem On 4 September 2013 15:32, Christian Grobmeier grobme...@gmail.com wrote: Kureem, this sounds nice. As far as I understood it, once could use Castafiore in conjunction with Struts. In other terms, Castafiore could be used as a Struts plugin which then calls Struts Actions and replaces Tiles, JSP whatever. Is that correct? Cheers Am 04.09.13 10:01, schrieb Kureem Rossaye: Hi, Indeed, I have read the incubation proposal guide. The only thing I could not figure out is how to recruit a champion. However, after re-reading the guide, I missed something. I should have prefixed the subject of the mail with [PROPOSAL]. So I am resending the proposal with the proper subject. ** PROPOSAL Abstract Castafiore framework is a web frameworks, fully component oriented, ajax based, one page appplication. Although the framework can be viewed as a classical component oriented web framework like GWT, it has been designed and implemented with a particular goal in mind. It is to be able to make existing javascript libraries java-able. Meaning that the framework allows to easily take a javascript library like e.g jquery ui and use the components and features via java. The integration of the javascript libraries need to be easy and natural. Actually companies like ext js and smartgwt have made their components java-able using GWT. I wish to provide an alternative to gwt that is much easier, fast, lightweight, and much more productive. Proposal Castafiore framework has been designed and implemented with the following goals in mind 1. Fully object oriented 2. Simple API that is very close to html itself We wanted an API that is closer to html markup and javascripts event model. I believe that this would help web developers easily visualize the rendering when reading source code. 3. Write a full application with only java 4. No need for compiler to convert to javascript like gwt.Javascript is rendered at runtime. 5. The same API can be used to make an software that is server centric and or client centric. Meaning that the user can make part of his application server centric and part of his application client centric. He can of course choose to make the whole application client centric or server centric depending on the requirement. All of this using the same API. 6. Low memory footprint 7. Easy packaging of application. Everything can be packaged in a single jar. This includes images, css or javascript as well 8. Same API used to create custom components. No need to external set of API or specific programming technique to create custom components. Creating a custom components should be done only the same way as writing an application. 9. No need for javascript to create custom components. 10. Although there is no need for javascript to create an application, it should be easy to integrate external javascript libraries and use them in java codes itself. This should be done is a natural way just like we would do in an HTML page. This should be like this so that javascript library authors with some java skills find it natural and easy to provide a castafiore component together with the library. e.g. The author of flexgrid should should find it easy to create a castafiore component thus making his library usable directly in java. *Actually, I wanted to create a java web framework for javascript programmers. They should find it easy and fun to integrate and distribute their js libraries as a castafiore component. They will be able to distribute their libraries as a single jar. This is very convenient for java developers to just download the jar, include in classpath, and using the library, components and feature right away in their web application in pure java. Furthermore the castafiore framework
Re: Web voting
Am 03.09.13 12:18, schrieb Tammo van Lessen: I find Loomio [1] looks very promising. It's probably not exactly tailor-made for our decision making progress but it can showcase [2] what is possible and if it can help us. Looks pretty nice. Is it a requirement to send individual votes to the ml (like with voting on releases). in some cases we need secret votes (like with the IPMC chair vote) Loomio looks hackable actually. Best, Tammo [1] https://www.loomio.org/ https://www.loomio.org/discussions/4847 -- https://github.com/loomio/loomio (AGPL) [2] https://www.loomio.org/discussions/4847 On Mon, Sep 2, 2013 at 6:52 PM, Jordan Zimmerman jor...@jordanzimmerman.com wrote: Why does Apache need to develop this? There are many ASP-based voting apps that could be used, e.g. Survey Monkey. -Jordan On Sep 2, 2013, at 8:20 AM, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Sep 2, 2013 at 7:28 AM, Suresh Marru sma...@apache.org wrote: We don't need to worry for this vote, but in general relying on voter's statement is not a good idea. An authoritative resource to verify the binding and non-binding votes is [1]. [1] - http://people.apache.org/committers-by-project.html#incubator-pmc - 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: [PROPOSAL] Creation of the Incubator Ombudsman
On Wed, Jul 31, 2013 at 2:05 AM, Marvin Humphrey mar...@rectangular.com wrote: Bertrand, Christian, Alex, On Tue, Jul 30, 2013 at 12:44 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: people should feel free to contact people that they trust (IPMC members, mentors, ASF members) privately if there's a need, and not having someone elected in the ombudsman role means people are free to talk to whoever *they* think will help. I question how well the Incubator communicates to newcomers that such resources are available to them. What if a podling contributor has no people that they trust because they don't know anybody around here? I'm also skeptical that the absence of an ombud makes things easier because newcomers are free to find the best person to talk to. That's like saying that an airport is better off without a help desk. But there is a helpdesk. It's general@incubator.apache.org. Tons of people are there. I think we should tell people they can always seek help there. I simply doubt that an appointed person who might go awol works better than a whole list. And yes, I definitely know that general@ is not always responsive as it should be. But why do we believe an Ombudsperson is different? The difference between the Incubator's overview documentation (what we think you need to know) and the information in WhatToExpect (what you really need to know) is jarring. http://incubator.apache.org/incubation/Process_Description.html http://wiki.apache.org/incubator/WhatToExpect If we're so approachable, why doesn't anybody know it? it's a good point to say nobody knows how to deal with issues. But how exactly does the Ombud solve it? We need to create a new page telling people: if in trouble, ask the Ombudsperson. What is different to: if in trouble, ask at general@? What I am trying to say: it seems we have a problem with our docs and we should fix that first instead of inventing new roles. Fixing docs turned out not to be easy at the incubator. I have read the whole thread. Still i am not sure when to approach an Ombudsperson. And what powers that person have to change the problems. Even if the Ombud knows and addresses a problem, what else can he do than pinging general@? What I am trying to say is: what problems do we actually have which need to be handled through a proxy? And how do we guarantee the Ombud is responsive, unlike some mentors or general@? Again, I will not object if you want to start this experiment. Cheers Christian Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Creation of the Incubator Ombudsman
On Wed, Jul 31, 2013 at 10:37 AM, Alan Cabrera l...@toolazydogs.com wrote: On Jul 30, 2013, at 8:44 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Jul 30, 2013 at 5:55 AM, Marvin Humphrey mar...@rectangular.com wrote: ...Bertrand was skeptical about an ASF-wide ombud, but didn't raise any objection to an Incubator-specific position. http://s.apache.org/NAa ... Just laziness on my part...what I said there also applies to an Incubator ombudsman, I'll repeat it here: I don't think we need it - people should feel free to contact people that they trust (IPMC members, mentors, ASF members) privately if there's a need, and not having someone elected in the ombudsman role means people are free to talk to whoever *they* think will help. An ombudsman is there when all the normal processes don't work. It alleviates an organization from from having to heavily codify what to do in all manner of situations, thus keeping things simple. Can you point me to any cases where normal processes didn't work which can be fixed with the Ombud? I know we have problems releasing packages. The Ombud will not make a difference here. I know we have problems overseeing projects. Shepherds have helped here. Nothing to do for an Ombud. What else can an Ombudsperson do instead of general@? I'll note that most of those who seem to think that the position is not needed are those who are well established and well connected in the ASF community. I am still asking my questions on general@, and never in private. And I have a lot of questions. It's true that I am know quite a few folks at the ASF, but I ask incubator related questions at general@. In fact, I consider asking questions in private problematic. I'll also mention a point I made a while back, sometimes it's better to have an ombudsman look into things rather than a random ASF member. I am sorry if I missed an important message you already made, but maybe you can point me to it. I didn't find it easily. I would like to know what these things are. Thanks! Christian PS: I appreciate this discussion even when I do not agree on the necessity of the Ombudsperson (yet). The intention - making the incubator a better place - is highly appreciated Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
