Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

Directly on this proposal, I agree. In Zipkin (incubating) we are lucky that mentors are already active. However, we should not take this for granted and certainly it would be harder and more fragile if our mentors were not looking carefully and voting. -A On Mon, Apr 1, 2019, 10:30 AM Craig

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to askingIPMC to vote

Have enough mentor votes in dev vote, and carry them to incubator vote, really could make the IPMC vote more flexible. IPMC member could help on recheck from different view, which sometimes is necessary. Fresh eyes are good to the community and assist the project speed up to graduate, in my

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

I have a related question. In Zipkin (incubating) last release of one of our projects, we had 3 IPMC +1 votes prior to the formal verification vote. Then we basically just waited 72hrs anyway with no additional votes but it didn't matter as we had what we needed (another came later but still) [1]

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

Just like so many things, this is how it used to be. In fact, back in the day the only time the IPMC was asked to vote was when there were not enough mentor votes. If you look at all the podlinga I've mentored I have only ever asked for an IPMC vote on two occasions (that I recall). One

[RESULT][VOTE] Release Apache NetBeans 11.0 (incubating) [vote candidate 4]

Dear all, By Justin's leave, I'm ignoring my previous cancel thread on this vote and announce the results after a very eventful voting period. I'd wished for another code drop, to address the arisen issues, though perfection is the greatest enemy of good enough, and I'm still traveling,

Re: [CANCELLED][VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

Thank you Justin! Since I'm still, traveling with little or none internet access, I'm going to ignore this thread and publish the result of the vote thread. On 3/30/19 2:17 PM, Justin Mclean wrote: Hi, I think it was a bit hasty to cancel this vote, after as I said, a -1 vote is not a veto

[DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

This is a proposal to recommend that all Mentors SHOULD vote on podling releases prior to sending the release for a vote to the IPMC. This is not a MUST, since there are many good reasons why a mentor might be unable to perform the checks needed to vote. We are volunteers after all. But if

Re: List of Projects that went straight to Top Level Projects

On Sun, Mar 31, 2019 at 9:53 PM Dave Fisher wrote: > > Hi Sam, > > That’s a cool table. Does your code look at the resolution tag? Doe we > possibly have some errors in podlings.xml? No, I don't currently look at the resolution tag, but that should be easy enough to add. That should take care

Re: List of Projects that went straight to Top Level Projects

Hi Sam, That’s a cool table. Does your code look at the resolution tag? Doe we possibly have some errors in podlings.xml? (1) BVal incubated as BeanValidation and here is a snippet from podlings.xml: The Bean Validation project will create an implementation of Bean Validation as

Re: List of Projects that went straight to Top Level Projects

I've gone ahead and added information from podlings.xml to this data. We have a number of entries which are in podlings.xml but don't contain incubator in their establishment resolution (Tika, Tapestry, Pig, Myfaces...) - Sam Ruby On Sun, Mar 31, 2019 at 8:08 PM Sam Ruby wrote: > > In March, I

Re: List of Projects that went straight to Top Level Projects

In March, I wrote a script to find establishment resolutions, and to scan those resolutions for the word 'incubator': https://whimsy.apache.org/incubator/graduated#summary As always, the data is a bit dirty. There are a number of projects that were created before we had establish resolutions,

Re: List of Projects that went straight to Top Level Projects

Hi Dave Thanks very much for this. I will take a closer look at it and get back to you if I have any questions. Thanks Sharan On 31. 03. 19 20:44, Dave Fisher wrote: Hi Sharan, Despite all of the discussions about why one wants to do this you have your reasons. Greg gives one way to

[jira] [Closed] (INCUBATOR-235) File.mkdir() may fail and cause crash.

[ https://issues.apache.org/jira/browse/INCUBATOR-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bd2019us closed INCUBATOR-235. -- Resolution: Not A Bug > File.mkdir() may fail and cause crash. >

[jira] [Created] (INCUBATOR-235) File.mkdir() may fail and cause crash.

bd2019us created INCUBATOR-235: -- Summary: File.mkdir() may fail and cause crash. Key: INCUBATOR-235 URL: https://issues.apache.org/jira/browse/INCUBATOR-235 Project: Incubator Issue Type: Bug

Re: List of Projects that went straight to Top Level Projects

Hi Sharan, Despite all of the discussions about why one wants to do this you have your reasons. Greg gives one way to research / tease out this info from Board resolutions. I’ll point out a page which may have the data you need. (Graduations from the Incubator to another TLP do not require a

Re: List of Projects that went straight to Top Level Projects

This was an outcome of the last time the IPMC processes were challenged. Basically the board agreed that in cases where the initial PMC consisted of plenty of existing experienced ASF people there was no need for incubation. There was never an intention of going straight to TLP if there was not

Re: Voting on releases with serious unaddressed issues

"What is important is tat it has been addressed and the podling is fixing the issue" - big +1000 Thank you to everyone for doing the right thing here. Including Justin for agreeing to change his vote - I think that was the right thing to do even though, on this occasion, he could have cited my

Re: Setting up Tuweni

Hi - > On Mar 30, 2019, at 11:41 PM, Kenneth Knowles wrote: > > Hi Dave, > > What should a podling put here? I notice a few things: > > - you changed the start date from Feb 25 (date of the vote passing) to > March 25 (date of the commit) I put that in because it when we are actually

Re: tuweni

Hi - > On Mar 31, 2019, at 1:46 AM, Oleg Tikhonov wrote: > > Thank you all !!! > Very impressed :-) > > My first intention was - to have a look at source code, read a readme etc. > Look forward for more progress from where I could help. > > Thanks again. > Best regards, > Oleg > > BTW: >

Re: List of Projects that went straight to Top Level Projects

On Sun, Mar 31, 2019 at 7:43 AM Justin Mclean wrote: > Hi, > > > Actually, it is pretty easy to tell. The bottom of the resolution will > say > > something like "". Compare Royale[1] (with a discharge of > responsibilities) > > compared to Serf[2]. > > Perhaps? > > Royale has: > "RESOLVED, that

Re: List of Projects that went straight to Top Level Projects

Hi, > Actually, it is pretty easy to tell. The bottom of the resolution will say > something like "". Compare Royale[1] (with a discharge of responsibilities) > compared to Serf[2]. Perhaps? Royale has: "RESOLVED, that all responsibilities pertaining to Apache FlexJS encumbered upon the Apache

Re: List of Projects that went straight to Top Level Projects

On Sun, Mar 31, 2019 at 7:06 AM Greg Stein wrote: > On Sun, Mar 31, 2019 at 6:57 AM Justin Mclean wrote: > >... > >> there. The board resolutions don’t make it clear if it’s straight TLP or >> not from what I can see > > > Actually, it is pretty easy to tell. The bottom of the resolution will

Re: List of Projects that went straight to Top Level Projects

On Sun, Mar 31, 2019 at 6:57 AM Justin Mclean wrote: >... > there. The board resolutions don’t make it clear if it’s straight TLP or > not from what I can see Actually, it is pretty easy to tell. The bottom of the resolution will say something like "". Compare Royale[1] (with a discharge of

Re: List of Projects that went straight to Top Level Projects

Ah, OK. I’d be interested in the outcome of that research too. I don’t think it’s common to skip incubation and I’m sure a lot would not be learned by skipping it. Gj On Sun, 31 Mar 2019 at 13:44, wrote: > Hi Geertjan > > Thanks for the email and I'm not thinking of doing it at all. > > I'm

Re: List of Projects that went straight to Top Level Projects

hi, > Does anyone know if there is a list of projects that bypassed incubation? For > example - I know a couple of projects Royale and Kibble that went straight to > TLP. Is there a list anywhere for all projects like this? Not that I know. It’s rare, and there are some that are more

Re: List of Projects that went straight to Top Level Projects

Hi Sharan, On the top of my mind: Apache STeVe, Apache Whimsy/Whimsical Best regards, Pierre Smits *Apache Trafodion , Vice President* *Apache Directory , PMC Member* Apache Incubator , committer *Apache

Re: List of Projects that went straight to Top Level Projects

On Sun, Mar 31, 2019 at 6:28 AM Sharan Foga wrote: > Hi All > > Does anyone know if there is a list of projects that bypassed incubation? > For example - I know a couple of projects Royale and Kibble that went > straight to TLP. Is there a list anywhere for all projects like this? Royale was

Re: List of Projects that went straight to Top Level Projects

Hi Geertjan Thanks for the email and I'm not thinking of doing it at all. I'm planning to do some research for on the embedding of ASF culture and incubator is one of the main way this happens. Sometimes as in the cases of the projects I mentioned, the process is bypassed so one of the

Re: List of Projects that went straight to Top Level Projects

I would highly recommend that you don’t do this. What would be the reason to go straight to TLP? There’s a lot to learn and many mistakes to make, and speaking from experience, it is best to learn and make mistakes in the incubator, which is precisely its purpose. Gj On Sun, 31 Mar 2019 at

List of Projects that went straight to Top Level Projects

Hi All Does anyone know if there is a list of projects that bypassed incubation? For example - I know a couple of projects Royale and Kibble that went straight to TLP. Is there a list anywhere for all projects like this? Thanks Sharan

Re: Voting on releases with serious unaddressed issues

Hi, > For the record, no. No. It was never simply called theft. These files were > part of the donation received from Oracle. We did not add these files in > any way in Apache and simply received them as part of the donation. We have > now removed them, so that this kind of stupid accusation can

Re: Voting on releases with serious unaddressed issues

On Sun, 31 Mar 2019 at 05:51, Davor Bonaci wrote: > The issue at hand is simply called theft, For the record, no. No. It was never simply called theft. These files were part of the donation received from Oracle. We did not add these files in any way in Apache and simply received them as part

Misleading clutch info (was: tuweni)

FYI -- Forwarded message - From: Oleg Tikhonov Date: Sun, 31 Mar 2019 at 09:46 Subject: Re: tuweni To: Felix Schumacher Cc: BTW: https://incubator.apache.org/clutch/tuweni.html I guess the creation date should be updated to "now" instead of " Updated: 01/01/1970 "

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

On Sun, Mar 31, 2019 at 10:08 AM Justin Mclean wrote: > Hi, > > > The LICENSE file has a table that maps a file to its license "key" and > the > > license is then stored in the (top-level) "licenses" directory (in the > > header of the table, there is a note about that: "text is in file in > >

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

Hi, > The LICENSE file has a table that maps a file to its license "key" and the > license is then stored in the (top-level) "licenses" directory (in the > header of the table, there is a note about that: "text is in file in > licenses directory"). We used to put all the licenses into the LICENSE

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

Hi, > It has never been a practice or assumption in Apache NetBeans that all our > mentors vote on all our releases. We do explicitly ask our mentors to vote > in the podling dev list, normally at least one (in this case Ate) does, > while at least two of the other three tend to vote in the IPMC

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

On Sun, Mar 31, 2019 at 9:36 AM Justin Mclean wrote: > > > > > For the record, we have 4 mentors, two of which have voted +1 on this > > release so far. > > One voted on the IPMC list (right?). I think Graig was asking why they > didn’t vote on the podling dev list. > > It has never been a

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

Hi, > Would you please have a list? I tried this: > java -jar ~/Downloads/apache-rat-0.12.jar . >rat > cat rat | grep '== File:' | grep -e '\.java$' -e '\.jsp$' -e '\.php$' -e > '\.js$' | grep -v 'test/unit/data' | grep -v 'test/qa-functional/data’ You might want to add .sh and .xml files to

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

Hi, >> I will again raise the question of why the mentors failed to vote on the >> release. I'd like to make it a stronger suggestion that Mentors SHOULD vote >> on releases prior to sending the release vote to the IPMC. >> > > For the record, we have 4 mentors, two of which have voted +1 on

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

Hi Justin, Some more questions on the LICENSE(/NOTICE). On Sat, Mar 30, 2019 at 2:43 AM Justin Mclean wrote: > I think there some more work to do on licensing here, and these will be > needed to be fixed in a later release: > - You are not compiling with the terms of the licenses of the

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

Hi Justin, On Sat, Mar 30, 2019 at 7:58 AM Justin Mclean wrote: > HI, > > > I assume we are taking about files like: > > > https://github.com/apache/incubator-netbeans/blob/master/java/java.hints/test/unit/data/org/netbeans/test/java/hints/AddCast1.java > > Those are some of the files yes but

Re: [CANCELLED][VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

Yes, we have -- after a bit of to and fro -- now 4 IPMC votes: Craig, Justin, Ate, and Mark. And we have the right amount of time, i.e., 72 hours. Let's mark the items listed by Justin as blockers for the next release (the cat picture deletion is a PR already). I'd say there's nothing stopping

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

On Sat, Mar 30, 2019 at 10:05 PM Craig Russell wrote: > > > I will again raise the question of why the mentors failed to vote on the > release. I'd like to make it a stronger suggestion that Mentors SHOULD vote > on releases prior to sending the release vote to the IPMC. > For the record, we

Re: Voting on releases with serious unaddressed issues

On Sun, Mar 31, 2019 at 7:49 AM Adrian Cole wrote: > > I'm excited about netbeans becoming an apache TLP, and also interested > in learning if there are things in that process (beyond the photo > snatching) other podlings like the one I am should be careful of. > Here it is:

Re: Setting up Tuweni

Hi Dave, What should a podling put here? I notice a few things: - you changed the start date from Feb 25 (date of the vote passing) to March 25 (date of the commit) - reporting group is left as 2 - the first monthly report is May, two months after the new incubation start month I don't know

Re: Voting on releases with serious unaddressed issues

The images have been deleted. The sample containing them has been deleted. Of the millions of lines of code in Apache NetBeans, the deleted sample is so completely unimportant that it is impossible to express its unimportance. There isn’t even a metaphor I can think of to illustrate this. Thanks,