|
|
|
This thread is locked; no one can reply to it.
|
| Wiki spam |
|
kenmasters1976
Member #8,794
July 2007
|
|
William Labbett
Member #4,486
March 2004
 |
Does anyone maintain the wiki anymore?
|
|
Edgar Reynaldo
Major Reynaldo
May 2007
 |
Tomasu's still around. You can catch him on IRC on #allegro. Tomasu - please don't nuke everything again...:'( My Website! | EAGLE GUI Library Demos | My Deviant Art Gallery | Spiraloid Preview | A4 FontMaker | Skyline! (Missile Defense) Eagle and Allegro 5 binaries | Older Allegro 4 and 5 binaries | Allegro 5 compile guide |
|
SiegeLord
Member #7,827
October 2006
 |
A serious option to consider is migrating as much content as possible to GitHub. Although, in terms of spam, there aren't any good tools to prevent this on GitHub either. "For in much wisdom is much grief: and he that increases knowledge increases sorrow."-Ecclesiastes 1:18 |
|
dthompson
Member #5,749
April 2005
 |
+1 for GitHub. Would hope there'd be less spam there because the consequences of getting blocked there would technically be greater. Porting should be easy enough - I added the getting started article in a few seconds. Nice that they accept MediaWiki formatting! ______________________________________________________ |
|
Chris Katko
Member #1,881
January 2002
 |
SiegeLord said: Although, in terms of spam, there aren't any good tools to prevent this on GitHub either. ...review the commits before committing them? -----sig: |
|
Peter Hull
Member #1,136
March 2001
|
You can "Restrict editing to collaborators only" in settings but then it goes against the spirit of a wiki, doesn't it?
|
|
Edgar Reynaldo
Major Reynaldo
May 2007
|
Personally, I find limiting it to allegro.cc members would be sufficient. However, who has time to review all those commits Chris? If there were a daily log or archive or history then it might work, but there has to be some kind of concrete versioning control so you can 'rewind' to any point in time. I've lost several pages I didn't have backed up in one fashion or another, and it turns me off to editing wikis. My Website! | EAGLE GUI Library Demos | My Deviant Art Gallery | Spiraloid Preview | A4 FontMaker | Skyline! (Missile Defense) Eagle and Allegro 5 binaries | Older Allegro 4 and 5 binaries | Allegro 5 compile guide |
|
Ariesnl
Member #2,902
November 2002
 |
hmmm personally I alway's liked the allegro wiki. Perhaps one day we will find that the human factor is more complicated than space and time (Jean luc Picard) |
|
dthompson
Member #5,749
April 2005
|
The only annoyance I've noticed with the GitHub wiki is that directly uploading images is non-trivial. (who knows - perhaps this is a good thing.) This tutorial explains how it can be done, though this only seems possible for those with push permissions. Edit: I'm starting to flesh things out - see the main page. ______________________________________________________ |
|
SiegeLord
Member #7,827
October 2006
|
Thanks dthompson, that's a good start. How are you doing the transfer from mediawiki's syntax to markdown? Manually? "For in much wisdom is much grief: and he that increases knowledge increases sorrow."-Ecclesiastes 1:18 |
|
dthompson
Member #5,749
April 2005
|
I've started out by copying the mediawiki straight over, then converting to Markdown before doing any serious editing. As an aside, I'm hosting a few of the images on my website for the moment - would it be possible for me to get push permissions for the wiki repository at some point to move them over (as mentioned above)? ______________________________________________________ |
|
SiegeLord
Member #7,827
October 2006
|
I think what might be possible to do is to create another repository, just for the wiki. Then we can be more liberal in letting people push to that compared to the main source repository. I'll try setting that up tonight. "For in much wisdom is much grief: and he that increases knowledge increases sorrow."-Ecclesiastes 1:18 |
|
dthompson
Member #5,749
April 2005
|
Sounds good. ______________________________________________________ |
|
Edgar Reynaldo
Major Reynaldo
May 2007
|
Let's see, so now we need write access to the repo to edit the wiki? I would prefer the allegro wiki if that is the case. My Website! | EAGLE GUI Library Demos | My Deviant Art Gallery | Spiraloid Preview | A4 FontMaker | Skyline! (Missile Defense) Eagle and Allegro 5 binaries | Older Allegro 4 and 5 binaries | Allegro 5 compile guide |
|
dthompson
Member #5,749
April 2005
|
You can edit on GitHub without repo push access. ______________________________________________________ |
|
SiegeLord
Member #7,827
October 2006
|
Alright, I created a new repository just for the wiki: https://github.com/liballeg/allegro_wiki. I also created a github team that can push to the wiki. For now, it's set up so that anyone with a Github account can edit it, but only those on that team can push to it via git (to add images etc). We can see how that works, and if there's any spam (if so, we'll have to lock it down to being editable only by people on that team). The intention is for membership to be super liberal though, just to weed out the bots. "For in much wisdom is much grief: and he that increases knowledge increases sorrow."-Ecclesiastes 1:18 |
|
dthompson
Member #5,749
April 2005
|
Brilliant, thanks! (also, great to see Alex has now appeared on my profile page...) Just pushed the logo to the wiki repo, seems to be displaying fine in place of the hotlink from a.cc. Will do the rest of the images later. ______________________________________________________ |
|
Ariesnl
Member #2,902
November 2002
|
So when I want to write an article I have to do it on github from now ? Perhaps one day we will find that the human factor is more complicated than space and time (Jean luc Picard) |
|
Chris Katko
Member #1,881
January 2002
|
Github supports markdown, which is WAYYYY quicker to write most stuff in than oldschool 90's "wiki" formatting. -----sig: |
|
dthompson
Member #5,749
April 2005
|
Yes indeed. There's a preview tab and everything. ______________________________________________________ |
|
|
