One process that could be made a little easier is the contribution of code documentation and suggested improvements of doc-strings.
New or improved doc-strings do not change any functionality, impact any tests, require peer review… If we could simply suggest new doc-strings for example in the JIRA-issue, have enough eyeballs stare at it, improvements, amendments…, then after sign-off, a committer could simply copy&paste this approved enhancement in the official code. Low-impact and it could make it easier to get community involvement and contributions for clojure & clojurescript's documentation, which arguably could use a little patch here and there. Having to go thru the whole official patch process to suggest an improved docstring is a bit much… and god forbid that you have to thru that multiple time before all the , and . are approved. -FrankS. On Jan 18, 2013, at 1:33 PM, Andy Fingerhut <andy.finger...@gmail.com> wrote: > The issue that Clojure, its contrib libraries, and ClojureScript do not > accept github pull requests has been brought up several times before on this > email list in the past. Feel free to search the Google group for terms like > "pull request". Short answer: Rich Hickey prefers a workflow of evaluating > patches, not pull requests. It is easier for him. You aren't likely to > change his preference on this issue. That choice wasn't made in order to > make it harder on contributors. > > Instructions on creating patches for Clojure are under the heading > "Developing and submitting patches to Clojure and Clojure Contrib" on this > web page: > > http://dev.clojure.org/display/design/JIRA+workflow > > I suspect they are quite similar for ClojureScript, but I haven't submitted a > ClojureScript patch before to know for sure. > > Andy > > On Jan 18, 2013, at 1:01 PM, Irakli Gozalishvili wrote: > >> I have being trying to engage community and to contribute to clojurescript >> for a while already, >> but so far it's being mostly frustrating and difficult. I hope to start >> discussion here and maybe >> get some constructive outcome. >> >> ## Rationale >> >> I'm primarily interested in clojurescript and not at all in clojure, because >> of specific reasons (that >> I'll skip since their irrelevant for this discussion) dependency on JVM is a >> problem. Removing >> that's dependency is also my primary motivation to contribute. >> >> ## Problems >> >> - I do understand that most of the clojurescript audience is probably also >> interested in clojure, >> but please don't enforce that. Have a separate mailing list so that people >> interested in >> clojurescript and not clojure could follow relevant discussions without >> manually filtering out >> threads. >> >> - What is the point of being on github if you don't accept pull requests and >> require I do understand >> that there maybe specific reasons why jira flow was chosen, but seriously >> that's another ball >> thrown at potential contributor to joggle. Not to mention that there are >> several options how >> jira and github could be integrated. >> >> - My latest attempt was to configure travis.ci for integration tests >> https://github.com/clojure/clojurescript/pull/21 >> >> Integration tests are great specially because they run on every pull >> request and post details back >> into pull requests. This also means that lot of local test run time can be >> saved. Not to mention that >> for clojurescript tests you need JVM, v8, spidermonkey and more… >> >> If these things are intentionally made hard to stop new people with more >> clojurescipt interests then please >> make it more clear, cause otherwise it just a motivation killer. >> >> Thanks >> -- >> Irakli Gozalishvili >> Web: http://www.jeditoolkit.com/ > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en