What are the technical requirements for graduation? On Mon, Mar 16, 2015 at 11:39 AM Vicente J. Ruiz Jurado <v...@ourproject.org> wrote:
> El 16/03/15 a las 08:35, Christian Grobmeier escribió: > > I would like to highlight that retirement does not mean end of life. > > There is a chance thing will get easier once on GitHub. Don't > > forget, Apache is not only a great community, it's also a set of > > rules, frameworks, restrictions and so on. It's do-able for a bigger > > community. But the Wave community hardly is able to allocate time to > > do that final step with the release. No offense, I know for myself > > how hard it is to allocate time. > > > > In a GitHub environment, Wave would have done that release already > > (or most likely). > > > > I agree, that protocols may have a good place at Apache. But just > > because retirement is not successful​ this time does not mean it's > > not successful another time. If Wave can build up a community, it > > can always come back to incubation. > > > > However my feeling says, you need to make access easier to Wave. This > > means also the full power of pull requests, which we only offer > > partially. > > Hi there: > > At this moment, I see Apache Wave mainly as a protocol, so IMHO Apache > is a good place for something like this. > So I vote to stay and to avoid the "forking nightmare" of a protocol. > > If not, we should find another organization, different than "github". > > Meanwhile, I'm close to release a new version of kune with a totally new > user interface: > http://kune.cc > https://github.com/comunes/kune/ > I think that kune is a good example of how Wave can be integrated in 3rd > party software. I try to maintain minimal differences with the Apache > Wave code and Wave for us is just some more maven dependencies. > > The main goals of Apache Wave and kune are different. I'm trying since > 2002 to build collaborative spaces for any kind of project/area (not > just FLOSS projects), like a "social multipurpose github": > > https://en.wikipedia.org/wiki/Ourproject.org > > I started to develop kune in 2007 and using the same > technology/frameworks than Wave, when Google released wave, I just > replaced our non-concurrent editor with Wave. So I'm playing with Wave > code, since the first FedOne release. > > For some stats of code, etc: > > https://www.openhub.net/p/apache_wave > https://www.openhub.net/p/kune > > kune.cc is in production since four years ago hosting 20.000 documents, > 90% are waves. > > When some developer/contributor arrives to kune, I'll always try to > suggest to start contributing to wave, but til now, people prefer to > talk than to walk (or code). > > Sorry for the "ad block", but I think that clarifies my point. > > Greetings, > > Vicente > > >
