I don't always remember how to create a patch, either, but I do remember where to go to get the short instructions to do so in case I forget. In case you are curious, the process for creating a patch is documented here, under the heading "Developing and submitting patches to Clojure and Clojure Contrib". This page is linked to from the contributing and patches pages you give links for in your message.
http://dev.clojure.org/display/design/JIRA+workflow On my screen it is about 2 1/2 screenfuls. If you would prefer not to go through those steps, I understand, but it isn't terribly arcane. Andy On Oct 6, 2012, at 9:02 AM, Jay Fields wrote: > The CA process isn't what stops me from contributing, the post a patch > to Jira is what seems broken to me. I don't even remember how to > create a patch. Clojure is on github - we live in a fork & pull > request world, it's time for Clojure to get on board with that. > > I once noticed that a Clojure fn didn't have a type hint on a return > value. Adding ^String made a substantial performance difference. Not > knowing the process, I forked, and did a pull request. I got this > response: > > "Clojure projects cannot accept pull requests so all issues need to be > logged in the appropriate JIRA project and patches can be accepted > from people who have a signed Contributor's Agreement on file: > > http://clojure.org/contributing > http://clojure.org/patches"; > > Which is informative and correct, but, do you really think I'm going > to go through that trouble? If you said yes, you're wrong. > > Cheers, Jay -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en
