On Tuesday, December 4, 2012 6:26:27 PM UTC-7, Stuart Rackham 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 it's a sign of a project reaching a certain level of success :) > 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). > As Fedora does it, we could handle everything in the open, through this list (or a dedicated admin list). We can handle any sensitive information (like domain account credentials) using a file shared between admins (like a Google Doc). > > 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 :-) > The best way to make this easy for all is to have a common collaboration point...typically by putting the website into a git (or hg) repository and using a CI server to publish the site automatically. My experience in doing this sort of thing is with GitHub pages (not the page creator, just the hosted bit), but we can use other solutions. Free is the key word here. Using GitHub pages, Heroku, OpenShift or alternative we can basically turn over the infrastructure (i.e., apache httpd) of the site to the PaaS. > > 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. > While I've reserved the domains, I can't commit to handling the whole site. However, we can figure out how to enable the (growing) community to manage it, which is more scalable anyway. I think taking a phased approach is best: Phase 1: Setup a 301 redirect from asciidoc.org / asciidoc.info to methods.co.nz/asciidoc (done) - note that this does not allow for deep linking, such as asciidoc.org/userguide.html Phase 2: Setup virtual host on methods.co.nz to accept requests for asciidoc.org / asciidoc.info, thus allowing the domains to be fully functional (pending Stuart and Dan's coordination) Phase 3: Move the existing contents (or source) of the site to a git or hg repository and deploy to a PaaS provider (GitHub pages, Heroku, OpenShift, etc) using CI (Jenkins, etc) Phase 4: Repurpose the site to present the technology in a more compelling way (i.e., rebranding) I realize that each phase is more ambitious than the previous, and the last phase in particular may not happen for awhile. Phase 2 is probably the most important in the short term. Changes to the documentation should wait until deep linking is possible. Again, feedback is welcome. This proposal is the advice I have to give, but certainly not set in stone. -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/-/HaO5CS3AzAcJ. 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.
