There are two questions here: 1. Is the Wave podling at the ASF going to terminate? 2. Is the Wave codebase going to persist somewhere else, in which case, where, and who will be a part of that effort?
The first requires a vote of the PPMC, followed by a vote of the Incubator PMC. The second just requires a consensus, here. Upayavira On Wed, 29 Nov 2017, at 05:06 PM, Upayavira wrote: > I would say that the vote should happen as soon as it can. The ASF won't > put us under undue pressure to move things elsewhere (so long as they > actually happen!) > > Upayavira > > On Wed, 29 Nov 2017, at 04:01 PM, Yuri Z wrote: > > Ok, let's wait some time. But, repo, jira and documentation will stay - > > as > > read only. > > > > On Wed, Nov 29, 2017 at 5:39 PM Zachary Yaro <zmy...@gmail.com> wrote: > > > > > If possible, I think it would be better to hold off on the vote until we > > > know what the new homes for the mailing list, code repo, and documentation > > > will be, and ensure we can update waveprotocol.org with those details. > > > > > > Zachary Yaro > > > > > > On 29 November 2017 at 04:41, Yuri Z <vega...@gmail.com> wrote: > > > > > > > So, if we have a consensus, I will send the retirement vote email in a > > > few > > > > days. > > > > > > > > On Wed, Nov 29, 2017 at 11:35 AM Yuri Z <vega...@gmail.com> wrote: > > > > > > > > > Yeah, I think I still have admin permissions for waveprotocol.org > > > > > I can add you as admin in can you want to start working on it. > > > > > > > > > > > > > > > On Mon, Nov 27, 2017 at 10:53 PM Zachary Yaro <zmy...@gmail.com> > > > wrote: > > > > > > > > > >> Just so I understand, what would be the criteria for the project > > > > rejoining > > > > >> the Apache Incubator in the future? > > > > >> > > > > >> For instance, we have had several people (myself included) comment > > > that > > > > >> they would become more frequent contributors to the project once the > > > > >> server > > > > >> and client were sufficiently decoupled that a JavaScript client could > > > be > > > > >> worked on separately from the Java GWT client. Should that happen, > > > and > > > > >> regular work on the project continue, could the project easily > > > > >> rejoin, > > > > or > > > > >> would there be a higher barrier to reentry? > > > > >> > > > > >> > > > > >> And on another note, if the project is retired, what happens to the > > > > >> documentation and mailing list archives from Apache, and would > > > anything > > > > be > > > > >> done to help migrate that elsewhere? > > > > >> > > > > >> (On a related note, do we still have access to waveprotocol.org and > > > the > > > > >> related mailing list? That would seem to be the logical place to > > > > migrate > > > > >> to.) > > > > >> > > > > >> Zachary Yaro > > > > >> > > > > >> On 27 November 2017 at 14:43, Dustin Pfannenstiel < > > > > >> dustin.pfannenst...@nth-estate.com> wrote: > > > > >> > > > > >> > I've set up a repo and organization for the code base on github. > > > > >> > https://github.com/TimaeusWave/WaveServer > > > > >> > > > > > >> > Thanks for the years of support and, well, just everything. > > > > >> > > > > > >> > DMP > > > > >> > > > > > >> > > On Nov 27, 2017, at 11:33 AM, Upayavira <u...@odoko.co.uk> wrote: > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> > > On Mon, 27 Nov 2017, at 04:46 PM, John D. Ament wrote: > > > > >> > >> The in depth "incubator required stuff" is at > > > > >> > >> https://incubator.apache.org/guides/retirement.html for review > > > > >> > >> > > > > >> > >> Basically, > > > > >> > >> > > > > >> > >> - We have this conversation. Ensure that there's consensus on > > > the > > > > >> > future > > > > >> > >> of the project. > > > > >> > >> - Call a vote. When we call a vote, one of us will send notice > > > to > > > > >> > >> incubator. > > > > >> > >> - Vote again on general@incubator. > > > > >> > >> > > > > >> > >> I do want to make sure there are two things abundantly clear: > > > > >> > >> > > > > >> > >> - Retirement isn't failure. Wave didn't fail as a project. > > > > >> > >> - It's better to describe it as "this isn't a good fit as an > > > Apache > > > > >> > >> project." Apache projects tend to have at least three people > > > > >> available > > > > >> > >> at all times, either making changes, merging in changes, or able > > > to > > > > >> cut > > > > >> > >> releases. > > > > >> > > > > > > >> > > What John described above is the process from Apache's side. > > > > >> > > > > > > >> > > The code is publicly available under an Apache License. Any of > > > > >> > > you > > > > can > > > > >> > > push your local repo up to GitHub and share it with whoever you > > > > like, > > > > >> > > using a name that includes the word "Wave", so that would be a > > > step > > > > >> > > alongside the more ASF-focussed administrative tasks above. > > > > >> > > > > > > >> > > Upayavira > > > > >> > > > > > >> > > > > > >> > > > > > > > > > > > >
