You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Cliff Schmidt <cl...@gmail.com> on 2007/03/15 22:01:44 UTC
Instructions for new committers (was Getting accounts/karma set up)
I'm resending the same email I sent to set up all the original
committers back in August. The three recently elected committers
should follow all of this *with one exception and one clarification*:
- instead of sending the requested information to me, send it to
qpid-private@i.a.o. (I only did this all myself last time because we
didn't yet have a functioning PPMC.)
- the forwarding email address in #4 should be identical what was
written on the CLA that you faxed in.
When all this is done for each new committer, anyone on the PPMC can
request the new account by following the instructions at
http://apache.org/dev/pmc.html#newcommitter. PPMC members can also
look at old emails I have sent for the last couple committers (which
were cc'd to the qpid-private list) for examples.
The only parts that I will have to do is giving the new accounts qpid
karma and Jira access. I'll take care of the former when the accounts
are ready, but the latter requires each new committer to set up a Jira
account (if not already done) and to let me know their Jira id.
Cliff
---------- Forwarded message ----------
From: Cliff Schmidt
Date: Aug 30, 2006 10:53 AM
Subject: Getting accounts/karma set up
To: qpid-dev
Now that we have a mailing list set up with (hopefully) all the
committers subscribed by now, the next step is to get svn accounts set
up. So each committer should complete the following steps:
*NOTE for committers on other projects*
If you are already a committer on another Apache project, most of
these steps will not apply to you; *however*, please read step 1
closely and consider whether a) you have changed employers since
submitting your CLA, b) you would now be working on a project that
your employer might have a work-for-hire claim on and might not want
this IP licensed, and c) you actually thought about these things when
you submitted your CLA on the previous project. Also, *please send me
your userid* so that I can make sure you get qpid karma.
1. Read and sign the individual CLA
(http://apache.org/licenses/icla.txt). If you have an employer who
could possibly have any work-for-hire claim on your IP (usually the
case with a company that does any business remotely related to the
IP), be sure to show them the CLA, particularly section 5, and
describe the scope of the project. Better yet, have your employer
sign a corporate CLA (http://apache.org/licenses/cla-corporate.txt) to
make it very clear that they are willing to license their IP, as
contributed to the ASF by you. Having an explicitly signed corporate
CLA is generally a good thing for both the individual and the ASF
(this is, of course, not legal advice; each individual might want to
consider consulting their own personal attorney).
2. Fax in your individual CLA to the fax number listed on the form
(still required even if your employer signs a CCLA). If applicable,
make sure your employer has faxed in their CCLA.
3. Check the ASF Secretary's web page to see when the CLA has been
received: http://people.apache.org/~jim/committers.html#unlistedclas.
This requires him to periodically grab dozens of faxes and manually
enter them into a registration file -- so please allow a week or two
for this to happen.
4. While waiting for step 3, send me an email with the following
template filled out with your info:
Preferred userid: {id}
Full name: {name}
Forwarding email address: {email}
Faxed in individual CLA: {yes/no} (this should usually be 'yes'
before bothering to send me this info)
CLA has been recorded: {yes/no} (it's okay for this to be 'no' --
I'll just wait to see it recorded before sending in the account
request)
You can send this to me privately to reduce unnecessary noise and
potential email address harvesting. I'll compile all the info and
send out account creation requests to the root folks, cc'ing the
qpid-private list (more on that later). Choose any id you like
(within the typical character constraints) as long as it doesn't
conflict with something already listed in the CVS/SVN id column of
http://people.apache.org/~jim/committers.html#cvs/svn-committers. The
full name should match what you listed on your individual CLA. The
forwarding email address is for emails sent to {id}@apache.org. The
yes/no question about whether the CLA has been recorded is based on
whether you see your name listed at
http://people.apache.org/~jim/committers.html#unlistedclas.
5. While you're waiting for your account to be created, take a look
at some of the docs linked from http://apache.org/dev/, particularly
http://apache.org/dev/new-committers-guide.html.
Cliff
Re: Instructions for new committers (was Getting accounts/karma set up)
Posted by Rupert Smith <ru...@googlemail.com>.
Hi, I've been a bit slow about chasing this up, but should really get my
account sorted out soon. I've followed the above instructions (about 2 weeks
ago), and have heard nothing back yet. What do I need to do to get this
account opened and working?
On 15/03/07, Cliff Schmidt <cl...@gmail.com> wrote:
>
> I'm resending the same email I sent to set up all the original
> committers back in August. The three recently elected committers
> should follow all of this *with one exception and one clarification*:
>
> - instead of sending the requested information to me, send it to
> qpid-private@i.a.o. (I only did this all myself last time because we
> didn't yet have a functioning PPMC.)
>
> - the forwarding email address in #4 should be identical what was
> written on the CLA that you faxed in.
>
> When all this is done for each new committer, anyone on the PPMC can
> request the new account by following the instructions at
> http://apache.org/dev/pmc.html#newcommitter. PPMC members can also
> look at old emails I have sent for the last couple committers (which
> were cc'd to the qpid-private list) for examples.
>
> The only parts that I will have to do is giving the new accounts qpid
> karma and Jira access. I'll take care of the former when the accounts
> are ready, but the latter requires each new committer to set up a Jira
> account (if not already done) and to let me know their Jira id.
>
> Cliff
>
> ---------- Forwarded message ----------
> From: Cliff Schmidt
> Date: Aug 30, 2006 10:53 AM
> Subject: Getting accounts/karma set up
> To: qpid-dev
>
>
> Now that we have a mailing list set up with (hopefully) all the
> committers subscribed by now, the next step is to get svn accounts set
> up. So each committer should complete the following steps:
>
> *NOTE for committers on other projects*
> If you are already a committer on another Apache project, most of
> these steps will not apply to you; *however*, please read step 1
> closely and consider whether a) you have changed employers since
> submitting your CLA, b) you would now be working on a project that
> your employer might have a work-for-hire claim on and might not want
> this IP licensed, and c) you actually thought about these things when
> you submitted your CLA on the previous project. Also, *please send me
> your userid* so that I can make sure you get qpid karma.
>
> 1. Read and sign the individual CLA
> (http://apache.org/licenses/icla.txt). If you have an employer who
> could possibly have any work-for-hire claim on your IP (usually the
> case with a company that does any business remotely related to the
> IP), be sure to show them the CLA, particularly section 5, and
> describe the scope of the project. Better yet, have your employer
> sign a corporate CLA (http://apache.org/licenses/cla-corporate.txt) to
> make it very clear that they are willing to license their IP, as
> contributed to the ASF by you. Having an explicitly signed corporate
> CLA is generally a good thing for both the individual and the ASF
> (this is, of course, not legal advice; each individual might want to
> consider consulting their own personal attorney).
>
> 2. Fax in your individual CLA to the fax number listed on the form
> (still required even if your employer signs a CCLA). If applicable,
> make sure your employer has faxed in their CCLA.
>
> 3. Check the ASF Secretary's web page to see when the CLA has been
> received: http://people.apache.org/~jim/committers.html#unlistedclas.
> This requires him to periodically grab dozens of faxes and manually
> enter them into a registration file -- so please allow a week or two
> for this to happen.
>
> 4. While waiting for step 3, send me an email with the following
> template filled out with your info:
> Preferred userid: {id}
> Full name: {name}
> Forwarding email address: {email}
> Faxed in individual CLA: {yes/no} (this should usually be 'yes'
> before bothering to send me this info)
> CLA has been recorded: {yes/no} (it's okay for this to be 'no' --
> I'll just wait to see it recorded before sending in the account
> request)
>
> You can send this to me privately to reduce unnecessary noise and
> potential email address harvesting. I'll compile all the info and
> send out account creation requests to the root folks, cc'ing the
> qpid-private list (more on that later). Choose any id you like
> (within the typical character constraints) as long as it doesn't
> conflict with something already listed in the CVS/SVN id column of
> http://people.apache.org/~jim/committers.html#cvs/svn-committers. The
> full name should match what you listed on your individual CLA. The
> forwarding email address is for emails sent to {id}@apache.org. The
> yes/no question about whether the CLA has been recorded is based on
> whether you see your name listed at
> http://people.apache.org/~jim/committers.html#unlistedclas.
>
> 5. While you're waiting for your account to be created, take a look
> at some of the docs linked from http://apache.org/dev/, particularly
> http://apache.org/dev/new-committers-guide.html.
>
> Cliff
>
Re: Instructions for new committers (was Getting accounts/karma set up)
Posted by Martin Ritchie <ri...@apache.org>.
I've been following this up on the Incubator General list as there is
a bit of confusion about what the correct procedure is. I hope to have
a resolution shortly.
On 04/04/07, Rupert Smith <ru...@googlemail.com> wrote:
> Hi, I've been a bit slow about chasing this up, but should really get my
> account sorted out soon. I've followed the above instructions (about 2 weeks
> ago), and have heard nothing back yet. What do I need to do to get this
> account opened and working?
>
> Rupert
>
> On 20/03/07, Rupert Smith <ru...@googlemail.com> wrote:
> >
> > Preferred userid: rupertlssmith
> > Full name: Rupert Lindsay Stewart Smith
> > Forwarding email address: rupertlssmith@gmail.com
> > Faxed in individual CLA: yes
> > CLA has been recorded: yes
> >
> >
> > Jira ID: rupertlssmith
> >
> > ---------- Forwarded message ----------
> > From: Cliff Schmidt < cliffschmidt@gmail.com>
> > Date: Mar 15, 2007 9:01 PM
> > Subject: Instructions for new committers (was Getting accounts/karma set
> > up)
> > To: QPID Dev <qpid-dev@incubator.apache.org >
> >
> > I'm resending the same email I sent to set up all the original
> > committers back in August. The three recently elected committers
> > should follow all of this *with one exception and one clarification*:
> >
> > - instead of sending the requested information to me, send it to
> > qpid-private@i.a.o. (I only did this all myself last time because we
> > didn't yet have a functioning PPMC.)
> >
> > - the forwarding email address in #4 should be identical what was
> > written on the CLA that you faxed in.
> >
> > When all this is done for each new committer, anyone on the PPMC can
> > request the new account by following the instructions at
> > http://apache.org/dev/pmc.html#newcommitter. PPMC members can also
> > look at old emails I have sent for the last couple committers (which
> > were cc'd to the qpid-private list) for examples.
> >
> > The only parts that I will have to do is giving the new accounts qpid
> > karma and Jira access. I'll take care of the former when the accounts
> > are ready, but the latter requires each new committer to set up a Jira
> > account (if not already done) and to let me know their Jira id.
> >
> > Cliff
> >
> > ---------- Forwarded message ----------
> > From: Cliff Schmidt
> > Date: Aug 30, 2006 10:53 AM
> > Subject: Getting accounts/karma set up
> > To: qpid-dev
> >
> >
> > Now that we have a mailing list set up with (hopefully) all the
> > committers subscribed by now, the next step is to get svn accounts set
> > up. So each committer should complete the following steps:
> >
> > *NOTE for committers on other projects*
> > If you are already a committer on another Apache project, most of
> > these steps will not apply to you; *however*, please read step 1
> > closely and consider whether a) you have changed employers since
> > submitting your CLA, b) you would now be working on a project that
> > your employer might have a work-for-hire claim on and might not want
> > this IP licensed, and c) you actually thought about these things when
> > you submitted your CLA on the previous project. Also, *please send me
> > your userid* so that I can make sure you get qpid karma.
> >
> > 1. Read and sign the individual CLA
> > (http://apache.org/licenses/icla.txt). If you have an employer who
> > could possibly have any work-for-hire claim on your IP (usually the
> > case with a company that does any business remotely related to the
> > IP), be sure to show them the CLA, particularly section 5, and
> > describe the scope of the project. Better yet, have your employer
> > sign a corporate CLA (http://apache.org/licenses/cla-corporate.txt) to
> > make it very clear that they are willing to license their IP, as
> > contributed to the ASF by you. Having an explicitly signed corporate
> > CLA is generally a good thing for both the individual and the ASF
> > (this is, of course, not legal advice; each individual might want to
> > consider consulting their own personal attorney).
> >
> > 2. Fax in your individual CLA to the fax number listed on the form
> > (still required even if your employer signs a CCLA). If applicable,
> > make sure your employer has faxed in their CCLA.
> >
> > 3. Check the ASF Secretary's web page to see when the CLA has been
> > received: http://people.apache.org/~jim/committers.html#unlistedclas<http://people.apache.org/%7Ejim/committers.html#unlistedclas>
> > .
> > This requires him to periodically grab dozens of faxes and manually
> > enter them into a registration file -- so please allow a week or two
> > for this to happen.
> >
> > 4. While waiting for step 3, send me an email with the following
> > template filled out with your info:
> > Preferred userid: {id}
> > Full name: {name}
> > Forwarding email address: {email}
> > Faxed in individual CLA: {yes/no} (this should usually be 'yes'
> > before bothering to send me this info)
> > CLA has been recorded: {yes/no} (it's okay for this to be 'no' --
> > I'll just wait to see it recorded before sending in the account
> > request)
> >
> > You can send this to me privately to reduce unnecessary noise and
> > potential email address harvesting. I'll compile all the info and
> > send out account creation requests to the root folks, cc'ing the
> > qpid-private list (more on that later). Choose any id you like
> > (within the typical character constraints) as long as it doesn't
> > conflict with something already listed in the CVS/SVN id column of
> > http://people.apache.org/~jim/committers.html#cvs/svn-committers<http://people.apache.org/%7Ejim/committers.html#cvs/svn-committers>
> > . The
> > full name should match what you listed on your individual CLA. The
> > forwarding email address is for emails sent to { id}@apache.org<id...@apache.org>
> > . The
> > yes/no question about whether the CLA has been recorded is based on
> > whether you see your name listed at
> > http://people.apache.org/~jim/committers.html#unlistedclas
> > <http://people.apache.org/%7Ejim/committers.html#unlistedclas>.
> >
> > 5. While you're waiting for your account to be created, take a look
> > at some of the docs linked from http://apache.org/dev/, particularly
> > http://apache.org/dev/new-committers-guide.html.
> >
> > Cliff
> >
>
--
Martin Ritchie