Reply to Re: Taking over the Dink Solutions
If you don't have an account, just leave the password field blank.
Let's clarify.
I want somebody else to maintain the Dink Solutions because 1) it's good to shift maintainers once a in a while, to give fresh energy and goals to projects, 2) Dukie left ages ago and I haven't written a walkthrough in a while either, 3) currently the Dink Solutions only rely on me and will disappear from the surface of Earth if I don't pay the next month's hosting bill.
Indeed, solutions.dinknetwork.com is an alias ("CNAME" in DNS slang) to my dedicated server (aka. when I reboot that server, Dink Solutions is down
). To change the alias, contact redink1.
I can give access to the current "dinksols" account on my server if there's a problem with hosting, but I think it'd be best that the web hosting relies on more than one single person.
Technically the website is built using the SPIP CMS, with custom templates to manage the *cough* design and the translations. Of course, the new maintainer(s) can change this. Keep on eye on security updates whatever CMS you use though.
The contents of the website can be downloaded in real time through rsync rsync://solutions.dinknetwork.com/dinksols-www/ (90MB) and rsync://solutions.dinknetwork.com/dinksols-dumps/ (database - 6MB).
We have no formal author agreement or copyright license on the walkthroughs, but I doubt any past contributor will complain. It would be good to formalize this and explicitely use (for instance) Creative Commons BY-SA for new walkthroughs.
So far, yeoldetoast is offering hosting and Skull is offering maintenance. Great
I'd rather keep the details on this thread rather than by private mail, so that everybody can see where this is going.
Feel free to ask any other questions about DinkSols
I want somebody else to maintain the Dink Solutions because 1) it's good to shift maintainers once a in a while, to give fresh energy and goals to projects, 2) Dukie left ages ago and I haven't written a walkthrough in a while either, 3) currently the Dink Solutions only rely on me and will disappear from the surface of Earth if I don't pay the next month's hosting bill.
Indeed, solutions.dinknetwork.com is an alias ("CNAME" in DNS slang) to my dedicated server (aka. when I reboot that server, Dink Solutions is down
). To change the alias, contact redink1.I can give access to the current "dinksols" account on my server if there's a problem with hosting, but I think it'd be best that the web hosting relies on more than one single person.
Technically the website is built using the SPIP CMS, with custom templates to manage the *cough* design and the translations. Of course, the new maintainer(s) can change this. Keep on eye on security updates whatever CMS you use though.
The contents of the website can be downloaded in real time through rsync rsync://solutions.dinknetwork.com/dinksols-www/ (90MB) and rsync://solutions.dinknetwork.com/dinksols-dumps/ (database - 6MB).
We have no formal author agreement or copyright license on the walkthroughs, but I doubt any past contributor will complain. It would be good to formalize this and explicitely use (for instance) Creative Commons BY-SA for new walkthroughs.
So far, yeoldetoast is offering hosting and Skull is offering maintenance. Great
I'd rather keep the details on this thread rather than by private mail, so that everybody can see where this is going.Feel free to ask any other questions about DinkSols
