Moving to GH issues for Feature Requests #52

Closed
opened 2026-02-06 19:14:54 +03:00 by OVERLORD · 7 comments
Owner

Originally created by @anthonylavado on GitHub (Dec 12, 2018).

Originally assigned to: @anthonylavado on GitHub.

Right now we call out using Feathub in the readme. While the service is "free" for the time being, it's hard to tell if it's very active/will stay up.

I'd like to come up with one solid place to monitor, and right now that's here on this repo.

Ideally, I would like to do something similar to what twbs/bootstrap has set up, where there's a feature request link on their readme, that brings you this:
https://github.com/twbs/bootstrap/issues/new?template=feature.md&labels=feature

It opens the issue creator, populates it with a Feature Request template, and will apply the appropriate label.

Does this sound good?

Originally created by @anthonylavado on GitHub (Dec 12, 2018). Originally assigned to: @anthonylavado on GitHub. Right now we call out using Feathub in the readme. While the service is "free" for the time being, it's hard to tell if it's very active/will stay up. I'd like to come up with one solid place to monitor, and right now that's here on this repo. Ideally, I would like to do something similar to what twbs/bootstrap has set up, where there's a feature request link on their readme, that brings you this: https://github.com/twbs/bootstrap/issues/new?template=feature.md&labels=feature It opens the issue creator, populates it with a Feature Request template, and will apply the appropriate label. Does this sound good?
OVERLORD added the roadmap label 2026-02-06 19:14:54 +03:00
Author
Owner

@thejacer87 commented on GitHub (Dec 12, 2018):

i never liked using feathub. i guess it keeps the issue queue cleaner... but i prefer everything in one spot

@thejacer87 commented on GitHub (Dec 12, 2018): i never liked using feathub. i guess it keeps the issue queue cleaner... but i prefer everything in one spot
Author
Owner

@BnMcG commented on GitHub (Dec 12, 2018):

Would prefer to use GitHub for this, could be useful in conjunction with milestones for version releases as well.

@BnMcG commented on GitHub (Dec 12, 2018): Would prefer to use GitHub for this, could be useful in conjunction with milestones for version releases as well.
Author
Owner

@anthonylavado commented on GitHub (Dec 12, 2018):

Thanks folks, I'll put this together tonight.

@anthonylavado commented on GitHub (Dec 12, 2018): Thanks folks, I'll put this together tonight.
Author
Owner

@JustAMan commented on GitHub (Dec 12, 2018):

I'm for single tracking place, too.

@JustAMan commented on GitHub (Dec 12, 2018): I'm for single tracking place, too.
Author
Owner

@Terror-Gene commented on GitHub (Dec 13, 2018):

The main reason i prefer feathub is because it gives a clear list of what the most requested features are. makes it easy to see if its already been requested & is easy to +1. But that's just my opinion from an end user point of view.

@Terror-Gene commented on GitHub (Dec 13, 2018): The main reason i prefer feathub is because it gives a clear list of what the most requested features are. makes it easy to see if its already been requested & is easy to +1. But that's just my opinion from an end user point of view.
Author
Owner

@andrewrabert commented on GitHub (Dec 13, 2018):

+1 for GitHub issues. We're already using quite a few services and technologies - best to keep it simple for now.

@andrewrabert commented on GitHub (Dec 13, 2018): +1 for GitHub issues. We're already using quite a few services and technologies - best to keep it simple for now.
Author
Owner

@anthonylavado commented on GitHub (Jan 11, 2019):

This is done. Closing.

@anthonylavado commented on GitHub (Jan 11, 2019): This is done. Closing.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#52