One of the things that we still need to figure out is where we're going to store tasks for dist-git style tasks. Storing them in dist-git is the initially obvious place to put things (in a tasks dir, possibly) but that isn't ideal for non-packager folks who are interested in helpging maintain those tasks.
tasks
Look into other methods for storing the task data. Some possible solutions would include git submodules and git subtrees but is certainly not limited to those solutions.
One thing that occurs to me is that we may not need "just one" solution here. I'm having a hard time figuring out a better solution to the use case of "packager wants to maintain a check when updating the specfile" than using a task subdir in each branch.
task
It may make sense to have that in addition to allowing non-packagers to create a separate task repo in a system separate to dist-git
Things have changed a bit since this ticket was written and it's no longer quite valid