Hi Lex That would be great if you could take this on -- your encyclopedic knowledge of AsciiDoc and your having answered more questions on this list than anyone makes you really well qualified for this task.
The first job would be to copy the current Google Code Hg repo to a new canonical repo on Github at https://github.com/asciidoc/asciidoc. It doesn't exist at the moment: as per Dan's email at the start of the thread, currently only Dan, myself and Charbel Bitar are members of the Github asciidoc organization (https://github.com/asciidoc). @Dan: How do we go about adding Lex to the team? What is ownership / membership protocol for https://github.com/asciidoc? This can go ahead if there is no dissension on using the existing https://github.com/asciidoc organization (there's no intrinsic reason for using the github.com/asciidoc organization on Github, but it has the name and it already exists). Cheers, Stuart On Thu, Nov 28, 2013 at 3:30 PM, Lex Trotman <[email protected]> wrote: > Stuart and all, > > First of all a big thanks to Stuart for all his work in creating and > supporting Asciidoc to its current point. > > I'm willing to help reviewing PRs and committing them on a github based > asciidoc, but as a contractor there are times when I am just not available > for a while, so there also needs to be others (witness how long its taken > for me to respond to this thread :). > > Also if he is interested I would suggest Dan or other Asciidoctor > representative be added to keep the flow of information between the > projects up, and to allow their compatibility patches to be available in > say a branch of Asciidoc as well as Asciidoctor (users then only need to go > to one place). > > @Michel, the canonical recipe for converting hg to git seems to be using > the fast-export scripts, something like: > > git clone git://repo.or.cz/fast-export.git > git init git_repo > cd git_repo > ../fast-export/hg-fast-export.sh -r /path/to/old/mercurial_repo > git checkout HEAD > > I can't try it at the moment, but if you or anybody can see if that seems > to get a viable copy of the hg repo then the git can be put up on github in > the usual fashion. > > Does the github asciidoc organisation already exist? > > Cheers > Lex > > > On 28 November 2013 08:07, Stuart Rackham <[email protected]> wrote: > >> I agree with Dan, the canonical repo should be >> https://github.com/asciidoc/asciidoc and commit rights should be >> broadened to other contributors (criteria?) to try an resolve the patch >> bottleneck. But I don't have the time to do this. >> >> Cheers, Stuart >> >> On 10/12/12 22:32, Dan Allen wrote: >> > The holder of the asciidoc organization on GitHub, Charbel Bitar, >> > has graciously given us permission to use the organization for the >> > AsciiDoc project. At the moment, Stuart and I have been made admins. >> > Anyone else interested in helping to manage it, please speak up. >> > >> > Now that we have the space, it's time to decide what to do with it. I'll >> > raise three uses. Feel free to suggest others. >> > >> > AsciiDoc mirror on GitHub:: >> > >> > Regardless of where the canonical source code repository is located, I >> > think there is tremendous benefit in having a mirror on GitHub. I've >> > observed first hand how much visibility GitHub brings to a project. The >> > obvious benefit is that you can say "find us on GitHub", which is a >> > surprisingly powerful. It also makes it so easy to see the activity and >> > history of a project, more so than any other web-based viewer I've ever >> > come across. Finally, it provides a very elegant way to share patches >> > (either through pull requests or just the "forks" themselves). That >> > definitely beats sending patch files through a mailinglist. Do not >> > underestimating the impact this can have. >> > >> > I experimented with using hg-git to sync the mirror [1] and it >> > works splendidly. One of us can setup a job on a CI server to sync >> > regularly or via a commit trigger. >> > >> > Shall I proceed with adding an AsciiDoc mirror under >> > http://github.com/asciidoc? >> > What should we call the mirror repository? asciidoc? asciidoc-mirror? >> > >> > Keep in mind, those questions depend on... >> > >> > AsciiDoc on GitHub:: >> > >> > Instead of a mirror, can we just switch to Git and make the one hosted >> > at GitHub the canonical repository? I suppose this is really a question >> > for Stuart to answer. Stuart, are you attached to hg or would you be >> > open to using git instead? I've never seen a project that had less >> > participation after moving to Git, so it seems like a risk-free choice. >> > >> > Community add-ons:: >> > >> > Should we offer to host community add-ons that are already well known >> > under the asciidoc organization? (Repos that come to mind are those >> > listed on the plugins page [2]) >> > >> > The organization already has the Maven plugin and it should remain there >> > given that Charbel gave us access to use the organization. >> > >> > To address the concern Lex raised in another thread, we could make it >> > clear that being under the asciidoc organization doesn't mean the add-on >> > is supported or stable, necessarily. For the time being, only those in >> > the main AsciiDoc repository are expected to be production quality. >> > Support is naturally understood to mean community support. >> > >> > I look forward to hearing your responses and, if supportive of the idea, >> > ready to activate the asciidoc organization on GitHub and keep the >> > project growing! >> > >> > Cheers, >> > >> > -Dan >> > >> > [1] https://github.com/mojavelinux/asciidoc-mirror (temporary URL!) >> > [2] http://www.methods.co.nz/asciidoc/plugins.html >> > >> > -- >> > Dan Allen >> > Principal Software Engineer, Red Hat | Author of Seam in Action >> > Registered Linux User #231597 >> > >> > http://google.com/profiles/dan.j.allen >> > http://mojavelinux.com >> > http://mojavelinux.com/seaminaction >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "asciidoc" group. >> > 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. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "asciidoc" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/asciidoc. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- > You received this message because you are subscribed to the Google Groups > "asciidoc" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/asciidoc. > For more options, visit https://groups.google.com/groups/opt_out. > -- Stuart Rackham methods: Recruitment Systems EMail: [email protected] Phone: +64(9)415 6259 Mobile: +64(21)115 7168 -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/groups/opt_out.
