[Oxygentank] [wsf-c-dev] content on WSF/C on wso2.org

[Chatra Nakkawita]

Hi,

I suggest we keep the 'Apache' part in Rampart/C so that if we do
release it as a separate project, then we dont have to keep adding the
word 'Apache' to all Library and project conten on wso2.org. Also it is
specifically mentioned in all content that Apache Rampart/C is the
security module of Apache Axis2/C. So having 'Apache' even now doesn't
create a big problem.

Also on project page http://wso2.org/projects/rampart/c it mentions that
it is a sub-project of Axis2/C other than for it being Axis2/C's
security module. If ever it goes out as its own project then we only
have to change that line in the project page.

Thanks,
Chatra

Sanjiva Weerawarana wrote:

> We should IMO move Rampart/C into the new Rampart project. I think we
> discussed this a while back and concluded we should do it a bit later
> once Axis2/C 1.0 shipped right?
>
> Sanjiva.
>
> Samisa Abeysinghe wrote:
>
>> Chatra Nakkawita wrote:
>>
>>>
>>> I need to clarify 2 things:
>>> 1. Rampart C module, is it not called Apache Rampart/C? I know that
>>> this
>>> module is a sub-project of Apache Axis2/C and not a project of its own.
>>> But this does not qualify it to be called Apache Rampart/C. Or have we
>>> been wrong on this matter from day1? We've been using 'Apache
>>> Rampart/C'
>>> in all our documentation/articles/tutorials etc on wso2.org.
>>>   
>>
>> AFAIK, to call some thing Apache XYZ, it has to be an Apache project.
>> Apache Axis2/C is the Apache project, Rampart/C is just a module
>> within it, at least as of now.
>>
>> Samisa...
>>
>> _______________________________________________
>> Wsf-c-dev mailing list
>> Wsf-c-dev at wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/wsf-c-dev
>>
>