incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Weir <apa...@robweir.com>
Subject Re: Making mailing lists useful (was Re: [Proposal])
Date Fri, 12 Aug 2011 02:56:58 GMT
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> wrote:
>>> On 12/08/2011, at 10:25, "Dennis E. Hamilton" <dennis.hamilton@acm.org>
wrote:
>>>
>>>> +1 on putting materials like the suggested list-post subject categories on
the community wiki.  I see no reason why it needs to be maintained 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?
>

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?

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.

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.:

-----------------

Subject: [PATCH] Topic tags for ooo-dev mailing list

In first section of the mailing list webpage [1] please add the following:

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:

etc/

[1] http://incubator.apache.org/openofficeorg/mailing-lists.html


-----------------

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?

>>
>> 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 fluid
>> 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 email
>> 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
>>>
>>>
>>>
>
>

Mime
View raw message