Return-Path: X-Original-To: apmail-cxf-dev-archive@www.apache.org Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D2C3C9039 for ; Sat, 25 Feb 2012 18:30:41 +0000 (UTC) Received: (qmail 27694 invoked by uid 500); 25 Feb 2012 18:30:41 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 27616 invoked by uid 500); 25 Feb 2012 18:30:40 -0000 Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list dev@cxf.apache.org Received: (qmail 27608 invoked by uid 99); 25 Feb 2012 18:30:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Feb 2012 18:30:40 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [64.95.72.244] (HELO mxout.myoutlookonline.com) (64.95.72.244) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Feb 2012 18:30:34 +0000 Received: from mxout.myoutlookonline.com (localhost [127.0.0.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id AE9FB55477A for ; Sat, 25 Feb 2012 13:30:10 -0500 (EST) X-Virus-Scanned: by SpamTitan at mail.lan Received: from S10HUB001.SH10.lan (unknown [10.110.2.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id BA1EB554935 for ; Sat, 25 Feb 2012 13:30:09 -0500 (EST) Received: from S10BE002.SH10.lan ([::1]) by S10HUB001.SH10.lan ([::1]) with mapi id 14.01.0289.001; Sat, 25 Feb 2012 13:30:10 -0500 From: Andrei Shakirin To: "dev@cxf.apache.org" Subject: RE: WS-Policy Article: https://cwiki.apache.org/confluence/display/CXF/Using+WS-Policy+in+CXF+projects Thread-Topic: WS-Policy Article: https://cwiki.apache.org/confluence/display/CXF/Using+WS-Policy+in+CXF+projects Thread-Index: Aczv5zfU0g1220UwS9GbR/BbrUJ2IACrb8sAAFQipeA= Date: Sat, 25 Feb 2012 18:30:08 +0000 Message-ID: References: <1330029490401-5509279.post@n5.nabble.com> In-Reply-To: <1330029490401-5509279.post@n5.nabble.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [94.216.196.175] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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 Conten= t: 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 ca= n be added to http://cxf.apache.org/docs/transports.html (as additional top= ic in the list to HTTP Transport, JMS Transport, Local Transport) 2) information from https://cwiki.apache.org/confluence/display/CXF/Using+W= S-Policy+in+CXF+projects can be added / merged to http://cxf.apache.org/do= cs/ws-policy.html 3) https://cwiki.apache.org/confluence/display/CXF/Scalable+CXF+application= s+using+JMS+transport is candidate to external blog, because it is not dire= ctly 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 int= o Resources and Articles afterwards. What is your opinion and the next steps? Regards, Andrei. -----Original Message----- From: Glen Mazza [mailto:glen.mazza@gmail.com]=20 Sent: 23 February 2012 21:38 To: dev@cxf.apache.org 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 w= ith 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 duplicat= e information in multiple places. If you have anecdotal information not re= ally 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 C= XF wiki, I fear we'd eventually have dozens of obsolete and duplicative art= icles 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 i= s 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).=20 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 in= termediate 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/author= ship 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 pe= rson, etc.--off to an external blog it needs to go, with a link on the CXF = resources page instead. =20 Thanks, Glen -- View this message in context: http://cxf.547215.n5.nabble.com/WS-Policy-Art= icle-https-cwiki-apache-org-confluence-display-CXF-Using-WS-Policy-in-CXF-p= rojects-tp5499465p5509279.html Sent from the cxf-dev mailing list archive at Nabble.com.