To be clear, our principle aim is to make a wave platform. Dogfooding our own software is only a major step if we call it one - I don't think we should move discussion there *yet*, but thats an obvious goal. Git isn't hosted in a subversion repository after all.
-J On Thu, Jul 25, 2013 at 1:46 AM, Upayavira <u...@odoko.co.uk> wrote: > Just a small thought to consider during this discussion. > > You are talking about some major changes to the tooling and workflow > typical of Apache communities. Wave is currently in the incubator, > making it a probationary project. > > I would say that the principal aim should be to understand the > principles of the ASF, to demonstrate that understanding, and graduate > from the incubator. > > Having done that, life will be easier when attempting such things as > getting Wave enabled servers, engaging in PR, etc. > > Remember that graduation is based upon how the community operates, and > has nothing to do with the quality, or otherwise, of the code-base. > > And the next big thing is getting that release out - proving that we > understand how to correctly license(etc) our code. (We didn't actually > get to the point of releasing, did we??) > > Upayavira > > On Wed, Jul 24, 2013, at 12:47 PM, Alfredo Abambres wrote: >> @Christian: below are some small considerations of mine about WWers and >> AW >> >> Disclosure: I'm a WWers member and I'm speaking as myself solely, not for >> the network/organization WWer.org. >> >> On Wed, Jul 24, 2013 at 11:35 AM, Christian Grobmeier >> <grobme...@gmail.com>wrote: >> >> > I like WW being an independent community which creates buzz running by >> > its own rules. >> > >> >> At this moment, as I see it, "*independent*" is the keyword on all this >> conversation. >> >> >> > >> > BTW, there is always the possibility to bring the WW community to the >> > ASF too. Given >> > the tools WW is using, it doesn't make sense at the moment. Maybe later >> > when AW >> > is stable and installed at ASF it makes sense to include the WW community >> > as >> > part of the AW community. Something similar happened with Apache >> > OpenOffice. >> > People were running a support forum for OpenOffice and they have >> > joined the project. >> > >> >> Thanks for your suggestions, it's great to see that our work matter and >> that we can still add lots of value to the future of Wave and Apache >> Wave. >> >> I *personally* don't see WWer.org ever becoming a AW community (but >> things >> change, right?!). That doesn't mean, that the community (people) that now >> represent WWer.org can't form other communities, even within AW. IMO, >> WWers >> members are probably the best prepared ones to assume that role and make >> it >> happen, on a similar approach to your example about Apache OpenOffice >> support forum. >> >> It's great to know that those "doors" exist and may be open when needed. >> Once again thanks.
