First of all, this is a great proposal and as a occasional Groovy coder, Groovy would be a very valuable addition to the Apache family.
My only concern is with the timing of the below: > Groovy 2.4 will > be the last major release under Pivotal Software's sponsorship, which > is scheduled to end on March 31, 2015. > Groovy has historically been hosted at Codehaus. While the project has started > to migrate off the Codehaus infrastructure, some critical tools of the > project are > still hosted there: JIRA, the mailing-list, and the deprecated wiki. > Codehaus has > announced end-of-support for mid-April, making the migration critical. > Even though the sponsorship of the core team by > Pivotal is ending on March 31st, the sheer size and diversity of the > community is a guarantee against the project being orphaned. Apache is a largely volunteer-driven organization. Some podling setup stages, like getting git repositories and web pages can take up to two weeks - Easter is also around the corner. Migration of mailing lists is very much a manual operation where each subscriber has to sign up manually. You can script-invite (ask me for one such script), but still each subscriber has to confirm to move over. Migrating issues and wikis can take some preparation. Importing code from Github is however very easy (DVCS!), but only after the Software Grants + CLAs have been signed, sent and accepted. Just creating @apache.org accounts can take a week or two. Several of the above are in a dependency chain. Obviously your mentors will know this and guide you (and help you ping the right people when needed). You have a very strong mentor list, so I am not too concerned. Is the wider Groovy community aware that transitioning to Apache is not done overnight? There is no guarantee this will be complete by mid-April, which to me sounds optimistic. Have anything be done to ask Codehaus for an extension of support during the migration process?
