Questions about BLP/N

edit

1) Does the current noticeboard work well for addressing problems brought to the board for attention?

2) If not, is this because of

(a) Difficulty intrinsic to addressing often significant content problems
(b) Problems related to the way reports are addressed at the board
(b) Both

3) If the way reports to the board are responded to is a problem, independent of the difficulty of the underlying issues, why? Is the noticeboard in the ideal format, and issues of response are primarily a problem relating to community inattention?

4) Would the system of reporting problems to BLP/N, seeking greater attention and assistance resolving these problems via the board, and coordinating this effort work better if the board had a more efficient organization?

Organizational thoughts

edit

The way the board functions right now isn't ideal. It runs the same way as incident reports do at AN/I, but with far less attention. Because AN/I has so many eyeballs, each reported problem with any merit has a good chance of getting attention from people watching the page. BLP/N doesn't have nearly as many editors patrolling it, and faces some challenges that separate it from AN/I.

Like most noticeboards, the sections are archived automatically by a bot. This gives each section a finite number of days (let's say 7) to get the attention requested by the poster. Since nearly all reports to the noticeboard concern a specific article, respondents may: comment on the noticeboard thread, edit the article, comment on the article talkpage, or all three. A report with no response on the noticeboard may be completely handled or not handled at all, and nothing identifies the difference. It happens, then, that reports of a problem article will appear on the noticeboard, scroll up to the top of the table of contents without any attention or action, and get archived off the page with no improvement.

I believe that the ideal method for reporting, discussing and resolving BLP problems to a noticeboard includes the following qualities:

  • A respondent can quickly scan the page to see outstanding reports
  • Reports are grouped by type and status (in progress, resolved, oustanding)
  • New reports building on a history of prior reports automatically include reference to that history
  • Activity towards resolving a problem can be noted automatically in the report
  • Problems don't leave the page until they have been resolved or dismissed

This type of efficient board design is already implemented on Wikipedia, on bot-assisted noticeboards like WP:AN3, AIV and SPI. Below is an example of what this sort of thing might look like applied to BLP/N, and how it might function with bot reports and etc.

SPI and BLP/N both currently make use of a bot to track and manages changes and issue alerts to an IRC channel. The BLP/N bot is currently limited to reporting edits to the page, but conceivably could be adapted to manage the tasks suggested below and also alert editors in the IRC channel to new reports, relevant changes to articles currently reported to the board, archive and maintain resolved reports, etc.

Examples

edit

Resolved

edit

Open

edit

Eyeballs only

edit