none
Revisiting en-us again. RRS feed

Answers

All replies

  • There is nothing preventing you from reverting the title change and adding a tag. If the person who edited the title has an issue with your reverting it and changing it to a tag, they will contact you. If the two of your are unable to agree on an approach, escalate to the Wiki Community Council for resolution,

    tony soper

    • Proposed as answer by tonysoper_MSFT Tuesday, April 10, 2012 4:21 PM
    Tuesday, April 10, 2012 4:20 PM
  • Hi - it sounds like the question here is no so much about that specific article but around reaching a concensus on the general title guidelines for English articles. Something we might want to discuss here rather than let this play out article-by-article.

    So here is a suggestion...

    Maybe people who feel strongly that "(en-us)" needs to be added in the title of English article could clarify the benefits and how they make use of that in practice? Sharing this could help to either get more people to understand/support the practice or end it.

    And to add my 2 cents: The current TN wiki is very English centric and needs a better solution for other languages (in the works). Besides "fairness" between languages, I'm just not sure what is the practical value of adding "(en-us)" in the title.

    Wednesday, April 11, 2012 6:01 PM
  • Exactly, this isn't a war amongst wiki-ers, but an ask for guidelines from the top.

    Reasons for a tag - sure, no problem as the wiki search supports tagging.  But in the title of the wiki--- is it really necessary?

    Wednesday, April 11, 2012 6:05 PM
  • Ed also posted a Wiki article that will hopefully capture the ideas discussed here.
    Thursday, April 12, 2012 6:18 PM
  • Let me give you an example

    On many times Windows get root cert updates.  http://support.microsoft.com/kb/931125

    This leads to wiki posts of http://social.technet.microsoft.com/wiki/contents/articles/1291.microsoft-root-certificate-program.aspx which leads to this wiki http://social.technet.microsoft.com/wiki/contents/articles/1658.windows-root-certificate-program-members-en-us.aspx which leads to http://social.technet.microsoft.com/wiki/contents/articles/9016.windows-root-certificate-program-members-march-2012-en-us.aspx listing the official root cert members.

    All writing on this should start and stop with a Microsoft employee.  These are definitive documenation of contents of updates that get on systems and having a community member go back and put even the mere en-us in the subject line means that I as a person vetting patching content for stuff that goes on my network has to check and make sure that the only thing changed by a community member was the subject line.

    Can these types of documentation wiki posts that should only have Microsoft content and nothing but content written by Microsoft employees be locked to read only by community members?

    These really should be in KBs where we in the community can't edit them.  But since they are on wikis, can permissions be adjusted?

    Tuesday, April 17, 2012 8:28 PM
  • Susan, no, there is no locking of topics, because it is anti-wiki. It is fairly easy to keep tabs on a topic by using the check mark on the edit screeen that says "Email me updates to this page". The e-mail that you receive on edit shows you edits in green for additions and red for deletions. At a glance you can then tell if something other than the subject line was changed.

    tony soper

    Tuesday, April 17, 2012 8:56 PM
  • Then should this type of content b on a wiki?  It's the root cert update details of patches that only Microsoft controls linked off a KB article that only Microsoft posts.  It's not content that is community driven, only Microsoft can post it. Is it therefore wiki-able content?

    They build new root cert update pages each time there's a new root cert.  There's one out today which made me go look for the cert details which made be see that it got community edited.

    Tuesday, April 17, 2012 9:01 PM
  • It is up to the original poster to decide if there is potential improvement to the content by the community.

    tony soper

    Tuesday, April 17, 2012 9:04 PM
  • It is fairly easy to keep tabs on a topic by using the check mark on the edit screeen that says "Email me updates to this page".

    tony soper

    And I had checked the "Alert me" box on this thread so was immediately alerted to the fact that the discussion was about to go off topic! :)

    Now - the issue around en-us is not really about enforcement, it's more a lack of consensus. Unless someone feels otherwise, it might be better to leave the enforcement discussion out of this.

    Tuesday, April 17, 2012 9:06 PM
  • But shouldn't you as Microsoft give guidance to what Microsoft uses the wiki for?

    And (getting back on topic) shouldn't there be a guidance on format?  I still say en-us as a tag, sure, but in the title?  You sure?  How about a ruling on that?

    Tuesday, April 17, 2012 9:09 PM
  • Internally, each Microsoft group does have guidance on what to use the Wiki for. If you have feedback for a particular wiki article, written by a Microsoft employee, I encourage you to share your feedack with the auther. Their e-mail address should be listed in their profile.

    I believe that after the announcement of the first of the non-english language wikis yesterday that the council has made a ruling on "en-us" in the title. And, of course, the need to do so has changed now. I am not sure if the council has posted on that or not yet, however, the underlying issues are the same for any edit to a topic.


    tony soper

    Tuesday, April 17, 2012 9:15 PM
  • Typically I don't find email addresses in profiles which is why I end up asking here?  Where are they supposed to be?
    Tuesday, April 17, 2012 9:31 PM
  • see http://social.technet.microsoft.com/wiki/contents/articles/9352.wiki-how-to-contact-a-wiki-author-or-contributor-en-us.aspx

    Typically, but not always, it is in the "Biography" section of the user's profile. If there isn't one there, you can leave a comment on the article. Microsoft employee authors are supposed to be watching these and responding as appropriate.


    tony soper

    Tuesday, April 17, 2012 9:46 PM