Skip to main content
Ask Ubuntu

Return to Answer

prettified :)
Source Link
Nitin Venkatesh
Nitin Venkatesh
  • 22.5k
  • 14
  • 8
  1. Clear definitions of abandoned questionsClear definitions of abandoned questions.

    • Older than __ months , OP not seen in __ months and or not responded to requests for additional information after 3 days (3 days is the expiration you set on allocated questions).

    • Not a bug report, no clear answer to a problem, inactivity.

Older then __ months , OP not seen in __ months and or not responded to requests for additional information after 3 days (3 days is the expiration you set on allocated questions).

Not a bug report, no clear answer to a problem, inactivity.

  1. Clear guidance for triage of bug reports. Seems there are 3 types

    Clear guidance for triage of bug reports. Seems there are 3 types

    • Open source drivers -> perhaps most should be triaged to Lanuchpad

    • Open source drivers that should be triaged up stream -> Examples would be kernel and gnome/kde

    • Closed source drivers -> Should be triaged to ATI/Nvidia/Wireless etc

Open source drivers -> perhaps most should be triaged to Lanuchpad

Open source drivers that should be triaged up stream -> Examples would be kernel and gnome/kde

Closed source drivers -> Should be triaged to ATI/Nvidia/Wireless etc

Bug reports should be triaged and closed if they are inactive, but IMO leave them open if it seems to affect a sufficient # of people to stimulate a productive discussion on askubuntu.com.

  1. Encourage answers (either new or upvoted) >> closureEncourage answers (either new or upvoted) >> closure

  2. Ask for community support for closure.Ask for community support for closure. This is the team work part, but it seems as if closure requests are inactive.

  1. Define how active (or inactive) the moderators should be with closure. My suggestion is for clear guidelines for how many flags / posts on http://chat.stackexchange.com/rooms/206/ubuntu-regulators are appropriate per user per day (otherwise the moderators are going to be swamped with closure requests and the community effort is circumvented).Define how active (or inactive) the moderators should be with closure.

My suggestion is for clear guidelines for how many flags / posts on Ubuntu Regulators chatroom are appropriate per user per day (otherwise the moderators are going to be swamped with closure requests and the community effort is circumvented).

My suggestion would be to limit users to no more then 5 flags / posts on the http://chat.stackexchange.com/rooms/206/ubuntu-regulatorsUbuntu Regulators chatroom per day.

Sort of depends on if your preference is to make a concerted effort at closure, and if so you should increase the flags / close votes users have per day and encourage posts on http://chat.stackexchange.com/rooms/206/ubuntu-regulatorsUbuntu Regulators chatroom or answers, in which case you should encourage answers / bounties and limit close requests by moderators.

  1. Encourage setting bounties for "good questions"Encourage setting bounties for good questions. Perhaps 1 point for offering a bounty for good questions.
  1. Clear definitions of abandoned questions.

Older then __ months , OP not seen in __ months and or not responded to requests for additional information after 3 days (3 days is the expiration you set on allocated questions).

Not a bug report, no clear answer to a problem, inactivity.

  1. Clear guidance for triage of bug reports. Seems there are 3 types

Open source drivers -> perhaps most should be triaged to Lanuchpad

Open source drivers that should be triaged up stream -> Examples would be kernel and gnome/kde

Closed source drivers -> Should be triaged to ATI/Nvidia/Wireless etc

Bug reports should be triaged and closed if they are inactive, but IMO leave them open if it seems to affect a sufficient # of people to stimulate a productive discussion on askubuntu.com.

  1. Encourage answers (either new or upvoted) >> closure

  2. Ask for community support for closure. This is the team work part, but it seems as if closure requests are inactive.

  1. Define how active (or inactive) the moderators should be with closure. My suggestion is for clear guidelines for how many flags / posts on http://chat.stackexchange.com/rooms/206/ubuntu-regulators are appropriate per user per day (otherwise the moderators are going to be swamped with closure requests and the community effort is circumvented).

My suggestion would be to limit users to no more then 5 flags / posts on http://chat.stackexchange.com/rooms/206/ubuntu-regulators per day.

Sort of depends on if your preference is to make a concerted effort at closure, and if so you should increase the flags / close votes users have per day and encourage posts on http://chat.stackexchange.com/rooms/206/ubuntu-regulators or answers, in which case you should encourage answers / bounties and limit close requests by moderators.

  1. Encourage setting bounties for "good questions". Perhaps 1 point for offering a bounty for good questions.
  1. Clear definitions of abandoned questions.

    • Older than __ months , OP not seen in __ months and or not responded to requests for additional information after 3 days (3 days is the expiration you set on allocated questions).

    • Not a bug report, no clear answer to a problem, inactivity.

  1. Clear guidance for triage of bug reports. Seems there are 3 types

    • Open source drivers -> perhaps most should be triaged to Lanuchpad

    • Open source drivers that should be triaged up stream -> Examples would be kernel and gnome/kde

    • Closed source drivers -> Should be triaged to ATI/Nvidia/Wireless etc

Bug reports should be triaged and closed if they are inactive, but IMO leave them open if it seems to affect a sufficient # of people to stimulate a productive discussion on askubuntu.com.

  1. Encourage answers (either new or upvoted) >> closure

  2. Ask for community support for closure. This is the team work part, but it seems as if closure requests are inactive.

  1. Define how active (or inactive) the moderators should be with closure.

My suggestion is for clear guidelines for how many flags / posts on Ubuntu Regulators chatroom are appropriate per user per day (otherwise the moderators are going to be swamped with closure requests and the community effort is circumvented).

My suggestion would be to limit users to no more then 5 flags / posts on the Ubuntu Regulators chatroom per day.

Sort of depends on if your preference is to make a concerted effort at closure, and if so you should increase the flags / close votes users have per day and encourage posts on Ubuntu Regulators chatroom or answers, in which case you should encourage answers / bounties and limit close requests by moderators.

  1. Encourage setting bounties for good questions. Perhaps 1 point for offering a bounty for good questions.
Source Link
Panther
Panther
  • 103.2k
  • 17
  • 17

Observations / feedback on http://cleanup.thepcspy.com/info/ after spending some time with cleanup.

Team work and answers to questions is to be encouraged !!!

  1. Clear definitions of abandoned questions.

Older then __ months , OP not seen in __ months and or not responded to requests for additional information after 3 days (3 days is the expiration you set on allocated questions).

Not a bug report, no clear answer to a problem, inactivity.

I think this needs to be defined as tight as possible for the cleanup process, guidelines can be relaxed after the cleanup.

  1. Clear guidance for triage of bug reports. Seems there are 3 types

Open source drivers -> perhaps most should be triaged to Lanuchpad

Open source drivers that should be triaged up stream -> Examples would be kernel and gnome/kde

Closed source drivers -> Should be triaged to ATI/Nvidia/Wireless etc

Bug reports should be triaged and closed if they are inactive, but IMO leave them open if it seems to affect a sufficient # of people to stimulate a productive discussion on askubuntu.com.

IMO bug reports should be encouraged and, Ideally, experienced users should mentor new users (new meaning new to LP or new to bug reports).

Perhaps award a point for Question -> new bug report ?

  1. Encourage answers (either new or upvoted) >> closure

  2. Ask for community support for closure. This is the team work part, but it seems as if closure requests are inactive.

I think closure should be primarily a community decision.

  1. Define how active (or inactive) the moderators should be with closure. My suggestion is for clear guidelines for how many flags / posts on http://chat.stackexchange.com/rooms/206/ubuntu-regulators are appropriate per user per day (otherwise the moderators are going to be swamped with closure requests and the community effort is circumvented).

My suggestion would be to limit users to no more then 5 flags / posts on http://chat.stackexchange.com/rooms/206/ubuntu-regulators per day.

Perhaps ask the moderators to limit their activity to 5 closures / day.

Sort of depends on if your preference is to make a concerted effort at closure, and if so you should increase the flags / close votes users have per day and encourage posts on http://chat.stackexchange.com/rooms/206/ubuntu-regulators or answers, in which case you should encourage answers / bounties and limit close requests by moderators.

  1. Encourage setting bounties for "good questions". Perhaps 1 point for offering a bounty for good questions.