Mass removal of groups - Revision history

Alba at 18:46, 31 August 2011

2011-08-31T18:46:11Z

@@ Line 1: / Line 1: @@
 ==Motivation==
 As of January 2011, there are about 1000 groups that received less than one post per day in the last 18 months.
@@ Line 157: / Line 151: @@
 news.groups.proposals. The "Followup-To:" header is set on this message,
 so simply replying to this post should do the right thing.</pre>
 [[Category:Group Removal]]

Alba at 18:19, 31 August 2011

2011-08-31T18:19:19Z

← Older revision		Revision as of 18:19, 31 August 2011
Line 3:		Line 3:
	*[[Content and Format of a Request for Discussion (RFD)]]		*[[Content and Format of a Request for Discussion (RFD)]]
	*[[The Great Downsizing 2011/1]]		*[[The Great Downsizing 2011/1]]
			*[[The Great Downsizing 2011/2]]

	==Motivation==		==Motivation==

Alba: /* Stage 3 */

2011-04-10T14:01:16Z

Stage 3

← Older revision		Revision as of 14:01, 10 April 2011
Line 32:		Line 32:
	*The group lists may be revised during this stage.		*The group lists may be revised during this stage.
	*This stage shall take at least 8 weeks, with announcements posted every 4 weeks.		*This stage shall take at least 8 weeks, with announcements posted every 4 weeks.
	*The minimum procedure involves three announcements: 1st RFD, 2nd RFD, LCC		*The minimum procedure involves three announcements: 1st RFD, 2nd RFD, [[LCC]]

	===Stage 4===		===Stage 4===

Alba at 13:01, 2 February 2011

2011-02-02T13:01:30Z

← Older revision		Revision as of 13:01, 2 February 2011
Line 2:		Line 2:
	*[[Final RFD / Last Call for Comments]]		*[[Final RFD / Last Call for Comments]]
	*[[Content and Format of a Request for Discussion (RFD)]]		*[[Content and Format of a Request for Discussion (RFD)]]
			*[[The Great Downsizing 2011/1]]

	==Motivation==		==Motivation==

Alba: /* Example for a pointer */

2011-02-02T12:59:27Z

Example for a pointer

← Older revision		Revision as of 12:59, 2 February 2011
Line 152:		Line 152:
	comp.unix.xenix.sco XENIX versions from the Santa Cruz Operation.		comp.unix.xenix.sco XENIX versions from the Santa Cruz Operation.

	If you have any objections, please make them heard in news.groups.proposals.		If you have any objections, please make them heard in moderated group
	~~Note that a~~ "Followup-To: ~~news.groups.proposals~~" is set on this message, so		news.groups.proposals. The "Followup-To:" header is set on this message,
	~~replies appear in that group~~.</pre>		so simply replying to this post should do the right thing.</pre>

	[[Category:Group Removal]]		[[Category:Group Removal]]

Alba: /* Example for a pointer */

2011-02-02T12:46:16Z

Example for a pointer

@@ Line 129: / Line 129: @@
 Followup-To: news.groups.proposals
 Subject: The Great Downsizing of comp.unix.*
 comp.unix.advocacy		Arguments for and against Unix and Unix versions.
@@ Line 138: / Line 150: @@
 comp.unix.sys3		System III UNIX discussions.
 comp.unix.sys5.r3		Discussing System V Release 3.
-comp.unix.xenix.sco		XENIX versions from the Santa Cruz Operation.</pre>
+comp.unix.xenix.sco		XENIX versions from the Santa Cruz Operation.
 [[Category:Group Removal]]

Sbonine: typo

2011-02-01T14:01:21Z

typo

← Older revision		Revision as of 14:01, 1 February 2011
Line 52:		Line 52:
	Automatic tools should be used as much as possible. The board will divide the list of groups to be inspected among its members; it is not required that every board member check every candidate group.		Automatic tools should be used as much as possible. The board will divide the list of groups to be inspected among its members; it is not required that every board member check every candidate group.

	The ~~extend~~ of manual checks might be proportional to the found traffic in the group. For example, the rule might be that any newsgroup that has had any posting in the past 12 months should be inspected by at least two Board members.		The extent of manual checks might be proportional to the found traffic in the group. For example, the rule might be that any newsgroup that has had any posting in the past 12 months should be inspected by at least two Board members.

	If a traffic tally is done the result does not need to be precise. Knowing the magnitude (e.g. more than 50, less then 100) is enough to verify the removal decision. Anyway, it is not clear how to count crossposts, and how to treat on-topic		If a traffic tally is done the result does not need to be precise. Knowing the magnitude (e.g. more than 50, less then 100) is enough to verify the removal decision. Anyway, it is not clear how to count crossposts, and how to treat on-topic

Alba: /* Template for a RFD */

2011-02-01T09:59:50Z

Template for a RFD

← Older revision		Revision as of 09:59, 1 February 2011
Line 92:		Line 92:
	- no group names matching *.misc		- no group names matching *.misc
	- zero on-topic, non-crossposted threads in the past 18 months		- zero on-topic, non-crossposted threads in the past 18 months
	- ~~threads where an~~ on-topic ~~question~~ received no on-topic answer		- on-topic questions that received no on-topic answer do not count
	do not count

	DISTRIBUTION:		DISTRIBUTION:

Alba at 09:36, 1 February 2011

2011-02-01T09:36:51Z

← Older revision		Revision as of 09:36, 1 February 2011
Line 1:		Line 1:
			'''See also:'''
			*[[Final RFD / Last Call for Comments]]
			*[[Content and Format of a Request for Discussion (RFD)]]

	==Motivation==		==Motivation==
	As of January 2011, there are about 1000 groups that received less than one post per day in the last 18 months.		As of January 2011, there are about 1000 groups that received less than one post per day in the last 18 months.

Alba: /* Template for a RFD */

2011-02-01T09:32:22Z

Template for a RFD

← Older revision		Revision as of 09:32, 1 February 2011
Line 72:		Line 72:
	==Template for a RFD==		==Template for a RFD==
	<pre>Newsgroups: news.announce.newgroups,news.groups.proposals,news.groups		<pre>Newsgroups: news.announce.newgroups,news.groups.proposals,news.groups
	Subject: 1st RFD: The Great Downsizing {year}-{episode}		Subject: 1st RFD: The Great Downsizing {year}/{episode}
	From: Big-8 Management Board <board@big-8.org>		From: Big-8 Management Board <board@big-8.org>
	Followup-To: news.groups.proposals		Followup-To: news.groups.proposals
Line 88:		Line 88:
	- no group names matching *.misc		- no group names matching *.misc
	- zero on-topic, non-crossposted threads in the past 18 months		- zero on-topic, non-crossposted threads in the past 18 months
	- threads where an on-topic question received no on-topic answer do not count		- threads where an on-topic question received no on-topic answer
			do not count

	DISTRIBUTION:		DISTRIBUTION:
Line 96:		Line 97:
	news.groups		news.groups

	Because of the magnitude of the group list this proposal is not ~~crossposted~~ to		Because of the magnitude of the group list this proposal is not cross-
	target groups. In the course of these proceedings the B8MB will post pointers		posted to target groups. In the course of these proceedings the B8MB
	to this announcement to appropriate groups. Readers are encouraged to take		will post pointers to this announcement to appropriate groups. Readers
	initiative and spread the message.		are encouraged to take initiative and spread the message.

	PROCEDURE:		PROCEDURE:

	~~User feedback for candidate groups should take place in news.groups.proposals.~~		The procedure shall take at least 8 weeks, with announcements posted
	~~The group lists may be revised during this stage.~~ The procedure shall take at		every 4 weeks: 1st RFD, 2nd RFD, and LCC. The group lists may be re-
	least 8 weeks, with announcements posted every 4 weeks: 1st RFD, 2nd RFD, and LCC.		vised during this stage. Discussion about candidate groups should take
	After ~~that~~ the board votes on each newsgroup individually. More details can be		place in moderated group news.groups.proposals. After publication of
	found here:		the LCC the board votes on each newsgroup individually.
			More details can be found here:

	http://www.big-8.org/wiki/Mass_removal_of_groups		http://www.big-8.org/wiki/Mass_removal_of_groups

	~~NEWSGROUPS LINE~~:		NEWSGROUP LINES:
	{insert one-line descriptions of newsgroups from checkgroups}		{insert one-line descriptions of newsgroups from checkgroups}