From owner-svn-doc-all@freebsd.org Sat Jul 9 00:01:45 2016 Return-Path: Delivered-To: svn-doc-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 072D1B85DE0; Sat, 9 Jul 2016 00:01:45 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D719B1EB7; Sat, 9 Jul 2016 00:01:44 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u6901i4s033425; Sat, 9 Jul 2016 00:01:44 GMT (envelope-from dru@FreeBSD.org) Received: (from dru@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u6901ijM033408; Sat, 9 Jul 2016 00:01:44 GMT (envelope-from dru@FreeBSD.org) Message-Id: <201607090001.u6901ijM033408@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: dru set sender to dru@FreeBSD.org using -f From: Dru Lavigne Date: Sat, 9 Jul 2016 00:01:44 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r49075 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jul 2016 00:01:45 -0000 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 koobs@FreeBSD.org. 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 @@ drm-next-4.6 branch on GitHub.

+ + + &os; IRC Admin Team + + + + IRC Admin Team + irc@FreeBSD.org + + + + + + + Kubilay + Kocak + + koobs@FreeBSD.org + + + + + + + Eitan + Adler + + eadler@FreeBSD.org + + + + + &os; IRC Wiki + + + +

The &os; IRC Admin team manages the &os; Project's IRC + presence on the freenode IRC network, looking after:

+ +
    +
  • Registrations and ongoing management of channels within + the official namespace (#freebsd*).
    • + +
  • Liaising with freenode staff.
    • + +
  • Allocating freebsd hostmask cloaks for users.
    • + +
  • General user support.
    • +
+ +

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.

+ +

These activities were completed over the last few + quarters:

+ +
    +
  • Registration of &os; Group Contacts (GC) with freenode + staff. For information on what this means, see the group + registration page.
    • + +
  • Created a &os; NickServ account to assign as primary + owner/founder of the #freebsd* namespace + channels.
    • + +
  • The primary channels are owned/founded by a generic &os; + account that is owned and managed by the &os; Project.
    • + +
  • Created the Services::IRC component in Bugzilla + for change requests and issue reports.
    • + +
  • Obtained a report of all registered freenode channels + matching the #freebsd* namespace and assessed the + list for current ownership and activity status.
    • + +
  • Assigned freebsd/ user cloaks to users requesting + them. For more information, see IRC + Cloaks.
    • + +
  • Obtain a report on all nicknames and accounts with + existing freebsd/* user cloaks.
    • + +
  • Liaise with freenode staff on upcoming changes to freebsd + channels.
    • +
+ +

The goals for the next few quarters are to:

+ +
    +
  • Complete the transfer of founder ownership for all + #freebsd* 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.
    • + +
  • Deregister defunct and inactive #freebsd* + 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.
    • + +
  • 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.
    • + +
  • Standardize and re-create channel access lists. + Existing access lists and user permissions for all + #freebsd* 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.
    • + +
  • Determine the methods for informing project members and + the community of future changes to IRC services, procedures, + and policies.
    • + +
  • Determine methods to designate existing channel founders + as channel managers or similar.
    • + +
  • Update the channels list on the Wiki to distinguish + official and unofficial channels.
    • + +
  • Establish consistent modes, entry messages, and topics for + all channels.
    • +
+ +

Users are invited to /join #freebsd-irc 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.

+ +

While the vast majority of the broader community interacts on + the freenode IRC network, the &os; developer presence there + needs to be significantly improved.

+ +

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.

+ +

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.

+ +