-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Asciidoctor #200
Comments
@mojavelinux, we're reviewing here. For reference: gratipay/inside.gratipay.com#563 (comment) I'd suggest linking directly to http://asciidoctor.org/docs/#contribute-to-asciidoctor for onboarding. @whit537, what's the trick for https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+user%3Aasciidoctor -style issue queries to work for people not logged into GitHub? |
It's |
Actually, open is even better. :-) https://github.com/search?q=user%3AAsciidoctor&state=open&type=Issues |
@whit537 agreed, that is a much better view. We still haven't found the best way to present issues that span our numerous repositories. It does get me thinking about creating a page on asciidoctor.org that uses the GitHub Issues API to fetch specially marked issues. The team is in the best position to flag issues that are ready for contribution and that gives the best chance for a newcomer to make sense of what needs to be done. I'll open an issue in asciidoctor.org to track that initiative. |
Agreed. That section could definitely use improvement. We have an open issue for that. asciidoctor/asciidoctor.org#403 |
I have changed those links and approved the team. Welcome to Gratipay! |
Thanks Gratipay team! 🎉 |
https://gratipay.com/Asciidoctor/
(This application will remain open for at least a week.)
The text was updated successfully, but these errors were encountered: