Just on the web technology an important statement from several codemotion talks I heard in Rome was, that especially Google likes to completely throw over their own exiting projects and Open Source efforts. Shutting down Google Code is only a side-effect. AngularJS (something to consider aside from JVM or other programming languages btw.) 2 will be a drastic breach with existing Angular 1 and force significant rewrite of exiting code. As well as re-learning a lot by people working with it right now.
Many Apache projects are well-respected and trusted as foundations of business-critical apps, not just the Web server that started it all. So nobody keeps us or other projects from creating several branches, but unlike the Googles (or WURFLs) we should not throw everything away that was there or even hide it from existing users. As for the migration from OpenDDR to DeviceMap it may not yet give the same number of results in GitHub (12 repositories for "OpenDDR", 5 for "DeviceMap") but aside from mostly contributions by Radu, there's this Clojure port/wrapper: https://github.com/timgalebach/clj-devicemap I am listed for Clojure, when I can I'll give it a try, but especially for more/new languages we may try to gather support by those who use a language in question more than some of us. E.g. compared to Java, Groovy or some .NET I also don't have as many lines of code in say Clojure or Scala under my belt as others. Werner On Mon, Mar 30, 2015 at 8:51 PM, Reza Naghibi <[email protected]> wrote: > Its not really the technical hurdle of maintaining multiple branches or > modules, its the management side of it, or more specifically the PMC. Will > this project be able to properly foster and guide 2.0 to success? We cannot > deny its been a rollercoaster ride to this point and I think we all share > blame in not seeing the warning signs. I admit, since becoming heavily > involved, my agenda has been to move away from the legacy OpenDDR client. I > can say that I have not been successful in uniting the project around 1.x > client (either that or we just have an extremely vocal resistance). > > Right now there are no new committers since no code for 2.0 has been > actually written. So point taken Bertrand, my idea to rebuild the PMC is a > bit premature since there are no obvious candidates right now. > > This is kind of my conundrum... is it safe to plow forward with 2.0? In my > view, nothing has changed. > > Will web technology wait for us? Is this a project or a playground? How > well can a democratic project handle competing goals? > > Sorry for the rhetorical questions. > > > On Mon, Mar 30, 2015 at 2:18 PM, Werner Keil <[email protected]> > wrote: > > > Hi, > > > > At least regarding some who showed their interest and will to contribute > > like Volkan (who submitted things more than just once on JIRA including > > patches, etc.) we all as PMC have not followed up on those (probably just > > one or two) more dedicated prospects. I sent this on the "private" > mailing > > list, not sure what happened to the thread, or of anybody (except > Bertrand > > maybe) is properly subscribed to that list...? > > > > Projects like Tamaya are still taking shape and the API is discussed, but > > onboarding of one or the other new committer happened a bit more > smoothly. > > Developong new ideas and branches next to each other, this happens in > many > > projects. Take Tomcat or Commons Config: > > http://commons.apache.org/proper/commons-configuration/ > > The 1.x and 2.x branch exist side by side. Also in SVN btw. > > > > > > Werner > > > > On Mon, Mar 30, 2015 at 7:47 PM, Bertrand Delacretaz < > > [email protected] > > > wrote: > > > > > Hi, > > > > > > On Mon, Mar 30, 2015 at 7:23 PM, Reza Naghibi <[email protected]> > wrote: > > > > ...If there was a way to reboot, maybe re-enter the incubator and > > reform > > > the > > > > PMC, I would do that in a second.... > > > > > > A PMC is formed out of the project's committers, so if you have people > > > in mind who would help make what you think is right happen, why don't > > > you ask them to get involved here? > > > > > > Also, the way things happen in Apache projects is by creating and > > > committing code - what prevents you from implementing your ideas? They > > > can always go to a new module if others want to keep the existing code > > > as is. > > > > > > -Bertrand > > > > > >
