Conversation
Collaborator
|
personally speaking, i think creating user assignable issue labels like "Feature Request" gives an easier way to track this kind of thing without needing to manually update a markdown file. i could be misunderstanding the intention behind this though. i can see a use case for this in the event we want to migrate over to codeberg or some other git provider, but we could just leave the github repos open as a read only mirror. i think any purpose this document would serve is done better by the github issue tracker |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I basically ported the IDEAS.md from finix, changed the idea to be more about requesting modules than implementing functionality because that doesn't really make sense for community modules. Please give feedback on if we think there is a better way to handle this kind of idea.