> 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 12 +1s (9 from PMC).
>
vote thread was
https://lists.apache.org/thread/j1tz0t90q72l3hp8frv9xzr0ozqstgg9
.
> 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 12 +1s (9 from PMC).
Please vote on the acceptance of the GoCQL driver and its IP Clearance:
https://incubator.apache.org/ip-clearance/cassandra-gocql-driver.html
All consent from original authors of the donation, and tracking of
collected CLAs, is found in:
- https://github.com/gocql/gocql/issues/1751
-
https://cwi
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-1896
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.
>>
>
> 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-drive
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
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
tion 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 matu
刘浩杨)
* Hongtao Gao (高洪涛)
* Ignasi Barrera
* Mick Semb Wever
* Sheng Wu (吴晟)
* Shinn Zhang (张鑫)
* Willem Ning Jiang (姜宁)
* Yongsheng Peng (彭
sibility 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
> > > 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
> 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
> 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
> 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.
>
> 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 wh
> 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
> 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 ne
as the initial members of the Apache SkyWalking
Project:
* Haoyang Liu (刘浩杨)
* Hongtao Gao (高洪涛)
* Ignasi Barrera
* Luke Han (韩卿)
* Mick Semb Wever
* Sheng Wu (吴晟)
> >
> > 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 t
pache 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 t
> 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 l
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
> 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 interfere
> 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 men
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.
> > 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 vote
> 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
fi
> 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 buil
> 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.
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 ros
tao 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
> 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)
rega
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 Copy
> 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 bu
> 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-
> 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 RE
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-bui
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
- P
> 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 un
ers all work at
different companies around the globe. Most operate their own tracing sites, but
some no longer operate sites at all: 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
>
> 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
> 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 unsu
> [ ] +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
44 matches
Mail list logo
