I'm all for moving to Github and reorganizing the development model,
problem is that I just don't have the time at the moment to do it.
As I was the one who put GitHub on the table, if I may help just let me
know.
Cheers,
Michel
BTW, loomio looks like a really nice tool.
Cheers, Stuart
On 27/11/13 09:39, Eduardo Santana wrote:
I these questions still open?
Have you tried https://www.loomio.org to organize the community?
Em terça-feira, 1 de janeiro de 2013 04h20min55s UTC-3, Stuart Rackham
escreveu:
On 10/12/12 23:22, Lex Trotman wrote:
> On 10 December 2012 20:32, Dan Allen <[email protected]
<javascript:>> wrote:
>> The holder of the asciidoc organization on GitHub, Charbel Bitar,
has
>
> Profuse thank you to him for that.
>
>
>> 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.
>>
>
> I guess since this looks like a significant point of change, the
> question of how the asciidoc community is going to operate needs
to be
> addressed. Who manages it and how are decisions made? Is Stuart
> BDFNow? Does he have time? Is it a democracy? if so how does that
> work? These issues need to be addressed *before* major changes are
> made and especially before any suggestions for incompatible changes
> (see my comment elsewhere).
Excellent questions Lex! At the moment it's probably a benign
dictatorship. I think your key point is worth reiterating viz ``These
issues need to be addressed *before* major changes are made...''
Cheers, Stuart
>
>> 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.
>
> That also depends on some of the answers to the questions above.
>
>>
>> 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.
>
> Agree.
>
>>
>> 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.
>
> How do you suggest that this is made clear?
>
> Cheers
> Lex
>
>>
>> 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
<https://github.com/mojavelinux/asciidoc-mirror> (temporary URL!)
>> [2] http://www.methods.co.nz/asciidoc/plugins.html
<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://google.com/profiles/dan.j.allen>
>> http://mojavelinux.com
>> http://mojavelinux.com/seaminaction
<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]
<javascript:>.
>> To unsubscribe from this group, send email to
>> [email protected] <javascript:>.
>> For more options, visit this group at
>> http://groups.google.com/group/asciidoc?hl=en
<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.
