On 5/13/11 11:36 AM, Ed Burns wrote:
>>>>>> On Fri, 13 May 2011 08:50:51 -0400, Andy Schwartz <andy.schwartz_at_oracle.com> said:
>>>>>>
>
> AS> Jakob -
> AS> I was just thinking the same thing! We should do this.
>
> AS> Also, regarding twitter hash tags...
>
> AS> For our last EG meeting folks were using #jsr344_experts. Could we
> AS> simplify this to #jsr344? This has two benefits:
>
> AS> 1. It's shorter.
> AS> 2. Non-EG members may feel discouraged from chiming in on
> AS> #jsr344_experts tweets/discussions. We want to encourage all community
> AS> members to participate, regardless of whether they consider themselves
> AS> to be part of the group of "_experts".
>
> AS> Andy
>
> AS> On 5/13/11 8:12 AM, Jakob Korherr wrote:
> JK> WDYT of creating such a twitter account also for our JSR-344 (--> @jsr344)?
>
> Note that technology outlives JSRs. JSF has been through three now. We
> don't want the identity to be bound to a specific JSR number.
On the flip side, each JSR does have an identity of its own. I don't
think it is especially bad to expose/express that via a twitter id.
(Actually, I think that calling attention specifically to our JSR could
be a good thing.)
> To that
> end, I have created @jsf_spec as the official twitter account of the JSF
> specification.
>
Not sure whether this topic is still open for discussion, but isn't
there some benefit to establishing a consistent naming convention across
JSRs? Almost seems like the JCP should be recommending that all JSRs
grab their @jsr<#> twitter ids and use this as a public communication
channel. This would make it easy for interested parties to locate/tune
in to JSR-related news.
In any case, whatever our twitter id, I am glad to see that we're
getting social. :-)
Andy