Thanks Kyo, That makes sense to me, and I hope it is sucessful for you. I have two follow up questions that would help the board to understand that this is a reasonable step for the project to take first are the majority of PMC members supportive of this approach? and secondly to what extent is your PMC made up of people from the same employer? I'm trying to understand whether doing things "offline" for a spike like this is OK or whether we can help you to do it more transparently. This is a difficult line to draw, so please bear with me while I figure it out.
d. On 2020/03/16 14:54:39, "Lee, Kyo (US 398L)" <huikyo....@jpl.nasa.gov.INVALID> wrote: > Hello, > > As I briefly mentioned in the report, we have refactored OCW by applying > xarray and dask. This refactoring requires almost rewriting the entire codes. > For that reason, the lead developer has developed and maintained the > refactoring version in a personal Github branch. > After adding test modules and documentation, we will follow the ASF guideline. > Thank you for your understanding. > > Best regards, > Kyo Lee > > On 3/16/20, 12:08 AM, "Danny Angus" <da...@apache.org> wrote: > > Hi OCW PMC, > > The board were pleased, but I have to say somewhat surprised by the news > that OCW is revitalising itself after a period of notable inactivity. We are > however unclear on the statements about "personal github" and "permission to > release". As you know Apache practice is for development to be collaborative > and public. Perhaps you could help us to understand why your current > direction is a good one, and that it is supported by the majority of the PMC, > and whether it is going to be a one-off, followed by normal collaborative > practices. > > >
