You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by "Geir Magnusson Jr." <ge...@pobox.com> on 2007/02/18 23:16:39 UTC

[announce] New Apache Harmony Committer : Xiao-Feng Li

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


Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Tim Ellison <t....@gmail.com>.
Keep up the good work Xiao-Feng.

Geir Magnusson Jr. wrote:
> 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
> 
> 

Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Alexey Varlamov <al...@gmail.com>.
Well done, congrats!
--
Alexey

2007/2/19, Andrew Zhang <zh...@gmail.com>:
> Congrats!
>
> On 2/19/07, Geir Magnusson Jr. <ge...@pobox.com> wrote:
> >
> > 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
> >
> >
>
>
> --
> Best regards,
> Andrew Zhang
>

Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Andrew Zhang <zh...@gmail.com>.
Congrats!

On 2/19/07, Geir Magnusson Jr. <ge...@pobox.com> wrote:
>
> 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
>
>


-- 
Best regards,
Andrew Zhang

Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Mark Hindess <ma...@googlemail.com>.
Congratulations!

-Mark

On 18 February 2007 at 17:16, "Geir Magnusson Jr." <ge...@pobox.com> wrote:
> 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
> 



Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Alexei Fedotov <al...@gmail.com>.
Congratulations!

On 21 Feb 2007 16:34:22 +0300, egor.pasko@gmail.com
<eg...@gmail.com> wrote:
> Congratulations!
>
> On the 0x282 day of Apache Harmony Geir Magnusson, Jr. wrote:
> > 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
> >
> >
>
> --
> Egor Pasko
>
>


-- 
With best regards,
Alexei,
ESSD, Intel

Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by eg...@gmail.com.
Congratulations!

On the 0x282 day of Apache Harmony Geir Magnusson, Jr. wrote:
> 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
> 
> 

-- 
Egor Pasko


Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Leo Li <li...@gmail.com>.
 Congratulations!


On 2/19/07, Geir Magnusson Jr. <ge...@pobox.com> wrote:
>
> 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
>
>


-- 
Leo Li
China Software Development Lab, IBM

Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Richard Liang <ri...@gmail.com>.
Congratulations!

On 2/19/07, Geir Magnusson Jr. <ge...@pobox.com> wrote:
> 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
>
>


-- 
Richard Liang
China Development Lab, IBM

Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Rana Dasgupta <rd...@gmail.com>.
Well done, Xiao feng

On 2/20/07, Weldon Washburn <we...@gmail.com> wrote:
>
> Xiao Feng,
> Congratulations!
>
>
> On 2/18/07, Geir Magnusson Jr. <ge...@pobox.com> wrote:
> >
> > 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
> >
> >
>
>
> --
> Weldon Washburn
> Intel Enterprise Solutions Software Division
>

Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Weldon Washburn <we...@gmail.com>.
Xiao Feng,
Congratulations!


On 2/18/07, Geir Magnusson Jr. <ge...@pobox.com> wrote:
>
> 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
>
>


-- 
Weldon Washburn
Intel Enterprise Solutions Software Division

Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Vladimir Ivanov <iv...@gmail.com>.
Congratulations!
 Vladimir

On 2/19/07, Alex Blewitt <al...@gmail.com> wrote:
> On 18/02/07, Geir Magnusson Jr. <ge...@pobox.com> wrote:
> > Please join the Apache Harmony PMC in welcoming the project's newest
> > committer, Xiao-Feng Li.
>
> Congratulations!
>
> Alex.
>

Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Alex Blewitt <al...@gmail.com>.
On 18/02/07, Geir Magnusson Jr. <ge...@pobox.com> wrote:
> Please join the Apache Harmony PMC in welcoming the project's newest
> committer, Xiao-Feng Li.

Congratulations!

Alex.

Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Yu Zhang <cl...@gmail.com>.
Congratulations! 

Yu
----- Original Message ----- 
From: "Geir Magnusson Jr." <ge...@pobox.com>
To: <de...@harmony.apache.org>
Sent: Monday, February 19, 2007 6:16 AM
Subject: [announce] New Apache Harmony Committer : Xiao-Feng Li


> 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
>

Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Mikhail Markov <mi...@gmail.com>.
Congratulations, Xiao-Feng!

Mikhail

On 2/19/07, Geir Magnusson Jr. <ge...@pobox.com> wrote:
>
> 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
>
>

Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Stepan Mishura <st...@gmail.com>.
Congratulations!

-Stepan.


On 2/19/07, Geir Magnusson Jr. wrote:
>
> 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
>
>


-- 
Stepan Mishura
Intel Enterprise Solutions Software Division

Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Gregory Shimansky <gs...@gmail.com>.
Geir Magnusson Jr. wrote:
> Please join the Apache Harmony PMC in welcoming the project's newest 
> committer, Xiao-Feng Li.

Congratulations! Keep up the good work.

-- 
Gregory


Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by LvJimmy,Jing <fi...@gmail.com>.
Though a bit late, Congratulations! :)

2007/2/19, Geir Magnusson Jr. <ge...@pobox.com>:
> 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
>
>


-- 

Best Regards!

Jimmy, Jing Lv
China Software Development Lab, IBM

Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Alexey Petrenko <al...@gmail.com>.
Congratulations!

2007/2/19, Geir Magnusson Jr. <ge...@pobox.com>:
> 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
>
>

Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Mikhail Loenko <ml...@gmail.com>.
Congratulations!

2007/2/19, Geir Magnusson Jr. <ge...@pobox.com>:
> 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
>
>

Re: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by Oliver Deakin <ol...@googlemail.com>.
Congrats! :)

Geir Magnusson Jr. wrote:
> 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
>
>

-- 
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU


RE: [announce] New Apache Harmony Committer : Xiao-Feng Li

Posted by "Morozova, Nadezhda" <na...@intel.com>.
Welcome and congrats!

Cheers, 
Nadya
 
>-----Original Message-----
>From: Geir Magnusson Jr. [mailto:geir@pobox.com]
>Sent: Monday, February 19, 2007 1:17 AM
>To: dev@harmony.apache.org
>Subject: [announce] New Apache Harmony Committer : Xiao-Feng Li
>
>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