With the upmost respect for Jeremy, has anyone considered forking the project and maintaining a more public facing roadmap and feature list? With a focus on: organizing and involving others in the direction and decision making I think TW can really expand!
That fork would be "downstream" from the original, taking all of its features, and the original TW can "pull" anything Jeremy deems worthy. The downstream maintainer should be a trusted and longtime member of the community, of course.
There is much precedence for this kind of relationship in the open source community. There are already some examples in TW with NoteSelf and Maarfapad. I want a more centralized, community focused edition of TW, similar to the early relationship with Debian Linux and Ubuntu Linux, CentOS and Redhat, etc.
I'd like to see a public, current, and community driven roadmap and feature list, and a responsive set of core developers that have direct access to accept pull requests, etc. As Ive stated before, I want to see TW infrastructure be able to support a "Google Summer of Code" developer/team, or even a "Senior Project" team of software developer students at a university.
Something I'd like to see on the roadmap: plugin update notifications. As the core is always kept small and lean, plugins are a central part of the TW ecosystem, but currently we have to go to to google groups, search, find one as an attachment or a link to tiddlyspot (sidtenote: pray tiddlyspot never goes down as much excellent work is there!), hope it works, drag it over. Some day you have to remember to go back and check the source to see if theres been an update, etc.
Objections I foresee to "downstream proposal":
- You're free to do this yourself
- Yes that is true - if I could, I would. It can also be dismissive to point this out to someone making suggestions to the community.
- We're happy with TW as it is
- Ok - great. Then this post/call-to-action is not meant for you
- We dont want TW to break backwards compatibility
- This could and should be a core concern for whatever "downstream" projects exist as well, using version numbering to signal backwards compatible changes
Best,
Diego