Hi Glen,

I have got it.
Sure, my intention was to add published information directly to CXF User's 
Guide or link it to User's Guide Table of Content.

Could you give me some advises what is the right way to do it:
a) not sure how to update CXF User's Guide and User's Guide Table of Content: 
should I provide a JIRA patch or is it editable via apache cwiki?
b) is it necessary to have kind of review before update it?

Actually, I see it so:
1) https://cwiki.apache.org/confluence/display/CXF/Custom+CXF+Transport  can be 
added to http://cxf.apache.org/docs/transports.html (as additional topic in the 
list to HTTP Transport, JMS Transport, Local Transport)
2) information from 
https://cwiki.apache.org/confluence/display/CXF/Using+WS-Policy+in+CXF+projects 
 can be added / merged to http://cxf.apache.org/docs/ws-policy.html
3) 
https://cwiki.apache.org/confluence/display/CXF/Scalable+CXF+applications+using+JMS+transport
 is candidate to external blog, because it is not directly about CXF features, 
but more regarding Spring JMS configuration in CXF projects. I will move it 
from Apache wiki to external blog and link it into Resources and Articles 
afterwards.

What is your opinion and the next steps?

Regards,
Andrei.

-----Original Message-----
From: Glen Mazza [mailto:[email protected]] 
Sent: 23 February 2012 21:38
To: [email protected]
Subject: Re: WS-Policy Article: 
https://cwiki.apache.org/confluence/display/CXF/Using+WS-Policy+in+CXF+projects

Andrei, the CXF Wiki is not a good place for "articles" -- that information you 
wish to impart to the community should either go to an external blog with a 
reference on our Resources page or incorporated within the CXF User's Guide, 
where everyone can update it and we don't have to maintain duplicate 
information in multiple places.  If you have anecdotal information not really 
fitting for a User's Guide, external blog entries are best.

If everyone placed his own articles separate from the User's Guide on the CXF 
wiki, I fear we'd eventually have dozens of obsolete and duplicative articles 
as one-time authors write something and forget about it afterwards as they move 
on to other things, and others become reluctant to update what is identified as 
somebody else's work.

I pulled out your links from the External Resources page 
(http://cxf.547215.n5.nabble.com/CONF-Apache-CXF-gt-Resources-and-Articles-td5499502.html).
 
Non-external CXF wiki pages should instead be linked to within the CXF User's 
Guide directly or listed in the User's Guide Table of Contents (as an 
intermediate step before directly incorporating the article into the guide.) 
Also, note nothing on the Wiki is owned by anybody but the whole team, and 
anyone can update any page.  The moment you claim or imply ownership/authorship 
of a page as you had on the Resource page--i.e., this page is my work, only I 
should be updating it, or if the article is written in the first person, 
etc.--off to an external blog it needs to go, with a link on the CXF resources 
page instead.  

Thanks,
Glen


--
View this message in context: 
http://cxf.547215.n5.nabble.com/WS-Policy-Article-https-cwiki-apache-org-confluence-display-CXF-Using-WS-Policy-in-CXF-projects-tp5499465p5509279.html
Sent from the cxf-dev mailing list archive at Nabble.com.

Reply via email to