Re: [Jack-Devel] jackaudio.org website shut down due to hacking

On 05/30/2014 11:57 PM, Adrian Knoth wrote:
> On 05/30/14 19:34, Robin Gareus wrote:
> 
>>> If someone else wants to volunteer to resurrect the roughly 60 pages
>>> of content that were at jackaudio.org (and realistically, it is
>>> probably more like 20 of real stuff that is needed), get in touch. I
>>> can give you full access to everything you will need.
> 
>> last time this happened, Adi and I began moving the content to
>> https://github.com/jackaudio/jackaudio.github.com/wiki
>>
>> Back then, we started from an old mysql dump (because mysql + drupal was
>> broken). Then mysql+drupal was fixed before we've completed the process
>> and the site was never fully migrated to github-pages. Yet most of it is
>> already in the wiki there.
>>
>> github pages are far from the non plus ultra, but they certainly suffice
>> for the jackaudio.org site. It's all in git and from our POV the
>> infrastructure maintains itself.
>>
>> Unless someone comes up with a better idea, I suggests to resume the
>> migration to gh-pages.
> 
> Well, trac.jackaudio.org (a.k.a. "the wiki") is still up. OTOH, having
> everything on github doesn't sound too bad either.
> 
> Anyway, for the time being, I've generated the API reference (doxygen)
> and pushed it to
> 
>    http://jackaudio.github.io/api/
> 
> This URL is also linked from jackaudio's wiki frontpage on github.
> 
> If we (or the volunteer(s)) decide to go the GH page route (I'm totally
> down for that), all we have to do is to push another file and switch the
> DNS:
> 
> 
> https://help.github.com/articles/setting-up-a-custom-domain-with-github-pages
> 
> 
> I also second your suggestion: if nobody else steps up with a better
> idea, we move the remaining bits to github. This also encourages
> collaboration, if any. ;)
> 
> 

I'd like to volunteer.
I also second the GitHub Page route. Since the wiki-pages are already
available in the markdown format, they (most likely) can be moved into
the generated page. One thing i think is important is to ensure, that
there won't be to much of a lock-in of the page to the GitHub
infrastructure.
I'm thinking about a work flow, using a static site generator. Locally
generated content will be pushed to the github page and the
configuration and content for the generator would also be checked in, so
everyone can collaborate by cloning the repo and sending pull requests.
Do you agree with this?

- Markus

1401640075.5783_0.ltw:2,a <538B5480.40007 at spectralbird dot de>