Re: Bug#333858: Proposed improved patch for yaird

[Sven Luther <sven.luther@wanadoo.fr>]

On Tue, Oct 18, 2005 at 01:54:25PM +0200, Jonas Smedegaard wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Tue, 18 Oct 2005 11:51:43 +0200
> Sven Luther <sven.luther@wanadoo.fr> wrote:
> 
> > On Tue, Oct 18, 2005 at 11:31:28AM +0200, Jonas Smedegaard wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > What do you think?
> > > 
> > > Well, after some thinking I actually think we would actually be
> > > better off with both core and debian dir at Alioth but separate from
> > > debian-kernel.
> > 
> > Well, you do what you want, but i believe that having at least the
> > debian part in the kernel svn repo alongside initrd-tools and
> > initramfs-tools is a good idea.
> 
> Why?
> 
> The only win that I can see is the convenience for you (singular or
> plural) to not need join another project to participate in yaird work.

Yes, all kernel tools in the same place :) Easier to make changes that affect
all three tools and such. I even incroporated kernel-package, altough Manoj
maintains it in tla.

> Compare this with the raised noise - both that of other kernel work
> irrelevant for some yaird developers, and that of yaird

This is again you speak about noise, i don't see what noise is this, nobody
force you to subscribe or follow d-k list. It is not even a alioth list.

> internals irrelevant for devoted initramfs-tools fans. Creating another
> mailinglist for yaird work means creating a project within/alongside
> the kernel project - being just as inconvenient for you to join, and
> confusing for new participants to understand.

I don't follow you, and i don't really care about mailing lists, what is
important is the repo.

> > > I find the traffic on d-k overwhelming too, and a great part of it
> > 
> > d-k kernel traffic is in no way correlated to where the archive is
> > kept. Nobody forces you to read it.
> 
> You are right - having write access to the kernel SVN arhive does not
> mandate listening on the channel related to that work. But what is
> teamwork without a team "channel" for coordinating the work?

Well, there are other ways to coordinates.

> > > (dealing with bugreports against kernels) I am unable to do anything
> > > sane about. But even if I can cope with the load I would want others
> > > participating in maintaining also the Debian packaging of yaird, and
> > > maybe they dislike the "marriage" or the kernel maintainers may
> > > start worrying about write too many with access to the kernel, as
> > > you point out also, Erik.
> > 
> > Bah, there are already 30 or so commiters, ...
> 
> Ok, so you have a very open policy on your team resources. Great.

Indeed, based on peer review, and control of commit logs.

> > > Also, I suspect the d-k team generally do not care much about
> > > yaird, so
> > 
> > No, i don't think this is right.
> 
> Ok. So should we then assume the opposite: that the majority of the 30
> (?) team members find yaird relevant to keep track on?

I guess i am in favour of yaird, with a few others, maks is in favour of
initramfs-tools with a few others, and most peopel just plain don't care :)

And as always, the one doing the work is the one which end up with the
decision :)

> One of the things that worries me is what the dispute last night
> (european time) between you and Maximilian about importance of pushing 

Bah, no major things, and not really related to initramfs over yaird.

> > > let's flip it around and invite Sven Luther (and whoever else
> > > wanting to participate) into a separate yaird project at Alioth.
> > 
> > Nope, i don't think i will be able to go into
> > yet-another-alioth-project, or sorry.
> 
> Why? I honestly do not understand.

Just too much RL work lately, and counting parted, the kernel, d-i, parted,
..., i just reached saturation of projects i can participate, nothing personal
there.

Friendly,

Sven Luther