You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The structure and management of the project. Simple things breaking on updates, no way to tell what is currently going on.
Describe the solution you'd like
People(plural) helping with maintaining the source code, tests, wiki pages(you need those instead of one giant readme), issues, etc.
Splitting the plugins from the main extension. Use submodules if you want it together. It's just that I have no idea what is the extension itself and what is a plugin when looking through files. Everything is neatly mangled, and exists peacefully together. E.g: here easymotion (plugin right?) is hardcoded in the logic for vim modes
Describe alternatives you've considered
Not using the extension
Additional context
Are you doing okay? It seems like this project is growing way bigger than anticipated and there haven't been much restructuring or any pauses for any proper fixes/solutions to come along. My best additional context is the giant readme which is a huge mess no one is ever going to read it in one go(therefore split it up), let alone find exactly what they want easily. For this project to be manageable you need to restructure everything with the future in mind.
840 (841 with this) issues to be solved is way too daunting. You need to remove duplicates, make labels and have people label their own issues as questions, suggestions, feedback, bug or whatever have you. I have a hard time seeing this project living in 2 years from its current state.
The text was updated successfully, but these errors were encountered:
That'd be great; I'm always happy to accept contributions
wiki pages(you need those instead of one giant readme)
Agreed, improving user documentation and splitting it up into wiki pages is on my near-term to-do list
Splitting the plugins from the main extension
This isn't feasible at the moment
It seems like this project is growing way bigger than anticipated and there haven't been much restructuring or any pauses for any proper fixes/solutions to come along.
Reducing technical debt has been a focus recently, actually. There are a series of large refactors I'd like to do in the near future, but tackling them immediately would mean creating a lot of additional work in merge conflicts with existing PRs.
840 (841 with this) issues to be solved is way too daunting.
I have a hard time seeing this project living in 2 years from its current state.
Is your feature request related to a problem? Please describe.
The structure and management of the project. Simple things breaking on updates, no way to tell what is currently going on.
Describe the solution you'd like
People(plural) helping with maintaining the source code, tests, wiki pages(you need those instead of one giant readme), issues, etc.
Splitting the plugins from the main extension. Use submodules if you want it together. It's just that I have no idea what is the extension itself and what is a plugin when looking through files. Everything is neatly mangled, and exists peacefully together. E.g: here easymotion (plugin right?) is hardcoded in the logic for vim modes
Describe alternatives you've considered
Not using the extension
Additional context
Are you doing okay? It seems like this project is growing way bigger than anticipated and there haven't been much restructuring or any pauses for any proper fixes/solutions to come along. My best additional context is the giant readme which is a huge mess no one is ever going to read it in one go(therefore split it up), let alone find exactly what they want easily. For this project to be manageable you need to restructure everything with the future in mind.
840 (841 with this) issues to be solved is way too daunting. You need to remove duplicates, make labels and have people label their own issues as questions, suggestions, feedback, bug or whatever have you. I have a hard time seeing this project living in 2 years from its current state.
The text was updated successfully, but these errors were encountered: