Given... Nicolas Mailhot (nicolas.mailhot@xxxxxxxxxxx) said: > - Hierarchical or tag-oriented classification ? > - Relationship between classification and spins/repositories/tasks? > - Single view of available repositories or multiple simplified > (task-oriented? spin-oriented?) views? > - Should we build those views from a single classification or can we > afford to maintain different classification efforts per spin? > - How are we going to merge classification from different repositories? > - What is the classification workflow for Fedora? For > third-party/private repositories without pkgdb access? > - Do we need the comps mandatory/default/optional tristate or > something else? > - How do we scale from a three-package private repository to a > Fedora-everything repository? > - Do we need to manipulate packages? Package groups? Something else? > - Do we need multilevel inheritance? (group A is in group B which is > in group C, etc) > - What is the right file format. XML, something else? > - How can a classification file/set of files be audited for syntax > errors (preferably in automated way) > - i18n needs? > - CLI tool needs? > - GUI tools needs? ... > There are lots of questions. Short term just putting everything into > comps is the way to go but for mid-term to happen it should start > soonish. I'm not sure 'we need to answer 10-15 questions before we can even do the classification' implies 'right now we need to change it so everything is listed.' Bill -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
