From: Alex Legler <a3li@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [1/3] Automatic *XML->Wiki wiki.gentoo.org
Date: Wed, 26 Jun 2013 15:54:47 +0200 [thread overview]
Message-ID: <51CAF2A7.6000403@gentoo.org> (raw)
In-Reply-To: <20130616002853.GD29913@orbis-terrarum.net>
[-- Attachment #1: Type: text/plain, Size: 3441 bytes --]
On 16.06.2013 02:28, Robin H. Johnson wrote:
> From the infra perspective, I would like to add that I support this
> move, I just have a few concerns on the conversion, one of which is
> dealt with here.
>
>> I've committed my draft XSL to the gentoo/xml/htdocs/xsl location, named
>> guidexml2wiki.xsl. It still requires some updates that I'll work on soon
>> (such as handling internal links) as I'll be using it more and more for the
>> guides on gentoo.org/doc/en to move to the wiki as well.
>> ProjectXML generates towards GuideXML, so should be usable chained.
> It would be nice to move the foundation/ content to the Wiki as well I
> think.
>
Sure. It doesn't count as a project I guess, so you would move into
Foundation:.* ?
>> PS An ebuild for a single stylesheet seems like overkill to me, but i've
>> been proven incorrect in the past...
> I think it would help a lot of the devs that are put off by the concept
> of XML/XSLT. Just give them a little wrapper script to generate wiki
> output.
>
> One of my large concerns was how to handle some of the tag conversion.
> We have a lot of custom tags, plus some interesting behavior in some
> tags.
>
> Sven's XSL makes a very good start, but somebody needs to put in some
> TLC for the following tags in conversion, and/or can we have it emit
> something useful so we know when we hit a tag that's missing in the
> XSLT.
>
> Here's my list of tags found in proj/ that aren't in the XSLT so far:
> (the "/>" is just because I collapsed the tag of any attributes, there probably
> needs to be an audit of how the XSL handles attributes).
>
> 179 <body/>
ignore, needed by guidexml
> 145 <i/>
<i>.*?</i> -> ''\1''
> 74 <mail/> (optional attribute link)
This functionality is replaced by the {{Mail}} template.
Usage:
* {{Mail|a3li}} -> <a href="mailto:a3li@gentoo.org">Alex Legler</a>
* {{Mail|a3li|foo}} -> <a href="mailto@a3li@gentoo.org">foo</a>
* {{Mail|a3li@g.o}} -> <a href="mailto:a3li@g.o">a3li@g.o</a>
* {{Mail|a3li@g.o|foo}} -> <a href="mailto:a3li@g.o">foo</a>
> 27 <dev/>
Project members will have to be recreated using the form.
> 25 <br/>
keep "<br />"
> 18 <license/>
Discard, everything is the same CC license, the old 2.x version allows
upgrade to the 3.0 we use.
> 15 <extrachapter/> (optional attribute position)
Discard, GuideXML specific.
> 9 <resource/> (attribute resource)
These resource things could just become a list:
* foo
* bar
* baz
> 7 <project/>
> 7 <name/>
> 7 <longname/>
> 7 <longdescription/>
> 7 <description/>
> 6 <subproject/> (attribute ref)
Dump information, contents need to be recreated using the form as well.
Longdescription should 'just' be the first paragraph of the wiki page.
> 4 <goals/>
> 2 <summary/>
> 2 <requirements/>
Does anyone actually use the goals feature? imo, discard.
> 2 <recruitment/>
> 2 <keyword/>
> 2 <job/>
> 2 <details/>
> 2 <contact/>
Discard. I have moved staffing needs already.
> 1 <var/>
> 1 <subtitle/>
> 1 <stmt/>
> 1 <ident/>
> 1 <const/>
>
We have proper syntax hilighting in the wiki. Discard?
> 1 <extraproject/> (attribute name)
Shouldn't these be proper projects?
--
Alex Legler <a3li@gentoo.org>
Gentoo Security/Ruby/Infrastructure
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2013-06-26 13:55 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 14:22 [gentoo-dev] RFC: Moving project pages to wiki.gentoo.org Alex Legler
2013-06-09 15:44 ` Ulrich Mueller
2013-06-09 16:01 ` Alex Legler
2013-06-09 15:57 ` Andreas K. Huettel
2013-06-09 16:03 ` Alex Legler
2013-06-10 6:48 ` Dirkjan Ochtman
2013-06-10 12:36 ` Sergey Popov
2013-06-10 13:29 ` Diego Elio Pettenò
2013-06-10 14:31 ` Michał Górny
2013-06-10 15:15 ` Alex Legler
2013-06-10 15:47 ` Hans de Graaff
2013-06-10 20:38 ` Ultrabug
2013-06-11 10:49 ` Sergey Popov
2013-06-10 23:06 ` Jason A. Donenfeld
2013-06-11 10:20 ` Sven Vermeulen
2013-06-11 11:05 ` Theo Chatzimichos
2013-06-11 12:15 ` Alex Legler
2013-06-13 16:33 ` Sven Vermeulen
2013-06-16 0:28 ` [gentoo-dev] [1/3] Automatic *XML->Wiki wiki.gentoo.org Robin H. Johnson
2013-06-26 13:54 ` Alex Legler [this message]
2013-07-08 20:02 ` Sven Vermeulen
2013-07-09 15:46 ` [gentoo-dev] " Steven J. Long
[not found] ` <51DB41CA.8090707@yahoo.ca>
2013-07-09 23:53 ` [gentoo-dev] " Alex Xu
2013-07-10 0:29 ` Alex Legler
2013-07-10 0:45 ` Alex Xu
2013-07-10 6:58 ` Tom Wijsman
2013-07-10 9:10 ` Michael Weber
2013-07-10 9:26 ` Tom Wijsman
2013-07-10 8:23 ` Sven Vermeulen
2013-06-16 1:21 ` [gentoo-dev] [2&3]/3 API & files Robin H. Johnson
2013-06-16 12:08 ` Alex Legler
2013-06-16 19:44 ` Robin H. Johnson
2013-06-16 22:12 ` Alex Legler
2013-06-16 22:56 ` Alex Xu
2013-06-18 18:06 ` Robin H. Johnson
2013-06-22 9:20 ` Markos Chandras
2013-06-22 10:14 ` Alex Legler
2013-06-16 4:01 ` [gentoo-dev] RFC: Moving project pages to wiki.gentoo.org "Paweł Hajdan, Jr."
2013-06-16 9:01 ` Tom Wijsman
2013-06-16 10:53 ` Alex Legler
2013-06-16 19:40 ` Robin H. Johnson
2013-06-16 20:12 ` Kent Fredric
2013-06-16 20:36 ` Andreas K. Huettel
2013-06-16 23:17 ` Alex Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51CAF2A7.6000403@gentoo.org \
--to=a3li@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox