Resources and development for BLPs
Resources and development for BLPs
This is about the second point here. I think it's an important recommendation to make and as noted, we need to be more specific about it. Software development and technical enhancements whose end-goal is to improve the quality of our content, anything that can improve monitoring, allow easier and more efficient reviewing, collaboration, and improve our protection systems for more flexibility in its use, etc, can help on the BLP issue. I think for example, that watchlists and recent changes are completely outdated (not efficient and usable enough) as monitoring/reviewing tools for projects with more than a few hundreds of pages. Various ways have been proposed to improve the situation, several projects have made requests for specific implementation, but little has been achieved. There are plenty of enhancement requests in those lines at bugzilla - but they're not implemented or even considered because we don't have enough developers. In general, I think the foundation needs to invest much more (in resources and staff) in development and response to enhancement requests, and those which could help on the BLP issue in particular
I agree. As a recent example, I know that recently there was (kinda) new type of log that sometimes gets BLP violations in it and did not have a way to be suppressed items in the log to remove problem LP content. The developers are aware of the concern but it had not moved to the top of anyone's to do list yet. When new items of concern are identified it would be great if there was adequate staff to get them fixed with in a day or two at the longest. I know that they are working on loads of important stuff and need to prioritize there work, but it would be great if we did not have these items stall after they are brought to the attention of staff.