On Thursday, October 31, 2013 09:35:31 AM Andrew Buczko wrote: > I wouldn't say it as "one who knows the most" but rather "one who is an > expert", just a suggestion. > > Also, as we get more members can we have more than one expert? This will > levitate the problem a rigid hierarchy since there will be more than one > person to go to.
yes: > If you're not the only one who is the de facto handler for a project, please add others who help > > On Wed, Oct 30, 2013 at 5:09 PM, Omar Rassi <[email protected]> wrote: > > Just added my entry :) > > > > On Wed, Oct 30, 2013 at 2:01 PM, Torrie Fischer <[email protected]>wrote: > >> Howdy, hakkers! > >> > >> Over the last month or two, I've been trying to figure out a nice clean > >> way > >> for others to figure out who is responsible for what in the space. > >> Originally > >> I considered toying with the idea of having each Champion claim a title > >> of > >> something they're responsible for, such as Champion of System > >> Administration, > >> Champion of the Machine Shop, etc. > >> > >> The problem with that is it creates a rigid hiearchy of who is in charge > >> of > >> something that could take a significant effort to change along with > >> obvious > >> feelings of resentment towards those who are percieved as having more > >> power. > >> > >> After thinking back to how open source development works, I've created > >> this > >> wiki page: > >> > >> https://synhak.org/wiki/Maintainers > >> > >> It is an informal way for people to openly state that they are indeed the > >> person who knows the most about how to work something. For example, if > >> the > >> internet at the space is down, I often get a few text messages about it > >> long > >> before someone mentions it on the discuss list. I'm not the one who > >> configures > >> our network, I just happen to keep the machines that use it happy :) > >> > >> If you feel confident that you can take responsibility for something at > >> the > >> space, add yourself to that table! It doesn't mean you're required to do > >> anything or that you've made some kind of commitment to be on call 24/7. > >> All > >> it means is that we now have some documentation of who to go to for the > >> fastest resolution of issues or who to ask for questions. If you're not > >> the > >> only one who is the de facto handler for a project, please add others who > >> help > >> out as well. If you don't know who is the maintainer of something, you > >> can ask > >> Chris or I and we'll figure it out. > >> > >> tl;dr: If you're a core volunteer who contributes a lot of effort towards > >> our > >> infrastructure, you should add yourself to the new Maintainers page on > >> the > >> wiki. > >> _______________________________________________ > >> Discuss mailing list > >> [email protected] > >> https://synhak.org/mailman/listinfo/discuss > > > > _______________________________________________ > > Discuss mailing list > > [email protected] > > https://synhak.org/mailman/listinfo/discuss _______________________________________________ Discuss mailing list [email protected] https://synhak.org/mailman/listinfo/discuss
