On Wed, Jun 12, 2013 at 10:08 PM, Joseph Gentle <jose...@gmail.com> wrote:
> Thanks for your input, but this decision should be made by people who
> actually contribute code.
>
... or who may start contributing code, depending on the direction Apache
Wave takes from now on (if different from current one).
I've only contributed 3 tiny commits, but I'll give my opinion anyway.
Options are as described in the first email:
Option 1) I'm for this option *only* if there's a very high priority on
simplifying the wave codebase. If instead we're simply going to fix bugs
and keep the 300k LOC, I personally am unlikely to contribute anything
remotely big.
If option 1 is chosen by the community, I'm willing to put some time for
this refactoring, if that's the path the community chooses.
Option 2) I would not be able to contribute in this case, at least until a
minimum working server+client is in place. I'm no expert in federation, ot,
or web development, so am only likely to work on this if there's something
already in place that I can tinker with.
So is there enough manpower to pull this off? How committed would be the
people that go ahead and start essentially from scratch? (these are not a
rethoric questions)
Option 3) This looks like a sensible choice, but introduces some doubts
about contributing to the existing ("old") codebase. E.g. if I continue
writing my email-wave bot for current WiaB, and the parallel project ends
up being a success, will I be able to easily port the email-wave bot to the
new wave platform? I probably can't know at the moment, so what do I do?
Postpone all efforts and wait for the alternative to be finished, or code
away and cross my fingers that my work is not wasted?
--
Saludos,
Bruno González
_______________________________________________
Jabber: stenyak AT gmail.com
http://www.stenyak.com
