| 1 |
Dnia 2014-09-28, o godz. 00:13:15 |
| 2 |
Tom Wijsman <TomWij@g.o> napisał(a): |
| 3 |
|
| 4 |
> On Sat, 27 Sep 2014 17:54:48 -0400 |
| 5 |
> "Anthony G. Basile" <blueness@g.o> wrote: |
| 6 |
> |
| 7 |
> > The hardened project has two herds: hardened and hardened-kernel, the |
| 8 |
> > former for toolchain related stuff and the latter for the kernel. We |
| 9 |
> > really need to keep that distinction. So mapping herds to projects |
| 10 |
> > doesn't work. But, mapping hardened/hardened-kernel to our |
| 11 |
> > *subprojects* structure does. Perhaps that might be a more natural |
| 12 |
> > solution in general, not just for hardened. |
| 13 |
> > |
| 14 |
> > We might proceed by associating each herd to a project, and then |
| 15 |
> > letting them decide whether to absorb the herd(s) into their project |
| 16 |
> > level, or break it down to subprojects. So as another example, ppc |
| 17 |
> > and ppc64 teams are merging into one team (powerpc) with one lead |
| 18 |
> > (currently jmorgan). There also we want to keep two herds for the |
| 19 |
> > two different arches for keywording/stabilizing requests. If we just |
| 20 |
> > say "ppc and ppc64 herds belong to powerpc team", then it will be |
| 21 |
> > easy to change "herd" to "subproject" requiring nothing more than |
| 22 |
> > just a webpage put up if it doesn't already exist. |
| 23 |
> |
| 24 |
> Yes, if you do create a one-on-one mapping then it becomes possible. |
| 25 |
> The question becomes "does every herd want to become a (sub)project?". |
| 26 |
> |
| 27 |
> Ideally, they should! Theoretically, there is no problem. Practically, |
| 28 |
> for some herds it'll involve extra work setting up the project related |
| 29 |
> stuff and so on when there is no need for it. |
| 30 |
> |
| 31 |
> Example: If I were to create a MATE herd, that doesn't mean I want a |
| 32 |
> MATE project; documentation wise, the Gentoo Wiki article suffices. |
| 33 |
|
| 34 |
I don't know if you know it but setting up the project wiki page takes |
| 35 |
less time than reaching into depths of CVS and editing herds.xml. |
| 36 |
|
| 37 |
You just convinced me that we should definitely drop herds. Otherwise, |
| 38 |
we'll never going to get out of the dumb distinction what project |
| 39 |
and herd is and isn't, and when one or the other, or both should be |
| 40 |
used. |
| 41 |
|
| 42 |
-- |
| 43 |
Best regards, |
| 44 |
Michał Górny |
Archives