liolocI started using repopack for my own project and I thought of something. If your project is open source and you don't want people contributing a bunch of tasks that aren't in your roadmap, it would be helpful if you could create a roadmap and then if submitted tasks aren't inline with it, they get shelved until further notice. My thought process was that if projects on repopack get bombarded by ai
liolocagent submissions, you need an automated way of triaging those submissions. Let me know what you guys think, do you think something like this would be useful?
bluehi lioloc, interesting idea
blueso first of all, even if your project is public, you'll be able to control what guests (users with no assigned role) are able to do
blueso having a public project won't mean automatically anyone can create a task
bluenext, I think it could be valuable to introduce limits for guests, too. so one task per 24h, or some other kind of limit. alternatively, limits should be based on prior work. if you have no merged tasks in a project, maybe limit one user to 5 open tasks. and that limit can rise if/when tasks can get done/merged
bluenext, I'm working on a change to the permissions model that would allow you to configure your project such that guests can both open tasks, but also work on their own tasks, a bit akin to a PR system. that allows you to decide if you want a completely "open" project (anyone can create task and submit code), or a project where people can only open tasks, but not start working on them until you assign them
bluethe new permissions will be:
blue"task.create replaces task.report exactly for creation and visibility: create tasks and see tasks you created without task.read"
bluenew permission: "task.work permits claiming an open, unassigned task only if you created it. Once assigned to you (by yourself or someone else), permit title edits, unassignment, closing with a reason, normal owner workflow including submission for review, and relevant revisions/stacking where safe"
bluenew permission: "code.submit requires code.read and permits pushing only the canonical active task branch of a task currently assigned to the pusher."
blueso if you just want people to submit tasks, but not work on them ('only issues'): you'd set the GUEST role to have only `task.create`
blueif you want people to also do 'PRs' of their own work, you'd give GUEST `task.work`, so they can self-assign, and also `code.submit`
blueand if you want yourself to decide by assigning, you'd give them in addition to task.create, only code.submit
blueotherwise, regarding triaging, you could have automated jobs running on new tasks