Dear Stuart,
First of all let me thank you for your great work! AsciiDoc is really
awesome!
I've been reading this mailing list for quite some time now and it seems
to me there's a growing community of contributors. Most of them also
seem to be quite competent and possibly qualified to review and submit
patches to AsciiDoc even without requiring to bother you.
The first step IMHO should be to migrate to GitHub where you have a
platform and tools to make the community even more stronger. People
could fork AsciiDoc and integrate their patches theirselves.
Additionally, pull requests are a great way to keep track of patches
that should be integrated into the mainline.
I understand that you put a lot of work into AsciiDoc and that you're
looking for something making your life easier. So, the second step
should be to add GitHub community users to the list of project
contributors which will allow them to take over some of your duties
(like reviewing patches or even accepting pull requests). You could even
think about creating a virtual 'organization' where you can manage
users/contributors and permissions.
I've contributed to several GitHub projects myself and I can say that
it's really a breeze to work with this platform. I'm also part of two
organizations and I've had good experiences so far.
I would really love to see AsciiDoc on GitHub. I would even consider
contributing myself (and not only reading the mailing list) if you'd
allow me to of course :-) And I think a lot of people think the same way.
Cheers,
Michel
Hi All
I've been working on AsciiDoc for over a decade now and it really has
been incredibly rewarding, mainly because of all you AsciiDoc users
and contributors out there -- without your input AsciiDoc would not be
what it is today (Sourceforge alone has recorded over 25 thousand
downloads for the 8.6.8 release, and that's not even counting packaged
distributions or repository downloads!).
With the 8.6.9 release out of the way I've decided that now is a good
time for me to get out of the driver's seat.
The problem is not AsciiDoc, it's the current development model (if
you could call it that) which relies heavily on myself (hard to
believe, but when AsciiDoc was first released in 2002 there was no Git
or Mercurial).
Despite the best will in the world I just don't have enough spare time
to manage the development adequately (I apologise to submitters for
not not reviewing and integrating your patches over the last six
months or so).
So where to from here? I don't have the answers and I'd be interested
to hear your thoughts on the subject.
Cheers, Stuart
--
Stuart Rackham
--
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.
