I'm not sure this is the right place, but it seems like the logical place to me. I need a node-patches@ mailing list for the node project. Any additional steps I need to take to get this done? Thanks Mike
Karsten, Can you create for Mike and make him the owner. thx Carl. On 11/10/2011 07:48 AM, Mike Burns wrote:
I'm not sure this is the right place, but it seems like the logical place to me.
I need a node-patches@ mailing list for the node project. Any additional steps I need to take to get this done?
Thanks
Mike
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/10/2011 04:48 AM, Mike Burns wrote:
I'm not sure this is the right place, but it seems like the logical place to me.
+1
I need a node-patches@ mailing list for the node project. Any additional steps I need to take to get this done?
Done. I used this (new) procedural: http://ovirt.org/wiki/Creating_and_configuring_mailing_lists Creating and fixing lists is a good "first task to prove your mettle" for new Infra contributors. We'll get there soon. Right now, I'd like a few of you to step up with your sshkey to get sudo access to ovirt.org. As I document more and more of the standard procedures (SOPs), it will be easy for others on this list to be able to take on these tasks. - - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFOvC1i2ZIOBq0ODEERAmXRAJ95yOxq2MNY3J2HaSmO0rcnKEva+QCgrK7U QUR+p5tSEz9VvwgUKQKLpmA= =kGUu -----END PGP SIGNATURE-----
On 11/10/2011 03:00 PM, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/10/2011 04:48 AM, Mike Burns wrote:
I'm not sure this is the right place, but it seems like the logical place to me. +1
I need a node-patches@ mailing list for the node project. Any additional steps I need to take to get this done? Done.
I used this (new) procedural:
http://ovirt.org/wiki/Creating_and_configuring_mailing_lists
Creating and fixing lists is a good "first task to prove your mettle" for new Infra contributors. We'll get there soon.
Right now, I'd like a few of you to step up with your sshkey to get sudo access to ovirt.org. As I document more and more of the standard procedures (SOPs), it will be easy for others on this list to be able to take on these tasks.
is it added to the projects page?
On Thu, 2011-11-10 at 15:14 -0500, Carl Trieloff wrote:
On 11/10/2011 03:00 PM, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/10/2011 04:48 AM, Mike Burns wrote:
I'm not sure this is the right place, but it seems like the logical place to me. +1
I need a node-patches@ mailing list for the node project. Any additional steps I need to take to get this done? Done.
I used this (new) procedural:
http://ovirt.org/wiki/Creating_and_configuring_mailing_lists
Creating and fixing lists is a good "first task to prove your mettle" for new Infra contributors. We'll get there soon.
Right now, I'd like a few of you to step up with your sshkey to get sudo access to ovirt.org. As I document more and more of the standard procedures (SOPs), it will be easy for others on this list to be able to take on these tasks.
is it added to the projects page?
Link was there previously, but I updated it to point to the right place. Mike
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
I don't mind taking care of mailman administration. Ofer.
-----Original Message----- From: infra-bounces@ovirt.org [mailto:infra-bounces@ovirt.org] On Behalf Of Karsten 'quaid' Wade Sent: 10 November 2011 22:01 To: infra@ovirt.org Subject: Re: Mailing list request
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/10/2011 04:48 AM, Mike Burns wrote:
I'm not sure this is the right place, but it seems like the logical place to me.
+1
I need a node-patches@ mailing list for the node project. Any additional steps I need to take to get this done?
Done.
I used this (new) procedural:
http://ovirt.org/wiki/Creating_and_configuring_mailing_lists
Creating and fixing lists is a good "first task to prove your mettle" for new Infra contributors. We'll get there soon.
Right now, I'd like a few of you to step up with your sshkey to get sudo access to ovirt.org. As I document more and more of the standard procedures (SOPs), it will be easy for others on this list to be able to take on these tasks.
- - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFOvC1i2ZIOBq0ODEERAmXRAJ95yOxq2MNY3J2HaSmO0rcnKEva+QCgrK7U QUR+p5tSEz9VvwgUKQKLpmA= =kGUu -----END PGP SIGNATURE----- _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/13/2011 11:52 PM, Ofer Schreiber wrote:
I don't mind taking care of mailman administration.
Great, thanks! I have an sshkey from you already, so I can setup the access later today. Folks on this list, we have some things to think about: 1. What is a good process for bringing on new system administrators? Meaning, since we're giving limited-to-full sudo access, we want appropriate barriers in place so we can create the trust before we give out the keys. In Ofer's case, the trust exists by being part of the original RHEV team. :) So at a minimum we should extend that same courtesy to people from our various organizations - anyone can gain an entry via organizational association. 2. What are ways to get proof that people are able to do the job? We all like to think we know how to admin our Linux systems, but doing it for a project moves from "my laptop is broken, darn it" to "the servers are broken and the mission is in peril, oops." Think of this as, "What is the merit in a meritocratic Infrastructure team?" In the Fedora Project, new people to the Infrastructure team go through a probation period. They are given one or a few relatively minor tasks - ones that must be done according to the established procedures, but not anything that will break important systems in the event of a mistake. Success in those tasks helps someone get on to a specific team that handles a sub-system of the overall infrastructure. Any other ideas on how to handle establishing merit? Thanks - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFOwWw52ZIOBq0ODEERAk6jAJ4zJ8hE5volBNcxUXJZDPQffkMUVwCfYP9w CjMT7XA7i6/cqgKetuz2OZk= =nJ2J -----END PGP SIGNATURE-----
On 11/14/2011 02:30 PM, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/13/2011 11:52 PM, Ofer Schreiber wrote:
I don't mind taking care of mailman administration. Great, thanks! I have an sshkey from you already, so I can setup the access later today.
Folks on this list, we have some things to think about:
1. What is a good process for bringing on new system administrators?
Meaning, since we're giving limited-to-full sudo access, we want appropriate barriers in place so we can create the trust before we give out the keys. In Ofer's case, the trust exists by being part of the original RHEV team. :)
So at a minimum we should extend that same courtesy to people from our various organizations - anyone can gain an entry via organizational association.
2. What are ways to get proof that people are able to do the job?
We all like to think we know how to admin our Linux systems, but doing it for a project moves from "my laptop is broken, darn it" to "the servers are broken and the mission is in peril, oops."
Think of this as, "What is the merit in a meritocratic Infrastructure team?"
In the Fedora Project, new people to the Infrastructure team go through a probation period. They are given one or a few relatively minor tasks - ones that must be done according to the established procedures, but not anything that will break important systems in the event of a mistake. Success in those tasks helps someone get on to a specific team that handles a sub-system of the overall infrastructure.
Any other ideas on how to handle establishing merit?
Good question. let's jump and #asfinfra on freenode and ask as I believe the ASF team has mostly worked through this question in a lot more detail than we will need over the years. Carl.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/15/2011 11:23 AM, Carl Trieloff wrote:
Good question. let's jump and #asfinfra on freenode and ask as I believe the ASF team has mostly worked through this question in a lot more detail than we will need over the years.
Yeah, wow, no doubt - hearing about it all right now. I'll write up a summary to send back to this thread. - - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFOwzcg2ZIOBq0ODEERAkeSAKC7EidTLzUmge55/iSMngE7AQH0TwCeOO9M YHA18+BW5joKtGCWGyLptrw= =gZBT -----END PGP SIGNATURE-----
participants (4)
-
Carl Trieloff -
Karsten 'quaid' Wade -
Mike Burns -
Ofer Schreiber