Are there developers today not familiar with github?
Anyway, my main concern is getting us going with the least overhead so we can focus on creating content for the guidelines with the time that we have to spend on this. Having one stop shopping for a repo including issues and a wiki is a key benefit of
github so I prefer it as well.
And I don’t care what we call this, as long as the general public, especially our users, are allowed to participate. My understanding is that working groups had restrictions around non-member participation which is not what I want.
To be an effective Architecture Council that can influence the community to do the right thing, we need to be able to drive initiatives such as this. These guidelines need to be owned by the Architecture Council and involve the brightest minds in the community.
So whatever gets us there, lets do it.
Doug.
I think all platform committers are familiar with
git.eclipse.org, so we should probably stick with that. There's no need to make everyone learn a second tool.
|