On Wed, 14 Sep 2016 10:28:17 +0200
Vít Ondruch <vondruch(a)redhat.com> wrote:
Why do you prefer to have the "taskotron" directory instead
"taskotron" namespace (the same as for docker files)? TBH, this will
make synchronization between RHEL and Fedora much harder, because I
can't see any internal use for "taskotron" directory.
One of the things that we're prioritizing is ease of use for packagers.
The feedback we've received thus far is that keeping everything in the
same git repo is the preferred way to store checks.
I'm of the belief that if this isn't as easy to use as falling off a
horse, we're not going to see as much adoption as we could. Moving all
the checks into a separate git repository is another barrier to entry.
Is adding a directory to dist-git that big of a deal? I'm not sure I
understand how a few more directories will make synchronization that
much more difficult - RHEL can just ignore the "taskotron" directory if
they're not using it, no?
Dne 12.9.2016 v 22:44 Tim Flink napsal(a):
> I wrote up a quick draft of the new dist-git task storage proposal
> that was discussed in Brno after Flock.
> Please review the document and either let me know (or fix in the
> wiki page) things which aren't clear or bits that I forgot.
> qa-devel mailing list