Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: allura-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of noreply@sourceforge.net
 designates 216.34.181.60 as permitted sender)
Content-Type: multipart/related;
 boundary="===============3975272163920951005=="
MIME-Version: 1.0
To: "[allura:tickets] " <5966@tickets.allura.p.re.sf.net>
From: "Dave Brondsema" <brondsem@users.sf.net>
Reply-To: "[allura:tickets] " <5966@tickets.allura.p.re.sf.net>
Subject: [allura:tickets] #5966 Move allura wiki to apache
Message-ID: 
 </p/allura/tickets/5966/99bb8f9c1d815a7255f5cbca5f17f0c150904c77.tickets@allura.p.sourceforge.net>
Date: Thu, 12 Sep 2013 18:46:24 +0000

--===============3975272163920951005==
Content-Type: multipart/alternative;
 boundary="===============4782342933567469734=="
MIME-Version: 1.0

--===============4782342933567469734==
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Code changes in db/5966

Haven't actually moved it yet, but I've tested the process and will do so soon.


---

** [tickets:#5966] Move allura wiki to apache**

**Status:** code-review
**Labels:** asf 
**Created:** Wed Mar 13, 2013 06:44 PM UTC by Dave Brondsema
**Last Updated:** Wed Sep 11, 2013 06:48 PM UTC
**Owner:** Dave Brondsema

After [#4646] we should move sf.net/p/allura/wiki content to allura-vm.apache.org/p/allura/wiki  We can do this with the `wiki-copy.py` script, which is currently in SF's private repo, but should be moved over to Allura proper.  It'll copy main page content, but not attachments, history or comments I don't think.  We'll have to manually deal with those.

After complete, a link tool can be set up at sf.net/p/allura/wiki to redirect to apache.  IIRC, it should handle specific pages correctly too.


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.
--===============4782342933567469734==
MIME-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<div class="markdown_content"><p>Code changes in db/5966</p>
<p>Haven't actually moved it yet, but I've tested the process and will do so soon.</p>
<hr />
<p><strong> <a class="alink" href="http://sourceforge.net/p/allura/tickets/5966/">[tickets:#5966]</a> Move allura wiki to apache</strong></p>
<p><strong>Status:</strong> code-review<br />
<strong>Labels:</strong> asf <br />
<strong>Created:</strong> Wed Mar 13, 2013 06:44 PM UTC by Dave Brondsema<br />
<strong>Last Updated:</strong> Wed Sep 11, 2013 06:48 PM UTC<br />
<strong>Owner:</strong> Dave Brondsema</p>
<p>After <a class="alink" href="http://sourceforge.net/p/allura/tickets/4646/">[#4646]</a> we should move sf.net/p/allura/wiki content to allura-vm.apache.org/p/allura/wiki  We can do this with the <code>wiki-copy.py</code> script, which is currently in SF's private repo, but should be moved over to Allura proper.  It'll copy main page content, but not attachments, history or comments I don't think.  We'll have to manually deal with those.</p>
<p>After complete, a link tool can be set up at sf.net/p/allura/wiki to redirect to apache.  IIRC, it should handle specific pages correctly too.</p>
<hr />
<p>Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to <a href="https://sourceforge.net/p/allura/tickets/">https://sourceforge.net/p/allura/tickets/</a></p>
<p>To unsubscribe from further messages, a project admin can change settings at <a href="https://sourceforge.net/p/allura/admin/tickets/options.">https://sourceforge.net/p/allura/admin/tickets/options.</a>  Or, if this is a mailing list, you can unsubscribe from the mailing list.</p></div>
--===============4782342933567469734==--

--===============3975272163920951005==--