I vote stay, for what it's worth. I would have an easier time funding one or more developers if I know the resulting code would eventually reside under the Apache umbrella. Best of luck either way though.
On Tue, Dec 10, 2013 at 9:48 AM, Upayavira <u...@odoko.co.uk> wrote: > It seems to me that the time has come to make a decision here, and for > now, I'm going to ask that we consider just one simple question: > > * Should Wave stay within Apache, or leave. > > I'm going to ask that we postpone any discussion about either option > that isn't required to make the decision, until the vote is complete. If > discussion is to occur, please move it to a separate thread, to keep the > [VOTE] thread clean. > > I'm going to suggest that this vote runs for 72hrs, and that we aim for > consensus. Should anyone wish to change their vote based upon the votes > of others, that's fine, only your last vote will count. > > I'm going to suggest that for this vote to succeed, we'll need full > consensus of committers/PPMC members. Community votes are also very much > welcome, but committer/PPMC votes will be the ones that make up the > final tally. If this vote does not receive a consensus, then the status > quo will continue until another event occurs to change it. > > I myself am not going to vote, as I see this as a vote for those who > feel ownership of the project and its codebase. I couldn't make an > impartial vote anyway. > > So, here's your chance to cast your votes: > > [ ] Wave should stay at Apache > [ ] Wave should leave Apache, and find a home elsewhere > > Thanks, > > Upayavira >
