jaekwon
commented
10 months ago Ok, if we can limit AI usage to within a section within an "awesome" repo (in the bottom of the scroll), then I see it as a good compromise. But only if Jarvis stays within those bounds, and is not made mandatory nor overly promoted. This way we are not completely stopping it, and we have bounds we can enforce and learn from.
We should consider creating a repository similar to the community-driven "awesome-gno" on GitHub.
Could be:
We include a disclaimer stating that the content is community-generated/curated and unofficial. This repository would provide a space for community discussions, initiatives, recipes, and scripts. We can be less restrictive regarding AI limitations (#39) and use the Wiki feature instead of PRs for maintaining news and summaries. It would also make moderation more manageable by distributing the responsibility. Over time, it could reference new forks, important tweets, and more.
This would make the current repo stricter overall, while also allowing for more accessibility and other topics on the new one.
I believe that it's probably too early now and we should focus on pushing the limits of the current repo and wait for more foundations (especially the README), I believe this move will be important for scaling the initiative.