[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Moving vmdebootstrap development discussions so debian-cloud?

On 2016-10-29 19:52:09, Lars Wirzenius wrote:
> This might be a bit a crazy idea, but what do people on -cloud think
> about moving vmdebootstrap development discussions from its Alioth
> list to debian-cloud@lists.debian.org?
> I have two reasons for suggesting this: better spam filtering, and
> more exposure to and feedback from vmdebootstrap users. A third, but
> admittedly weaker reason would be to have more cross-pollination
> between different image creation tooling.
> It seem to me that lists.d.o has much better spam filtering than
> Alioth does. I'd like to benefit from that.
> While I realize that not everyone on -cloud uses vmdebootstrap, and
> that vmdebootstrap is not only for virtual machines, I think -cloud
> has most of the users and as I gear up for making reasonably large
> changes, I think it would benefit development to get feedback from any
> planned changes as early as possible rather than only after the
> changes have been implemented and included in a new release of
> vmdebootstrap.

I fully agree and even that I didn't try vmdebootstrap it's on my list to do.

> Here's how I would implement this:
> * Change documentation to refer to -cloud instead of the Alioth list.
> * In the next upload, use -cloud instead of the Alioth list in the
>   Maintainer field. This would mean bug reports come to -cloud as
>   well.
> The Alioth list has been rather quiet, except for spam, so I do no
> expect a large amount of extra mail to -cloud.
> So, what do you think? Good idea? Bad idea?

I think it will put vmdebootstrap development into wider audience which we can
benefit from as well, thus I think it may be a good idea.

|_|0|_|                                                  |
|_|_|0|                  "Panta rei"                     |
|0|0|0|             -------- kuLa --------               |

gpg --keyserver pgp.mit.edu --recv-keys 0x686930DD58C338B3
3DF1  A4DF  C732  4688  38BC  F121  6869  30DD  58C3  38B3

Attachment: signature.asc
Description: PGP signature

Reply to: