I do not agree at all with you. Any piece of software that gets used widely needs to be maintained with some formal process otherwise there's no way to insure consistency of future releases. It gets worse as you increase the # of people that can modify code.
Tickets may seem to you as overhead but it's a decent way to track issues and fixes according to release plans. Looking at a bunch of commits in git is limited compared to dedicated ticket logging solutions like Jira. Providing patches attached to the ticket links the ticket to the code in git is much more usable. Refusing pull requests is a way to force issues to be logged in Jira. The main entrance gate is in Jira, not the other way around. Clojure is not the only open source projects driven by a ticket reporting system. This may look as overhead to you but it is still lighter than similar processes in many software businesses. You can report the kind of problems you highlighted on the mailing list so at least others can take ownership of the issue if you do not feel inclined to post it in Jira. Luc > 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 > > On Sat, Oct 6, 2012 at 11:40 AM, Softaddicts > <lprefonta...@softaddicts.ca> wrote: > > This insistence on the so-called "CA pain" seems to me overemphasized. > > It's a one shot process. > > > > Even if it takes 4 weeks for the paper to reach its destination, it does not > > prevent anyone from starting to work on some contribution. The CA > > needs to be in by the time the work is about to get published, not by the > > time > > you start to contribute. > > > > My writing is horrible, worst than a doctor, I hate filling forms by hand > > but I > > was able to fill the CA, stamp it and drop it in the mailbox in less than > > 10 mns. > > > > I live in Canada close to the US, I can understand the frustration if you > > have to drop > > by your local post office if it needs to get stamped over there but one time > > processes like this rarely benefit from an optimization. > > > > I would be surprised that we end up with >250,000 contributors in the next > > 3 years. There is simply not enough Clojure wired brains out there to get to > > numbers like the above. > > > > If it ever happens, you can bet than Clojure Core will come out > > with something to avoid being flooded by papers if it is legally feasible. > > > > Laws in many countries have been slow to move to consider > > electronic formats as legally binding documents. > > This may well be why a written CA is needed considering that contributors > > come > > different countries. What may seem obviously legal in one country may not > > be legal > > at all in another. > > > > Better documentation is to me by far a more urgent priority to attract > > newbies > > than allowing CAs to be submitted electronically given the legal fees > > involved just > > to get an opinion about its feasability. > > > > Luc P. > > > > > >> +1 to lowering the barrier to entry for contributing to the community. > >> > >> One of the much lauded features of Git is that it can be used to create a > >> "network of trust". In principle this means you can open your repo up to > >> anyone, but by being choosy about the pull requests you accept you can > >> control what's going to get in. > >> > >> This is perfect for something like documentation. > >> > >> Also, as it's been said before, a pen and paper CA is a pain. > >> > >> > >> On Friday, 5 October 2012 08:26:39 UTC-5, Mayank Jain wrote: > >> > > >> > > >> > > >> > On Fri, Oct 5, 2012 at 6:54 PM, Michael Klishin > >> > <michael....@gmail.com<javascript:> > >> > > wrote: > >> > > >> >> > >> >> > >> >> 2012/10/5 Michael Fogus <mef...@gmail.com <javascript:>> > >> >> > >> >>> You say that as if it's a bad thing. I'm of the opinion that these > >> >>> kinds of efforts should have a low barrier to contribution and be fun. > >> >>> > >> >> > >> >> My apologies, I did not imply that it is a bad thing, only that it is > >> >> not > >> >> entirely clear what direction the project > >> >> will take. While for CDS it is pretty clear (at least to people who have > >> >> started it). > >> >> > >> >> While we are at this fun stuff, can we also make the CA submission > >> >> process fun? > >> >> > >> > +1 > >> > > >> >> > >> >> -- > >> >> MK > >> >> > >> >> http://github.com/michaelklishin > >> >> http://twitter.com/michaelklishin > >> >> > >> >> -- > >> >> You received this message because you are subscribed to the Google > >> >> Groups "Clojure" group. > >> >> To post to this group, send email to > >> >> clo...@googlegroups.com<javascript:> > >> >> Note that posts from new members are moderated - please be patient with > >> >> your first post. > >> >> To unsubscribe from this group, send email to > >> >> clojure+u...@googlegroups.com <javascript:> > >> >> For more options, visit this group at > >> >> http://groups.google.com/group/clojure?hl=en > >> >> > >> > > >> > > >> > > >> > -- > >> > Regards, > >> > Mayank. > >> > > >> > >> -- > >> 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 > > -- > > Softaddicts<lprefonta...@softaddicts.ca> sent by ibisMail from my ipad! > > > > -- > > 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 > -- Softaddicts<lprefonta...@softaddicts.ca> sent by ibisMail from my ipad! -- 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
