Re: [DISCUSS] Responsibilities and Improvements (was: Re: Whimsy general@ subs check
Hi Justin, Daniel, Thank you for your answer. Justin, one more question, are Default Guidelines, you've prepared some time ago, applicable only for projects under incubation or it is inherited 'as is' to TLP? чт, 7 мар. 2019 г. в 00:18, Justin Mclean : > Hi, > > > 1) Removal question and its allowance in general: this question asked > > during every talk I gave related to ASF. My fellows ask me if someone can > > remove Committer or PMCs. Some folks think it is possible by the vote of > > PMC. > > The PMC may vote on it but only the board can remove a PMC member, they > have been reluctant to do so in the past, and I don’t think they would > remove people for being inactive. The PMC can remove committers but it’s > extremely rare. > > > Here I need some general understanding which I can use for > > answering questions. > > > > 2) Inactive members removal: Lack of active PMCs member makes me thinks > > that at some point some removal will be necessary. > > Merit doesn’t not expire and only the board can remove PMC members, a > project could ask for removed but only the board can actually remove them. > In general there's no issue in having inactive member and they may decide > to become active again. > > Some time back there was an attempt to clean up any project which > mentioner the 6 month inactivity thing, not all of them were caught. > > Thanks, > Justin > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Responsibilities and Improvements (was: Re: Whimsy general@ subs check
Hi Daniel, There are two independent questions here. 1) Removal question and its allowance in general: this question asked during every talk I gave related to ASF. My fellows ask me if someone can remove Committer or PMCs. Some folks think it is possible by the vote of PMC. They refer to docs I've shared: mnemonic project & incubator guide. Here I need some general understanding which I can use for answering questions. 2) Inactive members removal: Lack of active PMCs member makes me thinks that at some point some removal will be necessary. We can continuously grow the roster for a TLP project, but sometimes I feel there are ~30 members and only 5-7 active members. So why don't we narrow the roster to 7 and invite new members? It looks reasonable that if you want a binding vote, approve releases, propose new committers you need to join community communication channels and be there. My idea is, first of all, ask PMCs if they want to stay or leave and, second of all, to always keep committership, because it is based on merit. And here for option 2, I don't have any severe issues to address. If it a bad idea, not a problem. In that case, I also would be happy if I understand this topic better. Sincerely, Dmitriy Pavlov ср, 6 мар. 2019 г. в 23:12, Daniel Gruno : > On 3/6/19 9:08 PM, Dmitriy Pavlov wrote: > > Hi Ross, > > > > Thank you for your reply. Apache Ignite PMCs do not support this idea, so > > inactive PMCs will be still there. > > > > But still, it is not clear for me in general, why following > > projects/guidelines contains removal procedure for Committer PMC: > > - https://mnemonic.apache.org/develop/bylaws/ after 6 months of > inactivity > > both PMC and Committer status may be removed. > > - Default Incubator guidelines > > https://wiki.apache.org/incubator/DefaultProjectGuidelines It contains > > procedures of consensus-based removal, - it is ok to remove for > Incubator? > > is it ok for TLP? > > > > If both PMC & Committer roles are merit-based, and merit does not expire, > > how it even possible to remove TLP committer/PMC (excepting some extreme > > cases)? > > > > This question is not only mine, but it is also often asked and I would > like > > to know the answer. > > Turn the question around; *why* are you looking to remove people? What > is the problem you are trying to solve here? How will removing someone > from the PMC/committer list help address the issues you are facing? > > > > > Sincerely, > > Dmitriy Pavlov > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Responsibilities and Improvements (was: Re: Whimsy general@ subs check (was: .... introduce "[DISCUSS]" threads for podling ... release candidates))
Hi Ross, Thank you for your reply. Apache Ignite PMCs do not support this idea, so inactive PMCs will be still there. But still, it is not clear for me in general, why following projects/guidelines contains removal procedure for Committer PMC: - https://mnemonic.apache.org/develop/bylaws/ after 6 months of inactivity both PMC and Committer status may be removed. - Default Incubator guidelines https://wiki.apache.org/incubator/DefaultProjectGuidelines It contains procedures of consensus-based removal, - it is ok to remove for Incubator? is it ok for TLP? If both PMC & Committer roles are merit-based, and merit does not expire, how it even possible to remove TLP committer/PMC (excepting some extreme cases)? This question is not only mine, but it is also often asked and I would like to know the answer. Sincerely, Dmitriy Pavlov ср, 6 мар. 2019 г. в 18:47, Ross Gardler : > Merit does not expire. People who are not active today should be able to > become active tomorrow without having to jump through approval hoops. > > In projects there is no concept of emeritus PMC. Here in the IPMC the > issue is very different. Most people earn merit transitively - become a > member, become a mentor, become an IPMC member. It's different. > > Please don't use what is being discussed here as being transitive to a PMC > based entirely on directly earned merit. > > Get Outlook for Android<https://aka.ms/ghei36> > > ____ > From: Dmitriy Pavlov > Sent: Tuesday, March 5, 2019 4:46:09 AM > To: general@incubator.apache.org > Subject: Re: [DISCUSS] Responsibilities and Improvements (was: Re: Whimsy > general@ subs check (was: introduce "[DISCUSS]" threads for podling > ... release candidates)) > > I absolutely agree with Greg Stein. I can't find any single reason to keep > unsubscribed members of IPMC in the roster. These members can be asked to > subscribe, and if they do, then ok; if don't - it is perfectly ok to > remove. > > Similarly, I don't see reasons for having inactive TLP PMC members. I've > suggested the same change in Apache Ignite, but I don't clearly understand > why remained members resisting this change. > > > пн, 4 мар. 2019 г. в 09:58, Ross Gardler : > > > That's right Greg. And since we are filling in gaps for people... > > > > I was originally against the pTLP concept (though I supported the > > experiments) or any of the derivatives that came from it. I think I have > > changed my position. Largely based on the fact that every single project > > I've discussed the ASF with in the last 3-5 years has had a very > inaccurate > > perception of how the ASF works. I believe a large part of this is due, > in > > part, to the issues being discussed in this thread. > > > > I do not understand how a foundation which prides itself in having very > > little bureaucratic red tape can be seen as having so much red tape. The > > projects I talk to just want to build software. It used to be that the > ASF > > focused on running the legal and operational aspects of the foundation > > projects and developers on projects wrote code. I'm not sure that's true > > anymore. > > > > We need to fix it. > > > > I look forward to hearing how the IPMC will seek to strip down the > > bureaucracy and get back to mentoring the incoming projects on how the > ASF > > is structured so they can get (relatively) quick and clear answers to > their > > questions. > > > > Ross > > > > > > From: Greg Stein > > Sent: Sunday, March 3, 2019 10:19 PM > > To: general@incubator.apache.org > > Subject: Re: [DISCUSS] Responsibilities and Improvements (was: Re: Whimsy > > general@ subs check (was: introduce "[DISCUSS]" threads for podling > > ... release candidates)) > > > > On Sun, Mar 3, 2019 at 10:37 PM Ross Gardler wrote: > > > > > If a podling is a committee in its own right then it can be empowered > to > > > act on behalf of the board and this its releases can be an act of the > > > foundation. > > > > > >... > > > > > Podlings would only become full TLPs once they have demonstrated their > > > ability to do formal releases. > > > > > > > The above pair of concepts was offered in $priorCycle as "provisional > TLPs" > > (pTLP). I believe the idea ended when Sam pointed out that if a pTLP is > > trusted, then why not just call it a TLP and trust it to label its > releases > > appropriately? Thus, just create TLPs immediately for a "podling" > > > > [ I know Ross knows this; but for $others who may want to look at > > historical proposals, and compare/contrast to current discussion ... > search > > for "pTLP" ] > > > > Cheers, > > -g > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: [DISCUSS] Responsibilities and Improvements (was: Re: Whimsy general@ subs check (was: .... introduce "[DISCUSS]" threads for podling ... release candidates))
I absolutely agree with Greg Stein. I can't find any single reason to keep unsubscribed members of IPMC in the roster. These members can be asked to subscribe, and if they do, then ok; if don't - it is perfectly ok to remove. Similarly, I don't see reasons for having inactive TLP PMC members. I've suggested the same change in Apache Ignite, but I don't clearly understand why remained members resisting this change. пн, 4 мар. 2019 г. в 09:58, Ross Gardler : > That's right Greg. And since we are filling in gaps for people... > > I was originally against the pTLP concept (though I supported the > experiments) or any of the derivatives that came from it. I think I have > changed my position. Largely based on the fact that every single project > I've discussed the ASF with in the last 3-5 years has had a very inaccurate > perception of how the ASF works. I believe a large part of this is due, in > part, to the issues being discussed in this thread. > > I do not understand how a foundation which prides itself in having very > little bureaucratic red tape can be seen as having so much red tape. The > projects I talk to just want to build software. It used to be that the ASF > focused on running the legal and operational aspects of the foundation > projects and developers on projects wrote code. I'm not sure that's true > anymore. > > We need to fix it. > > I look forward to hearing how the IPMC will seek to strip down the > bureaucracy and get back to mentoring the incoming projects on how the ASF > is structured so they can get (relatively) quick and clear answers to their > questions. > > Ross > > > From: Greg Stein > Sent: Sunday, March 3, 2019 10:19 PM > To: general@incubator.apache.org > Subject: Re: [DISCUSS] Responsibilities and Improvements (was: Re: Whimsy > general@ subs check (was: introduce "[DISCUSS]" threads for podling > ... release candidates)) > > On Sun, Mar 3, 2019 at 10:37 PM Ross Gardler wrote: > > > If a podling is a committee in its own right then it can be empowered to > > act on behalf of the board and this its releases can be an act of the > > foundation. > > > >... > > > Podlings would only become full TLPs once they have demonstrated their > > ability to do formal releases. > > > > The above pair of concepts was offered in $priorCycle as "provisional TLPs" > (pTLP). I believe the idea ended when Sam pointed out that if a pTLP is > trusted, then why not just call it a TLP and trust it to label its releases > appropriately? Thus, just create TLPs immediately for a "podling" > > [ I know Ross knows this; but for $others who may want to look at > historical proposals, and compare/contrast to current discussion ... search > for "pTLP" ] > > Cheers, > -g > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Accept Training into the Apache Incubator
Hi Lars, Thank you for proposing and driving this topic. Surely, we can wait, but I'm absolutely sure more committers gives a greater variety of technical visions. Moreover, we didn't change anything essential in the proposal. I'm pretty sure a number of contributors may and will come later. Sincerely, Dmitriy Pavlov ср, 20 февр. 2019 г. в 10:58, Lars Francke : > The vote for accepting "Training" into the Apache Incubator passes* with 21 > binding +1 votes, 6 non-binding +1 votes and no other votes. > * Because of the late addition of Jim to the Proposal I'll leave everyone > another 24h to object (we are in no rush) before I'll go and make this > official. > > Thanks for voting! > > 21 binding +1 votes: > Bernd Fondermann > Bertrand Delacretaz > Christofer Dutz > Felix Cheung > Furkan Kamaci > . > Henry Saputra > Jim Jagielski > Justin Mclean > Kenneth Knowles > Kevin A. McGrail > . > Lars Francke > Liang Chen > Matt Sicker > Mohammad Asif Siddiqui > Myrle Krantz > . > Paul King > Sharan Foga > Thomas Weise > Vinayakumar B > Von Gosling > . > Woonsan Ko > > > 6 non-binding +1 votes: > Brahma Reddy Battula > Ciprian Borodescu > Dmitriy Pavlov > Hans-Peter Zorn > Julian Feinauer > . > Sönke Liebau > > > Thank you everyone, > Lars > > > On Wed, Feb 13, 2019 at 8:57 AM Lars Francke > wrote: > > > Hi everyone, > > > > we've discussed the proposal for the Training project in [1] and [2]. The > > proposal itself can be found on the wiki[3]. > > > > According to the Incubator rules[4] I'd like to call a vote to accept the > > new "Training" project as a podling in the Apache Incubator. > > > > A vote for accepting a new Apache Incubator podling is a majority vote. > > Everyone is welcome to vote, only Incubator PMC member votes are binding. > > It would be helpful (but not required) if you could add a comment stating > > whether your vote is binding or non-binding. > > > > This vote will run for at least 72 hours (but I expect to keep it open > > for longer). Please VOTE as follows: > > > > [ ] +1 Accept Training into the Apache Incubator > > [ ] +0 Abstain > > [ ] -1 Do not accept Training into the Apache Incubator because ... > > > > Thank you for everyone who decided to join in in the past discussions! > > Lars > > > > [1] < > > > https://lists.apache.org/thread.html/5c00016b769135cc302bb2ce4e5f6bbfeeda933a07e9c38b5017d651@%3Cgeneral.incubator.apache.org%3E > > > > > > > [2] < > > > https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E > > > > > > > [3] <https://wiki.apache.org/incubator/TrainingProposal#preview> > > > > [4] < > > > https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor > > > > > >
Re: [VOTE] Accept Training into the Apache Incubator
+1 (non-binding) ср, 13 февр. 2019 г. в 18:05, Ciprian Borodescu : > +1 > > On Wed, Feb 13, 2019 at 4:52 PM Thomas Weise wrote: > > > +1 (binding) > > > > > > On Wed, Feb 13, 2019, 6:40 AM Mohammad Asif Siddiqui < > > asifdxtr...@apache.org> > > wrote: > > > > > +1 (binding) > > > > > > Regards > > > Asif > > > > > > On Wed, Feb 13, 2019 at 8:09 PM Julian Feinauer < > > > j.feina...@pragmaticminds.de> wrote: > > > > > > > +1 (non-binding) > > > > I really liked the idea from the start and probably will find some > time > > > to > > > > contribute! > > > > > > > > Julian > > > > > > > > Am 13.02.19, 15:18 schrieb "Kevin A. McGrail" >: > > > > > > > > +1 Binding. I'll also try again to get Udacity, Udemy, > Coursera, > > > > Pluralsight involved now that this is going to a formal incubator > > > > podling. > > > > I am hoping once a domino falls, more will help. > > > > > > > > Regards, > > > > KAM > > > > -- > > > > Kevin A. McGrail > > > > Member, Apache Software Foundation > > > > Chair Emeritus Apache SpamAssassin Project > > > > https://www.linkedin.com/in/kmcgrail - 703.798.0171 > <(703)%20798-0171> > > > > > > > > > > > > On Wed, Feb 13, 2019 at 7:00 AM Vinayakumar B < > > > vinayakum...@apache.org > > > > > > > > > wrote: > > > > > > > > > +1 (binding) > > > > > > > > > > -Vinay > > > > > > > > > > > > > > > On Wed, Feb 13, 2019 at 4:58 PM Hans-Peter Zorn < > hz...@inovex.de > > > > > > > wrote: > > > > > > > > > > > +1 (non-binding) > > > > > > > > > > > > Looking forward to work on this! > > > > > > Thanks, > > > > > > Hans-Peter > > > > > > > > > > > > > Am 13.02.2019 um 08:57 schrieb Lars Francke < > > > > lars.fran...@gmail.com>: > > > > > > > > > > > > > > Hi everyone, > > > > > > > > > > > > > > we've discussed the proposal for the Training project in > [1] > > > and > > > > [2]. > > > > > The > > > > > > > proposal itself can be found on the wiki[3]. > > > > > > > > > > > > > > According to the Incubator rules[4] I'd like to call a vote > > to > > > > accept > > > > > the > > > > > > > new "Training" project as a podling in the Apache > Incubator. > > > > > > > > > > > > > > A vote for accepting a new Apache Incubator podling is a > > > > majority vote. > > > > > > > Everyone is welcome to vote, only Incubator PMC member > votes > > > are > > > > > binding. > > > > > > > It would be helpful (but not required) if you could add a > > > comment > > > > > stating > > > > > > > whether your vote is binding or non-binding. > > > > > > > > > > > > > > This vote will run for at least 72 hours (but I expect to > > keep > > > > it open > > > > > > for > > > > > > > longer). Please VOTE as follows: > > > > > > > > > > > > > > [ ] +1 Accept Training into the Apache Incubator > > > > > > > [ ] +0 Abstain > > > > > > > [ ] -1 Do not accept Training into the Apache Incubator > > because > > > > ... > > > > > > > > > > > > > > Thank you for everyone who decided to join in in the past > > > > discussions! > > > > > > > Lars > > > > > > > > > > > > > > [1] < > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/5c00016b769135cc302bb2ce4e5f6bbfeeda933a07e9c38b5017d651@%3Cgeneral.incubator.apache.org%3E > > > > > > >> > > > > > > > > > > > > > > [2] < > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E > > > > > > >> > > > > > > > > > > > > > > [3] < > > > https://wiki.apache.org/incubator/TrainingProposal#preview> > > > > > > > > > > > > > > [4] < > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > - > > > > > > To unsubscribe, e-mail: > > general-unsubscr...@incubator.apache.org > > > > > > For additional commands, e-mail: > > > general-h...@incubator.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: [DISCUSS] Training (incubating) Proposal
Hi Lars, About the project: I've got only one thing to say here: Apache Incubator is intended to be a place where a community is build up and everybody (mostly newcomers) learn guides and policies. So straight-to-TLP is also a possible option, but some incubation process isn't bad at all. But still, it is up to board to decide if we go to TLP without incubation. I'm now interested in more technical aspects of contributing to Apache Training: source code for labs, presentations. For example, I can start working on Apache Ignite training, so I will need to contribute 2 types of presentations (source and prepared for students), project code for labs, solved labs, publish it using some website or wiki. Are there any VCS compatible presentation development tools? Can we use, for example, Google Docs for presentations? Sincerely, Dmitriy Pavlov пн, 4 февр. 2019 г. в 12:56, Hans-Peter Zorn : > Hi all, > > I have been creating training material for various big data apache > projects (mostly Apache Spark) for the last five years and we would like to > contribute those. I for myself have not been directly involved with the ASF > directly, however I have been contributing to some open source projects in > the past. We have been in discussion about this with Lars Francke and > Sören Liebau the last weeks. Currently most of the material we have is > powerpoint and zeppelin notebooks at the moment but learning on how to make > this more collaboration friendly format-wise would be one thing we would > like to see in this project. > > > Kind regards, > Hans-Peter > > > > > Am 25.01.2019 um 13:49 schrieb Lars Francke : > > > > Hello everyone, > > > > this is the result of the discussion I started in December 2018[1]. > > > > I would like to start this thread to get feedback on a proposal we've > been > > working on for a project focused on developing training material for > Apache > > & 3rd party projects. > > > > The full proposal can be found here < > > https://wiki.apache.org/incubator/TrainingProposal> > > > > Disclaimer: It is a bit different than most other proposals as it > basically > > starts at zero. > > > > Our main goals for this discussion are: > > * Finding mentors and interested contributors > > * Discuss whether this should be a Incubator project, straight to TLP or > a > > Central Service > > * Sharpen the scope of the project > > > > While I personally have a relatively long history as a contributor, > > committer etc. at Apache I've never been a mentor before so we would love > > for some experienced people to help us out. > > > > We're looking forward to all kinds of feedback. > > > > Cheers, > > Lars > > > > [1] < > > > https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E > >> > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Training (incubating) Proposal
Hi Lars, I'd like to be a part of this. I'm PMC at Apache Ignite. Sometimes I need to give individual feedback to developers related to both Apache policies and spirit of developing software in a community way. Why not invest effort into training and education materials instead? I gave several talks in Russia related to The Apache Software Foundation and blog about The Apache Way. I also assist newcomers joining Apache Ignite. So count on my support, and I definitely would like to became committer at Training. Sincerely, Dmitriy Pavlov ср, 30 янв. 2019 г. в 01:25, Lars Francke : > Craig, > > that's great news. Thank you for volunteering. I've added you to the Wiki. > > Cheers, > Lars > > On Tue, Jan 29, 2019 at 11:01 PM Craig Russell > wrote: > > > Hi Lars, > > > > I'll volunteer to mentor the project if it ends up incubating. And I'd > > like to join the discussion as a member of the (P)PMC. The idea of an > open > > source project to help rationalize training materials is very appealing. > > > > I'm also very interested in the ecosystem of not-for-profit education and > > I think this project would be a great fit. > > > > Craig > > > > > On Jan 28, 2019, at 5:49 AM, Lars Francke > > wrote: > > > > > > I've been going back and forth on the topic of TLP vs. Incubator > podling. > > > > > > I don't really have a strong opinion but I'm leaning slightly in favor > of > > > "straight to TLP" and the past discussion (linked in previous mail) did > > > also have more voices in favor of TLP. But of course there are > arguments > > to > > > be made for both sides. > > > > > > I've been wondering if anyone here has opinions on this part of the > > > proposal? > > > > > > In a related thread I asked about how to proceed in terms of choosing > > > members for a PMC and one suggestion was to make it depend on the > route: > > > > > > * Incubator: On graduation ask and assess current PMC members and see > if > > > everyone has proven their merit and is willing to continue > > > * TLP: Start with a PMC consisting of only ASF members (plus additional > > > committers) and then accept additional members for the PMC on a > "normal" > > > basis > > > > > > Cheers, > > > Lars > > > > > > > > > On Fri, Jan 25, 2019 at 1:49 PM Lars Francke > > wrote: > > > > > >> Hello everyone, > > >> > > >> this is the result of the discussion I started in December 2018[1]. > > >> > > >> I would like to start this thread to get feedback on a proposal we've > > been > > >> working on for a project focused on developing training material for > > Apache > > >> & 3rd party projects. > > >> > > >> The full proposal can be found here < > > >> https://wiki.apache.org/incubator/TrainingProposal> > > >> > > >> Disclaimer: It is a bit different than most other proposals as it > > >> basically starts at zero. > > >> > > >> Our main goals for this discussion are: > > >> * Finding mentors and interested contributors > > >> * Discuss whether this should be a Incubator project, straight to TLP > > or a > > >> Central Service > > >> * Sharpen the scope of the project > > >> > > >> While I personally have a relatively long history as a contributor, > > >> committer etc. at Apache I've never been a mentor before so we would > > love > > >> for some experienced people to help us out. > > >> > > >> We're looking forward to all kinds of feedback. > > >> > > >> Cheers, > > >> Lars > > >> > > >> [1] < > > >> > > > https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E > > >>> > > >> > > > > 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 > > > > >
Re: Voting in new IPMC members
Hi, I also think any negative votes -1 are veto for committer and PMC. Assigning roles in a community is a very sensitive subject so allowing veto seems natural for me, but playing democracy is dangerous. We still have for example -0.9 vote that means not a veto but disagreement. Sincerely, Dmitry Pavlov ср, 7 нояб. 2018 г., 12:31 Bertrand Delacretaz : > On Tue, Nov 6, 2018 at 12:34 PM wrote: > > ...For instance [1] which states: > > "For committership, that is typical. Most PMCs allow a veto for adding > new members to the PMC.” ... > > Interesting, I missed that indeed, I'll start a discussion on our > members@ list to see what people think. > > Thanks for being persistent in arguing ;-) > > -Bertrand > > > 1. > https://lists.apache.org/thread.html/406150947529308214f1ab80b42ed670a71df0537c1a860c1da2f82f@1380817899@%3Cgeneral.incubator.apache.org%3E > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Default project guidelines
Hi Justin, Thank you for such a short and informative article. I'll definitely link to it from Apache Ignite wiki space. What do you think about including a link to http://community.apache.org/newcommitter.html This page also gives a good level of understanding what should and should not a potential committer or PMC do. I've also don't understand how the process of committer removal connected with principles: - Meritocracy - Merit does not expire How and when committer may be removed? Is it applicable to TLP projects? Sincerely, Dmitriy Pavlov вс, 16 сент. 2018 г. в 10:20, Justin Mclean : > Hi, > > [1] being this link > https://wiki.apache.org/incubator/DefaultProjectGuidelines < > https://wiki.apache.org/incubator/DefaultProjectGuidelines> sorry I > forgot to add it in the last email. > > Thanks, > Justin
Re: Project probe: AsyncFlows Framework
Hi Constantine, Anyway, thank you for bringing this idea here. I hope the project will find enthusiasts. About similar projects, it's totally not a problem. Let's Darwin decide. About community. Unfortunately, it is a paramount thing in Apache projects. If there are no sufficient volunteers involved, the project has a high risk that development is stopped and the project is retired. Sincerely, Dmitriy Pavlov вт, 11 сент. 2018 г. в 4:31, Dave Fisher : > Hi Constantine, > > I took a few minutes to look into your project. You have some interesting > ideas. You might want to look into the features of some current Apache > projects and incubator podlings. > > (1) Events > Pulsar > Kafka > ActiveMQ > (2) Topologies > Storm > Heron > Airflow > I’m sure there are many. > > Regards, > Dave > > Sent from my iPhone > > > On Sep 10, 2018, at 2:48 PM, Constantine Plotnikov < > constantine.plotni...@gmail.com> wrote: > > > > Hello All! > > > > I would like to probe if there is interest in the project AsyncFlows that > > define DSL for asynchronous programming. The project is approximately the > > same domain as Netty, MINA, HttpCore Async, Vert.X - asynchronous network > > applications. However I belive tha the project provides higher level DSL > > and significantly more usable from developer's perspective. > > > > The project repository: https://github.com/const/asyncflows > > The home page has small developers guilde for the framework. > > > > The biggest problem with the project is that there is no community for it > > now. And I'm the sole its developer, and I'm able to spend only some > small > > time on it. The project is getting out of the research stage. I'm getting > > to the point of infrastructure setup (CI, maven central, etc), and > > theoretically some of this effort would not be needed if the project > would > > join some meta-project like Apache, and there would be a default legal > > framework for accepting contribution. > > > > I'm interested: > > 1. Are there developers that interested in working on such project? > > 2. Are there developers that interested in using such project? > > 3. Is the project suitable for Apach Incubator considering that there are > > already projects for the similar domain at Apache? > > 4. Is the project suitable for Apache Incubator considering the current > > lack of community and small resources that I could dedicate to it? > > > > Best Regards, > > Constantine Plotnikov > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
