Hi Bruno,
On 5 Dec 2013, at 16:09, Bruno Gonzalez (aka stenyak) wrote:
Technical point of view:
A big point for staying at Apache is that we have a big infrastructure
already in place: issue tracker, code repository, wiki, mailing list,
possibility to use virtual machines for free, etc.
However, that's also the problem: being provided and maintained by a
third party (from the point of view of our project), means there's no
flexibility as to what VCS we want to use (a read-only mirror at
github
is missing the whole point about git), what communication medium to
officially use (the dogfooding argument), etc.
This is what I've had the closest (though scarce) experience with, and
in my case, I feel it has slowed me down, having to divert potential
coding time into non-important stuff. I don't know how much time, but
surely > 0.
For that, I'd vote in favour of leaving apache.
At least the scm point could be solved: Git has arrived and you can ask
for a migration to a native
Git repository (like Cordova did)
Cheers
All in all, and unless things can be done in a different way while
still
staying at Apache, my opinion is that we would prolly be better off
outside Apache at this point (in the future maybe it'd be better to go
back, but I don't see how things could get worse by leaving Apache
now).
On 11/28/13 11:02, Christian Grobmeier wrote:
I believe it makes sense to discuss if the incubator is the right
place.
Incubation has a specific goal: forming a team which can do releases
and is - in a way - active.
I see there is little activity at all. The only person i have seen
working on the codebase recently was Ali.
He also was the release manager of package which had trouble to
receive the necessary votes from its own team.
---
http://www.grobmeier.de
@grobmeier
GPG: 0xA5CC90DB
