Re: Proposal for a recurrent architecture meeting and long term direction
Thanks for that reminder Isabel. As a recently added mentor, I have been struggling to understand all the interactions on MXNet. Besides the user, dev and private mailing lists, I am trying to watch - Two forums at https://discuss.mxnet.io/ and https://discuss.gluon.ai/ (although I can't read Chinese so really only 1 I guess) - Multiple lists on slack to include https://the-asf.slack.com/messages/C7FN4FCP9, https://the-asf.slack.com/messages/CEE9X9WN7, https://the-asf.slack.com/messages/CBS4K0CPJ - https://cwiki.apache.org/confluence/display/MXNET - Issues https://github.com/apache/incubator-mxnet/issues - Meetups and hangouts as noted on https://cwiki.apache.org/confluence/display/MXNET/Meetups+and+Hangouts I love all the effort and collaboration. So much inertia, so many amazing things in motion. But I am having a hard time tracking it all and I worry about what is not making it back to the public lists. I have often heard something to the effect, "If it doesn't happen on the mailing list, it doesn't happen". To quote http://www.apache.org/dev/pmc.html#mailing-list-naming-policy. "Decisions SHALL NOT be made in other mediums, like IRC or at conferences; rather discussions from such places must be brought back to the appropriate mailing list for all participants to discuss and decide upon." I wonder if others have trouble tracking it all too and if so, what effect that has on the community? Is this something that needs to be addressed before MXNet can graduate the incubator? Interested in others thoughts. Mike On Sat, Jan 19, 2019 at 1:11 PM Isabel Drost-Fromm wrote: > > > Am 19. Januar 2019 16:35:58 MEZ schrieb Pedro Larroy < > pedro.larroy.li...@gmail.com>: > > We talked with Timur about graphcore accelerators, and > >seems other people also missed the meeting > > Meetings like this always should be optional, what's more important: It > must be possible to follow the project from subscribing to its mailing > lists only. > > > >For next meeting I will send an agenda of topics to discuss in advance. > > That seems like a good idea to motivate ppl to participate. > > What's more important though is bringing discussions back here on list so > everyone can participate (at the very minimum, potential decisions have to > be brought back here. It helps with building transparency, community and > ultimately trust to also pro actively bring a brief summary of other > discussions here). > > Isabel > > -- > Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet. >
Re: Proposal for a recurrent architecture meeting and long term direction
Am 19. Januar 2019 16:35:58 MEZ schrieb Pedro Larroy : > We talked with Timur about graphcore accelerators, and >seems other people also missed the meeting Meetings like this always should be optional, what's more important: It must be possible to follow the project from subscribing to its mailing lists only. >For next meeting I will send an agenda of topics to discuss in advance. That seems like a good idea to motivate ppl to participate. What's more important though is bringing discussions back here on list so everyone can participate (at the very minimum, potential decisions have to be brought back here. It helps with building transparency, community and ultimately trust to also pro actively bring a brief summary of other discussions here). Isabel -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Re: Proposal for a recurrent architecture meeting and long term direction
Hi Pedro: Can you give a summary of takeaways, and possible decision proposal that might affect the technical directions? Thanks! Tianqi On Sat, Jan 19, 2019 at 7:36 AM Pedro Larroy wrote: > Hi Isabel. We talked with Timur about graphcore accelerators, and > seems other people also missed the meeting. > > For next meeting I will send an agenda of topics to discuss in advance. > > Thanks. > > Pedro. > > On Thu, Jan 17, 2019 at 2:43 PM Isabel Drost-Fromm > wrote: > > > > On Mon, Jan 14, 2019 at 08:03:42PM +0100, Pedro Larroy wrote: > > > If you wish to join the monthly architecture meeting today, please > > > join the hangout below: > > > > > > https://hangouts.google.com/call/ZXXqJ0ZL5m_dcHOVIeTcAEEE > > > > Likely I've missed the mail - can you point me to the summary of the > above > > meeting? > > > > > > Isabel >
Re: Proposal for a recurrent architecture meeting and long term direction
Hi Isabel. We talked with Timur about graphcore accelerators, and seems other people also missed the meeting. For next meeting I will send an agenda of topics to discuss in advance. Thanks. Pedro. On Thu, Jan 17, 2019 at 2:43 PM Isabel Drost-Fromm wrote: > > On Mon, Jan 14, 2019 at 08:03:42PM +0100, Pedro Larroy wrote: > > If you wish to join the monthly architecture meeting today, please > > join the hangout below: > > > > https://hangouts.google.com/call/ZXXqJ0ZL5m_dcHOVIeTcAEEE > > Likely I've missed the mail - can you point me to the summary of the above > meeting? > > > Isabel
Re: Proposal for a recurrent architecture meeting and long term direction
On Mon, Jan 14, 2019 at 08:03:42PM +0100, Pedro Larroy wrote: > If you wish to join the monthly architecture meeting today, please > join the hangout below: > > https://hangouts.google.com/call/ZXXqJ0ZL5m_dcHOVIeTcAEEE Likely I've missed the mail - can you point me to the summary of the above meeting? Isabel
Re: Proposal for a recurrent architecture meeting and long term direction
I joined it now. But I can't unmute myself. I see Pedro (I believe it's him). My question is: what do we think about Graphcore? https://www.graphcore.ai/technology On Mon, Jan 14, 2019 at 7:03 PM Pedro Larroy wrote: > Hi > > If you wish to join the monthly architecture meeting today, please > join the hangout below: > > https://hangouts.google.com/call/ZXXqJ0ZL5m_dcHOVIeTcAEEE > > Regards. Pedro. > > On Mon, Dec 17, 2018 at 1:18 AM Pedro Larroy > wrote: > > > > Hi > > > > I think you make good points. We can address your concerns by sending > > notes to the mailing list and use the wiki / RFCs appropriately so the > > community can follow and participate asynchronously so asynchronous > > participation is still possible. > > > > I would say let's try and see if they bring value, we can alway stop > > if they don't or do it more often if the time is not enough, I think > > once a month is a conservative choice that doesn't take too much time > > from our already busy lives. > > > > Other open source projects like IPFS do these kind of sessions and > > seems to work for them. > > > > It's also an opportunity to share what we are working on and collaborate > more. > > > > Pedro. > > > > On Sun, Dec 16, 2018 at 7:04 PM Tianqi Chen wrote: > > > > > > I feel that online meeting may not address most of the issues get > raised in > > > a short amount of time(1h) and still suffers the problem of not being > > > publically archivable. > > > > > > Maybe we can not try more asynchronous way? (RFC discussion in issues. > > > and/or discuss @dev). Just my two cents and I am not blocking the > proposal > > > > > > Tianqi > > > > > > > > > On Fri, Dec 14, 2018 at 5:34 AM Pedro Larroy < > pedro.larroy.li...@gmail.com> > > > wrote: > > > > > > > Hi MXNetters > > > > > > > > To address the project growth and increased contributions I'm > > > > proposing a monthly meeting / hangout to have community discussions > > > > about MXNet architecture and mid / longer term technical directions > > > > that require coordination beyond single PRs. > > > > > > > > TOPICS: > > > > > > > > The goal of this series is to address topics including but not > limited to: > > > > - How to best integrate features that have a big impact on the > project > > > > - Discussion about long term technical direction > > > > - Addressing of technical debt / refactoring needed. > > > > - Other architectures / framework support. Ex. ARM, Cuda etc. > > > > - Build system improvements and tooling such as code coverage, > static > > > > analysis etc. > > > > - Performance discussions. > > > > - Live discussion to address exceptional PRs with complex changes > > > > that are better discussed live than in written form. > > > > > > > > FREQUENCY: > > > > > > > > I propose to make this meeting on the second Monday of the month at > > > > 11am PST / 20pm CET > > > > > > > > So the tentative date for the first one would be on January 14th. > > > > > > > > If you think this arbitrary date is not good, please say so. In this > > > > case we can proceed to make a doodle to find a slot that works for > the > > > > interested parties. > > > > > > > > I have opened a group calendar for our meetings, hangouts and other > > > > events related to MXNet. > > > > > > > > > > > > > https://calendar.google.com/calendar/embed?src=6co88bqo3n4bjsbt1qrqmsvj4o%40group.calendar.google.com > > > > > > > > Pedro. > > > > >
Re: Proposal for a recurrent architecture meeting and long term direction
Hi If you wish to join the monthly architecture meeting today, please join the hangout below: https://hangouts.google.com/call/ZXXqJ0ZL5m_dcHOVIeTcAEEE Regards. Pedro. On Mon, Dec 17, 2018 at 1:18 AM Pedro Larroy wrote: > > Hi > > I think you make good points. We can address your concerns by sending > notes to the mailing list and use the wiki / RFCs appropriately so the > community can follow and participate asynchronously so asynchronous > participation is still possible. > > I would say let's try and see if they bring value, we can alway stop > if they don't or do it more often if the time is not enough, I think > once a month is a conservative choice that doesn't take too much time > from our already busy lives. > > Other open source projects like IPFS do these kind of sessions and > seems to work for them. > > It's also an opportunity to share what we are working on and collaborate more. > > Pedro. > > On Sun, Dec 16, 2018 at 7:04 PM Tianqi Chen wrote: > > > > I feel that online meeting may not address most of the issues get raised in > > a short amount of time(1h) and still suffers the problem of not being > > publically archivable. > > > > Maybe we can not try more asynchronous way? (RFC discussion in issues. > > and/or discuss @dev). Just my two cents and I am not blocking the proposal > > > > Tianqi > > > > > > On Fri, Dec 14, 2018 at 5:34 AM Pedro Larroy > > wrote: > > > > > Hi MXNetters > > > > > > To address the project growth and increased contributions I'm > > > proposing a monthly meeting / hangout to have community discussions > > > about MXNet architecture and mid / longer term technical directions > > > that require coordination beyond single PRs. > > > > > > TOPICS: > > > > > > The goal of this series is to address topics including but not limited to: > > > - How to best integrate features that have a big impact on the project > > > - Discussion about long term technical direction > > > - Addressing of technical debt / refactoring needed. > > > - Other architectures / framework support. Ex. ARM, Cuda etc. > > > - Build system improvements and tooling such as code coverage, static > > > analysis etc. > > > - Performance discussions. > > > - Live discussion to address exceptional PRs with complex changes > > > that are better discussed live than in written form. > > > > > > FREQUENCY: > > > > > > I propose to make this meeting on the second Monday of the month at > > > 11am PST / 20pm CET > > > > > > So the tentative date for the first one would be on January 14th. > > > > > > If you think this arbitrary date is not good, please say so. In this > > > case we can proceed to make a doodle to find a slot that works for the > > > interested parties. > > > > > > I have opened a group calendar for our meetings, hangouts and other > > > events related to MXNet. > > > > > > > > > https://calendar.google.com/calendar/embed?src=6co88bqo3n4bjsbt1qrqmsvj4o%40group.calendar.google.com > > > > > > Pedro. > > >
Re: Proposal for a recurrent architecture meeting and long term direction
Hi I think you make good points. We can address your concerns by sending notes to the mailing list and use the wiki / RFCs appropriately so the community can follow and participate asynchronously so asynchronous participation is still possible. I would say let's try and see if they bring value, we can alway stop if they don't or do it more often if the time is not enough, I think once a month is a conservative choice that doesn't take too much time from our already busy lives. Other open source projects like IPFS do these kind of sessions and seems to work for them. It's also an opportunity to share what we are working on and collaborate more. Pedro. On Sun, Dec 16, 2018 at 7:04 PM Tianqi Chen wrote: > > I feel that online meeting may not address most of the issues get raised in > a short amount of time(1h) and still suffers the problem of not being > publically archivable. > > Maybe we can not try more asynchronous way? (RFC discussion in issues. > and/or discuss @dev). Just my two cents and I am not blocking the proposal > > Tianqi > > > On Fri, Dec 14, 2018 at 5:34 AM Pedro Larroy > wrote: > > > Hi MXNetters > > > > To address the project growth and increased contributions I'm > > proposing a monthly meeting / hangout to have community discussions > > about MXNet architecture and mid / longer term technical directions > > that require coordination beyond single PRs. > > > > TOPICS: > > > > The goal of this series is to address topics including but not limited to: > > - How to best integrate features that have a big impact on the project > > - Discussion about long term technical direction > > - Addressing of technical debt / refactoring needed. > > - Other architectures / framework support. Ex. ARM, Cuda etc. > > - Build system improvements and tooling such as code coverage, static > > analysis etc. > > - Performance discussions. > > - Live discussion to address exceptional PRs with complex changes > > that are better discussed live than in written form. > > > > FREQUENCY: > > > > I propose to make this meeting on the second Monday of the month at > > 11am PST / 20pm CET > > > > So the tentative date for the first one would be on January 14th. > > > > If you think this arbitrary date is not good, please say so. In this > > case we can proceed to make a doodle to find a slot that works for the > > interested parties. > > > > I have opened a group calendar for our meetings, hangouts and other > > events related to MXNet. > > > > > > https://calendar.google.com/calendar/embed?src=6co88bqo3n4bjsbt1qrqmsvj4o%40group.calendar.google.com > > > > Pedro. > >
Re: Proposal for a recurrent architecture meeting and long term direction
I feel that online meeting may not address most of the issues get raised in a short amount of time(1h) and still suffers the problem of not being publically archivable. Maybe we can not try more asynchronous way? (RFC discussion in issues. and/or discuss @dev). Just my two cents and I am not blocking the proposal Tianqi On Fri, Dec 14, 2018 at 5:34 AM Pedro Larroy wrote: > Hi MXNetters > > To address the project growth and increased contributions I'm > proposing a monthly meeting / hangout to have community discussions > about MXNet architecture and mid / longer term technical directions > that require coordination beyond single PRs. > > TOPICS: > > The goal of this series is to address topics including but not limited to: > - How to best integrate features that have a big impact on the project > - Discussion about long term technical direction > - Addressing of technical debt / refactoring needed. > - Other architectures / framework support. Ex. ARM, Cuda etc. > - Build system improvements and tooling such as code coverage, static > analysis etc. > - Performance discussions. > - Live discussion to address exceptional PRs with complex changes > that are better discussed live than in written form. > > FREQUENCY: > > I propose to make this meeting on the second Monday of the month at > 11am PST / 20pm CET > > So the tentative date for the first one would be on January 14th. > > If you think this arbitrary date is not good, please say so. In this > case we can proceed to make a doodle to find a slot that works for the > interested parties. > > I have opened a group calendar for our meetings, hangouts and other > events related to MXNet. > > > https://calendar.google.com/calendar/embed?src=6co88bqo3n4bjsbt1qrqmsvj4o%40group.calendar.google.com > > Pedro. >
Re: Proposal for a recurrent architecture meeting and long term direction
Nice!!! Perfect! "I'm trying real hard to be the shepherd." -Jules Winnfield > On Dec 14, 2018, at 3:04 PM, Marco de Abreu wrote: > > That's a great idea, Pedro! > > -Marco > > Am Fr., 14. Dez. 2018, 14:34 hat Pedro Larroy > geschrieben: > >> Hi MXNetters >> >> To address the project growth and increased contributions I'm >> proposing a monthly meeting / hangout to have community discussions >> about MXNet architecture and mid / longer term technical directions >> that require coordination beyond single PRs. >> >> TOPICS: >> >> The goal of this series is to address topics including but not limited to: >> - How to best integrate features that have a big impact on the project >> - Discussion about long term technical direction >> - Addressing of technical debt / refactoring needed. >> - Other architectures / framework support. Ex. ARM, Cuda etc. >> - Build system improvements and tooling such as code coverage, static >> analysis etc. >> - Performance discussions. >> - Live discussion to address exceptional PRs with complex changes >> that are better discussed live than in written form. >> >> FREQUENCY: >> >> I propose to make this meeting on the second Monday of the month at >> 11am PST / 20pm CET >> >> So the tentative date for the first one would be on January 14th. >> >> If you think this arbitrary date is not good, please say so. In this >> case we can proceed to make a doodle to find a slot that works for the >> interested parties. >> >> I have opened a group calendar for our meetings, hangouts and other >> events related to MXNet. >> >> >> https://calendar.google.com/calendar/embed?src=6co88bqo3n4bjsbt1qrqmsvj4o%40group.calendar.google.com >> >> Pedro. >>
Re: Proposal for a recurrent architecture meeting and long term direction
That's a great idea, Pedro! -Marco Am Fr., 14. Dez. 2018, 14:34 hat Pedro Larroy geschrieben: > Hi MXNetters > > To address the project growth and increased contributions I'm > proposing a monthly meeting / hangout to have community discussions > about MXNet architecture and mid / longer term technical directions > that require coordination beyond single PRs. > > TOPICS: > > The goal of this series is to address topics including but not limited to: > - How to best integrate features that have a big impact on the project > - Discussion about long term technical direction > - Addressing of technical debt / refactoring needed. > - Other architectures / framework support. Ex. ARM, Cuda etc. > - Build system improvements and tooling such as code coverage, static > analysis etc. > - Performance discussions. > - Live discussion to address exceptional PRs with complex changes > that are better discussed live than in written form. > > FREQUENCY: > > I propose to make this meeting on the second Monday of the month at > 11am PST / 20pm CET > > So the tentative date for the first one would be on January 14th. > > If you think this arbitrary date is not good, please say so. In this > case we can proceed to make a doodle to find a slot that works for the > interested parties. > > I have opened a group calendar for our meetings, hangouts and other > events related to MXNet. > > > https://calendar.google.com/calendar/embed?src=6co88bqo3n4bjsbt1qrqmsvj4o%40group.calendar.google.com > > Pedro. >
Proposal for a recurrent architecture meeting and long term direction
Hi MXNetters To address the project growth and increased contributions I'm proposing a monthly meeting / hangout to have community discussions about MXNet architecture and mid / longer term technical directions that require coordination beyond single PRs. TOPICS: The goal of this series is to address topics including but not limited to: - How to best integrate features that have a big impact on the project - Discussion about long term technical direction - Addressing of technical debt / refactoring needed. - Other architectures / framework support. Ex. ARM, Cuda etc. - Build system improvements and tooling such as code coverage, static analysis etc. - Performance discussions. - Live discussion to address exceptional PRs with complex changes that are better discussed live than in written form. FREQUENCY: I propose to make this meeting on the second Monday of the month at 11am PST / 20pm CET So the tentative date for the first one would be on January 14th. If you think this arbitrary date is not good, please say so. In this case we can proceed to make a doodle to find a slot that works for the interested parties. I have opened a group calendar for our meetings, hangouts and other events related to MXNet. https://calendar.google.com/calendar/embed?src=6co88bqo3n4bjsbt1qrqmsvj4o%40group.calendar.google.com Pedro.
