Hi Paul, Thanks, good to know. Sorry for the misleading email.
Cheers, Ivan. On 21 April 2011 08:47, pmbauer <paul.michael.ba...@gmail.com> wrote: > Ivan, > clojure/core use a different workflow than is typical for github > projects. > The github readme doesn't indicate, but you may find the process here: > > http://clojure.org/contributing > http://clojure.org/patches > > Cheers, > pm > > On Apr 20, 1:44 am, Ivan Koblik <ivankob...@gmail.com> wrote: > > Hello Konrad, > > > > Git workflow is a little bit different. You don't really need commit > rights > > to contribute. I found a rather nice explanation of Git workflow here: > http://www.eqqon.com/index.php/Collaborative_Github_Workflow > > > > Hope it helps. > > > > Cheers, > > Ivan. > > > > On 19 April 2011 16:40, Konrad Hinsen <konrad.hin...@fastmail.net> > wrote: > > > > > > > > > On 19 Apr, 2011, at 13:56 , Stuart Halloway wrote: > > > > > >> Concerning my own modules in old contrib, there are three that I use > > > myself and that I am planning to maintain, independently of where they > will > > > end up: > > > >> - clojure.contrib.monads > > > >> - clojure.contrib.macro-utils > > > >> - clojure.contrib.generic > > > > > > There is an empty repos already waiting for your macro utils: > > >https://github.com/clojure/tools.macro > > > > > Great, thanks, I'll start with that one. Monads depend on it anyway. > But I > > > need commit permissions, which I probably don't have, but I don't even > know > > > how to find out without trying to do a commit. Can you please add me in > the > > > right place? My github account is khinsen. > > > > > > I have put some suggested names for the other new projects at > > >http://dev.clojure.org/display/design/Contrib+Library+Names. Please > review > > > and comment, either there or here on the list. > > > > > It seems that for now the top-level namespaces (well, next-to-top) are > > > - clojure.core > > > - clojure.data > > > - clojure.java > > > - clojure.tools > > > > > I would like to suggest a new one, clojure.control, for control > structures. > > > This would be the natural home for monads, but also for parallelization > > > frameworks and even for threading macros. None of this really fits into > > > "data" or "tools". > > > > > If the goal is to keep the number of top-level namespaces as small as > > > possible, I'd even propose to put clojure.contrib.generic under that > label. > > > Otherwise, I'd propose yet another namespace, clojure.interfaces, where > the > > > various submodules of generic would find their home next to other > protocols > > > and interfaces of general interest. > > > > > Konrad. > > > > > -- > > > 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 > -- 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
