Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 40046 invoked from network); 23 Nov 2006 15:18:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Nov 2006 15:18:36 -0000 Received: (qmail 53598 invoked by uid 500); 23 Nov 2006 15:18:42 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 53563 invoked by uid 500); 23 Nov 2006 15:18:42 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 53554 invoked by uid 99); 23 Nov 2006 15:18:42 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Nov 2006 07:18:42 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of nbeyer@gmail.com designates 66.249.82.234 as permitted sender) Received: from [66.249.82.234] (HELO wx-out-0506.google.com) (66.249.82.234) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Nov 2006 07:18:30 -0800 Received: by wx-out-0506.google.com with SMTP id i26so596928wxd for ; Thu, 23 Nov 2006 07:18:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BgYbRFHbKpWRxOkU7o6s5eP/S1NdWsVSLa5wDUvSAZNjd/oqHSkSpuJcz3VUZ4vA9lhZWIcZ1rRAOxSJSghOP//VHjx672bSUNA9JSiLPTE5OvC7flGFL/wfrDOoXL4zNbmdxxmZaF7TnFXemXpjzzuSrVh5OBM+q/pmHZucVDA= Received: by 10.90.51.17 with SMTP id y17mr7712924agy.1164295088973; Thu, 23 Nov 2006 07:18:08 -0800 (PST) Received: by 10.90.66.18 with HTTP; Thu, 23 Nov 2006 07:18:08 -0800 (PST) Message-ID: <3b3f27c60611230718g58222019j9484e033845bfe1d@mail.gmail.com> Date: Thu, 23 Nov 2006 09:18:08 -0600 From: "Nathan Beyer" To: dev@harmony.apache.org Subject: Re: [announce] New Apache Harmony Committer : Nadezhda Morozova In-Reply-To: <4565367E.10301@pobox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4565367E.10301@pobox.com> X-Virus-Checked: Checked by ClamAV on apache.org Congratulations! On 11/22/06, Geir Magnusson Jr. wrote: > Please join the Apache Harmony PMC in welcoming the project's newest > committer, Nadezhda Morozova. > > Nadya has shown sustained dedication to the project, especially in the > area of documentation and the website, an ability to work well with > others, and share the common vision we have for Harmony. We all continue > to expect great things from her. > > 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 >