Hi, Reading the IRC meeting log, I understand you guys want to work on a process to make it easy for new volunteers to start joining FI smoothly. Being a new volunteer member, I thought I would share some problems I faced, hoping to stir more thought leading to a good process in the short run. Let's define what we'll probably need:
1- Network layout: Being a new member, I have no idea what the network topology is, what are the server names, external/internal IPs ... Some form of a document (wiki drawing of the network?) would be extremely helpful IMHO
2- Xen-guests: In the near future, it seems everything will be running in Xen guests! A new technology, most new admins will not have mastered yet! I guess we need a quick intro to installing/handling Xen guests in the FI network. This should explain whatever templates/KS-files you guys use.
3- Server Access: Having registered myself and submitted my SSH/GPG keys, it is totally unclear to me what kind of access this gives me! Please make it clear to the new volunteer, what he can access to start working on. Perhaps some (playground) Xen-guests, for testing new deployments would be helpful?
4- Breaking down tasks: I think volunteers are more suited to working on longer term tasks, rather than immediate attention tasks. We might need to start defining longer term goals, and break those goals into smaller tasklets that many volunteers can start working on. As time goes on, natural leaders will emerge to handle managing those micro-projects.
Ok, those are the points I could think of (well it is 3:30am here!), I just hope to get this new process going soon.
Best Regards
---------- Forwarded message ---------- From: Ahmed Kamal email.ahmedkamal@googlemail.com Date: Oct 6, 2006 3:37 AM Subject: NewAdmin process To: fedora-infrastructure-list@redhat.com
Hi, Reading the IRC meeting log, I understand you guys want to work on a process to make it easy for new volunteers to start joining FI smoothly. Being a new volunteer member, I thought I would share some problems I faced, hoping to stir more thought leading to a good process in the short run. Let's define what we'll probably need:
1- Network layout: Being a new member, I have no idea what the network topology is, what are the server names, external/internal IPs ... Some form of a document (wiki drawing of the network?) would be extremely helpful IMHO
2- Xen-guests: In the near future, it seems everything will be running in Xen guests! A new technology, most new admins will not have mastered yet! I guess we need a quick intro to installing/handling Xen guests in the FI network. This should explain whatever templates/KS-files you guys use.
3- Server Access: Having registered myself and submitted my SSH/GPG keys, it is totally unclear to me what kind of access this gives me! Please make it clear to the new volunteer, what he can access to start working on. Perhaps some (playground) Xen-guests, for testing new deployments would be helpful?
4- Breaking down tasks: I think volunteers are more suited to working on longer term tasks, rather than immediate attention tasks. We might need to start defining longer term goals, and break those goals into smaller tasklets that many volunteers can start working on. As time goes on, natural leaders will emerge to handle managing those micro-projects.
Ok, those are the points I could think of (well it is 3:30am here!), I just hope to get this new process going soon.
Best Regards
We got them both, it sometimes takes people a while to respond.
https://www.redhat.com/mailman/private/fedora-infrastructure-list/2006-Octob...
-Mike
On 10/6/06, Ahmed Kamal email.ahmedkamal@googlemail.com wrote:
---------- Forwarded message ---------- From: Ahmed Kamal email.ahmedkamal@googlemail.com Date: Oct 6, 2006 3:37 AM Subject: NewAdmin process To: fedora-infrastructure-list@redhat.com
Hi, Reading the IRC meeting log, I understand you guys want to work on a process to make it easy for new volunteers to start joining FI smoothly. Being a new volunteer member, I thought I would share some problems I faced, hoping to stir more thought leading to a good process in the short run. Let's define what we'll probably need:
1- Network layout: Being a new member, I have no idea what the network topology is, what are the server names, external/internal IPs ... Some form of a document (wiki drawing of the network?) would be extremely helpful IMHO
2- Xen-guests: In the near future, it seems everything will be running in Xen guests! A new technology, most new admins will not have mastered yet! I guess we need a quick intro to installing/handling Xen guests in the FI network. This should explain whatever templates/KS-files you guys use.
3- Server Access: Having registered myself and submitted my SSH/GPG keys, it is totally unclear to me what kind of access this gives me! Please make it clear to the new volunteer, what he can access to start working on. Perhaps some (playground) Xen-guests, for testing new deployments would be helpful?
4- Breaking down tasks: I think volunteers are more suited to working on longer term tasks, rather than immediate attention tasks. We might need to start defining longer term goals, and break those goals into smaller tasklets that many volunteers can start working on. As time goes on, natural leaders will emerge to handle managing those micro-projects.
Ok, those are the points I could think of (well it is 3:30am here!), I just hope to get this new process going soon.
Best Regards
Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
On 10/7/06, Mike McGrath mmcgrath@fedoraproject.org wrote:
We got them both, it sometimes takes people a while to respond.
https://www.redhat.com/mailman/private/fedora-infrastructure-list/2006-Octob...
-Mike
Some context around this one would probably be nice, Ahmed was having some troubles with the infrastructure list, he wanted to make sure his emails were getting to the list :D
Regarding the content of your email, the network diagram could be useful to those working on the whole network but for the most part we keep it more semi-private, at least not totally public. Longer term project would certainly be a great way for people to get involved but it seems no one ever signs up to do whats on the schedule except for our regulars. And even then rarely is help offered. A lot of the projects listed on the schedule have been there for many months because work force is so scarce :( So if there's something on there anyone wants to work on make sure to take it or let the project manager know.
-Mike
Sorry for the double post, but I didnot get my posts except when you replied!!
I understand your point about the network layout public availability. But this would fall under "security through obscurity" wouldn't it ;)
About, the scarce workforce, I have tried to join many projects, but got lost! For instance, my last attempt was at helping with the firewall re-write. I contacted Luke, who was very responsive and helpful, albeit a bit busy. Me not knowing anything about the servers, the network layout, or even the requirements for the firewall, I just couldn't do anything to help :(
Well, perhaps, I should be tackling some priority 2 problems (to be simpler & of lower urgency), such as the "aliases" issue. I have no problem following this task if someone would tell me what needs to be done. Ideally, I would click on the project name, to get a detailed page saying: 1- Login to x.xx.xx.xx using some auth account 2- Query the ldap server at yy.yy.yy.yy 3- Write a script to verify all aliases against /etc/mail/aliases
Unfortunately, such a page doesnot yet exist. Any pointers to how I can go ahead ?
Best Regards
On 10/7/06, Mike McGrath mmcgrath@fedoraproject.org wrote:
On 10/7/06, Mike McGrath mmcgrath@fedoraproject.org wrote:
We got them both, it sometimes takes people a while to respond.
https://www.redhat.com/mailman/private/fedora-infrastructure-list/2006-Octob...
-Mike
Some context around this one would probably be nice, Ahmed was having some troubles with the infrastructure list, he wanted to make sure his emails were getting to the list :D
Regarding the content of your email, the network diagram could be useful to those working on the whole network but for the most part we keep it more semi-private, at least not totally public. Longer term project would certainly be a great way for people to get involved but it seems no one ever signs up to do whats on the schedule except for our regulars. And even then rarely is help offered. A lot of the projects listed on the schedule have been there for many months because work force is so scarce :( So if there's something on there anyone wants to work on make sure to take it or let the project manager know.
-Mike
On 10/7/06, Ahmed Kamal email.ahmedkamal@googlemail.com wrote:
About, the scarce workforce, I have tried to join many projects, but got lost! For instance, my last attempt was at helping with the firewall re-write. I contacted Luke, who was very responsive and helpful, albeit a bit busy. Me not knowing anything about the servers, the network layout, or even the requirements for the firewall, I just couldn't do anything to help :(
Well, perhaps, I should be tackling some priority 2 problems (to be simpler & of lower urgency), such as the "aliases" issue. I have no problem following this task if someone would tell me what needs to be done. Ideally, I would click on the project name, to get a detailed page saying: 1- Login to x.xx.xx.xx using some auth account 2- Query the ldap server at yy.yy.yy.yy 3- Write a script to verify all aliases against /etc/mail/aliases
The aliases thing is actually a flat file, we need someone to verify that there aren't spaces/special characters in the file, just that the aliases actually work and that we aren't breaking anything.
-Mike
infrastructure@lists.fedoraproject.org