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
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 -
>
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 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
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 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 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,
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 wrote:
> Just so I understand, what would be the criteria for the project rejoining
> the Apache
Pablo - those are reasonable steps for the non-Apache side of this, yes.
On Tue, 28 Nov 2017, at 11:58 AM, Pablo Ojanguren wrote:
> I agree too. This project/community doesn't make enough progresses for
> being under Apache umbrella.
>
> However regarding the future of the project I still work
I agree too. This project/community doesn't make enough progresses for
being under Apache umbrella.
However regarding the future of the project I still work in my own fork
that can benefit Wave, so I want to
keep Wave somewhere.
>From a practical standpoint, I did recap this tasks (what else?)
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
Amir - email wave-dev-unsubscr...@incubator.apache.org.
On Mon, 27 Nov 2017, at 07:48 PM, Amir N. Nashat wrote:
> Hello!
>
> Is it possible to be removed from this mailing list? I don't see an
> unsubscribe link.
>
> Thanks
>
> On Mon, Nov 27, 2017 at 11:43 AM, Dustin Pfannenstiel <
>
Hello!
Is it possible to be removed from this mailing list? I don't see an
unsubscribe link.
Thanks
On Mon, Nov 27, 2017 at 11:43 AM, Dustin Pfannenstiel <
dustin.pfannenst...@nth-estate.com> wrote:
> I've set up a repo and organization for the code base on github.
>
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 wrote:
>
>
>
> On Mon, 27 Nov 2017, at 04:46 PM, John D.
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
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
Ok, I agree. Can you elaborate regarding retirement plan?
On Mon, Nov 27, 2017 at 4:14 PM, John D. Ament
wrote:
> Unfortunately, I have to agree that it's likely time for the podling to
> retire. I believe we've reviewed all necessary internally and there would
> be
Unfortunately, I have to agree that it's likely time for the podling to retire.
I believe we've reviewed all necessary internally and there would be nothing
encumbering the podling from keeping the name "Wave" and moving to a dedicated
github project/set of repos.
Ultimately, that's not a
Dear all,
The time has come for me to resign as a mentor for this project. John D
Ament has said he is prepared to help, but to be honest, given the
recent level of (in)activity, I think the time has come for us to admit
that we are not going to achieve in any reasonable time the goal of the
17 matches
Mail list logo