Libera talk:IRC cloaks

Guidelines
The following are proposed guidelines for assigning cloaks. I've briefly explained my reasoning below each point.
 * 1) Only allowable cloaks are those of the form lykos/nick or lykos/something/nick, where nick is a nick attached to the user's account (not necessarily account name)
 * 2) * This rule is partially from freenode staff (they don't really want to hand out cloaks with 4+ parts), and partly to ensure that cloaks generally follow freenode conventions
 * 3) Only exception to rule #1 is for the official game bots (lykos, skoll), where nick can be arbitrary
 * 4) * Because they're special like that. Right now they're lykos/bot, but we may want to change that in the future
 * 5) Developers (those with push access to GitHub) can have lykos/something/nick, where something is completely arbitrary (and possibly jokey)
 * 6) * Because we can :). Basically I want to restrict jokey cloaks to a small subset of users, so that there isn't any drama towards who gets them and who doesn't. I also don't want to open the floodgates for jokey cloaks because then suddenly everyone will want one. By forcing other users to have boring cloaks, they'll ideally only request it if they actually have interest in the project.
 * 7) Contributors (those who have had at least one PR accepted into the repository, or who have contributed towards wiki documentation) can gain the cloak lykos/contributor/nick
 * 8) * A pretty low bar, but I think that's fine, it means that someone who wants a lykos cloak can contribute towards the project in order to gain one, which imo is how it should be. We should of course apply discretion as to what counts as a contribution, but imo the bar should be low. The wiki was included because not everyone has coding skills, and documentation is important too (which includes things like strategy and new player guides).
 * 9) Additionally, anyone in the above categories can gain the cloak lykos/nick instead of what is listed for that category
 * 10) * In case they don't like 3 part cloaks, such as if they're affiliated with another project too
 * 11) Non-affiliated users (users who do not fall into any of the above categories) should not receive cloaks
 * 12) * The bar for getting a contributor cloak is super low, so I don't see a need to open it up further; let people who are interested in the project get a project cloak, and those who aren't don't get one. Combined with the no-jokey-cloak guideline, this should serve as a good way to ensure that cloaks aren't just handed out like candy, since revoking a cloak if we decide to have tighter policies in the future from a ton of people is rather poor taste
 * 13) Official bots used exclusively in lykos-related channels can receive a bot cloak lykos/bot/nick, where nick is the bot operator. No other bots (including test bots) can receive bot cloaks
 * 14) * A lot of channels have bans on */bot/*, and I don't want to hand out lykos/bot/nick to non-official bots. Vgr suggested lykos/test-bot/nick or lykos/testing-bot/nick, but that would break the normal pattern of using /bot/ by like pretty much every other project out there. For access to #lykos-test for test bots, we can just do it based on account name (or better yet, fix the bot to not require being opped)

Please leave comments below, rather than inline. -- Skiz zerz  05:12, 16 October 2016 (UTC)


 * Sounds good to me. nyuszika7h (talk) 09:21, 16 October 2016 (UTC)
 * Actually, not sure about bot cloaks with only the bot operator's nick. That could imply the bot is the operator. Unaffiliated and botters cloaks have 4-part /owner/bot/botname, but we can probably just use the bot's name too, since it's not like they can call their bot lykos on freenode. nyuszika7h (talk) 13:43, 16 October 2016 (UTC)
 * Agreed on the bot cloaks, if lykos/owner/bot/botname is the standard, I'd be ok going with that. My only reservation was handing out lykos/bot/blah, because then it may seem like the bot is official when it isn't. For the 4-part bot cloak, I think requiring the bot be running lykos is acceptable. For official bots (like mwrcbot and Caroline), we can adjust rule #7 to say lykos/bot/botname (so lykos/bot/mwrcbot or lykos/bot/Caroline). -- Skiz zerz  18:14, 16 October 2016 (UTC)


 * I like these guidelines. I do think that maybe test bots that are used exclusively for testing should be able to get /bot/ cloaks. I don't think we have any non-test bots used exclusively in lykos channels right now (Caroline is used elsewhere, mwrcbot is logged in as Caroline too). But there are a few bots used only for lykos testing. Jacob1 (talk) 13:34, 16 October 2016 (UTC)


 * I'd go with the 4-parts bot cloaks too, e.g. lykos/Vgr/bot/Wolfbot for mine, and so on so forth. Contributors IMO should be more than just a few edits, but I think that we shouldn't just someone's contributorness(?) off the number of edits, but by their content and quality, but most importantly the user's willingness to keep contributing and not just walk off with an easily-earned cloak. Otherwise, that seems fine with me; can't think of anything else that could be changed, it's mostly fine for the rest. Vgr (talk) 18:30, 16 October 2016 (UTC)


 * Would it make sense to define contributors over commits instead of PRs? Some people with write access to the repo have contributed by directly pushing to it instead of sending a PR. --Xnrand (talk) 19:09, 16 October 2016 (UTC)
 * Well those people are actually developers, so they can get cloaks with #3 Jacob1 (talk) 19:10, 16 October 2016 (UTC)
 * Looking at https://github.com/orgs/lykoss/teams, write access does not seem to be congruent with devness --Xnrand (talk) 19:14, 16 October 2016 (UTC)
 * Well yeah, that page is *really* inaccurate. Some people have write access but shouldn't, and remind me again why I'm "just" a Developer? I mean, strictly speaking about the project, we're all on equal footing (also I don't mean specifically me, but the hierarchy in general is slightly weird) Vgr (talk) 19:16, 16 October 2016 (UTC)