Re: Package "ownership" per team, and the use of `mr' to handle this.
>> The "community" folder is more of a concern to me.
>
> What do you mean?
It is more complex. .. just a bit.
>> Concerning reorganisation, it may be helpful to have some package flocking
>> together a bit more. For instance, my mgltools packages I have combined into
>> one big subfolder. The perl packages could go into one, too (bioperl,
>> bioperl-run, ... and dependencies like gbrowse for instance). But this is
>> nothing we need to discuss at large, I'd say, the individual (active)
>> maintainers should just be given the freedom to prepare such subfolders when
>> they see their suite of software to be represented properly that way.
>
> I believe what you're proposing would break tools like svn-buildpackage -- it
> expects some "layouts" like:
No. It just works, expecting only a checked-out debian folder.
[...]
> I believe that re-organizing the repo as {trunk,tags,branches}/package would
> let us scale a bit further -- who just wants the code can checkout trunk/*,
> anyone else can checkout *.
Ah, so I don't get all those tags. Well. Yes. But I don't suffer enough because of those, yet.
Best,
Steffen
Reply to: