Hello All. I think its important to consider whether staying at Apache is even a choice at this juncture. This is the second time Christian has raised question about incubator being a suitable place for Wave. It appears that Apache expects given amount of activity/progress for a project to be considered sufficiently active. Some posts in this discussion are probably assuming that moving away is a strategic decision. Its not. It can certainly be looked at positively, but its more a suggestion from the project mentor.
Several companies are housing there open source projects at Github. Its just a collaboration medium. Wave is still going to need a governing body, people who are responsible for authenticity and quality of code among other things. Its no different than having designated committers when we are at Apache. Just being an incubator project does not guarantee code quality or any of the goodies unless there are actual project contributors taking care of things like code review. Github may help to build up a community, processes being easier to follow and with more visibility among the programming community. Project will have to be careful to not loose the openness in the absence of governing organization like Apache. If Wave gains sufficient momentum, we can always think of coming back to Apache or any of the other Open Source initiatives for that matter. Nothing succeeds like success. The important things to consider before the actual move is done is to have quick process set up, a Google discussion group, canonical Github tree, trademarks questions etc. Even these things need lot of attention. It will always boil down to availability of interested parties who can contribute enough time. Good thing is, as long as the code and related IPs are under open source license, project has an existence of it's own irrespective of organizations, whoever has time and ideas can take it forward. Cheers. Pratik. On Fri, Nov 29, 2013 at 6:20 PM, Raphael Bircher <r.birc...@gmx.ch> wrote: > Hi Upayavira > > Am 29.11.13 13:24, schrieb Upayavira: > > The way open source communities such as this one work, the road map >> needs to be defined by the people doing the work. It would be easy for >> some of us to come up with a cool roadmap, but if coders aren't behind >> it, it will be pointless effort. >> > That's true. I have just the feeling, that wave is a bit loost in space. I > don't talk about a long time roadmap. I talk about a short roadmap, from > release to release. > > >> If folks are interested in coding Wave, whether at Apache or elsewhere, >> I'd encourage them to jump in and start suggesting where they think it >> should go. >> > I just want to say, that in my point of view, the Apache Structure is not > the problem. I beleve a move to GitHub will not help for the long term. For > my point of view, it's the wrong way to adress the problem. > > Greetings Raphael > >
