Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: neutral (herse.apache.org: 216.86.168.178 is neither permitted
 nor denied by domain of geir@pobox.com)
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <F487C761-0BEB-4ECF-B6DF-22F64EF34B68@pobox.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: dev@harmony.apache.org
From: "Geir Magnusson Jr." <geir@pobox.com>
Subject: [announce] New Apache Harmony Committer : Xiao-Feng Li
Date: Sun, 18 Feb 2007 17:16:39 -0500

Please join the Apache Harmony PMC in welcoming the project's newest  
committer, Xiao-Feng Li.

Xiao-Feng has shown sustained dedication to the project, especially  
in the area GC and other VM issues, an ability to work well with  
others, and share the common vision we have for Harmony. We all  
continue to expect great things from him.

When your note from infrastructure with your account info comes  
through (which it hasn't, which is my fault, which I'll fix - I  
wanted to get this announcement out so we can put it on our report to  
the board ) :

As a first step to test your almighty powers of committership, please  
update the committers page on the website.  That should be a good   
(and harmless) exercise to test if everything is working.

Things to do :

1) test ssh-ing to the server people.apache.org.
2) Change your login password on the machine
3) Add a public key to .ssh so you can stop using the password
4) Set your SVN password  : just type 'svnpasswd'

At this point, you should be good to go.  Checkout the website from svn
and update it.  See if you can figure out how.

Also, anything checked out of SVN, be sure that you have checked out via
'https' and not 'http' or you can't check in. You can switch using "svn
switch". (See the manual)

Finally, although you now have the ability to commit, please remember :

1) continue being as transparent and communicative as possible.  You
earned committer status in part because of your engagement with others.
  While it was a  "have to" situation because you had to submit patches
and defend them, but we believe it is a "want to".  Community is the key
to any Apache project.

2)We don't want anyone going off and doing lots of work locally, and
then committing.  Committing is like voting in Chicago - do it early and
often.  Of course, you don't want to break the build, but keep the
"commit bombs" to an absolute minimum, and warn the community if you are
going to do it - we may suggest it goes into a branch at first.  Use
branches if you need to.

3) Always remember that you can **never** commit code that comes from
someone else, even a co-worker.  All code from someone else must be
submitted by the copyright holder (either the author or author's
employer, depending) as a JIRA, and then follow up with the required
ACQs and BCC.

Again, thanks for your hard work so far, and welcome.

The Apache Harmony PMC