Fider.io (where our petitions are currently hosted) is shutting down at the end of the year. We are planning a migration of those petitions to a new petitions category here on the forums. I will be using this thread as a planning doc/to do list.
[x] Export existing data
[x] Set up petitions category
including new labels (Difficulty: Easy, Moderate, Hard, Request: Add, Modify, Remove feature, Planned, Completed, Declined, anything else?)
[x] Transfer votes? If so, how? Matching emails isn’t 100% accurate. If not, are we restarting all votes at 0 but leaving the top voted petitions as planned?
Only downside to this is doubling up on votes, not sure if we necessarily care, also not sure if the plugin supports that but I can check.
I think this is likely the easiest route, but again I agree with above about it being a shame to lose.
Other note, we can limit the number of active votes per users, again not sure if it is something we want/care about but is interesting:
The number of active votes is configurable and defaults to 10.
If the topic is closed or archived, the votes are released to the users and can be applied to other topics but the vote count on the topic remains.
If a topic is re-opened or unarchived, the votes are reclaimed and applied back to the users active vote count.
If a topic reclaims the votes of a user and they go over their limit, they simply need to wait until topics are closed or archived to allow them to vote again.
I don’t think we will, but I brought it up because it is interesting. I know some petition/voting platforms limit the number of votes so only the “most” cared about petitions actually get voted on, and then as features get added those votes get redistributed to the 2nd set of “most” cared about.
As mentioned on Slack, we have been wanting to do this for a while. This just forces our hands a bit earlier than I had planned.
Before creating a new thread please be sure to check for similar petitions and to rather vote for those instead
If there are no other similar petitions are found, please provide a general summary of the petition in the Title above.
Context
What are you trying to accomplish? Why would it be useful in ClassicPress?
Possible implementation
Not obligatory, but suggest a way to implement your petition.
Will you be able to help with the implementation?
Not obligatory, but are you willing to help implement this petition?
Petitions with help already “signed up” have a much higher chance of being planned and worked on.
Your now withdrawn comment does have some merits.
Decide where we want to be, and be the best at that, and leave chasing passing trends to twitter and facebook and the elephant/dinosaur (choose your eumhamism )others.
For the interim, I don’t think Fider has given us enough time to figure out exactly what we want to do with the petitions, so I think migrating them to the forums for the time being is the best way to ensure we don’t lose any data.
I think the approach I am going to take is leveraging @discobot to post the petitions in the following format:
[Petition Description]
Posted by [Author Name]
It had [# of votes] votes
Comments:
[Comment] ~ posted by [Comment Author Name]
[Comment] ~ posted by [Comment Author Name]
Note: the category is currently “muted” so it doesn’t flood the Latest section. Also, the voting plugin hasn’t been installed yet, we will do that once we confirm that is indeed the route we want to take.
Yes, great job with this. I like that we have the old vote count available independently of how we set up the voting plugin on the forums. That means we could consider approaches like leaving the “new” vote count at zero, which solves the problem of how to match up previous votes with forum users.
Honestly we could even leave that plugin out and just use likes to rank the petitions.
Another piece to this project is our API endpoint that retrieves petition data for ClassicPress sites. I’ve updated it to just return static data for now, instead of calling out to the Fider API which will go away soon:
Just to clarify, instead of self-hosting Fider, we’ve been planning to migrate the petitions to the forums for a while. This allows us to consolidate our platforms a bit more - one less login/account for people to have to worry about. Another benefit is that we can move threads into/out of the petitions category as needed if people make suggestions for improvement in other places or if the petition threads spawn other discussions.
I think it probably makes sense to take that approach for now, which also means no downtime is required to installed the plugin
What data from the json object do we require? With Discourse we can poll a category and return it in json. I believe we can do the “most wanted”, “recent”, and maybe “trending”.
This is going to need a bit more thought/work, because now we have two vote counts (from the old system contained in the post text, and from Discourse which is mostly zero). At the moment it is working fine so we can leave it as-is until that is solved satisfactorily, the only issue is that new petitions posted on the forums won’t be registered there.
Thanks for highlighting this since it is a major thing in the Dashboard widgets for CP. We need to update the links as well from the dashboard to the various posts on forum for people to vote on those.
