Skip to main content

Timeline for What to do about tag [oneget]?

Current License: CC BY-SA 3.0

8 events
when toggle format what by license comment
Mar 20, 2017 at 10:18 history edited CommunityBot
replaced http://superuser.com/ with https://superuser.com/
Aug 17, 2015 at 19:00 history tweeted twitter.com/#!/super_user/status/633352685199204352
Aug 15, 2015 at 20:52 answer added randomMod timeline score: 9
Aug 15, 2015 at 20:25 comment added MC10 I was thinking a new tag would just be too confusing as well, there is already the one with a similar name that you mentioned. I wonder why they didn't stick with the name, it sounds better to me.
Aug 15, 2015 at 20:13 comment added fixer1234 At least a couple of the questions predate the name change. I'm wondering if we should create a new tag and synonomize [oneget] with it. If going forward, nobody will be trying to use the name oneget, that probably isn't necessary. In terms of a new tag, there is already a [package-management] tag, so we're headed for confusion and tag misuse. A new tag should be named something like [windows10-packagemanagement]. For whatever good it will do, both tags need a wiki summary that clarifies proper tag selection.
Aug 15, 2015 at 19:53 comment added MC10 Is there any standard for handling tags for products that are renamed?
Aug 15, 2015 at 19:38 comment added random Mod Anything else? What was the first thing done to the tag?
Aug 15, 2015 at 18:59 history asked MC10 CC BY-SA 3.0