Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
meetings:2016_january [2016/01/05 16:44]
mikaela Simplify getting op attention at IRC
meetings:2016_january [2016/07/09 16:11] (current)
qguv add minutes
Line 3: Line 3:
   * Date: January 9th, 2016, time: 16:00 UTC   * Date: January 9th, 2016, time: 16:00 UTC
   * Location: ''#​archlinux-women''​ on Freenode.net   * Location: ''#​archlinux-women''​ on Freenode.net
-  * Minutes+  * [[https://​raw.githubusercontent.com/​archwomen/​meeting-notes/​master/​archlinux-women_minutes_20160109.txt|Minutes]]
   * Log   * Log
  
Line 26: Line 26:
  
 Projects Projects
-  * Great wiki cleanup+  * [[https://​archwomen.org/​wiki/​projects:​wiki_improvements:​start|The Great Wiki Cleanup]]
   * Classroom   * Classroom
     * C class - first 3 sections done, will have total of 6. Should have multiple classes on each section in various time zones. Once the rest of the syllabus is done teachers can work out a schedule.     * C class - first 3 sections done, will have total of 6. Should have multiple classes on each section in various time zones. Once the rest of the syllabus is done teachers can work out a schedule.
  
 Community Community
-  * Proposal to hold meetings on second Saturdays of the month rather than first Sundays.+  ​* Meetings 
 +    ​* Proposal to hold meetings on second Saturdays of the month rather than first Sundays. 
 +    * Schedule rename of meeting files 
 +    * Shorten [[https://​ptpb.pw/​WbT1.png|meeting commit messages]] 
 +      * http://​tbaggery.com/​2008/​04/​19/​a-note-about-git-commit-messages.html
   * Proposal to simplify requesting op-attention at IRC   * Proposal to simplify requesting op-attention at IRC
-          ​* Currently it's required to just "​!awops"​ on the channel while it could be desirable to do so in private and avoid getting negative ​atention+     * Currently it's required to just "​!awops"​ on the channel while it could be desirable to do so in private and avoid getting negative ​attention
-          * Possible solutions +     ​* Possible solutions 
-                  * Using phrik !awops & maybe even !ops should be made aliases to "​channel alert" which allows PMing and describing what is the problem (which is not possible with "​!awops"​). +        * Using phrik !awops & maybe even !ops should be made aliases to "​channel alert" which allows PMing and describing what is the problem (which is not possible with "​!awops"​). 
-                  * Externalizing !ops to #​AntiSpamMeta (antispammeta.net) or it's clone for wider audience ##​suchantispam. It allows calling ops with !ops in channel and /msg antispammeta !ops #channel with optional description,​ but would require requesting it to channel and ops being on the channel and requesting to be highlighted by alerts on #​archlinux-women.+        * Externalizing !ops to #​AntiSpamMeta (antispammeta.net) or it's clone for wider audience ##​suchantispam. It allows calling ops with !ops in channel and /msg antispammeta !ops #channel with optional description,​ but would require requesting it to channel and ops being on the channel and requesting to be highlighted by alerts on #​archlinux-women.
  
 ==== Final comments, questions, etc. ==== ==== Final comments, questions, etc. ====
  

meetings/2016_january.1452012260.txt.gz · Last modified: 2016/01/05 16:44 by mikaela