Way forward with Petitions Dashboard.

bahiirwa commented 3 years ago

Follow the archiving of the petitions subdomain and migration of petitions to forums, how do we navigate the APIs providing the data to the Petitions Dashboard.

Screenshot 2021-04-25 at 20 12 17

striebwj commented 3 years ago

We can leverage the Discourse API for this now instead: https://forums.classicpress.net/c/governance/petitions/77/l/top.json

bahiirwa commented 3 years ago

Thanks @striebwj

Will this structure change if there is a module/plugin of sort that enhances the upvote system?

I see a need to do some array looping involved to get this to work with the whole dashboard widget.

striebwj commented 3 years ago

The structure doesn't change much, but we have more sort options. We can pass ?order=votes to sort the topics by most upvoted: https://community.monzo.com/c/customersupport/bugreports/38.json?order=votes

Edit: it adds a vote_count column to the base json that is returned by Discourse

nylen commented 3 years ago

Here are the petition titles I get when using this order at https://forums.classicpress.net/c/governance/petitions/77.json?order=votes :

Update TinyMCE from v4 to v5
Finish the Custom Fields API
Manage comments for posts, pages, and CPTS in one place
Remove the auto-complete of the search string on the plugins page
Add Option To Turn Off wpautop
Bring Comments into the Posts menu
Allow editor role to edit privacy policy
Add capability to allow editor role edit menus
REST-API authentication option
Show notice if plugin update path does not exist any more
Option for comment functionality in media
Change basic settings of comment options
Add dismiss 'for a week' to core update notice
Add REST API key for security
Option to disable (gr)avatar in adminbar
Host Header Notification Email
Sell 'featured' plugin slots to sponsors
Auto delete wp-config-sample.php after install

This is mostly a list of recent petitions, since the ones that have upvotes on the forums are the ones that were created recently.

Here is what I get from the current API endpoint sorted by votes:

Remove Emojis (GDPR friendly)
Minimum PHP version should be 7.x
Disable (gr)avatar by default.
Improved Media Library
Remove XML-RPC specification
Hash passwords with bcrypt instead of md5
At installation, leave a choice between adding default content or not
Finish the Custom Fields API
Cleaning up the <head>
REST-API authentication option

This isn't perfect either but it is still closer to our current plans, and I think more reflective of what our community actually wants (or rather, what the initial bunch of potential users gathered up by Scott said they wanted).

Maybe we should be looking at making more of a "Roadmap" widget that shows what we've done, what we're working on, and what might be coming up after that.

bahiirwa commented 3 years ago

roadmap widget

That would a more worthwhile idea. It can have a link to the petitions.

nylen commented 3 years ago

Petitions on the forums are getting more activity now, so this may be worth revisiting.

ClassyBot commented 3 years ago

This issue has been mentioned on ClassicPress Forums. There might be relevant details there:

https://forums.classicpress.net/t/update-petitions-widget-in-dashboard/3560/5

striebwj commented 3 years ago

Only thing is I don't know how we would show what is planned?

I guess we could loop over the tags:

"tags": [
    "planned",
    "pull-request"
],

ClassyBot commented 3 years ago

This issue has been mentioned on ClassicPress Forums. There might be relevant details there:

https://forums.classicpress.net/t/petitions-widget-on-dashboard/3499/5

ClassyBot commented 3 years ago

This issue has been mentioned on ClassicPress Forums. There might be relevant details there:

https://forums.classicpress.net/t/update-petitions-widget-in-dashboard/3560/6

ClassicPress / ClassicPress-v1

Way forward with Petitions Dashboard. #79