On Thursday, December 6, 2012 4:48:08 AM UTC+1, Dan Allen wrote: > > (Google Groups once again ate my reply, so this reply will be > shorter...probably for the best :)) > > On Dec 4, 6:26 pm, Stuart Rackham <[email protected]> wrote: > > > > Thank you for this generous offer, I'd love to move AsciiDoc to it's own > > domain, it's been hanging off my site to long -- just a time and > > resources issue on my part. It's well past time AsciiDoc had it's own > > domain. > > +1 > > I think that's a sign of a certain level of success for a project. > > > > > I would prefer someone else/others to manage the domains, Dan's the > > obvious choice, but this is something the community needs to address (I > > don't know how this sort of stuff is done, but we don't want to lose > > control the domain names in the future). > > I think we can model after communities like Fedora and manage the > resource collectively. See phased approach proposal below. We can > stick sensitive data (like account credentials) in a shared document > (such as Google Docs). > > > > > I'm stretched to thin to take anything else on at the moment (I've been > > AWOL from the discussion list for a while now, but will get back to it > > hopefully soon :-) > > I'm pretty stretched too, so I'll do what I can to help out, but I > think if we get a few things setup we should be able to automate or > offload most of the work / responsibility. > > > > > To get the ball rolling I can change the docs and the website content to > > point to asciidoc.org. Longer term I'd like to offload the website > > administration to others -- shouldn't be to onerous the website itself > > is in the repo and the AsciiDoc AAP build scripts rebuild and upload the > > website. > > I think the key is to get the website source into hg or git and host > the site on a free PaaS. The first makes it a collaboration, rather > than coordination problem, and the second just saves all kinds of > headaches and enables easy automation. > > Eventually we'd like to get to a truly community-driven website for > AsciiDoc, but that won't happen overnight. I see this as a phased > approach. > > Phase 1: Reserve the domain names and point them at the methods.co.nz > server using a 301 redirect (done) > - keep in mind, this does not allow for deep linking, like > asciidoc.org/userguide.html > > Phase 2: Setup a virtual host on methods.co.nz for asciidoc.org / > asciidoc.info so that we can use deep linking on this domains (in > progress - Stuart and Dan) > > Phase 3: Import the website source into git or hg (preferably at > GitHub, BitBucket or similar) and publish the website to a free PaaS > (GitHub pages, Heroku, OpenShift, etc) using a CI tool (Jenkins, etc) > > Phase 4: Make the website (at least the home page) more inviting, > informative and attractive to the various types of AsciiDoc users > (essentially a rebranding). > > Each phase gets more ambitious, and it will all take time. Phase 2 is > the most important in the short term because it allows us to use the > new domains w/ deep linking. > > Keep in mind these phases are just a proposal. I welcome your feedback > or revisions. > > Btw, does AsciiDoc have a wiki? > > If we were to host the repository on GitHub or BitBucket, we could > leverage the wiki that is there. The phases I outlined would be a nice > thing to put on a wiki :) > > * Bonus if the wiki supports AsciiDoc, like GitHub :) >
mmmh... Gollum ? ;) > > -Dan > -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To view this discussion on the web visit https://groups.google.com/d/msg/asciidoc/-/guJldNMJfkQJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.
