Re: [IP CLEARANCE] Accept java-driver (into Cassandra)
Yes, this has all been discussed. It is a huge donation, and while we have spent many months working through all these issues, it's certainly appreciated receiving extra eyes. The graalvm dep is provided scope. Otherwise we have a ticket to address any things that slipped past us: CASSANDRA-18969 These things are hard blocking any release (which we want to immediately do). On Sun, 29 Oct 2023 at 20:00, wrote: > Hi, > > I also can see that code has dependencies that might not be compatible > with the Apache license. Are these optional dependencies? e.g. graalVM. Has > what to do about these dependencies been discussed by the project? > > Kine Regards, > Justin > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
[IP CLEARANCE] Accept java-driver (into Cassandra)
subject fix. On Sun, 29 Oct 2023 at 18:26, Mick Semb Wever wrote: > > > > The vote will be open for 72 hours (or longer). Votes by PMC members are >> considered binding. A vote passes if there are at least three binding +1s >> and no -1's. >> >> Vote passes with 30 +1s (ten binding). >> >> This page is updated: >> https://incubator.apache.org/ip-clearance/cassandra-java-driver.html > > > > > > Requesting clearance on the donation of the java-driver to the Cassandra > project. > > Thread behind the project's vote is at > https://lists.apache.org/thread/ryxcc043m9kkjyx9150hldr42kpcs0r0 > …and apologies, it was intended that general@incubator was cc'd on that > thread. > > Of note but not excuse, four of the incubator's PMC already have been > involved in the process. > > >
Re: [RESULT][VOTE] Accept java-driver
> The vote will be open for 72 hours (or longer). Votes by PMC members are > considered binding. A vote passes if there are at least three binding +1s > and no -1's. > > Vote passes with 30 +1s (ten binding). > > This page is updated: > https://incubator.apache.org/ip-clearance/cassandra-java-driver.html Requesting clearance on the donation of the java-driver to the Cassandra project. Thread behind the project's vote is at https://lists.apache.org/thread/ryxcc043m9kkjyx9150hldr42kpcs0r0 …and apologies, it was intended that general@incubator was cc'd on that thread. Of note but not excuse, four of the incubator's PMC already have been involved in the process.
[IP CLEARANCE] Apache Cassandra Harry
Apache Cassandra has received a code donation of Harry. The IP clearance document is at http://incubator.apache.org/ip-clearance/apache-cassandra-harry.html Please review in the next 72 hours, then IP clearance will proceed by lazy consensus, on condition the project's PMC vote that is running in parallel also passes. Thanks! Mick
Re: Podling releases and release policy
I agree. For example it would help heaps if there was a list of violations podling releases make, and which are immediate showstoppers and which need to be noted (filed as tickets) and fixed in a release before graduation. Certainly, having that list would help land this discussion a bit better. Justin, I think above all others you are the one sitting on a ton, the real wealth, of knowledge here. I appreciate the need to "know exactly what the rules are", but culturally I hope the emphasis remains on figuring out how the incubator can improve at helping podlings get to and through graduation without having to police them along the way. A lot of work has gone into improving the Incubator recently and it has been very much appreciated. I'm uncertain though as to whether seeking such explicit approval from the board and infra is but in the spirit of further policing podlings, or if in putting at ease some of the more serious concerns that the incubator has it allows it to better focus on what services it can better provide. I can't speak for all, but I know some folk really get the benefit from the public praise of catching podlings doing it right. The incubator's documentation isn't perfect, and it'll also be shifting sands and slightly out of date, so making it easy for newcomers in the incubator to know what are the good examples to be learning from always goes a long way. regards, Mick On Sat, 1 Jun 2019, at 13:55, Dave Fisher wrote: > Kevin and Justin, > > This is spot on. > > Disclaimer, signatures/checksums, Apache license, and a start to notes > are the minimum. > > Acceptance of issues to fix is also a requirement. > > Full compliance with Apache Release and Distribution Policies are some > of our agreed Incubation requirements for graduation recommendation. > > Do we need to confirm all requirements or should we limit to this > discussion to Releases? > > Regards, > Dave > > Sent from my iPhone > > > On May 31, 2019, at 8:45 PM, Kevin A. McGrail wrote: > > > > Hi Justin, > > > > Before putting it to the board, have we ever had a IPMC vote on the > > matter? I think the board wants to delegate because legally, there > > isn't a chance in hell they are going to vote on it any way but > > negatively because to me, they have no choice but to formally say no. > > This is a possible example of purposefully turning a blind eye because > > it's hard for podlings to come up to speed. > > > > So perhaps if we set an incubator policy of a podling release being a > > little more lenient, the board would delegate because the legal issues > > are about nil. It's like making a law where 20% of America is a > > criminal. Is it really enforceable and especially without prejudicial > > or preferential treatment? > > > > What I like to see from a podling is: acknowledgment of the issues, > > tickets on the issues, and consistent improvement. > > > > What we cannot see is: a podling NOT saying "incubating" in a release or > > saying no, we will not fix these issues. > > > > Perhaps we need a podling disclaimer for all podling releases that > > explains more about what is a podlings and what is an incubating > > release. Perhaps it can contain appropriate caveats that the release > > may have issues that are being worked on that up to and including > > licensing issues. Links to Jira as well would be good. Then if we > > enforce tickets about known issues, we can both hold podlings > > accountable and enlighten users about the risks. > > > > I agree there are some examples where podlings are pushing our good > > faith on not fixing issues. But there are others that are just > > overwhelmed and we need to help more with the podlings where English is > > a second language. Perhaps something to ask the new D committee to > > assist with. Lots of discussion about overcoming language barriers of > > late on board-chat too. > > > > Regards, > > KAM > >> On 5/31/2019 11:28 PM, Justin Mclean wrote: > >> Hi, > >> > >> It been suggested a few times by several people on several lists that > >> podling releases (particularly early one’s) don’t need to comply with > >> release and distribution policy even if they have serious issues. The > >> question has been asked to the board several times but we’ve never got a > >> clear answer (as the question is hypothetical) or the answer is no that’s > >> not allowed. The incubator does not set those policies, the board and > >> infra do. I’m going to ask the board to give us a clear answer on this to > >> see if they are OK to grant an exception to those policies for podling > >> releases and if our current DISCLAIMER covers those sort of issues. > >> > >> Anyone have anything to add or any objections to this before I ask them? > >> > >> The serious issues I’m talking about here include compiled source or > >> inclusion of GPL (or other Category X) code in a source release or a > >> Category X dependancy or include code that
Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top Level Project' resolution to board
It has been 8 days pass since the vote started, and the vote has passed with… 13 binding +1s 10 no-binding +1s and no -1s. I will email the 'Submission of the Resolution' to board@ It is my understanding that is all I need to do, that it is the board that will include the resolution under special orders for April's agenda. Is this correct? regards, Mick On Tue, 19 Mar 2019 at 16:21, Mick Semb Wever wrote: > > > > After the latest discussion amongst this dev community on this dev mailing > list[1], presenting Sheng Wu as the PMC Chair and the maturity model[2], and > then the discussion again on the incubator list[3], a vote for Apache > SkyWalking graduating to a top level project was called and has passed[4]. > From the past incubator discussions the PPMC altered the draft graduation > proposal, specifically the proposed PMC list: removing some inactive people > and adding all the podling Committers. > > > Apache SkyWalking entered the incubator on December of 2017. SkyWalking has > delivered 8 releases so far in total, and now shows a good cadence of > successful releases. > > During the podling's time in the Apache Incubator there has been > 3200+ commits on development of the project, > 378 Issues tagged as question in GitHub created, 373 resolved, > 850+ Pull request created and resolved, > 97 different contributors, > 9 elected new committers, and > 3 elected new PPMC members. > > And the dev ML has had 72 participants: > https://lists.apache.org/trends.html?d...@skywalking.apache.org:2019 > > Attached is the draft Resolution for the PPMC and IPMC to vote upon. > > Please take a minute to vote on whether or not Apache SkyWalking should > graduate to a Top Level Project by responding with one of the following: > > [ ] +1 Apache SkyWalking should graduate. > [ ] +0 No opinion > [ ] -1 Apache SkyWalking should not graduate (please provide the reason) > > The VOTE is open for a minimum of 72 hours. As there has been previous > discussions on past versions of this proposal, I have not preluded the vote > with a DISCUSS email. If feedback arises the vote period will be extended in > good faith. > > regards, > Mick > > > [1] > https://lists.apache.org/thread.html/9aab116a5df46d10a655bbf243f525260bad7763f6f65bce19ec33bd@%3Cdev.skywalking.apache.org%3E > [2] > https://cwiki.apache.org/confluence/display/SKYWALKING/Apache+Maturity+Model+Assessment+for+SkyWalking > [3] > https://lists.apache.org/thread.html/68b06b2efdcd4f519cd9aa3df55d46bf0dade28002065fbad75d4195@%3Cdev.skywalking.apache.org%3E > [4] > https://lists.apache.org/thread.html/9f05862dffb40a967f867ba0fee4ab8549b08736cde27571e303ab30@%3Cdev.skywalking.apache.org%3E > > > > > Establish the Apache SkyWalking 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 application performance management and monitoring (APM). > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache SkyWalking Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache SkyWalking Project be and hereby is > responsible for the creation and maintenance of software related to > application performance management and monitoring (APM); and > be it further > > RESOLVED, that the office of "Vice President, Apache SkyWalking" 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 > SkyWalking Project, and to have primary responsibility for management of > the projects within the scope of responsibility of the Apache SkyWalking > 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 SkyWalking > Project: > > * Haoyang Liu (刘浩杨) > * Hongtao Gao (高洪涛) > * Ignasi Barrera > * Mick Semb Wever > * Sheng Wu (吴晟) > * Shinn Zhang (张鑫) > * Willem Ning Jiang (姜宁) > * Yongsheng Peng (彭勇升) > * DongXue Si (司冬雪) > * Jian Tan (谭建) > * Kai Wang (王凯) > * Yang Bai (柏杨) > * Yao Wang (王垚)
[VOTE] Recommend 'Apache SkyWalking graduation to Top Level Project' resolution to board
After the latest discussion amongst this dev community on this dev mailing list[1], presenting Sheng Wu as the PMC Chair and the maturity model[2], and then the discussion again on the incubator list[3], a vote for Apache SkyWalking graduating to a top level project was called and has passed[4]. From the past incubator discussions the PPMC altered the draft graduation proposal, specifically the proposed PMC list: removing some inactive people and adding all the podling Committers. Apache SkyWalking entered the incubator on December of 2017. SkyWalking has delivered 8 releases so far in total, and now shows a good cadence of successful releases. During the podling's time in the Apache Incubator there has been 3200+ commits on development of the project, 378 Issues tagged as question in GitHub created, 373 resolved, 850+ Pull request created and resolved, 97 different contributors, 9 elected new committers, and 3 elected new PPMC members. And the dev ML has had 72 participants: https://lists.apache.org/trends.html?d...@skywalking.apache.org:2019 Attached is the draft Resolution for the PPMC and IPMC to vote upon. Please take a minute to vote on whether or not Apache SkyWalking should graduate to a Top Level Project by responding with one of the following: [ ] +1 Apache SkyWalking should graduate. [ ] +0 No opinion [ ] -1 Apache SkyWalking should not graduate (please provide the reason) The VOTE is open for a minimum of 72 hours. As there has been previous discussions on past versions of this proposal, I have not preluded the vote with a DISCUSS email. If feedback arises the vote period will be extended in good faith. regards, Mick [1] https://lists.apache.org/thread.html/9aab116a5df46d10a655bbf243f525260bad7763f6f65bce19ec33bd@%3Cdev.skywalking.apache.org%3E [2] https://cwiki.apache.org/confluence/display/SKYWALKING/Apache+Maturity+Model+Assessment+for+SkyWalking [3] https://lists.apache.org/thread.html/68b06b2efdcd4f519cd9aa3df55d46bf0dade28002065fbad75d4195@%3Cdev.skywalking.apache.org%3E [4] https://lists.apache.org/thread.html/9f05862dffb40a967f867ba0fee4ab8549b08736cde27571e303ab30@%3Cdev.skywalking.apache.org%3E Establish the Apache SkyWalking 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 application performance management and monitoring (APM). NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache SkyWalking Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache SkyWalking Project be and hereby is responsible for the creation and maintenance of software related to application performance management and monitoring (APM); and be it further RESOLVED, that the office of "Vice President, Apache SkyWalking" 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 SkyWalking Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache SkyWalking 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 SkyWalking Project: * Haoyang Liu (刘浩杨) * Hongtao Gao (高洪涛) * Ignasi Barrera * Mick Semb Wever * Sheng Wu (吴晟) * Shinn Zhang (张鑫) * Willem Ning Jiang (姜宁) * Yongsheng Peng (彭勇升) * DongXue Si (司冬雪) * Jian Tan (谭建) * Kai Wang (王凯) * Yang Bai (柏杨) * Yao Wang (王垚) * Zhang Kewei (张科伟) * Can Li (李璨) * Jiaqi Lin (林嘉绮) * Jinlin Fu (付金林) * Lang Li (李浪) * Wenbin Wang (王文斌) * Yixiong Cao (曹奕雄) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sheng Wu (吴晟) be appointed to the office of Vice President, Apache SkyWalking, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache SkyWalking Project be and hereby is tasked with the migration and rationalization of the Apache Incubator SkyWalking podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)
> SkyWalking received all feedbacks from our mentors and committers. > 1. Luke Han(mentor) asked for `step down`. > 2. All committers accept the `Invitation with condition`[1] Thanks Shen. Everyone, here's the updated graduation proposal, the third version of "take2", that includes the revised PMC list. == Establish the Apache SkyWalking 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 application performance management and monitoring (APM). NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache SkyWalking Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache SkyWalking Project be and hereby is responsible for the creation and maintenance of software related to application performance management and monitoring (APM); and be it further RESOLVED, that the office of "Vice President, Apache SkyWalking" 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 SkyWalking Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache SkyWalking 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 SkyWalking Project: * Haoyang Liu (刘浩杨) * Hongtao Gao (高洪涛) * Ignasi Barrera * Mick Semb Wever * Sheng Wu (吴晟) * Shinn Zhang (张鑫) * Willem Ning Jiang (姜宁) * Yongsheng Peng (彭勇升) * DongXue Si (司冬雪) * Jian Tan (谭建) * Kai Wang (王凯) * Yang Bai (柏杨) * Yao Wang (王垚) * Zhang Kewei (张科伟) * Can Li (李璨) * Jiaqi Lin (林嘉绮) * Jinlin Fu (付金林) * Lang Li (李浪) * Wenbin Wang (王文斌) * Yixiong Cao (曹奕雄) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sheng Wu (吴晟) be appointed to the office of Vice President, Apache SkyWalking, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache SkyWalking Project be and hereby is tasked with the migration and rationalization of the Apache Incubator SkyWalking podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator SkyWalking podling encumbered upon the Apache Incubator PMC are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)
> > > That can only be done if the committers have agreed to becoming > > > members, > > > > That is correct, they need to be offered and they need to agree. > > > > > in which case you might as well add them to the PPMC before > > > graduation. > > > > Since PPMC is an artificial construct that isn't recognized by the > > foundation -- this part is moot. IOW, after these individuals agree > > they may as well be put on the resolution straight away. > > Yes, and LDAP will need to be adjusted in Whimsy after graduation. > > I think there are two choices: > 1) follow the normal route to add committers to the PPMC and copy the > final list to the proposal. > This means sending a NOTICE to the IPMC, etc. > > 2) Conditionally invite the committers (proposal could fail), and add > them to the proposal. > Don't add them to the PPMC (because there has been no IPMC NOTICE) > If the proposal succeeds, then Whimsy can be used to update LDAP membership. Thanks for the clarification. I was becoming quite confused and unhelpful as a mentor at one point there :-) My understanding, with discussions with Sheng, is that they presumed (2) was possible and currently are following that approach. The confirmation by each of the current Committers that they are happy to become PMC should be cc'd to the private@skywalking ML. Sheng, can you also get confirmation from the mentors that they wish to be part of the graduated PMC. You have that confirmation from me. cheers, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)
> If possible can one of the PPMC members / mentors explain what these > issue are in a little more detail. All 7 items are resolved. The "Three most important issues to address in the move towards graduation" section had been misread by all of us, as the list had accumulated over time, and is now only consisting of resolved items. It's been fixed in the report. https://incubator.apache.org/projects/skywalking.html was more accurate, in that it provides dates over resolved items. regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)
> May I see a link to the planned Graduation Resolution? The planned graduation resolution is in this DISCUSS thread above, specifically here: https://lists.apache.org/thread.html/bf9512ac5441f602c41fe8fe7e11d9fa6121f04fc8d3f0cd39249b13@%3Cgeneral.incubator.apache.org%3E That includes the updates addressing feedback from both Justin and Sebb. Removing those two initial PPMC that have since been quiet has not been done, I'm waiting on confirmation on whether that is needed/requested. regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)
> I think the question is not "Is SkyWalking ready to graduate" but "Is > the proposed PMC list accurate". > > The PMC members are responsible for governing the TLP and as such need > to be familiar with what is expected of them. Governance activities are > conducted on the PPMC private list. If a PPMC member has not > participated in any governance activities during incubation, it's > unclear that they belong on the PMC. > > Reviewing the last several months of private@skywalking list, most of > the discussion of new committers has had only four or five > participants, who are clearly involved in governance of the project. If this is a criteria then there are two trusted committers from the initial podling creation that have since then not been active. They should be then removed. They are Sheng Wang and Yuntao Li. Those that were added in the last round will not have been involved in any private threads, and only the vote threads are on private. Every other podling related discussion has happen on the dev ML. > Well the graduation was put off last time because the project was not > correctly recognising merit, and they have fixed that by voting more folks > but but if they are not active then I’m not sure what has been fixed. It > seems this could be a symptom of the same problem? It is not. Those that have been added recently have had no need to be involved in any private ML discussions, as there has't been any since. It becomes a bit absurd if those PPMC last added can never be included in any podling graduation proposal. > Out of interest do we know who those 4 or 5 people work for (or the rest of > the proposed PMC members)? It’s good to have a PMC consisting of people from > different companies. They are from different companies: - Cloud Wise - terminus.io - tetrate.io - Daocloud - Ke Finance - Huawei - Tingyun - Cianiao - Yonghui super market - VBill Payment Co. And I don't see more than two PPMC from the same company. regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)
> > The cookies in the moderator mails expire after a few days. > This example was all done today. Numerous attempts have been made. > It also means that the person is aware that the private@ list is > something they need to follow. Not getting any response at all is not an indication of whether the list exist of not, unfortunately. Anyway… to the thread's discussion: every PPMC received an invitation (per Apache template) that requested subscription to both dev and private ML. Reading the ASF guidelines here: https://apache.org/foundation/governance/pmcs.html#communication ; I interpret it as they SHOULD be subscribed rather than MUST, and I'm curious as to whether how many of the TLPs are actually enforcing this among their pmc, if any. It's an interesting discussion… but I'm not entirely convinced it's an accurate shortcoming to whether the podling is ready for graduation or not. regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)
> Whimsy currently shows 6 PPMC members who are not subscribed. Digging into this more… It looks there's also been troubles subscribing from China, or more accurate receiving the confirm subscription emails from apache to chinese inboxes. (And it wouldn't surprise me if after creating a new mail accounts and getting things to work, folk would be forgetting then about private@skywalking ) There's some oddity like Yao Wang who is subscribed to dev ML but is not getting the confirm email using the same email address for the private ML. For example: ``` Hi. This is the qmail-send program at apache.org. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : ezmlm-manage: fatal: Illegal or outdated moderator request (#5.7.1) ``` Indeed if I look through my inbox I see some of those missing from the private ML having matching "CONFIRM subscribe to priv...@skywalking.apache.org" emails. But they say they did not get those emails. Folk are also just using the list.apache.org website, which is of no surprise considering the above errors. We'll continue with this, as the Chinese communities will need to have this sorted out, but we do believe that all have attempted to subscribe. Is there a reason that people with @apache.org addresses have to manually subscribe to these lists, if it's so mandatory? I would have thought this is something that should just then be automatic, and then in this situation it's just the problem of ensuring the @apache.org address is successfully forwarding emails. regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)
> I’m still not 100% sure that this project its ready to graduate. > Looking at the roster [1] only 1/2 the the proposed PMC members are > signed up to the projects private list. Some of the people suggested > have limited interaction on the mailing list(s) and in a couple of > cases have never sent an email to them that I can find. How was this > PMC list determined and where was this discussed? Perhaps the roster > needs to be adjusted in the proposal for it to be accepted by the IPMC? > What do others think? Yeeaah, something that's not catching me off-guard :-) I noticed this before we started this thread. We went through the roster and most of those "missing" are subscribed with other (non-apache) addresses. Most of them are there and have been involved, also discussion on the private ML is frowned upon except for votes on new committers/ppmc or security issues, so more activity is present on dev and notifications. There are two that have been quiet/inactive, but they remain trusted, so I would hesitate to remove them (as per norm for ASF projects). regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP (take2)
Thanks Justin for the reminder, this came up during the first discussion too and I completely skipped it. The updated proposal is, including improvement from Sebb's feedback, == Establish the Apache SkyWalking 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 application performance management and monitoring (APM). NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache SkyWalking Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache SkyWalking Project be and hereby is responsible for the creation and maintenance of software related to application performance management and monitoring (APM); and be it further RESOLVED, that the office of "Vice President, Apache SkyWalking" 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 SkyWalking Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache SkyWalking 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 SkyWalking Project: * Haoyang Liu (刘浩杨) * Hongtao Gao (高洪涛) * Ignasi Barrera * Luke Han (韩卿) * Mick Semb Wever * Sheng Wu (吴晟) * Shinn Zhang (张鑫) * Willem Ning Jiang (姜宁) * Yongsheng Peng (彭勇升) * DongXue Si (司冬雪) * Jian Tan (谭建) * Kai Wang (王凯) * Sheng Wang (旺盛) * Yang Bai (柏杨) * Yao Wang (王垚) * Yuntao Li (李运涛) * Zhang Kewei (张科伟) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sheng Wu (吴晟) be appointed to the office of Vice President, Apache SkyWalking, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache SkyWalking Project be and hereby is tasked with the migration and rationalization of the Apache Incubator SkyWalking podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator SkyWalking podling encumbered upon the Apache Incubator PMC are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP (take2)
> > > > 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 application performance monitoring: especially for > > microservice, Cloud Native and container-based architecture systems; > > also known as a distributed tracing system. . > > Seems to me this is a bit too specific (and long) - can the example > target systems be left out? > > e.g. it could perhaps be rephrased as: > > related to application performance monitoring (aka a distributed tracing > system) If this project description is to be updated in the graduation proposal, does it also need to be updated in the podling status file? and anywhere else? regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP (take2)
Apache SkyWalking entered incubation in December of 2017. The SkyWalking community has learnt a lot about how to do things in The Apache Way. The first time graduation was raised for discussion, five months ago, the IPMC thought SkyWalking was not yet ready because of issues around "Community growth and in particular how merit is recognised". That pushback has been helpful, the community has become a more open and engaged community. SkyWalking is making more consensus decisions via the ML, including discussions and decisions on issue, test, release, new committer and branding issues. Since the last graduation discussion, the community has voted in 9 new committers, 3 of them also as PPMC members. SkyWalking has also helped Zipkin with podling learnings. And having a Zipkin mentor involved in the recent discussions about the role and mechanisms of the IPMC and the board, and any possible improvements that could be made to the Incubator, it's witnessed and had a positive experience on the importance of being involved in the broader Apache community. After discussion in the podling's community on the dev ML https://lists.apache.org/thread.html/9aab116a5df46d10a655bbf243f525260bad7763f6f65bce19ec33bd@%3Cdev.skywalking.apache.org%3E …and no objections, I'm raising the thread here for further discussion. Some stats and the proposed resolution is below, but let us know if there's any other information we can provide to re-assure that the podling is ready for graduation. A few stats to help with the discussion: SkyWalking has delivered 8 releases so far in total, and appears now to have a good cadence of successful releases. During the podling's time in the Apache Incubator there has been 3200+ commits on development of the project, 378 Issues tagged as question in GitHub created, 373 resolved, 850+ Pull request created and resolved, and 97 different contributors. The dev ML has had 72 participants. https://lists.apache.org/trends.html?d...@skywalking.apache.org:2019 Also please check out Apache Maturity Model Assessment for SkyWalking https://cwiki.apache.org/confluence/display/SKYWALKING/Apache+Maturity+Model+Assessment+for+SkyWalking regards, Mick Semb Wever (SkyWalking mentor) == Establish the Apache SkyWalking 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 application performance monitoring: especially for microservice, Cloud Native and container-based architecture systems; also known as a distributed tracing system. . NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache SkyWalking Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache SkyWalking Project be and hereby is responsible for the creation and maintenance of software related to application performance monitoring: especially for microservice, Cloud Native and container-based architecture systems; also known as a distributed tracing system. ; and be it further RESOLVED, that the office of "Vice President, Apache SkyWalking" 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 SkyWalking Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache SkyWalking 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 SkyWalking Project: * Haoyang Liu (刘浩杨) * Hongtao Gao (高洪涛) * Ignasi Barrera * Luke Han (韩卿) * Mick Semb Wever * Sheng Wu (吴晟) * Shinn Zhang (张鑫) * Willem Ning Jiang (姜宁) * Yongsheng Peng (彭勇升) * DongXue Si (司冬雪) * Jian Tan (谭建) * Kai Wang (王凯) * Sheng Wang (旺盛) * Yang Bai (柏杨) * Yao Wang (王垚) * Yuntao Li (李运涛) * Zhang Kewei (张科伟) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sheng Wu (吴晟) be appointed to the office of Vice President, Apache SkyWalking, 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 SkyWalking PMC be and hereby is tas
Re: [VOTE] Release Apache NetBeans (incubating) parent 1
> Please vote accordingly: > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason +1 Hi Eric, I'm a long time user of NetBeans, my involvement the past decade has been minimal, but I am very excited about seeing Apache NetBeans. I was keen to try out the little tool that the Zipkin podling community wrote to help verify the basics on staged releases: https://github.com/openzipkin-contrib/apache-release-verification Unfortunately the tool isn't 100% for use on different projects due to little things like folder layouts and naming. But in the process a few things were unclear to me are: - what's the git sha to this release? - what's the gpg key used to sign? I had to go hunt and figure them out. I have no idea if the Incubator wishes/enforces that this information is provided in the vote email? regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator release votes
Craig, replies inline, > Apologies if these comments cross other discussions. It's hard to keep > track of all the threads that have forked from the original discussion. I'm struggling to keep up too :-/ > This is really sad, because in most of these cases the mentors have not > voted. And so it fell to the rest of the IPMC members to pay attention > enough to take time to vote. > > And recently, three cheers for Justin who has become very active in > looking at podling releases and voting. More below. >From experience, the role that Justin (and others that "interfere") take is >invaluable to the survival of the Incubator. And ultimately, in the longer >term, the foundation. I can also imagine that there are numerous problems and complaints made about the Incubator, just like there are bug tickets on each TLP. What I raised was but one, but one that was in need of an immediate voice. I don't presume that such problems are without their complications and require 'balancing', and I hope can be read in what I wrote to the board. > > 1) The Incubator's mission should be as a "facilitator". That is being a > > service provider for podlings to enter the Apache community, rather than a > > stern gatekeeper. The Incubator's website especially needs an update to > > better illustrate this spirit and goal. > > Patches welcome. Seriously though, there is very much material and a > very small bit that may seem to be contradictory. I'd suggest that when > you stumble across a confusing part, document it in an email and have a > discussion. There is a lot! And it *is* continuously improving. The organisation of it, and some knowledge about age and relevancy, especially pages under incubator.apache.org, could be improved. Even with mentoring two podlings I struggle to have (or link to) the tribal knowledge that others demonstrate. Reading some of Roy's post on the board thread only makes one feel more lost. The input of the Incubator's elders, people like Justin, are crucial here. I also think additional tooling, like those below, makes a really big difference to the motivation and enjoyment of a podlings journey: - https://incubator.apache.org/clutch/ - https://github.com/openzipkin-contrib/apache-release-verification > > > > 3) We need to relax IPMC's input on release voting… > > -- Letting the first release be dealt with only by the PPMC and mentors. > > Putting a release on Apache infrastructure has legal implications. In > order to protect individuals from legal issues, Apache requires a > release vote by the PMC (in this case, the IPMC) that passes with a > minimum of three +1 votes and more +1 votes than -1 votes. > http://www.apache.org/legal/release-policy.html#release-approval > > So when someone votes -1, that vote does not block the release. So if > all three mentors vote +1, it takes three -1 votes before any > additional voting is needed. This has been raised before. While this is technically true, and using it is itself a demonstration of the ASF rules, I don't think a cold demonstration of such is so wise against a podling's first release attempt. Many podlings will be fine, but some (particularly of different cultures/languages) will take offence before understanding. This is an example of something that can wait til a latter release. It should be easy enough to provide a softer feedback on a podling's first release. Remember these are established communities and the IPMC should, IMHO, first engage with them as strangers with no trust associated to them. I guess this also comes back to being more service-minded to the podlings. > > -- Understanding a minimal criteria every podling release must meet, and > > the broader criteria that TLP releases need to meet. And podlings only need > > to demonstrate in releases closer to graduation. > > The reason the podling releases come with a DISCLAIMER (emphasis mine) > is that perfection is not expected from podling releases. But it is > expected that before graduating, podlings are able to make releases > that are fully compliant with Apache guidelines for releases. I do hope this becomes a new agreement and a new habit in the incubator. thanks for the reply Craig, regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator release votes
> On the one side we have lengthy discussions about non-mentors from > resisting to interfere, but on the other hand podlings are begging for > such "interference". > Guess there are always two sides of the discussion. I politely disagree with you Chris. What I raised was that cold interference can be damaging to some podlings during their first release attempt. For the IPMC to endorse diversity and make the Incubator a safe and inclusive space it needs to accept that every podling community is different. Many communities will be perfectly fine with some armchair quarterbacking, appreciating the knowledge that's ultimately being shared and offered. Other communities will find it quickly overwhelming, unwelcoming and de-motivating. I do not think there's two sides to this discussion, but rather an opportunity for us to assume and accept such differences. Zipkin, like all podlings, will seek the input of the elders of the Incubator. But let them stub their toe a few times first, by themselves. regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Welcome Wagon
> An Incubator Welcome Wagon could be a Guide of Guides and include > introductory information about: > > (0) Onboarding > (1) Community Development > (2) Infrastructure and Builds > (3) Legal Policy > (4) Release Policy > (5) Press > (6) Foundation Structure +1 from me. I think also the mentors could benefit. I suspect many mentors only do a few podlings? And that means many mentors are first-timers. At least I felt kinda swamped, not so much from a lack of documentation, but a lack of presentation and organisation of it. Checklists for the different tasks would also be very welcome. regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Starting at the incubator and releases
I'll chime in, but on the technical front my experience is rather new in the incubator, i'm still learning. > Looking at some of the situations we currently have I think we may need > some more general guidance for incubating projects and making releases > after just joining the incubator. By far, the two biggest issues I see are: i) "too many cooks in the kitchen" and IPMC strangers _policing_ the rules on podlings, ii) "There is documentation _all over the place_ and it's not possible to know which of it is outdated and which is still current especially in the face of conflicting information." – Lars Francke. Addressing and improving the rules and process can help. But better documentation, automation of checks, and better communication style and channels, will go a lot further, imho. Another way to think of this is: it is not the podling that failed the release process, but the IPMC that failed the podling. Why were the tooling and documentation not put in place by the IPMC so that it then had to rely upon instead late policing and being the gatekeepers. > In this context “non approved” means > releases or distributions not approved by the PPPM and IPMC (usually by > voting) and available and promoted to the general public. Something that has been brought up is allowing a podling to incrementally improve their releases. What this actually means has not been stated clearly. The different types of resulting podling releases I'm aware of are… a) fully ASF compliant, b) legal but not fully ASF compliant, c) illegally ASF, d) staged/nightly/snapshot, e) external. With these types, my understanding is that a podling needs to demonstrate a number of releases of type (a) before raising its vote for graduation. What's not clear is what releases are (b), and where should (c) releases get hosted? (For example can they simply stay as staged releases.) If the goal is to encourage momentum, and for some podling cultures this means permitting incrementally improving ASF releases, then the more minimal the requirements to (a) are the better, and any shortcomings in releases of type (b) should be listed in a jira ticket rather than as a "-1" vote on the release. So far there's been the effort to minimise the requirements to (a), and this is very appreciated. https://lists.apache.org/thread.html/7690a00c6a8aba9f51a6dfaa9dc9273626715006eab4c43e6893a839@%3Cprivate.incubator.apache.org%3E It's still unclear to me what are all the soft requirements that when violated lead to type (b)? For example this document alludes to the distinction, but not the separation: https://wiki.apache.org/incubator/IncubatorReleaseChecklist Is this documented correctly anywhere? If this was better documented, and violations dealt with as jira tickets, it might well have been enough to have prevented the situation with Zipkin. I'm sure the same is true for the other podlings that have experienced such feedback as abrasive. Another thing is legal violations that lead to (a) but that are not specific to one podling, should not suddenly become a burden on a podling doing its first release. If other releases have the problem, for example it's not been properly identified before, it's brand new or the dust on how to deal with it is still settling, then for the love of god don't decide to pick on it with a podling's *first* release attempt. Get it in order (settled and documented) elsewhere before policing the podling. Taking release violations up with mentors first would also be another way around this problem. I'm also in favour of aiming for deprecating the need for the IPMC votes. With the correct documentation and tooling in place the PPMC vote with 3 mentors approval should be enough to get a release to at least type (b). > This doesn’t > cover snapshots, RCs or nightly which are not advertised to the general > public. Feedback / changes / thoughts from the rest of the IPMC members > welcome. Docker images need to be staged somewhere. Just like the actual convenience binaries need to be signed, checksummed, and tested as-is. So should docker images before they are released to https://hub.docker.com/u/apache Having to build docker images, to verify them as a release candidate, is not cool. Is this something we are to request of Infra? > 2. Can the PPMC make unapproved releases in other places after joining > the incubator? > > No but 3rd parties can and someone from the PPMC can act as a 3rd > party, it must be clear that: > a) These are produced by a 3rd party and not the PPMC and follow > Apache's branding and trademark policy. > b) This is not being used as a mechanism to avoid making Apache > releases. Please make it clear, and do what you can, to support a podling's existing release cadence. The Zipkin community with 15 repositories makes regular (fortnightly) releases. Just because one repository has been migrated to ASF does not mean the other 14
Re: the case of the maven wrapper
> > One of the tings I've noticed is that the vetos on a podling's first > > release can be a bit harsh. > > A -1 on a release is not a veto. A release can still pass if it gets 3 > +1 votes. However in this case because of the jar in a source release > it’s unlikely IMO to get 3 +1 IPMC votes. You're quite right. A "-1" is not a veto on a release vote. (It is on any other vote.) https://www.apache.org/foundation/voting.html I would still say that many people, especially those new to ASF, feel that a "-1" is a veto (and receive it harshly). As Incubator VP people do respect you, and comments on how we expect releases to be fixed (or improved for next time) i believe would be received better without the "-1", even if technically you are correct (and you are providing the feedback on ASF voting actually works). > > This would add some burden to the Incubator. > > I doubt the board will allow the incubator to do this, if you see an > issue at a TLP you can alway ask them to fix it al well. My suggestion/thought-bubble wasn't the burden being the responsibility in getting graduate projects in fixing their violations, but only in surveying the precedence and extent of violations among ASF projects. regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: the case of the maven wrapper
> As binaries are not allowed in source repos, the maven wrapper > introduces a small java source file which bootstraps the tool. This > has Apache license headers on it. Takari is an Apache licensed codebase. My understanding is that there is a requirement to include it in the NOTICE.txt file. Furthermore, Takari contains no copyright. Is this of concern? http://www.apache.org/dev/licensing-howto.html https://www.apache.org/legal/src-headers.html > As a part of Zipkin's first attempt to vote a release on the general > list … asking for it to be in the NOTICE box. One of the tings I've noticed is that the vetos on a podling's first release can be a bit harsh. I do really love the "community over code" motto, and i would hope to see the incubator being a leader in displaying the warmth and inclusion that leads to a healthy and enjoyable community. On releases I would rather see such vetos replaced with comments that are feedback, while still obvious that they are an issue that is expected to be fixed by the next release (and before graduation). I think this would be warmer feedback, and permit a more incremental approach to getting to the standard of release required for graduation. Momentum and results is an important motivator, and there's a lot to learn about the ASF requirements on the podling's journey to graduation. > It feels we are just > adding things to it and as an end user, I'm not sure how this would > add clarity. An apache release is first aimed at someone who builds the source artefact. Even if this isn't the popular use-case. This also highlights the value in having the takari wrapper in place. > Even if it did, I'm concerned that we are jumping to a > enforcement remediation when no-one seems to be doing it at all. I've seen this unfairness bite a bit already. Feedback that the incubator provides to podlings should be in context of the broader precedence in the ASF. If it's something that's not being strictly adhered to by graduate projects, it would make a world of difference to podlings if they saw everyone was getting pulled up on the violation. Otherwise it comes across as podlings are required to meet a standard well above the graduate projects, and that becomes a real deterrence for many to entering Apache. This would add some burden to the Incubator. Surveys of graduate projects would be required to see such precedence on issues. And resulting feedback to graduate projects can also be tricky, nobody likes to feel that they are being picked on. IDK, but maybe this feedback can go to the board, and the board can pick one issue per quarter and request projects address them by their next board report. regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-alpha
> Voting will start now (10th Nov. date) and will remain open for at least > 72 hours, Request IPMC to give their vote. > [ ] +1 Release this package. > [ ] +0 No opinion. > [ ] -1 Do not release this package because +1 (binding) Checked: - signatures and digests - source download builds - top level docs (README++) - rat check regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP
> Although a mistake was also made in not first voting this person in as a > committer. Correction. A previous vote had occurred for committer role, as I wrote below > Haoyang Liu was voted on to be a committer, and then later to PPMC. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP
Justin, answers inline… > I think that perhaps that SkyWalking may need to stay a little longer in > the incubator as: > - There still doesn’t seem to be a lot of discussion on the development > list. > - The initial PMC list doesn’t include all fo the current PPMC and > committers on the roster (and I cannot see any discussion about this). Well spotted. DongXue Si, Kai Wang, Sheng Wang, Yang Bai, Yuntao Li, Zhang Kewei, should all be part of the PPMC (and should have been from the podling creation). This has been corrected. > - A search of the private list show only one PPMC added past the initial > commuter list and they were added without NOTICE being sent (and only > corrected when I pointed it out). This was a mistake made, mea cupla, confusing the process for adding the initial PPMC and adding new PPMC. Everyone learnt by the mistake being made. Although a mistake was also made in not first voting this person in as a committer. > - The podling roster lists both PPMC and committers [1], including > people not on the initial list [2], but I’m unable to find any > discussion or votes to why they were added. Haoyang Liu was voted on to be a committer, and then later to PPMC. Shinn Zhang is Xin Zhang, who appears in the original proposal. There was some confusion about clashing apache IDs early on. This is one of the reasons I like see the chinese name used after the english name. > - Has a software grant been received or IP clearance happened? A software grant was not necessary, everything adequately covered by ICLAs. The IP clearance was done initially, but maybe we've missed a formality? Much appreciated that you've spotted these things Justin. regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP
After discussion in the podling's community on the dev ML https://lists.apache.org/thread.html/4ee8894c99275ee0f14fcdb250a66ef9d22a7ba87742fa613897849f@%3Cdev.skywalking.apache.org%3E and on a github ticket https://github.com/apache/incubator-skywalking/issues/1768 culminating with a positive vote https://lists.apache.org/thread.html/da9768f15c6448d5045409317baacd6a7eb441b99807c6a62478048a@%3Cdev.skywalking.apache.org%3E We'd like to bring this to a discussing at the IPMC. Please see the proposed resolution below and let us know what do you think. A few stats to help with the discussion: Now we have the developers from Tetrate, Bitmain, Huawei, OneAPM, Tingyun APM, Cloudwise APM, Alibaba Cainiao, dangdang.com, jd.com, VBill Payment, yonghui superstore, Tydic, terminus During the podling's time in the Apache Incubator there has been 2200+ commits on development of the project, 240+ Issues tagged as question in GitHub created, 236 resolved, 700+ Pull request created and resolved, and 65 different contributors. The dev ML has 32 subscribers. https://lists.apache.org/trends.html?d...@skywalking.apache.org:2018-9 Also please check out Apache Maturity Model Assessment for SkyWalking https://cwiki.apache.org/confluence/display/SKYWALKING/Apache+Maturity+Model+Assessment+for+SkyWalking regards, Mick Establish the Apache SkyWalking 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 application performance monitoring: especially for microservice, Cloud Native and container-based architecture systems; also known as a distributed tracing system. . NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache SkyWalking Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache SkyWalking Project be and hereby is responsible for the creation and maintenance of software related to application performance monitoring: especially for microservice, Cloud Native and container-based architecture systems; also known as a distributed tracing system. ; and be it further RESOLVED, that the office of "Vice President, Apache SkyWalking" 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 SkyWalking Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache SkyWalking 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 SkyWalking Project: * Haoyang Liu (刘浩杨) * Hongtao Gao (高洪涛) * Ignasi Barrera * Luke Han (韩卿) * Mick Semb Wever * Sheng Wu (吴晟) * Shinn Zhang (张鑫) * Willem Ning Jiang (姜宁) * Yongsheng Peng (彭勇升) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sheng Wu (吴晟) be appointed to the office of Vice President, Apache SkyWalking, 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 SkyWalking PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache SkyWalking Project; and be it further RESOLVED, that the Apache SkyWalking Project be and hereby is tasked with the migration and rationalization of the Apache Incubator SkyWalking podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator SkyWalking podling encumbered upon the Apache Incubator PMC are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache ServiceComb (incubating)
> Please vote on the resolution pasted below to graduate > Apache ServiceComb from the incubator to the top level project. > > [ ] +1 Graduate Apache ServiceComb from the Incubator. > [ ] +0 Don't care. > [ ] -1 Don't graduate Apache ServiceComb from the Incubator because... +1 (binding) regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Does Zipkin need to sign a SGA ?
It's come up that the migration of the github Zipkin repositories to ASF requires either a signed SGA or a sign-off from the Secretary. Chris raised this on `INFRA-16989 – Zipkin incubator project request for the GitHub repositories moving service`. I was under the impression that if the Copyright was already held by the community, it is held by 'The OpenZipkin Authors', that the ICLA from all those authors would suffice and a SGA not be required. And it's news to me that this would also require a sign-off from the ASF Secretary. What's the correct process here? who can help? should I forward the question to the Secretary? regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-RC2
> Voting will start now (2018/9/8 date) and will remain open for at least > 72 hours, Request IPMC to give their vote. > [ ] +1 Release this package. > [ ] +0 No opinion. > [ ] -1 Do not release this package because +1 Checked - sha512s ok - checked maven artefacts - source artefact builds - source artefact contents - DISCLAIMER, LICENSE and NOTICE files Question: - how come the binary comes in zip format but the source does not. regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: New podlings reporting schedule is monthly for 3 months
> It looks like Mick > added them without any prompting, but I'm not sure if there was any off > list discussion about it. That was just a bias for action. The reporting schedule had been entered into podlings.xml as group 3, and I just hurried to write the report on the presumption that cut-offs were strict to calendar months. Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-RC2
> First of all, there is a direct link to that build page, in README of > master and 5.x branches. See > https://github.com/apache/incubator-skywalking#compiling-project > We have both links to document and compiling guide. This is excellent in my opinion. >From the terminal I can read the README.md which clearly states: > # Compiling project > Follow this [document](docs/en/guides/How-to-build.md). Then opening, again from the terminal, `docs/en/guides/How-to-build.md` gives me everything i need to know. Justin, given that the next release will provide this information so clearly from the base directory, knowing that the next release will be in order, are you ok with letting this release pass through? regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-RC
Sheng, > Thank for guide. Document is included in source release. But i don't > point to there. It is in the source release, but it could be simpler to find. I think it would be fine if you added to the README.md a "Building" section like ``` # Building See documentation in docs/en/How-to-build.md ``` With this you can/should remove the "Guide to build the release from source" section from your release test/vote/announce emails. > So in your perspective, do we need another vote of this version, or > could fix this next time? Yes you will need a new release and vote :( Both LICENSE and NOTICE needs fixing. AFAIK regardless if you include antd, as iconfont is transitively included then the MIT license must be included too. regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Accept Zipkin into the Apache Incubator
> This vote will run at least 72 hours. Please VOTE as follows: > > [ ] +1 Accept Zipkin into the Apache Incubator > [ ] +0 No opinion > [ ] -1 Do not accept Zipkin into the Apache Incubator because… 72 hours has passed and the vote for accepting Zipkin into Apache Incubator has passed with: 15 binding "+1" votes 12 non-binding "+1" votes no "0" and no "-1" votes Binding votes: - Ate Douma - Henry Saputra - Mark Struberg - Byung-Gon Chun - Kevin A. McGrail - Josh Elser - Matt Sicker - Andrew Purtell - Ignasi Barrera - Willem Jiang - Von Gosling - Romain Manni-Bucau - James Taylor - Greg Trasuk - Mick Semb Wever Non-binding votes: - Adrian Cole - xin zhang - Sheng Wu 吴晟 - Xin Wang - Ashish Paliwal - Zen Lin - Andrey Redko - Mike Drob - Arpit Agarwal - Deepak Nair - Brian Devins - Peng Yongsheng 彭勇升 regards, Mick References: - VOTE: https://lists.apache.org/thread.html/3e4fe5458b8e545dbb18c5b54457259ccd74f117bac3d50005e40132@%3Cgeneral.incubator.apache.org%3E - PROPOSAL: https://lists.apache.org/thread.html/54798a5059db1d5716ed9910a15c92945509a25ec3b7ccb6b1215c53@%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: [VOTE] Accept Zipkin into the Apache Incubator
> This vote will run at least 72 hours. Please VOTE as follows: > > [ ] +1 Accept Zipkin into the Apache Incubator > [ ] +0 No opinion > [ ] -1 Do not accept Zipkin into the Apache Incubator because… +1 Accept Zipkin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Accept Zipkin into the Apache Incubator
l: staying for the community we've built. Our ASF champion, Mick Semb Wever, is both a committer and an experienced ASF member. The Zipkin developers thrive upon the diversity of the community. The Zipkin gitter channel is always active, and the developers often collaborate on fixes and changes in the code. They are always happy to answer users' questions as well. Zipkin is interested in continuing to expand and strengthen its network of developers and community members through the ASF. === Reliance on Salaried Developers === Zipkin has one full time salaried developer, Adrian Cole. Though some of the developers are paid by their employer to contribute to Zipkin, many Zipkin developers contribute code and documentation on their own time and have done so for a lengthy period. Given the current stream of development requests and the committers' sense of ownership of the Zipkin code, this arrangement is expected to continue with Zipkin' induction into the ASF. === Relationships with Other Apache Products === Zipkin, Apache Incubator Skywalking and Apache Incubator HTrace address similiar use cases. Most similarities are between Zipkin and HTrace: Zipkin hopes to help serve the community formerly served by HTrace, but understands the data services focus of HTrace may require different tooling. SkyWalking addresses more feature surface than Zipkin. For example, metrics collection is not a goal of Zipkin, yet it is a goal of SkyWalking. SkyWalking accepts Zipkin formats and can be used as a replacement server. SkyWalking PPMC member, Sheng Wu, has been a routine member of Zipkin design discussions and has offered to help Zipkin through ASF process. While Zipkin does not directly rely upon any Apache project, zipkin supports several Apache projects. Apache CXF, Apache Camel, Apache Incubator SkyWalking, Apache Incubator Dubbo, Apache Incubator ServiceComb and Apache Incubator HTrace all utilize Zipkin APIs in their core repositories. Many more do via community extensions. Apache Maven is primarily use by Zipkin, and can be used by projects who build upon Zipkin projects. === A Excessive Fascination with the Apache Brand === Zipkin recognizes the fortitude of the Apache brand, but the motivation for becoming an Apache project is to strengthen and expand the Zipkin community and its user base. While the Zipkin community has seen steady growth over the past several years, association with the ASF is expected to expedite this pattern of growth. Development is expected to continue on Zipkin under the Apache license whether or not it is supported by the ASF. == Documentation == The Zipkin project documentation is publicly available at the following sites: * https://zipkin.io: project overview * http://zipkin.io/zipkin-api/#/: swagger specification * https://github.com/openzipkin/b3-propagation: header formats * https://zipkin.io/zipkin/: Javadocs for the Zipkin server == Initial Source == The initial source is located on GitHub in the following repositories: * git://github.com/OpenZipkin/zipkin.git * git://github.com/OpenZipkin/zipkin-dependencies.git * git://github.com/OpenZipkin/zipkin-api.git * git://github.com/OpenZipkin/b3-propagation.git * git://github.com/OpenZipkin/docker-zipkin.git * git://github.com/OpenZipkin/docker-zipkin-dependencies.git * git://github.com/openzipkin/zipkin-reporter-java * git://github.com/openzipkin/brave * git://github.com/openzipkin/zipkin-aws * git://github.com/openzipkin/docker-zipkin-aws * git://github.com/openzipkin/zipkin-azure * git://github.com/openzipkin/docker-zipkin-azure * git://github.com/openzipkin/zipkin-gcp * git://github.com/openzipkin/docker-zipkin-gcp * git://github.com/openzipkin/brave-cassandra * git://github.com/openzipkin/docker-jre-full * git://github.com/openzipkin/brave-karaf Depending on community progress, other repositories may be moved as well == Source and Intellectual Property Submission Plan == Zipkin's initial source is licensed under the Apache License, Version 2.0. https://github.com/openzipkin/zipkin/blob/master/LICENSE All source code is copyrighted to 'The OpenZipkin Authors', to which the existing core community(members list in Initial Committers) has the rights to re-assign to the ASF. == External Dependencies == This is a listing of Maven coordinates for all of the external dependencies Zipkin uses. All of the dependencies are in Sonatype and their licenses should be accessible. == Cryptography == Zipkin contains no cryptographic algorithms. = Required Resources = == Mailing Lists == * Zipkin-dev: for development discussions * Zipkin-user: for community discussions * Zipkin-private: for PPMC discussions * Zipkin-commits: for code changes == Git Repositories == The Zipkin team is experienced in git and requests to transfer GitHub repositories(list in Initial Source) to Apache. == Issue Tracking == The community would like to continue using GitH
Re: [Question] Whimsy check about Image and website of SkyWalking project
> > Seems to me the script that generates that page has a bug. Thanks John and Craig. Shane helped us out on the whimsy ML https://lists.apache.org/thread.html/56c0a8dea0ec048661fa831dd958f0e41f15344d4325ece37fb5e662@%3Cdev.whimsical.apache.org%3E Shane highlighted that it was important that those keywords were themselves linked to the required urls. regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Question] Whimsy check about Image and website of SkyWalking project
> 2. The other question is, project should include its log in here[3], but > I didn't find the way to upload it. How should I do that? John, do you have any idea how/where these logos are uploaded to? regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ServiceComb Saga (incubating) version 0.2.0
> [ ] +1 Release this package as 0.2.0 > [ ] +0 No Opinion > [ ] -1 Do not release this package because +1 binding note, LoadBalancedClusterMessageSenderTest hangs when building. While using just`mvn install -DskipTests` works. Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
