svn commit: r49075 - head/en_US.ISO8859-1/htdocs/news/status
Dru Lavigne <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.cvs.doc |
|---|---|
| Message-ID | <[email protected]> |
Author: dru Date: Sat Jul 9 00:01:43 2016 New Revision: 49075 URL: https://svnweb.freebsd.org/changeset/doc/49075 Log: Add IRC Admin status report submitted by [email protected]. Reviewed by: wblock Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-04-2016-06.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-04-2016-06.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2016-04-2016-06.xml Fri Jul 8 21:17:30 2016 (r49074) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2016-04-2016-06.xml Sat Jul 9 00:01:43 2016 (r49075) @@ -1099,4 +1099,178 @@ <tt>drm-next-4.6</tt> branch on GitHub.</p> </body> </project> + + <project cat='team'> + <title>&os; IRC Admin Team</title> + + <contact> + <person> + <name>IRC Admin Team</name> + <email>[email protected]</email> + </person> + </contact> + + <contact> + <person> + <name> + <given>Kubilay</given> + <common>Kocak</common> + </name> + <email>[email protected]</email> + </person> + </contact> + + <contact> + <person> + <name> + <given>Eitan</given> + <common>Adler</common> + </name> + <email>[email protected]</email> + </person> + </contact> + + <links> + <url href="https://wiki.freebsd.org/IRC/">&os; IRC Wiki</url> + </links> + + <body> + <p>The &os; IRC Admin team manages the &os; Project's IRC + presence on the freenode IRC network, looking after:</p> + + <ul> + <li>Registrations and ongoing management of channels within + the official namespace (<tt>#freebsd*</tt>).</li> + + <li>Liaising with freenode staff.</li> + + <li>Allocating freebsd hostmask cloaks for users.</li> + + <li>General user support.</li> + </ul> + + <p>In order to facilitate a constructive and positive + environment for all members of the &os; community, IRC Admin + over the past 3-9 months has established and consolidated a + consistent baseline with respect to the management of its + channels on freenode. This report is a summary of what has + happened so far and things to come.</p> + + <p>These activities were completed over the last few + quarters:</p> + + <ul> + <li>Registration of &os; Group Contacts (GC) with freenode + staff. For information on what this means, see <a + href="https://freenode.net/groupreg">the group + registration page</a>.</li> + + <li>Created a &os; NickServ account to assign as primary + owner/founder of the <tt>#freebsd*</tt> namespace + channels.</li> + + <li>The primary channels are owned/founded by a generic &os; + account that is owned and managed by the &os; Project.</li> + + <li>Created the <tt>Services::IRC</tt> component in Bugzilla + for change requests and issue reports.</li> + + <li>Obtained a report of all registered freenode channels + matching the <tt>#freebsd*</tt> namespace and assessed the + list for current ownership and activity status.</li> + + <li>Assigned <tt>freebsd/</tt> user cloaks to users requesting + them. For more information, see <a + href="https://wiki.freebsd.org/IRC/Cloaks">IRC + Cloaks</a>.</li> + + <li>Obtain a report on all nicknames and accounts with + existing <tt>freebsd/*</tt> user cloaks.</li> + + <li>Liaise with freenode staff on upcoming changes to freebsd + channels.</li> + </ul> + + <p>The goals for the next few quarters are to:</p> + + <ul> + <li>Complete the transfer of founder ownership for all + <tt>#freebsd*</tt> channels. Existing channel creators, + some of whom are project members and others who are not, + will be contacted using known contact information or contact + information set in their registered NickServ account, in + order to initiate the transfer of the channel to the &os; + Project. If the contact information of the existing channel + owner cannot be obtained, or if no response is received + after a suitable period of time has elapsed, IRC Admin will + complete the ownership transfer with freenode staff.</li> + + <li>Deregister defunct and inactive <tt>#freebsd*</tt> + channels. Channels which have no visible signs of activity + based on last active time or registered owner last seen, + have been deprecated by alternative channels, or have no + other way of having ownership transferred will be + deregistered. For channels where a sunset period may be + suitable, a channel topic will be set, and optionally a + forwarding channel, informing users of the changes, + including support and contact information.</li> + + <li>Create and document baseline procedures and guidelines. + These include: Community and User Guidelines, a Code of + Conduct, Operator and Moderator Guidelines and Expectations, + Abuse Reporting and Dispute Resolution Guidelines, and + procedures for delegation of channel management.</li> + + <li>Standardize and re-create channel access lists. + Existing access lists and user permissions for all + <tt>#freebsd*</tt> channels remain in their states prior to + &os; Group Registration. Consolidation and reassignment to + the &os; Project is needed. In order to ensure a consistent + user and community experience in official &os; channels + going forward, access lists for all channels will be created + from the ground up. Users with existing access to channels + may, at the IRC Admin team's discretion, be provided with + the opportunity to re-apply for access subject to any + conditions, terms, or guidelines that may be + appropriate.</li> + + <li>Determine the methods for informing project members and + the community of future changes to IRC services, procedures, + and policies.</li> + + <li>Determine methods to designate existing channel founders + as channel managers or similar.</li> + + <li>Update the channels list on the Wiki to distinguish + official and unofficial channels.</li> + + <li>Establish consistent modes, entry messages, and topics for + all channels.</li> + </ul> + + <p>Users are invited to <tt>/join #freebsd-irc</tt> on the + freenode IRC network. The IRC Admin team welcomes ideas, + contructive criticism, and feedback on how the &os; Project + can improve the service and experience it provides to the + community.</p> + + <p>While the vast majority of the broader community interacts on + the freenode IRC network, the &os; developer presence there + needs to be significantly improved.</p> + + <p>There are many opportunities to be had by increasing the + amount and quality of interaction between &os; users and + developers, both in terms of developers keeping their finger + on the pulse of the community and in encouraging and + cultivating greater contributions to the Project over the long + term.</p> + + <p>It is critical to have a strong developer presence amongst + users and IRC Admin would like to call on all developers to + join the &os; freenode channels to help support that + presence. We are the &os; giants on whose shoulders the + future contributors stand. It is important to be there, in + force.</p> + </body> + </project> </report> _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/svn-doc-all To unsubscribe, send any mail to "[email protected]"