LinuxBBQ

^ should've said forked it! ;)

If anybody is willing: please create wiki articles for the releases found in /etc/os-release (http://linuxbbq.org/bbs/viewforum.php?f=3) and link these in http://linuxbbq.org/wiki/index.php/Active_Releases

Thank you!

by the way, 'base' stands for these:
- debian sid
- source-based (eg. szalonna, bacon)
- slackware (eg. bowlful)
- ubuntu
- debian jessie
- ...

please add these tags to the active and forthcoming releases :)

^ Whoops! Fixed :) I'm a bit curious about these tags: Type ( should Bork be standard release ? ) and Counter part ( successor ? )

^^ So everything in that forum page is 'active' ?
Cool.

stark, i'll post a detailed list later here :)

wuxmedia wrote:^^ So everything in that forum page is 'active' ?
Cool.

Eh ? Shouldn't the ones that are older than three months from their release date go to inactive ? Sorry I'm a bit confused.

@bacon No hurry :)

some are safe to upgrade, so /etc/os-release are 'active'. Cream is special because 'not to be installed'.

counterpart and successor tags are dead. type refers to light/special edition/desktop edition. you can set these to '-', we only have light versions :)

So just to be clear the following are going to be added to the Active list:

Cream
Hot Dog
Baconator
Popcorn Lite
Popcorn
Chlamydia
Emacspeak 40
Rape My X
Weckewerk
Bowlful
Bacon

And bacon, you might as well update the Notes section in Category:Releases as I suck at choosing the right words ;)

right, these update quite easy. Vic reported that even older ones work okay.

thanks stark. leave the wording to people like rhowaldt ;) he's busy, so let's give him some pressure :)

^ Np. Any idea why templates don't work in the wiki ? ( my guess would be they don't exist )

It's possible. It's a debian install, so probably totally fucked up (after previous experience) :) not as bad as the latest hot stable - colleague spent hours rewriting theme reference and installing all the extensions.
I'll have a look

How about creating a wiki with the github pages and edit the cname so that it redirects to the existing wiki ? ( don't know if it's possible )

This would ofcourse mean rewriting all the stuff in markdown ( which is nice and going to take alot of time )

I'm pretty sure I have no idea of what you speak, stark :)

I like our Wiki, not sure about the Github thing. Yes Wux, you can write Wiki pages on the Github's project site.

^ Apologies for the confusion.

Normally we can create a wiki per project ( i.e repo ) on github :
https://help.github.com/articles/about-github-wikis/

Advantages: Github markdown, offline availability ( just a git clone away for the entire wiki! ),etc.

And then Github allows to setup one website ( automatic site generator ) per user directly on github at username.github.com or username.github.io. Now if you own any domain then there's file named cname in your website's github repo ( where you're hosting your site's source ), now you can edit the cname file to redirect to your domain.

Pretty sure I explained it terribly and wrongfully and confused you even more so:

https://guides.github.com/features/pages/

https://help.github.com/articles/settin ... hub-pages/

And finally what I'm trying to say is:

Re-Wrting the wiki articles on github, and make those content available say at linuxbbq.github.io and edit the cname to forward to the existing wiki http://linuxbbq.org/wiki/index.php ? I'm not not entirely sure if the last two things are possible ( don't know how wiki domains work )

oh right, yeah see what you mean. don't see the point?
convert the entire thing to another format?
Ain't nobody got time fo' dat!

^ Github markdown is tempting but, Agreed :)

hey, good enough for wikipedia - good enough for me ;)

nah, no rewrite, the wiki format works well. thanks.

Top editing / adding stark!
And look at that, the web index page got updated without me even opening a laptop :)