Thank you all for your feedback so far, as you can see there are many perspectives and lots of things to be done.
@dupontbertrand I like the stages short, mid, long as they par with most of our development cycles. I also liked your idea of providing the LLM.txt to Blaze as you pointed out here How can Meteor position itself for the LLM age? - #11 by wreiske
Incorporating the inputs from others here, we should focus for now on short term improvements that won’t break existing setups at all:
- agents support via LLM.txt but also via various GitHub agents (How can Meteor position itself for the LLM age? - #11 by wreiske)
- get rid of es5 (as far as possible)
- review, test and merge the existing PRs (including the jQuery drop and the performance improvements)
- update the documentation to vitepress and optimize the ci for automatic page builds
- sketch out even more the current architecture and online documentation to be well prepared for future refactoring or even breaking improvements
- there are still some bugs reported in the issue list that need people who reproduce them and propose at least a potential solution idea
the big question
Who volunteers for these things?
-
We need multiple people for one PR because we need to make sure, that even if tests pass, there is no breaking change in our setups (which means missing test coverage).
-
I need someone who is willing to run their debugger hot and find the root cause of the bugs, reported
-
Someone needs to review PR code (at least 1 person, optimally 2) together with copilot
-
Of course people need to write code but for now I would opt to complete current PRs plus the agents stuff
-
I need at least one more person helping me with migration of the website, I am quite deep into vitepress but is lots of chores to be done, even with agents as we need still to manually read through and check if information is still valid