I just got to thinking, do we really have any documentation for developers on what do to when they have a problem with something infra manages? For now, people just try to ping us on IRC, but I'd rather them use bugzilla for that. I need to probably send an email out to the devs so that the old folks know about this too. I could try and come up with some basic FAQs that are related to infrastructure that could be nice for new devs to know about. Also, we could include some more basic info on how different things work (rsync/mirrors/etc). Thoughts?
Sounds like a good idea to me. Feel free to attach a patch when it's ready. =)
Alright, I'll get around to it when I have some opening in my infinate amount of free time I have.
I forgot to cc: you guys in on this. Feel free to comment/make a patch if you guys have time. I'm trying to reduce the amount of "Who do I ask for mailing list stuff" questions and any other FAQs we get a lot.
Is this still relevant? And wouldn't an infra FAQ or similar be more appropiate than a dev handbook section that's bound to get outdated fairly quickly?
I agree with Bryan, an infra FAQ would be better as the roles and responsibilities change too frequently for the handbook updates. No one is better suited to create such a FAQ than the infra team. <reassigning bug> A link to such a FAQ could be added to the handbook when the FAQ is completed.
I'd consider adding something like a FAQ to hb-introduction-new-devs.xml, if you infra people would come up with a list of WHAT YOU EXACTLY WANT TO GO VIA BUGS.
