*Jean-Baptiste, and ALL:
*
I am sure you had chance to convince yourself that
git + fork/pull is better then svn + patch.txt
I understand that you have apache guidelines,
but the switch should be easy:
1) treat github as the primary commit source,
require every git pull to contain an apache one liner
" Grant license to ASF for inclusion in ASF works (as per the Apache
License <http://www.apache.org/licenses/LICENSE-2.0> §5)"
2) replicate git to svn on schedule via hudson/jenkins job,
if github goes bust - just fall back to svn;
3) continue to produce snapshots and releases from svn
above all else, get an easy access to 500K github java developers
who are just eager to start committing to the karaf! :-)
what do you think?
Thank you,
Andrei
