Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of rgb.mldc@gmail.com designates
 209.85.161.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4E66165D.1040604@shanecurcuru.org>
References: 
 <CAP-ksoi8xzLsqawHRPsTRNatSisFWQjnsO30pS+5doouQfB1Mg@mail.gmail.com>
	<4E654A51.90508@laposte.net>
	<1038D59A-E3C9-4090-9B79-E5FBF54B7EF5@free.fr>
	<4E654D84.5000708@laposte.net>
	<4E66165D.1040604@shanecurcuru.org>
Date: Tue, 6 Sep 2011 16:10:38 +0200
Message-ID: 
 <CAEtvNKcSuoLWR9cQo+D8x86t+mYawgNdw9fg4nT+vmP2Q4WF2Q@mail.gmail.com>
Subject: Re: Real names (was: What is needed for Support Forums to be fully
 integrated into the Apache OpenOffice.org project)
From: RGB ES <rgb.mldc@gmail.com>
To: ooo-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2011/9/6 Shane Curcuru <asf@shanecurcuru.org>:
> There are a lot of differences between how Apache projects are managed an=
d
> how OOo services have been managed in the past. =A0This is one where the
> actual policies seem to be very similar; however the normal practice is v=
ery
> different.
>
> ----
> At Apache, anyone who signs an iCLA [1] must provide the ASF with their r=
eal
> name. =A0This is to ensure that the ASF knows specifically who is signing=
 the
> document. =A0Signing an iCLA is a required before anyone can become a vot=
ed in
> as a committer.
>
> When you sign an iCLA, you may optionally specify a "Public name", which =
is
> what Apache displays as public information associated with your Apache id
> (if/when you get one). =A0Thus by policy, Apache allows contributors to
> maintain a public pseudonym, although officially Apache does need to know
> (privately) your real name.

That's OK.

> In terms of actual practice, please note that very few committers at Apac=
he
> use a public pseudonym like this. =A0More than 98% of our committers use =
their
> real name, and most of them sign their real names in most emails.

That's maybe a cultural difference, not necessarily a need to "hide" a
"real identity". In my case, I do not feel that my real name, selected
by my parents forty two years ago represent me better that my (i.e.,
/selected by me/) usual pseudonym: I chose to be RGB when I put my
signature to a drawing more than twenty five years ago for several
reasons that identify me as an unique person. In a sense I'm more
"RGB" than I can be "Ricardo".
I understand that in order to be part of an organization you need to
provide a "legal" name, but for communication I do not think it is
important, as far as you can identify the person without doubts. When
I write my opinions, does it matter if my surname have Latin, mid
east, African, Saxon roots...? Does it matter my gender? I think the
answer for both questions is no.

> In terms of flames and spam, this generally works fine for Apache
> committers. =A0In terms of community, this allows your reputation to buil=
d
> associated to you, as your real name, and not to an alias.
>
> ----
> I think there are several subtle differences here between the typical Apa=
che
> community and what (I think) much of the OOo forum community is:
>
> - The OOo users are typically end-users, and not developers. =A0Thus I ca=
n
> imagine (but don't know; I'm just guessing) that the users more frequentl=
y
> resort to flames and ad hominem attacks.

I think you are wrong here. In almost two years since I'm admin on the
Spanish forums, I needed to suspend a user only once and that was for
a month only.
Forum users a quite calm: most of the time they ask their questions,
get an answer and then disappear.

> - OOo forum users and admins prefer forums. =A0I'd guess (but again; I do=
n't
> know) that as a whole they don't have as efficient spam traps and mail
> filters as most Apache committers do. =A0Thus I could see how it would be=
 more
> difficult to manage flames coming to your personal account there, whereas=
 in
> the majority of Apache communities it's not a significant issue (in part,
> because the community as a whole works to correct this kind of behavior).

You are oversimplifying here. I have very good and efficient spam
filters and tag system working on my email account (as a matter of
facts I use this email address for six different mailing lists without
problems), but after several decades of using almost every
communication technology available I still prefer forums. Why? I do
not think that's important (I do not want just another forum vs.
mailing list holy war). Let's say that /for me/ and for many people
(your mileage may vary) forums are better. No more, no less.

> - The OOo end-user community seems less tightly coupled with the project
> future than a typical Apache user community is. =A0Many Apache users coul=
d and
> might submit a bugzilla entry after seeking help for a while on a users@
> list. =A0It seems that most OOo end-users would not do this, they really =
only
> want the answer to their question and no more.

The typical OOo user is a very-very end user with normal to low (and
even /very/ low) computer skills. I think that's very different from
the typical user of other Apache projects: I cannot be sure but I
think that users of other Apache products have a medium to hight
computer level.

> It would be helpful to get a better understanding here, on ooo-dev@, of h=
ow
> the forums really work, and how much information actually does (or should=
)
> come back from the forum to the project developers.

Usually when a bug is discovered during forum interaction, if the user
do not report the bug by itself a volunteer interested on the issue
will report it. Afterwards the volunteer will keep an eye on the
issue.
Maybe an intermediate level were volunteers can talk directly with
developers could be useful... but I'm not so sure: on the issue
tracker it is already possible to follow a discussion.

Cheers
Ricardo