Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 230B610255 for ; Fri, 4 Oct 2013 14:43:28 +0000 (UTC) Received: (qmail 46291 invoked by uid 500); 4 Oct 2013 14:43:28 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 46249 invoked by uid 500); 4 Oct 2013 14:43:27 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 46241 invoked by uid 99); 4 Oct 2013 14:43:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Oct 2013 14:43:27 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Oct 2013 14:43:21 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=hMqjDAWy//dwVbk2taVjYLO6s7hfVOId1sMcSo/JvdU=; b=OSpiLigqI6UWkH4RTD1jWm9rrBW1TsHdGUQTIROcQF+9uwoyvPhz9i1VMEPK9vbu0vvAhXe++IPZ/E26jqSh0KuRg8LyEj6s6A7+Gb0+cDE1f3HaHdgXiVtV0jE41yGoCfuuWxIGQyL+Bu/qaWgP0OX62Io45timH8mufARbvvQ=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-1.v29.ch3.sourceforge.com) by sfs-alluradaemon-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VS6aq-0002TS-AT for allura-dev@incubator.apache.org; Fri, 04 Oct 2013 14:43:00 +0000 Content-Type: multipart/related; boundary="===============5205457434409705701==" MIME-Version: 1.0 To: "[allura:tickets] " <6534@tickets.allura.p.re.sf.net> From: "Dave Brondsema" Reply-To: "[allura:tickets] " <6534@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #6534 Wiki importer for github Message-ID:

Date: Fri, 04 Oct 2013 14:43:00 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============5205457434409705701== Content-Type: multipart/alternative; boundary="===============8903369086823257698==" MIME-Version: 1.0 --===============8903369086823257698== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Merged je/42cc_6534 to master. --- ** [tickets:#6534] Wiki importer for github** **Status:** code-review **Labels:** import github 42cc **Created:** Wed Aug 07, 2013 09:54 PM UTC by Dave Brondsema **Last Updated:** Wed Oct 02, 2013 08:59 AM UTC **Owner:** nobody Wikis are git repositories and can be accessed like `git clone https://github.com/OpenRefine/OpenRefine.wiki` for example. Check the main repo API first to see if the repo has wiki enabled. You can see https://sourceforge.net/p/googlecodewikiimporter/git/ for reference as an example of another wiki importer. It is a separate repo because it needs the "html2text" package to convert html to markdown, and that is a GPL library. Github supports many markup types. Find a full list and determine what the best way to convert them to markdown is. My guess is that few formats will have tools available to convert them directly to markdown, so my likely recommendation would be to render them as HTML (using [pypeline](http://pypeline.sourceforge.net/) as a generic way to handle many of those formats) and then html2text to get it into markdown. If html2text or any other GPL library is needed, this will have to be a separate repo from the main Allura repo. So please evaluate & test the conversion options first, before putting code into place. A second phase to all this (i.e. do it separately, after the basic import is all working) would be to handle revision history. This would mean going through each commit in the wiki git repo, and converting & updating every file that changes. This may be very time consuming, so when we get to it, we may want it to be a checkbox option, so users only do it if they want it. --- 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. --===============8903369086823257698== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

Merged je/42cc_6534 to master.


[tickets:#6534] Wiki importer for github

Status: code-review
Labels: import github 42cc
Created: Wed Aug 07, 2013 09:54 PM UTC by Dave Brondsema
Last Updated: Wed Oct 02, 2013 08:59 AM UTC
Owner: nobody

Wikis are git repositories and can be accessed like git clone https://github.com/OpenRefine/OpenRefine.wiki for example. Check the main repo API first to see if the repo has wiki enabled. You can see https://sourceforge.net/p/googlecodewikiimporter/git/ for reference as an example of another wiki importer. It is a separate repo because it needs the "html2text" package to convert html to markdown, and that is a GPL library.

Github supports many markup types. Find a full list and determine what the best way to convert them to markdown is. My guess is that few formats will have tools available to convert them directly to markdown, so my likely recommendation would be to render them as HTML (using pypeline as a generic way to handle many of those formats) and then html2text to get it into markdown.

If html2text or any other GPL library is needed, this will have to be a separate repo from the main Allura repo. So please evaluate & test the conversion options first, before putting code into place.

A second phase to all this (i.e. do it separately, after the basic import is all working) would be to handle revision history. This would mean going through each commit in the wiki git repo, and converting & updating every file that changes. This may be very time consuming, so when we get to it, we may want it to be a checkbox option, so users only do it if they want it.


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.

--===============8903369086823257698==-- --===============5205457434409705701==--