Move to GitHub?

[Erik Mogensen]

In previous posts I saw something about moving the OpenSearch spec and
review process etc to GitHub.

I made a gist of the raw wikimedia source for the main spec:

https://gist.github.com/mogsie/b44e8fc73e39d14b0891

There really isn't much to do:
- some &s were introduced
- internal links (Links like <a href='#Foo "Bar"'> need to be replaced
references to '#foo-bar')
- relative links might work if the pages are structured the same way as
before.

I'm not sure if e.g. github pages could be used to host the documents on
the same domain though; I guess it might be possible without too much link
rot!

[DeWitt Clinton]

Very nice. I have a stalled underway myself to do a high-fidelity
conversion from Mediawiki to Markdown, but this looks at least as far along.

What did you use to do the mappings of formats? I hear that pandoc
<http://pandoc.org/> is the current tool of choice.

Personally I still feel Github might be the right way to go. What do other
people think?

-DeWitt

Post by Erik Mogensen
In previous posts I saw something about moving the OpenSearch spec and
review process etc to GitHub.
https://gist.github.com/mogsie/b44e8fc73e39d14b0891
- some &amp;s were introduced
- internal links (Links like <a href='#Foo "Bar"'> need to be replaced
references to '#foo-bar')
- relative links might work if the pages are structured the same way as
before.
I'm not sure if e.g. github pages could be used to host the documents on
the same domain though; I guess it might be possible without too much link
rot!
--
-mogsie-
--
You received this message because you are subscribed to the Google Groups
"OpenSearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/opensearch.
For more options, visit https://groups.google.com/d/optout.

[Ed Summers]

Personally I still feel Github might be the right way to go. What do other people think?

+1 for moving to Github. I wouldn’t be opposed to having the source
in clean HTML. Perhaps that’s too old school?

//Ed

[Ed Summers]

Post by Ed Summers
+1 for moving to Github. I wouldn’t be opposed to having the source
in clean HTML. Perhaps that’s too old school?

On second thought having multiple HTML pages with similar styling etc might be better maintained using Jekyll or something like it.

If there was time it would be nice to get OpenSearch into IETF as an RFC. But I’m guessing that would involve some coordinated time and effort.

//Ed

[Erik Mogensen]

Post by DeWitt Clinton
Very nice. I have a stalled underway myself to do a high-fidelity
conversion from Mediawiki to Markdown, but this looks at least as far along.
What did you use to do the mappings of formats? I hear that pandoc
<http://pandoc.org/> is the current tool of choice.

That's the beauty of it, I didn't do any mapping.

- I found the source tab of the MediaWiki
- I pasted it into the gist
- I named the file xyzzy.mediawiki
- GitHub formats the mediawiki source for me.

Repeat: I did *not* do any format conversions. The GitHub gist has the raw
wikimedia *source* text in it!

I only noted what *needs* to be changed: some extraneous "&amp;" and
differences in how GitHub creates <a name> elements based on the different
section headers. But that's a *lot* less than actually converting the
source to Markdown, even with tools like pandoc...

Personally I still feel Github might be the right way to go. What do other

Post by DeWitt Clinton
people think?

You know my stance :)

[DeWitt Clinton]

Wow, that's excellent then. If people here are okay trusting Github to
format Mediawiki correctly enough to serve as the basis for the specs, then
we appear to have an easier path forward than I would have hoped for.
Thanks, Erik!

BTW, if anyone employed by Github is reading this and wants to contact me
directly, I'd be interested in seeing if we can recover the
github.com/opensearch account, given that it has no activity (and is
trademarked anyway). Otherwise I'll reach out through the published
channels.

-DeWitt

Post by Erik Mogensen

Post by DeWitt Clinton
Very nice. I have a stalled underway myself to do a high-fidelity
conversion from Mediawiki to Markdown, but this looks at least as far along.
What did you use to do the mappings of formats? I hear that pandoc
<http://pandoc.org/> is the current tool of choice.

That's the beauty of it, I didn't do any mapping.
- I found the source tab of the MediaWiki
- I pasted it into the gist
- I named the file xyzzy.mediawiki
- GitHub formats the mediawiki source for me.
Repeat: I did *not* do any format conversions. The GitHub gist has the raw
wikimedia *source* text in it!
I only noted what *needs* to be changed: some extraneous "&amp;" and
differences in how GitHub creates <a name> elements based on the different
section headers. But that's a *lot* less than actually converting the
source to Markdown, even with tools like pandoc...
Personally I still feel Github might be the right way to go. What do other

Post by DeWitt Clinton
people think?

You know my stance :)
--
-mogsie-
--
You received this message because you are subscribed to the Google Groups
"OpenSearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/opensearch.
For more options, visit https://groups.google.com/d/optout.