User:Ilbelkyr/lykos project stuff

(There's probably a better place for this page but it's where I'm writing up the draft for now. Comments welcome and, in fact, encouraged.)

After some discussion in ##werewolf-dev and some asking around, it seems a good number of lykos developers agree on separating the actual bot project from the ##werewolf channel more explicitly. This is a place for us to collect thoughts on that.

We'd move around some channels on freenode:

(Current people to poke for access: shark/jacob1 for ##werewolf-*, shark for #lykos; with group registration we could also poke staff about #lykos(-*))

Currently, all ##werewolf ops have push access to the GitHub repository, even those who are not involved with development; do we want to adjust that? (I'd say yes —Ilbelkyr (talk) 02:55, 5 April 2016 (UTC))
 * Yes, shun the non believers devs -- Skiz zerz  22:55, 6 April 2016 (UTC)


 * Yes, I say to remove the ops' push access (as well as the GitHub group membership). Vgr (talk) 23:28, 6 April 2016 (UTC)

Should all the developers with access be equal? This works well enough with the smallish group of people we have right now, but it might not scale if we end up with an influx of new developers. Not sure we need to worry about that just now, though.
 * I'd say yes for now, no reason not to that I can think of. -- Skiz zerz  22:55, 6 April 2016 (UTC)


 * Yes, there's no reason to make any sort of distinction for now. We can see to that later if needed. Vgr (talk) 23:28, 6 April 2016 (UTC)

The main developers probably should have channel access to #lykos; do we want to grandfather in the existing ##werewolf ops? (I'm not fundamentally opposed to having non-dev people with access but I'm not sure we actually need them. —Ilbelkyr (talk) 02:55, 5 April 2016 (UTC))


 * I wouldn't give any flags to the current ##werewolf ops in #lykos, I'd like to have the two completely separate as effectively "the bot" and "the instance". Vgr (talk) 23:28, 6 April 2016 (UTC)

Current channel access (for -dev), might need some cleanup for moving to #lykos:
 * founders: shark, jacob1
 * lots of flags: nyuszika7h
 * op flags +fs: ##werewolf ops
 * op flags +V: main lykos devs
 * some bots

For freenode group registration we'd need to decide on a group contact (or multiple, but afaik there still has to be one primary GC) as well. If we go by the list of voiced people in -dev, our options are


 * nyuszika7h
 * mostly active developer
 * was involved with the creation of ##werewolf and lykos
 * shark
 * mostly inactive developer
 * was involved with the creation of ##werewolf and lykos
 * already has +F
 * jacob1
 * active developer
 * already has +F
 * woffle (Skizzerz)
 * very active developer
 * Vgr (Vgr255)
 * very active developer
 * ilbelkyr (bcode)
 * lazy developer

We could vote but if we can reach consensus without needing to resort to voting that'd probably be even better.


 * I'm fine with anyone on that list except shark. Primary GC needs to be active, responsive, and actually involved with development. I think we should have at least 2 GCs, one on each side of the globe, so that anything that needs GC input can happen more rapidly. -- Skiz zerz  22:55, 6 April 2016 (UTC)


 * I'd say nyuszika7h as main GC and probably jacob1 as second. I'm interested but cannot propose nor vote myself. Vgr (talk) 23:28, 6 April 2016 (UTC)


 * For flags, let's please not have shark get any flags in #lykos. I'd give +FR to the GCs (maybe only main one if we're paranoid like that idk, and +SR to the second one in that case?), and +fsertoivV for all devs (including GCs, of course). Vgr (talk) 23:28, 6 April 2016 (UTC)