app
app copied to clipboard
Festify
Time-based voting
As requested by Twitter user @javey93, it would be practical to enable/disable voting based on pre-defined time slots (or manually).
For example, we're looking to use Festify in a work environment but concerned people spend an awfully long amount of time during the day searching and up voting for songs, even if there's a thousand in the queue and they're unlikely to be played. An idea that came up in a recent meeting was allotted time slots for a party to vote, so for us, that would be 8:30-9:00 (breakfast time), 12:30-1:30 (lunch) and 5:30-6:00 (after work).
Yes definitely, it would for us in a business environment.
We pride ourselves on not being a corporate company, so music is always blasting out the speakers, but as you can imagine is always the source of criticism. Your system defers criticism as it's a democracy! However people love your system so much that productivity is often affected by those that don't recognise when to get back to work! Festify is not currently in use for this reason, but I believe this feature would allow us to bring it back into action!
Hi guys!
Has there been any progress made on this? Festify was mentioned again in our office today; "We need Festify back" and we really do! If you could give me an idea of if you think this would get worked on, that would be awesome! Then I don't get my hopes up haha.
Also, we would be interested should you ever implement a payment plan, just putting that out there! A one-off payment would be harder for us to get through finance but possibly achievable!
Hey @javey93!
We're currently in the process of rewriting Festify for a cleaner internal structure. When this is finished, we can really begin adding in new features like this (our old architecture kinda held us back from experimenting with new features).
If you want to, you can check out the https://github.com/Festify/app/tree/fit-rewrite branch. :) The app over there can do everything the current web client can do, and a little bit more.
TL; DR: No progress so far, but once the rewrite is done we can start. :) The same applies for https://github.com/Festify/app/issues/102.
Wow guys, aim high! Congrats 😄
That sounds like a long job though! How soon are you looking to have that completed by?
(Many thanks for your reply dude! You guys rock, festify.rocks)
The only thing left for feature-completeness is playback. Playback itself takes a while to implement, but the actual limiting factor here is how soon we (the Festify team) can meet up again to work on Festify.
That's awesome! Thanks for being so open too!
I hope you can all arrange to meet soon! Do you have a donation page of sorts?
Oooooo, I notice you removed the blocked label! Does that mean it's technically possible now? 😄
Technically yes, we'd just have to alter the algorithm here. If you'd like to give it a shot yourself, feel free to clone the repo and contribute 😊
I marked all issues that require changes to the DB as blocked because we initially thought we'd have an easier migration path then. We then introduced new DB fields in the new version, so this blockage doesn't really make sense anymore. :D
Technically yes, we'd just have to alter the algorithm here. If you'd like to give it a shot yourself, feel free to clone the repo and contribute 😊
@leolabs We would also need to hide the voting buttons when voting is blocked, so its going to require a few more changes than that, I think :)
Oops, I misinterpreted the issue title 😄 You're right, there would be some more modifications to do.