Sahoo,
My comments were intended as general ones, aimed at any sort of
technical discussion, not necessarily singling out Felix. It's a large
community.
It's not about notifying developers. If I spent my day understanding
the technology mentioned in every email, I'd have no time left for
work (heck just getting through the emails is a challenge). There are
(for example) many blogs and docs on JMX, yet few developers
understand it. I understand it, but I get questions all the time
(basic ones). Yet it's been around for 5-6 years.
So when an email is sent to "the world", you must not assume that
everyone has your level of knowledge, or even has the time or
inclination to explore it in detail. It's a judgment call of course,
depending on the email.
So--first spell out an acronym or term the first time, and (ideally)
include a few URLs for reference. The value of an email rises by
virtue of such things...I can toil through our web site to find "OSGi"
or "Felix", or resort to google, etc. The point is I've spent 20
minutes trying to find something on the glassfish site before! (I'm
not saying that's the case with Felix, just a general principle).
Repetition counts--just because it was sent once a month ago has no
relevance to someone who is willing to look into it more *now*.
Advertisers know this well.
That this is true is clear from my years of experience even in WSARC/
LSARC; Sun senior engineers with decades of experience in some areas
still might need introduction to some cases.
Lloyd
On Apr 28, 2008, at 11:07 PM, Sahoo wrote:
> We try to publish important information using various channels like
> mailing list, blogs, etc. The OSGi information was published in "The
> Aquarium" in addition to being blogged by Jerome and myself. It also
> gets discussed in the V3 meeting that happens every Thursday. What
> other channel do you suggest us to use to notify developers?
>
> Thanks,
> Sahoo
>
> Lloyd L Chambers wrote:
>> OK.
>>
>> Remember that in a large developer community like this, there are
>> many areas of knowledge. I know for a fact that many developers
>> know little about JMX (for example). The same is true of any
>> number of technologies. So remember that emails can too easily
>> descend into area-of-expertise talk which leaves the majority of
>> developers out of the loop.
>>
>> Lloyd
>>
>> On Apr 28, 2008, at 8:09 PM, Sahoo wrote:
>>
>>> Lloyd,
>>>
>>> Pl. refer to an earlier email with subject line "Added support
>>> for launching GlassFish on Felix" that was sent out to dev alias
>>> almost a month back for more details.
>>>
>>> Thanks,
>>> Sahoo
>>>
>>> Lloyd L Chambers wrote:
>>>> Sahoo,
>>>>
>>>> Maybe I'm the only ignorant developer in the entire community,
>>>> but I don't know what Felix or "Felix mode" is.
>>>>
>>>> Lloyd
>>>>
>>>> On Apr 26, 2008, at 6:31 AM, Sahoo wrote:
>>>>
>>>>> Because of changes made by some developers in last couple of
>>>>> weeks, v3 build off trunk was not running on Felix. The tp2
>>>>> branch was OK most of the time. The failure on trunk went
>>>>> unnoticed for a long time because SQE had switched off Felix
>>>>> mode for QL. They have now changed QL to run both on HK2 as well
>>>>> as Felix mode. I have just now fixed [1] the code in trunk, so
>>>>> server can run on Felix mode again. *Please do not break Felix
>>>>> mode*. Run *latest* QL before checking in. It is mandatory that
>>>>> any change you make is compatible on both Felix as well as HK2
>>>>> mode. You are therefore encouraged to run dev tests on both
>>>>> modes. The instructions to run on Felix mode could not be
>>>>> simpler. It is given below:
>>>>>
>>>>> Option 1: Using env var:
>>>>> export GlassFish_Platform=Felix
>>>>> asadmin start-domain or java -jar glassfish-$version.jar
>>>>>
>>>>> Option 2: Using system property:
>>>>> java -DGlassFish_Platform=Felix -jar glassfish-$version.jar
>>>>>
>>>>> You can start in one mode, stop and restart in another.
>>>>>
>>>>> Thanks for your cooperation,
>>>>> Sahoo
>>>>>
>>>>> [1] http://fisheye4.cenqua.com/changelog/glassfish-svn/?cs=20614
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>
>>>>
>>>> ---
>>>> Lloyd L Chambers
>>>> lloyd.chambers_at_sun.com
>>>> Sun Microsystems, Inc
>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>> ---
>> Lloyd L Chambers
>> lloyd.chambers_at_sun.com
>> Sun Microsystems, Inc
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
---
Lloyd L Chambers
lloyd.chambers_at_sun.com
Sun Microsystems, Inc