Re: Sprint 5.0 (Asia, Spring 2019)
I've started https://www.mercurial-scm.org/wiki/5.0sprint, please fill it in with your interest/availability, or if there's other places that can host! On Tue, Oct 16, 2018 at 9:59 AM Gregory Szorc wrote: > On Sun, Oct 14, 2018 at 12:30 PM Kyle Lippincott > wrote: > >> Per the recent discussion at the 4.8 Sprint, let's discuss the next >> sprint now. The next one, for what is currently assumed to be the 5.0 >> release in Spring 2019, is currently scheduled to happen in Asia and I'm >> proposing Japan specifically. >> >> The past two sprints have been planned by Googlers and hosted by Google. >> Ideally a separate entity offers hosting space and handle logistics for >> this one. If no other entity steps up, I will attempt to organize this >> through Google again at Google's Tokyo office, but it is unclear if this is >> going to be acceptable. For Google's Tokyo office in particular, >> scheduling of a conference room is difficult, so getting agreement on the >> host, location, and timing earlier is *extremely* beneficial; let's be >> proactive about this. :) >> >> Please let me know if there are any questions or concerns. >> > > From a visa and transportation standpoint, Japan is likely our best option > in Asia. I think Hong Kong and Taiwan would also be up there. But I believe > some have more difficulty with visas for those locations compared to Japan. > > I would volunteer Mozilla to host. But I'm pretty sure we don't have a > suitable space in Japan. We /may/ have a suitable space in Taiwan. I'd have > to look into it... > ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
Re: Sprint 5.0 (Asia, Spring 2019)
On Sun, Oct 14, 2018 at 12:30 PM Kyle Lippincott wrote: > Per the recent discussion at the 4.8 Sprint, let's discuss the next sprint > now. The next one, for what is currently assumed to be the 5.0 release in > Spring 2019, is currently scheduled to happen in Asia and I'm proposing > Japan specifically. > > The past two sprints have been planned by Googlers and hosted by Google. > Ideally a separate entity offers hosting space and handle logistics for > this one. If no other entity steps up, I will attempt to organize this > through Google again at Google's Tokyo office, but it is unclear if this is > going to be acceptable. For Google's Tokyo office in particular, > scheduling of a conference room is difficult, so getting agreement on the > host, location, and timing earlier is *extremely* beneficial; let's be > proactive about this. :) > > Please let me know if there are any questions or concerns. > >From a visa and transportation standpoint, Japan is likely our best option in Asia. I think Hong Kong and Taiwan would also be up there. But I believe some have more difficulty with visas for those locations compared to Japan. I would volunteer Mozilla to host. But I'm pretty sure we don't have a suitable space in Japan. We /may/ have a suitable space in Taiwan. I'd have to look into it... ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
Sprint 5.0 (Asia, Spring 2019)
Per the recent discussion at the 4.8 Sprint, let's discuss the next sprint now. The next one, for what is currently assumed to be the 5.0 release in Spring 2019, is currently scheduled to happen in Asia and I'm proposing Japan specifically. The past two sprints have been planned by Googlers and hosted by Google. Ideally a separate entity offers hosting space and handle logistics for this one. If no other entity steps up, I will attempt to organize this through Google again at Google's Tokyo office, but it is unclear if this is going to be acceptable. For Google's Tokyo office in particular, scheduling of a conference room is difficult, so getting agreement on the host, location, and timing earlier is *extremely* beneficial; let's be proactive about this. :) Please let me know if there are any questions or concerns. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
