On Fri, May 27, 2016 at 9:23 PM, Marvin Humphrey wrote:
> On Fri, May 27, 2016 at 6:10 PM, Sterling Hughes wrote:
>> I just want to clarify here on the thread —- while I think in general there
>> may be problems with too many podlings/inactive mentors, that is not an
>> issue we often face.
>
> J
I will admit to being somewhat of a quiet mentor for Mynewt, particularly with
respect to vetting releases. I have been monitoring the community and signing
off on reports.
I've often seen more experienced mentors vote on releases, and held back on
voting based on trust in them. I'll try to do
On Fri, May 27, 2016 at 6:10 PM, Sterling Hughes wrote:
> I just want to clarify here on the thread —- while I think in general there
> may be problems with too many podlings/inactive mentors, that is not an
> issue we often face.
Justin Mclean has voted on so many releases over the last several
Hi,
> as always, snapshots in time is not as useful as trending data over time. I
> guess it is time to take a look at whimsy.. :-)
http://web.archive.org/web/*/http://incubator.apache.org/clutch.html
Justin
-
To unsubscribe, e
On 05/28/2016 05:31 AM, Niclas Hedhman wrote:
> And where is the sources for that?
https://svn.apache.org/repos/asf/comdev/projects.apache.org/
With regards,
Daniel.
>
> On Sat, May 28, 2016 at 11:27 AM, Daniel Gruno wrote:
>
>> On 05/28/2016 05:25 AM, Niclas Hedhman wrote:
>>> Thanks Justin,
And where is the sources for that?
On Sat, May 28, 2016 at 11:27 AM, Daniel Gruno wrote:
> On 05/28/2016 05:25 AM, Niclas Hedhman wrote:
> > Thanks Justin,
> > as always, snapshots in time is not as useful as trending data over
> time. I
> > guess it is time to take a look at whimsy.. :-)
>
> Or
On 05/28/2016 05:25 AM, Niclas Hedhman wrote:
> Thanks Justin,
> as always, snapshots in time is not as useful as trending data over time. I
> guess it is time to take a look at whimsy.. :-)
Or projects.apache.org :) Since there's already an incubator chart there
- should be easy to add another on
Thanks Justin,
as always, snapshots in time is not as useful as trending data over time. I
guess it is time to take a look at whimsy.. :-)
Cheers
On Sat, May 28, 2016 at 9:38 AM, Justin Mclean
wrote:
> Hi,
>
> > An additional graph that would be super-interesting to get is "Months in
> > Incuba
Hello all,
Voting for the release of 0.9.0-incubating-rc1 has been cancelled due to
some incorrectly packaged source [*].
Sorry for the confusion, and thank you to everyone who voted. A second
release candidate will be put up for a vote on the dev list shortly.
Thanks,
Chris
[*] For the newt r
+1 for clearing the name early based on the many comments already listed.
-s
p.s. I'm a committer on Airflow.
On Fri, May 27, 2016 at 6:43 PM, John D. Ament
wrote:
> TBH, I'm a bit surprised with the answer provided by Shane in the JIRA. My
> understanding has been that branding is an importan
TBH, I'm a bit surprised with the answer provided by Shane in the JIRA. My
understanding has been that branding is an important part of incubation, so
hearing that it should come near the conclusion is a bit perplexing.
Hopefully he can provide some clarification of it.
John
On Fri, May 27, 201
Hi,
> An additional graph that would be super-interesting to get is "Months in
> Incubation" for the current podlings, plotted over time.
Some of the data can be found here [1] (column B)
Thanks,
Justin
1. http://incubator.apache.org/clutch.html
Hey John,
I think the VOTE should be recalled based upon looking at newt. I’ll
admit — all my testing was on the git tags for the release, and not
the tarballs themselves. As a FYI, what happened is that only the newt
directory got released in newt tarball instead of the TLD:
https://github.
+ 1 (non-binding)
Regards
Liang
--
View this message in context:
http://apache-incubator-general.996316.n3.nabble.com/VOTE-Accept-PredictionIO-into-the-Apache-Incubator-tp49739p49872.html
Sent from the Apache Incubator - General mailing list archive at Nabble.com.
---
I'm still interested in figuring out how to build this thing, however I
feel that I need to vote -1 on the release on the following grounds:
- You're trying to release "Apache Mynewt" but not a single one of these
packages says "Mynewt" on them. Even the generated binary says "newt" and
not Mynew
I just want to clarify here on the thread —- while I think in general
there may be problems with too many podlings/inactive mentors, that is
not an issue we often face.
It is simply that this release came at a time when some of our mentors
were busy, and we want to get a release out the door—
On Fri, May 27, 2016 at 6:05 PM, John D. Ament wrote:
> I can agree that there's an issue with the overall number of podlings
> around. However, I don't agree with telling a podling that the IPMC isn't
> going to look at your vote and that your mentors should do that.
Well, a quick recap of the
I can agree that there's an issue with the overall number of podlings
around. However, I don't agree with telling a podling that the IPMC isn't
going to look at your vote and that your mentors should do that.
The funny thing though, MyNewt has more than the recommended 3 mentors, yet
this is stil
Hi Christopher,
I'm happy to take a look at the release. Its probably a bit hard since it
seems like its not buildable.
Your instructions seem to be "newt test all" When I run that I get
Johns-MBP-2:apache-newt-0.9.0-incubating johnament$ newt test go
-bash: newt: command not found
I'm used
On Fri, May 27, 2016 at 5:52 PM, Niclas Hedhman wrote:
> I respectfully disagree... One of the main reasons we went from 1 to 3
> recommended mentors, way back in the days, was that those 3 would be the
> primary people to ping for binding votes, without limiting the rest of the
> IPMC to do so.
I'll take care of the podling setup from the incubator side.
John
On Fri, May 27, 2016 at 12:05 PM Daniel Gruno wrote:
> With a wonderful 26 +1's (21 binding, 5 non-binding),
> this vote passes :)
>
> I shall start preparing the podling setup ASAP :)
>
> With regards and neighs,
> Daniel.
>
> O
I respectfully disagree... One of the main reasons we went from 1 to 3
recommended mentors, way back in the days, was that those 3 would be the
primary people to ping for binding votes, without limiting the rest of the
IPMC to do so.
If that is no longer the consensus, then we need to look at the
Hi,
> I think you need to ping your mentors, and if they are not able, then I
> think you need to raise this as an issue with the Incubator PMC, either in
> separate thread or put it in the report for next month.
AFAIK it's not the responsibility of the mentors to vote, it's the
responsibility o
I think you need to ping your mentors, and if they are not able, then I
think you need to raise this as an issue with the Incubator PMC, either in
separate thread or put it in the report for next month.
I am not on the PMC, and can't help at this point.
Niclas
On Sat, May 28, 2016 at 7:18 AM, Ste
+1 for doing it early. Waiting to the bitter end can delay graduation, and a
podling rename can be disruptive.
IMO part of incubation is about establishing and learning how to protect your
brand. Establishing a brand is not an exercise you want to have to do twice.
-Taylor
> On May 27, 2016, a
Hi,
It’s been 5 days since the start of the vote thread — we’re
waiting on 2 more votes +1 — already passed podling PMC.
Can folks jump in?
Thanks,
Sterling
On 25 May 2016, at 7:58, Sterling Hughes wrote:
Hi All,
Trying to get this out, we have one +1 binding vote on general@ (from
me),
I’ve always done the podling name search right away. I’m not
sure where that comment came from from Shane - my experience
has been the opposite.
++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Sec
I think the point is that name search is not a blocker for doing incubator
releases - it can be time consuming and there are many other "bureaucratic"
steps to get through in the beginning like IP clearance and license
checking.
For brand new projects, name search can therefore be delayed - their
Podling namesearch is essential step that needs to be completed before the
podling graduates. There is no specific guidance, as far as i know, on what
stage of podling you should do it.
That said, it would be better to do this early enough and get approval on
the name. If there is any reason to ch
We were getting ready to start the PNS for Airflow when I came across
this comment from Shane in regards to Kudu:
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-93
"This looks like a pretty good set of search data, but we usually
don't work on resolving PODLINGNAMESEARCHES until a podling
With a wonderful 26 +1's (21 binding, 5 non-binding),
this vote passes :)
I shall start preparing the podling setup ASAP :)
With regards and neighs,
Daniel.
On 05/27/2016 04:06 PM, Amol Kekre wrote:
> +1 (non-binding)
>
> Thks
> Amol
>
> On Fri, May 27, 2016 at 6:35 AM, Shane Curcuru wrote:
>
+1 (non-binding)
Thks
Amol
On Fri, May 27, 2016 at 5:53 AM, Jim Jagielski wrote:
> Thx for the feedback...
>
> I change my vote to +1 (binding)
> > On May 27, 2016, at 1:46 AM, Jean-Baptiste Onofré
> wrote:
> >
> > Hi Jim,
> >
> > good point. Let me try to explain this "gap" regarding my discu
+1 (non-binding)
Thks
Amol
On Fri, May 27, 2016 at 6:35 AM, Shane Curcuru wrote:
> +1 (binding)
>
> Daniel Gruno wrote on 5/24/16 1:56 AM:
> > Since it seems the discussion has died down, I am now calling a vote on
> > accepting Pony Mail into the Incubator. Sorry in advance for potato.
> >
> >
+1 (binding)
Daniel Gruno wrote on 5/24/16 1:56 AM:
> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.
>
> ### PROPOSAL BELOW #
Thx for the feedback...
I change my vote to +1 (binding)
> On May 27, 2016, at 1:46 AM, Jean-Baptiste Onofré wrote:
>
> Hi Jim,
>
> good point. Let me try to explain this "gap" regarding my discussion with the
> team:
>
> 1. Some people have been involved mostly in architecture and design mor
Great answers to the question of risk.
On Tue, May 24, 2016 at 8:19 PM, Poore, Joshua C. wrote:
> Hi Ted!
>
>
>
> DARPA XDATA is ending next March. We currently have support on another
> DARPA contract that is good through next year, excluding potential options.
> We also have some commercial
36 matches
Mail list logo
