This is great news and I am looking forward to it =)
According to proposal, the community want to stick with Github issues for
tracking issues and bugs?
I suppose this needs a nod by Greg Stein as rep from Apache Infra to
confirm that this is ok for incubation and how would it impact during
gradua
> I would favor a system of marker(s) indicating the code maturity (incl legal)
There is no standard afaik to indicate legal or community 'maturity'.
It would be something for a (RDF) vocabulary for artifacts to be
adopted industry wide.
Right now none of the Maven coordinates are a good fit fo
Brilliant - thank you Suneel :)
I see you're on the Incubator PMC and have added you to the wiki page.
On Thu, Jan 5, 2017 at 9:25 PM, Suneel Marthi wrote:
> I would like to sign up as mentor for MxNet.
>
> On Fri, Jan 6, 2017 at 12:12 AM, Henri Yandell wrote:
>
> > Hello Incubator,
> >
> > I'
I would like to sign up as mentor for MxNet.
On Fri, Jan 6, 2017 at 12:12 AM, Henri Yandell wrote:
> Hello Incubator,
>
> I'd like to propose a new incubator Apache MXNet podling.
>
> The existing MXNet project (http://mxnet.io - 1.5 years old, 15
> committers,
> 200 contributors) is very intere
Hello Incubator,
I'd like to propose a new incubator Apache MXNet podling.
The existing MXNet project (http://mxnet.io - 1.5 years old, 15 committers,
200 contributors) is very interested in joining Apache. MXNet is an
open-source deep learning framework that allows you to define, train, and
depl
Hi,
> is this referring to the tar ball having the name "incubator-trafficcontrol"
> and just changing that to "incubating-..." would suffice?
Yep that’s what’s required. You might find this check list [1] useful.
Thanks,
Justin
1. http://incubator.apache.org/guides/releasemanagement.html#chec
+1 from me too.
For Groovy, we had a discussion internally and with our mentors. The
src archive and website disclaimer seemed to be the things that were
cared about from a legal point of view and so that is what we renamed.
For us, "convenience binaries" were something that should be
convenient
Coming late to the party...
This has been discussed, and contentious, since "forever". A long time ago,
there was a notion that a podling release was not an ASF release (which was
the main reason for the "incubating" marker in all release and support
artifacts. But that pendulum has swung in the o
On Thu, Jan 5, 2017 at 9:41 AM, jean-frederic clere wrote:
> On 01/05/2017 01:51 AM, Niclas Hedhman wrote:
>> Hi,
>> Isn't the https://wiki.apache.org/incubator/January2017 supposed to be
>> editable by Mentors/IPMC members?
>
> So I probably have a problem... JeanFredericClere my user can't edit
On Thu, Jan 5, 2017 at 1:32 AM, Greg Stein wrote:
> Taking off my Infrastructure hat from within that issue, and speaking to
> this from a Foundation policy standpoint ... I think this is probably okay,
> if the docker image is named (say) u/apache/incubator-singa. We allow
> incubator projects in
On 01/05/2017 07:03 PM, Jacopo Cappellato wrote:
> On Thu, Jan 5, 2017 at 6:41 PM, jean-frederic clere
> wrote:
>
>> On 01/05/2017 01:51 AM, Niclas Hedhman wrote:
>>> Hi,
>>> Isn't the https://wiki.apache.org/incubator/January2017 supposed to be
>>> editable by Mentors/IPMC members?
>>
>> So I pr
On Thu, Jan 5, 2017 at 6:41 PM, jean-frederic clere
wrote:
> On 01/05/2017 01:51 AM, Niclas Hedhman wrote:
> > Hi,
> > Isn't the https://wiki.apache.org/incubator/January2017 supposed to be
> > editable by Mentors/IPMC members?
>
> So I probably have a problem... JeanFredericClere my user can't e
On 01/05/2017 01:51 AM, Niclas Hedhman wrote:
> Hi,
> Isn't the https://wiki.apache.org/incubator/January2017 supposed to be
> editable by Mentors/IPMC members?
So I probably have a problem... JeanFredericClere my user can't edit it
or is it too late?
Cheers
Jean-Frederic
>
> Cheers
>
-
[
https://issues.apache.org/jira/browse/INCUBATOR-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freddy Barboza closed INCUBATOR-144.
ticket created as a Test for Incubator projects
> Incubator Task
> --
>
>
[
https://issues.apache.org/jira/browse/INCUBATOR-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freddy Barboza resolved INCUBATOR-144.
--
Resolution: Resolved
this ticket was created as a test.
> Incubator Task
> -
[
https://issues.apache.org/jira/browse/INCUBATOR-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freddy Barboza reassigned INCUBATOR-144:
Assignee: Freddy Barboza
> Incubator Task
> --
>
> K
+1 Great to see the progress from the Ranger community.
On Wed, Jan 4, 2017 at 4:54 PM, Suneel Marthi wrote:
> +1 binding
>
> On Wed, Jan 4, 2017 at 5:48 PM, Ramesh Mani wrote:
>
> > Dear Incubator members,
> >
> > Apache Ranger Project community has successfully released 0.6.2 version
> > and
I'll point out that there was a discussion around docker and podlings back
over the summer, [1].
It appears that Greg is correct, it has not been presented to infra yet,
but the IPMC has moved forward on a proposal which seemed to be to allow
guacamole to publish as "apache/guacamole". I see no r
Hi
Deploying containers to Docker hub IMHO is the same as deploying Java artefacts
to Maven or Node.JS modules to NPM or whatever. It is a release of a
convenience binary in addition to the official source release.
As such:
+1 to supporting Docker, just like Maven Repositories or NPM repositor
Taking off my Infrastructure hat from within that issue, and speaking to
this from a Foundation policy standpoint ... I think this is probably okay,
if the docker image is named (say) u/apache/incubator-singa. We allow
incubator projects in our github namespace as
github.com/apache/incubator-singa.
20 matches
Mail list logo
