Trac Clean Up
@slaffik proposed the following actions to address the 654+ tickets in the Future Release milestone:
1) Go through tickets with 2nd-opinion and dev-feedback – and reply, close, or consider working on it.
2) Go through tickets that were updated years ago – and consider them to be closed by default, but read and investigate the value. If a ticket has been left for a long time in Trac, it’s either not that important, a duplicate, hard, or forgotten.
@johnjamesjacoby noted, “Proper organization, along with timely responses, I think are more important, but I agree that keeping it tidy reduces the cognitive burden of ‘holy moly there are 500 things to do.'”
Components maintainers
@slaffik and @djpaulgibbs will be preparing a post calling for BuddyPress component maintainers soon. Per previous dev chat, there’s a Google Spreadsheet @offereins prepared earlier this year. @slaffik has added a new sheet, ‘Blad 2’, listing components per trac.
Trac Tickets
BuddyPress MU (#4732) Closed as wontfix.
Add Help Pointers to Admin (#4672) Closed as wontfix.
BuddyPress 2016 Survey
The survey for Theme/Plugin Developers and Site Builders will be running through November 30, 2016. https://buddypress.org/2016/11/2016-buddypress-survey-site-builders-developers/
Slack log: https://wordpress.slack.com/archives/buddypress/p1478721656000684
