Henri,
I added your comments related to notice and licensing to the same issue
here - https://github.com/apache/incubator-mxnet/issues/8913
and created a separate issue to track the submodules here -
https://github.com/apache/incubator-mxnet/issues/8920.
Thanks,
Meghna Baijal
On Fri, Dec 1, 2017
One question about the below. We've noted that much of the source code for
MXNet is coming from the external DMLC repos. Are there plans to move
those repos into the ASF?
John
On Fri, Dec 1, 2017 at 7:13 PM Hen wrote:
> +1.
>
> Items I note should happen post release are:
>
> * Move the vario
+1.
Items I note should happen post release are:
* Move the various git submodules into third-party/ or similar so it's
simpler to see what is Apache original source when we review a release.
* Deal with the Copyright statements in perl-package (copyright holder has
approved doing this)
* Lots of
+1
On Thu, Nov 30, 2017 at 7:45 PM Chris Olivier
wrote:
> Hello All,
>
>
> This is a call for releasing Apache MXNet (incubating) 1.0.0, release
> candidate 1.
>
>
> Apache MXNet community has voted and approved the release.
>
>
> *Vote thread:*
>
> https://lists.apache.org/thread.html/568bf0c99
Hello Justin,
Thank you for your vote.
I have created a Github issue to track all your comments here -
https://github.com/apache/incubator-mxnet/issues/8913
I will make sure all these issues are fixed soon after the 1.0.0 release.
Thanks,
Meghna Baijal
On Thu, Nov 30, 2017 at 11:59 PM, Sebastian
Friday, December 1, 2017, 9:03:31 PM, Bertrand Delacretaz wrote:
> On Fri, Dec 1, 2017 at 8:51 PM, Mike Jumper wrote:
>> ...Gaining
>> experience conducting non-development user support/discussion via
>> mailing lists was important, and seems to me to be exactly the sort of
>> thing that should b
On Fri, Dec 1, 2017 at 3:36 PM Dave Fisher wrote:
> On Dec 1, 2017, at 12:03 PM, Bertrand Delacretaz <
> bdelacre...@codeconsult.ch> wrote:
>
> On Fri, Dec 1, 2017 at 8:51 PM, Mike Jumper
> wrote:
>
> ...Gaining
> experience conducting non-development user support/discussion via
> mailing lists
> On Dec 1, 2017, at 12:03 PM, Bertrand Delacretaz
> wrote:
>
> On Fri, Dec 1, 2017 at 8:51 PM, Mike Jumper wrote:
>> ...Gaining
>> experience conducting non-development user support/discussion via
>> mailing lists was important, and seems to me to be exactly the sort of
>> thing that should b
On Fri, Dec 1, 2017 at 8:51 PM, Mike Jumper wrote:
> ...Gaining
> experience conducting non-development user support/discussion via
> mailing lists was important, and seems to me to be exactly the sort of
> thing that should be done prior to graduation, not after
What we've seen is that some
On Fri, Dec 1, 2017 at 11:11 AM, sebb wrote:
> On 1 December 2017 at 18:57, Mike Jumper wrote:
>>...
>>
>> Speaking as a member of a recently-graduated podling that joined the
>> Incubator with an established user base, I think we would not have
>> done as well without a user@ list.
>
> So how di
On 1 December 2017 at 18:57, Mike Jumper wrote:
> On Fri, Dec 1, 2017 at 10:06 AM, sebb wrote:
>> On 1 December 2017 at 13:52, John D. Ament wrote:
>> > ...
>> >
>> > At the same time, if we're saying we want to limit the creation of user@
>> > lists, if a podling is already established and usin
On Fri, Dec 1, 2017 at 10:06 AM, sebb wrote:
> On 1 December 2017 at 13:52, John D. Ament wrote:
> > ...
> >
> > At the same time, if we're saying we want to limit the creation of user@
> > lists, if a podling is already established and using forums, discourse,
> > slack, google groups, etc, do w
On 1 December 2017 at 13:52, John D. Ament wrote:
> On Thu, Nov 30, 2017 at 7:54 AM Greg Stein wrote:
>
>> On Thu, Nov 30, 2017 at 3:51 AM, sebb wrote:
>>
>> > On 29 November 2017 at 13:44, John D. Ament
>> wrote:
>> > > On Wed, Nov 29, 2017 at 5:59 AM sebb wrote:
>> > >
>> > >> Top posting
>>
On Thu, Nov 30, 2017 at 7:54 AM Greg Stein wrote:
> On Thu, Nov 30, 2017 at 3:51 AM, sebb wrote:
>
> > On 29 November 2017 at 13:44, John D. Ament
> wrote:
> > > On Wed, Nov 29, 2017 at 5:59 AM sebb wrote:
> > >
> > >> Top posting
> > >>
> > >> The proposal includes a user@ mailing list.
> > >
14 matches
Mail list logo