On Thu, May 21, 2009 at 07:34:22PM +0200, Martin Bochnig wrote:
> I asked a question.
> I was polite.
> I didn't repeatedly apologize for things that I said in the _past_?
Well, you did put the word 'community' in double quotes ("scare quotes")
and 'lol' in the subject, and your e-mail was a bit of a tirade. I
could see how someone might find that offensive. Can't you?
At any rate, while project teams are supposed to use open project lists
on opensolaris.org and/or community lists, it's not generally the case
that _all_ project team communications happen in the open. I imagine
that's often the case in other communities too (e.g., in the IETF we
often have design teams doing work in private and then publishing their
work -- the _process_ is open, but not all team communications need to
be). That would often be a result of practicality: it's easy to call a
teammate, talk to them in the hallway, IM them, ...; whereas using
e-mail for every communication increases latency.
Perhaps we should encourage i-teams to use logged IRC channels / jabber
rooms more, but even so we're bound to have phone calls and hallway
discussions that are, by their very nature, not open.
What *is* open is the development _process_. Meaning:
- design reviews (these are not formally part of the Solaris
development process nowadays, but i-teams often do these in the open)
- architectural reviews
- code reviews
C-team review is often not conducted in the open, I think, but then
c-team reviews are not terribly interesting from a community openness
p.o.v.
Unlike Linux we don't have one big kernel list with enormous traffic.
Instead we split discussions up into multiple lists, as Liane explained.
> I wondered about the purpose of this list. And about the differences
> to other lists such as caiman in terms of traffic.
on-discuss is for general issues rlating to ON, such as general build
questions.
> I said that I think many things are still being discussed on internal lists.
> That's not true?
Not for ON specifically, no.
Nowadays we only use internal lists for customer support issues where
the person posting the initial message believes that the subject is a
private matter. Often the poster will get told to use an open list and
not name the customer.
> I am not participating in *any* project?
I wouldn't know. Are you?
Nico
--
