From: Marc G. Fournier <scrappy@hu...> - 2011-02-10 04:38:07
Okay, I suck at subjects, but hopefully it caught some eyes ...
We are slowly moving forward on plans to revitalize / revive SlashCode ...
as per Rob and Jamie's recommendations, we are rebranding completely to
avoid any potential trademark related issues ... as such, we are naming
the new project: HaXlash (pronounced: Hack-Slash)
Shane is dealing with getting the repo setup at GitHub, with instructions
on how to access the repo to follow shortly ... the repo is based on the
last available code from the slashcode report, minus that error at the end
of the clone (benign error, but it fooled me at the time) ...
I've setup a set of mailing lists @haxlash.org that we encourage ppl to
subscribe to and either lurk or get involved ... we will be cross-posting
major announcements to this list for hte next little while, but
discussions themselves will happen over there ...
The lists are:
haxlash-hackers ... for those developing
haxlash-general ... for those using
haxlash-commits ... for those that want to follow commits to github
haxlash-announce ... hopefully this one is obvious?
The lists are all setup so that only subscribers can post, so as to
minimize / eliminate potential for spam ...
I am also setting up MediaWiki to give us an environment to build docs on,
especially as pertains the myriad of distros that ppl out there are using
... nice thing about MediaWiki, everyone can get involved with
Although my personal goal is to get things working with both PostgreSQL
*and* Apache 2.2, I am setting up the main site right now on Apache
1.3+MySQL, so that we have a main site running Slashcode ...
Marc G. Fournier Hub.Org Hosting Solutions S.A.
Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@...