2012/10/18 kishore g <[email protected]>: > We havent made that decision. Most likely after we move to @asf, we will > have to keep the github repo as it is so that LinkedIn projects can use > them before migrating to apache helix. > > How easy is it to publish the jars we generate to Apache maven repository. very easy :-) Just inherits the Apache parent pom (see http://repo.maven.apache.org/maven2/org/apache/apache/9/). After that we will have to ask some karmas for deploying to repository.a.o. I can help on that if needed.
> > On Thu, Oct 18, 2012 at 11:06 AM, Olivier Lamy <[email protected]> wrote: > >> Hi, >> An other question I have in mind. >> Will package change before sources comes @asf or after. >> com.linkedin.helix -> org.apache.helix >> >> ? >> >> >> 2012/10/17 Olivier Lamy <[email protected]>: >> > Hi Folks, >> > I wonder about import sources process. (a git repo looks to be better >> > as sources come from git). >> > So we can use Apache git support. >> > >> > If I look at the contributors graph on github [1], I don't see a lot >> > of contributors. >> > So my question is: >> > * Are all of those contributors listed in initial committer list ? >> > * Do we need a software grant ? (IMHO nope due to the limited list of >> > github contributors, we only need to ensure they have a cla @asf) >> > >> > Thoughts ? >> > >> > Thanks, >> > -- >> > Olivier Lamy >> > Talend: http://coders.talend.com >> > http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> >> >> -- >> Olivier Lamy >> Talend: http://coders.talend.com >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy
