accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From els...@apache.org
Subject svn commit: r1490096 - /accumulo/site/branches/git/content/git.mdtext
Date Thu, 06 Jun 2013 00:46:21 GMT
Author: elserj
Date: Thu Jun  6 00:46:21 2013
New Revision: 1490096

URL: http://svn.apache.org/r1490096
Log:
ACCUMULO-1498 Update the section regarding what and how to request the change from INFRA

Modified:
    accumulo/site/branches/git/content/git.mdtext

Modified: accumulo/site/branches/git/content/git.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/branches/git/content/git.mdtext?rev=1490096&r1=1490095&r2=1490096&view=diff
==============================================================================
--- accumulo/site/branches/git/content/git.mdtext (original)
+++ accumulo/site/branches/git/content/git.mdtext Thu Jun  6 00:46:21 2013
@@ -97,7 +97,7 @@ multiple developers to teach contribute 
 4. The repository should be the irrefutable, sole source of information
 regarding the development of Apache Accumulo, and, as such, should have
 best-efforts given in creating a clean, readable history without any single
-entity having write access and all changes flowing through he/she. In other
+entity having to control all write access and changes (a proxy). In other
 words, the developers are the ones responsible for ensuring that previous
 releases are preserved to meet ASF policy, for not rewriting any public history
 of code not yet officially released (also ASF policy relevant) and for a
@@ -106,3 +106,52 @@ created by the application of multiple r
 identifying attributes but the same contents (git-rebase and git-cherry-pick).
 
 ## The implementation 
+
+### Contributors
+
+### Developers
+
+### Release Management
+
+## The infrastructure
+
+This section deals with the changes that must be requested through INFRA. As
+with any substantial INFRA request, the VOTE and result from the mailing should
+be referenced so INFRA knows that the request has been acknowledged. Likely, a
+PMC member should be the one to submit the request.
+
+### Repositories
+
+I believe that we will need multiple repositories to best align ourselves with
+how we currently track "Accumulo" projects. The repositories follow:
+
+1. The main source tree. This will track the standard trunk, branches, tags
+structure from Subversion for Apache Accumulo.
+
+2. One repository for every project in
+[contrib](https://svn.apache.org/repos/asf/accumulo/contrib): Accumulo-BSP,
+Instamo Archetype, Accumulo Pig, and the Wikisearch project. Each of these are
+considered disjoint from one another, and the main source tree, so they each
+deserve their own repository.
+
+Given the list of repositories that currently exist on the [ASF
+site](https://git-wip-us.apache.org/repos/asf) and a brief search over INFRA
+tickets, multiple repositories for a single Apache project is not an issue.
+Having this list when making the initial ticket will likely reduce the amount of
+work necessary in opening multiple INFRA tickets.
+
+### Mirroring
+
+It should be noted in the INFRA requst that each repository will also need to be
+configured to properly mirror to the [ASF Github](https://github.com/apache)
+account to provide the same functionality with current have via the git+svn
+mirror. This should be noted in the INFRA request. Same change needs to be
+applied for the [Apache hosted](http://git.apache.org) mirror'ing.
+
+### Mailing lists
+
+It should be noted in the INFRA request that commit messages should be sent to
+[commits@accumulo.apache.org](mailto:commits@accumulo.apache.org). The subject
+can be decided on using the [provided
+variables](https://git-wip-us.apache.org/docs/switching-to-git.html#contents).
+



Mime
View raw message