incubator-esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hirsch, Richard" <richard.hir...@siemens.com>
Subject AW: ...about requirements collection for David work packages
Date Fri, 02 Jan 2009 05:51:14 GMT
I think participation in the apache wiki is just restricted to committers.

D. 


-----Urspr√ľngliche Nachricht-----
Von: Darren Hague [mailto:dhague@fortybeans.com]
Gesendet: Do 1/1/2009 20:44
An: esme-dev@incubator.apache.org
Betreff: Re: ...about requirements collection for David work packages
 
Thanks, Daniel - my Confluence ID is dhague.

Cheers,
Darren

Daniel Kulp wrote:
> On Thursday 01 January 2009 8:03:33 am Darren Hague wrote:
>   
>> Update: I just found http://cwiki.apache.org/ which seems to be a
>> collection of Confluence spaces.
>>
>> I have created a JIRA ticket
>> (https://issues.apache.org/jira/browse/INFRA-1839) to request a
>> Confluence space for ESME.
>>     
>
> Space is created.....   I need confluence ID's for everyone to add them to the 
> esme-committers group so pages can be added/edited.   Just send them along.
>
> Dan
>
>
>   
>> Cheers,
>> Darren
>>
>> Darren Hague wrote:
>>     
>>> I commented on Daniel's initial thoughts at
>>> https://issues.apache.org/jira/browse/ESME-4 and on of the things that
>>> came up was the need to work on an ESME Kernel API for plugins to use.
>>>
>>> I thought that a Wiki would be the best place to collaborate on this -
>>> does anyone know if there is an appropriate Wiki space at Apache that
>>> we can use for this kind of collaboration (a Confluence instance,
>>> perhaps)?  The Incubator wiki seems to be dominated by Proposals &
>>> Reports, so is probably not appropriate for this sort of thing.
>>>
>>> Cheers,
>>> Darren
>>>
>>> Daniel Koller wrote:
>>>       
>>>> Hi all,
>>>>
>>>> as a part to start on the listed work packages I would like to put
>>>> down some
>>>> requirements regarding the topic
>>>>
>>>> "...Internal APIs and plugin mechanism.  ESME needs a way for
>>>> external code
>>>> to be plugged into it beyond what's available via REST.  This might
>>>> include
>>>> mechanisms for authentication/authorization, hooks into message
>>>> routing and
>>>> access control, etc.  I expect that the internal API/plugin mechanism
>>>> will
>>>> lead to commercial ESME plugins that will allow a commercial ecosystem
>>>> toevolve around
>>>> ESME..."
>>>> ,...as there already some requirements going around in my head.
>>>>
>>>> Some questions:
>>>> - Is it ok to start collecting requirements now, (or anything planned
>>>> before
>>>> that), and
>>>> - Are there any standards to be kept in mind? (e.g. one set of
>>>> requirements
>>>> for all work packages?)
>>>>
>>>> Kind regards,
>>>>
>>>> Daniel
>>>>         
>
>
>
>   



Mime
View raw message