Hey guys
It has come up on board and infra mailing lists that the git workflow that
is currently in place can not be used. Several issues with it where raised
including

* Canonical location for source code must be at the ASF
* Mailing lists are not being updated/touched with these changes
* The method of syncing the remote repository
* Process for tracking CLAs and Apache IDs for commits
* External org management (Who has access which can merge/secure)

The documentation on the policies around git [1] are currently not well
defined as the git service has been a work in progress. Even with this
being the case it is up to us as the PMC for Apache Usergrid to ensure we
are compliant with all ASF policies and any contributions meet IP
requirements.

We need to work to

* Ensure remediation of the outlined issues
* Discuss and come up with a workflow that meets our needs and is in
compliance with ASF policy and any board, infra, and IPMC requirements
* Review and ensure that the IP from the initial import to now for all
commits meets the ASF policies for contributions

As we are working to address these items I plan to bring up discussions
within board/infra and as a result produce a better documented policy for
git. If there are areas that will benefit all projects using git I would
like to create tickets and collectively work to improved the git service at
the ASF.

-Jake


[1] http://www.apache.org/dev/writable-git

Reply via email to