CHRP support / Mailing lists

[Thibaut VARENE]

On Thu, 2005-01-27 at 13:51 +0100, Fabio Massimo Di Nitto wrote:
> 
> | [...] I'd like to know whether there's an incentive
> | to support CHRP platform in general (such as Pegasos2:
> | www.pegasosppc.com). I've been given such a box for development
> | purposes, so I guess I can have a look at it if there are other
> | people interested.
> |
> | Debian supports this platform as part of the ppc port, and AFAICT,
> | supporting it is just a matter of adding a new kernel flavour [...]
> |
> This is Colin call here and i think we can move this discussion
> right on ubuntu-devel.

Done, but:

I ought to mention I'm no longer subscribed to u-devel. The signal/noise
ratio has become way too low for me to follow it. (thus please CC me in
answers).

Again, I think we need more mailing-lists. Ubuntu-devel has become the
default target for almost any kind of mails, hopefully dealing with
"something related to Ubuntu" (ranging from user-support, to real
development issues), which ends up in a "topic mess". I tend to wonder
"WTH is this mailing list about?" :P

I've suggested to Mako that we need a u-private mailing-list (or call it
u-maintainers), a la debian-private, that is to say a low traffic
mailing list that every Ubuntu Maintainer (and only them) has to be
subscribed to.

A u-project m-l would certainly be helpful too, to discuss openings and
new projects in Ubuntu, such as this mail requesting more mailing-lists,
which I am sending reluctantly to u-devel, even more given the fact I'm
no longer subscribed: I suspect that it'll be moderated :P

Ports specific m-l can probably be helpful as well, and maybe a kernel
m-l if the team is going to have more interaction, as it is happening on
debian. Oh, if you do so, please, pretty please, don't do as they did:
sending bug reports to the discussion list. In my very humble opinion,
bugs and discussions have to happen on separate m-l. That is not to
avoid reading bug reports, that is to be able to filter out more
efficiently conversations and bug-fixing.

Segmenting m-l traffic is IMHO a good thing, as it helps keeping each
m-l traffic as low as it can be, and thus increases the signal/noise
ratio, making subscribers more likely to follow them closely.

One last word about "tags": tagging mails to workaround the lack of m-l
is just a no-go IMHO. I read my mail from several places, I also read it
through webmail services, there's just no way i'll teach all my clients
to filter ubuntu-devel mails according to my particular interests.
That's one out of a handful of reasons I can put against mail tags. ;P

Anyway, that was my 2 cents for the day :)

HTH,

-- 
Thibaut VARENE
The PA/Linux ESIEE Team
http://www.pateam.org/