On Mon, Oct 21, 2019 at 2:23 AM Pierre-Yves Chibon <pin...@pingoured.fr>
wrote:

> On Sat, Oct 19, 2019 at 05:42:02PM -0700, Kevin Fenzi wrote:
> > On Sat, Oct 19, 2019 at 05:49:18PM +0000, Zbigniew Jędrzejewski-Szmek
> wrote:
> > > On Sat, Oct 19, 2019 at 03:52:03PM +0100, Richard W.M. Jones wrote:
> > > > On Fri, Oct 18, 2019 at 02:09:14PM -0400, Ben Cotton wrote:
> > > > > https://fedoraproject.org/wiki/Changes/OnDemandSideTags
> > > >
> > > > Nice idea.  Maybe I missed it, but I didn't see in the proposal if
> > > > there would be guidelines for naming the side tags so they don't
> > > > interfere with each other?
> > > >
> > > > For OCaml rebuilds they have been called ‘fNN-ocaml’ (NN = fedora
> > > > version), except where we needed to do further rebuilds in which case
> > > > we used ‘fNN-ocaml2’ etc.
> > >
> > > Good suggestion. I think even something like
> <fas-id>/<fNN>-<package>[-<something>]
> > > could be a way to avoid accidental conflicts.
> >
> > The already implemented koji sidetag plugin and fedpkg integration lets
> > this be free-form, but you can search / list them by owner as well.
> >
> > So, yeah, fNN-something-descriptive would be good, and if you wanted to
> > coordinate you can list the user and ask them.
>
> The format adopted for rawhide gating is:
> fXX-build-side-YYYY where both X and Y are integers.
>
> Allowing arbitrary words in the side-tag names may results in security
> issues,
> cf: https://pagure.io/fedpkg/issue/329#comment-583078


The comment was only about usernames. I still think we need descriptive
text so at least the purpose of the side tag is clear.

Thanks,
Richard
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Reply via email to