Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of imacat@mail.imacat.idv.tw
 designates 209.85.161.175 as permitted sender)
Message-ID: <4E449D25.2050809@mail.imacat.idv.tw>
Date: Fri, 12 Aug 2011 11:25:25 +0800
From: imacat <imacat@mail.imacat.idv.tw>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.1.16) Gecko/20110702 Icedove/3.0.11
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Re: Making mailing lists useful (was Re: [Proposal])
References: 
 <CAKQbXgAFTWzk9=6fFVJdLde0B1cYCZP9Gs-fVxAFK2C-QJkXzA@mail.gmail.com>
	<CAGj3215ZP4tLJg4+s3Z3rCx0+c-FCvuuXywr5TBzHEhH13u9tg@mail.gmail.com>
	<CAP-ksoiAoAY3By=oQ9jF_P8PeYJrdrit7YwsQkUTTj8Nm1uAMQ@mail.gmail.com>
	<7DE220F2-5AFE-4A01-AEEC-58CF1CA9F379@webmink.com>
	<CAHZP38DLw=ftMc=U_nyKxstQ61StV=XL9kF6ck+riUw4gX-0XA@mail.gmail.com>
	<CAA4ffp-WhXADh4vLZhiC2qj1EKzZ0LccC774kdEeVGk7LOTDEQ@mail.gmail.com>
	<003501cc5886$55214f10$ff63ed30$@acm.org>
	<B42E8700-4F27-418F-9260-512F7F7E38AB@gmail.com>
	<CAP-ksoiYS6f_LYNmyQ+us7Z8XoXFfX+_cGmRMwGi5aaL9UhsVw@mail.gmail.com>
	<CD7D9C68-7019-490D-B1ED-ED7A719C732E@webmink.com>
 <CAP-ksohRLu__fHDUO7iUS28WyoRPdZ4r+gi6C1nGm_h9TB_47w@mail.gmail.com>
In-Reply-To: 
 <CAP-ksohRLu__fHDUO7iUS28WyoRPdZ4r+gi6C1nGm_h9TB_47w@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig5968F6CBC4296600696D9B19"

--------------enig5968F6CBC4296600696D9B19
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

    So, I'm not the only one that thinks reading this list is a heavy
task. ^^;

On 2011/08/12 10:56, Rob Weir said:
> On Thu, Aug 11, 2011 at 9:48 PM, Simon Phipps <simon@webmink.com> wrote=
:
>>
>> On 12 Aug 2011, at 02:41, Rob Weir wrote:
>>
>>> On Thu, Aug 11, 2011 at 8:34 PM, Jean Weber <jeanweber@gmail.com> wro=
te:
>>>> On 12/08/2011, at 10:25, "Dennis E. Hamilton" <dennis.hamilton@acm.o=
rg> wrote:
>>>>
>>>>> +1 on putting materials like the suggested list-post subject catego=
ries on the community wiki.  I see no reason why it needs to be maintaine=
d anywhere else requiring higher ceremony.
>>>>>
>>>
>>> No one is going to find it on the wiki.  The new list subscriber,
>>> signing up on the list, is typically going to find the list from this=

>>> page:
>>>
>>> http://incubator.apache.org/openofficeorg/mailing-lists.html
>>>
>>> That is where the mailing list info is, the instructions on how to
>>> subscribe.  That is also where we point to other mailing list
>>> guidelines.  It is an ideal place to put the suggested topic tags,
>>> putting the mailing list info together in one place.
>>
>> How about adding a link from there to the wiki?
>>
>=20
> Because you're going to get negligible click through.  You might get
> some visitors to accidentally have their eyeballs glance over the list
> of topic tags if you have it there, in the page, right next to to list
> information that are seeking.  They might pick some of this up in
> passing.  But I expect that very few visitors will click through to a
> list of topic tags, unless that was the purpose of their visit.  And
> most cases it won't be.  And if it is actually the purpose of their
> visit, then having the info right there, without requiring a click, is
> even better, right?
>=20
> Let's do this in a way that makes the website most useful for the
> visitor to the website, rather than falling back to less useful
> approach that may be easier for the author.
>=20
> You can just submit a patch for the website.  This isn't rocket
> science.  No iCLA required. You don't even need markdown if you don't
> want to bother.  Just post something that looks patch like, e.g.:
>=20
> -----------------
>=20
> Subject: [PATCH] Topic tags for ooo-dev mailing list
>=20
> In first section of the mailing list webpage [1] please add the followi=
ng:
>=20
> In order to facilitate automated filtering of threads, etc., mailing
> list posters are requested to clearly identify the topic of their
> posts using one of the following tags:
>=20
> etc/
>=20
> [1] http://incubator.apache.org/openofficeorg/mailing-lists.html
>=20
>=20
> -----------------
>=20
> Any committer could then take that enhancement and add it to the
> website.    Note that by sending this as a patch you also inform the
> continuing membership of the list of the new topic tags.  If you
> merely put that info on the wiki, then it would not be noticed, unless
> of course you sent a note to the list.  But in that case, what effort
> have you really saved yourself?
>=20
>>>
>>> If topic tags are changing at so rapid a rate that updating the
>>> website for them is inconvenient, then we're probably misusing them.
>>> If they are meant to be hints to human readers, then they can be flui=
d
>>> and change frequently and allow small variations, like Twitter tags.
>>> In that case, there is no need to document them.  Subscribers learn
>>> the "folksonomy" by observation.  But if they are being used for emai=
l
>>> inbox filter rules, hard coded into subscriber mail clients, then
>>> these better be relatively fixed and we lose nothing by putting them
>>> on the website.
>>>
>>>
>>>>> - Dennis
>>>>>
>>>>
>>>> +1
>>>>
>>>> Jean
>>>>
>>>>
>>>>
>>
>>


--=20
Best regards,
imacat ^_*' <imacat@mail.imacat.idv.tw>
PGP Key http://www.imacat.idv.tw/me/pgpkey.asc

<<Woman's Voice>> News: http://www.wov.idv.tw/
Tavern IMACAT's http://www.imacat.idv.tw/
Woman in FOSS in Taiwan http://wofoss.blogspot.com/
OpenOffice.org http://www.openoffice.org/
EducOO/OOo4Kids Taiwan http://www.educoo.tw/


--------------enig5968F6CBC4296600696D9B19
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5EnSgACgkQi9gubzC5S1wGUQCbBF+warWAkMmgS5WEHbMWOzEH
OSQAoKn6nVR+018KhRZnBwj99y6WvgIn
=7k80
-----END PGP SIGNATURE-----

--------------enig5968F6CBC4296600696D9B19--