Changes

Jump to navigation Jump to search
Line 67: Line 67:     
I think recording in the wiki would be great. Just a page like [[Tool Authorization Exceptions Record]]. It could just have a table that has who and why and the person that authorized them. I see value in something like this that bioguy is suggesting and it would be an after the fact thing. Kinda like posting to the list when you brake something. It helps every one learn and keeps a record. I would prefer a wiki page over just a post to the list because it is easier to go back and look at and easier to organize. --[[User:Lucas|Lucas]] ([[User talk:Lucas|talk]]) 20:21, 23 February 2015 (CST)
 
I think recording in the wiki would be great. Just a page like [[Tool Authorization Exceptions Record]]. It could just have a table that has who and why and the person that authorized them. I see value in something like this that bioguy is suggesting and it would be an after the fact thing. Kinda like posting to the list when you brake something. It helps every one learn and keeps a record. I would prefer a wiki page over just a post to the list because it is easier to go back and look at and easier to organize. --[[User:Lucas|Lucas]] ([[User talk:Lucas|talk]]) 20:21, 23 February 2015 (CST)
 +
 +
I'm hesitant to tie Area Hosts' hands by creating policies so specific that problems inevitably happen requiring more voting to correct them. For example, the original policy required that every authorized user be listed on a physical list located on the tool. That turned into a really bad idea, and as a result we blatantly ignored our own policy. Personally, I prefer to let Area Hosts handle authorization exceptions in whatever way they deem best, which may be the Wiki, the mailing list, listing them in the same way maintenance records for the tool are recorded, etc. --[[User:Rdpierce|Rdpierce]] ([[User talk:Rdpierce|talk]]) 23:44, 23 February 2015 (CST)
    
== Minor style suggestions ==
 
== Minor style suggestions ==
833

edits

Cookies help us deliver our services. By using our services, you agree to our use of cookies.

Navigation menu