@alexmiller: I added some tests to http://dev.clojure.org/jira/browse/CLJ-1562. This is my first patch to Clojure so feedback welcome!

Great! I will take a look tomorrow. Have you signed a contrib agreement?

yes

Hi, can I ask a question?

(run! reduced (range)) returns 0, though the docstring says it “returns nil”. Is this the intended behavior?

@athos not sure if it’s intended behaviour, but looking at the source it will return whatever (proc <last-value-in-coll>) returns. So for example (run! identity [1]) returns 1, not nil as the doc suggests

@jonas: exactly

@athos: I created an issue for it here: http://dev.clojure.org/jira/browse/CLJ-1761

@jonas: Thanks!

jonas: I'd say the run! thing is definitely a simple bug, thx for the ticket.

Do Clojure and ClojureScript have an official birthday? If not, it seems a serious shortcoming: http://fsharpforfunandprofit.com/posts/happy-fsharp-day/ Should I open a ticket?

@alexmiller: @jonas: added tests to http://dev.clojure.org/jira/browse/CLJ-1761

Thx

@alexmiller: I'm sure it's been discussed and described before, but I haven't found it, so I'll ask again. How come Clojure isn't developed with git pull-requests (and git issues)

It would be better if the patch retained a commit with Jonas's original contribution

Rich prefers reviewing patches to pull requests

Fair enough

There were concerns at one point over whether a pr was a clear point of contribution but that was in the early days of pull requests and may be less of a concern now

concerning the patch with tests, you'd like to have two commits in there? one for Jonas and one for me?

That would be nice to retain his contribution

Or two patches

And re github issues, at the point where the decision was made, github issues were really basic. I'm still not sure they are up to the task although they have come a long way.

I think you have quite a workflow going on in Jira, which might be difficult to duplicate in github issues, although I'm not an expert on the subject.

I know lots of people don't like jira but I like it better than github issues for doing real tracking.

Although I wish we were actually using the workflow features jira actually has

In danger of committing internet-suicide, I'll admit to liking Jira

I just find working with pull-requests easier than submitting patches.

If I would like to contribute, what’s a good place to jump in? I’m looking at the jira right now and there are a lot of issues, are there any markers for easy or just documentation fixes?

@chris: I do believe there is.

http://dev.clojure.org/jira/secure/IssueNavigator.jspa?mode=hide&amp;requestId=10308

There is some sort of low hanging fruit thingy as well. I'll see if I can find it...

thanks

There is of course this you'll need to read:

http://dev.clojure.org/display/community/Contributing

where I found this:

http://dev.clojure.org/jira/secure/IssueNavigator.jspa?mode=hide&amp;requestId=10617

ok, awesome, thanks

Not that many marked as newbie though...

I read the contributing guide, but apparently not closely enough

there is also http://insideclojure.org/2015/05/01/contributing-clojure/

It would be cool if this channel could be used to solicit help from the community.

Both ensime and cider have tagged some of their issues with low hanging fruits.

Which is kind of nice for people starting out

I think the idea here is really to supplant the almost dead clojure-dev mailing list as a communication media

about other projects, maybe it's better to stick to their official communication channels

I would suggest, for example, to create a #cider-dev

but #C0617A8PQ folks already use gitter to do that

Oh, I wasn't talking about getting cider-stuff in here, I was suggesting that the issues in Clojure could be tagged in the same way, so that it'd be easier for people to start contributing.

btw I think the #C0617A8PQ people are here on Clojurians already.

@slipset: ooohhh got it. Yeah, I agree that this could be really nice!

there is a #C0617A8PQ, but AFAIK user centric. Development discussions are made on Gitter (at least the last time I checked it out)

anyway, back to clojure-the-lang....

I like the idea of tagging issues on Jira what we need to do to be able of doing that?

@alexmiller: do you are in favor of this issue tagging?

I already do that with the newbie tag

it's just hard to find issues that are a) suitable for newbies b) don't quickly gain patches

cider questions do not go here - use #C0617A8PQ etc for that

the idea of this room is also not to supplant the clojure-dev mailing list but to serve as an additional channel

@alexmiller: supplant was a bit stronger of my part - the mailing list is still a good channel for long-form reasoning, like the last conditional reader stuff

there are many people on the mailing list (like Rich) that are not here and that group is archived and searchable (whereas this one is less so). but sometimes live chat is useful. In the past that's happened on #C03S1KBA2 irc.

I'm happy to use all of them

another place to look for things useful to work on are Triaged tickets with no patch

http://dev.clojure.org/jira/secure/IssueNavigator.jspa?reset=true&amp;jqlQuery=project%3DCLJ+and+status%3Dopen+and+Approval%3DTriaged+and+Patch+is+null+order+by+issuetype+desc%2C+priority+desc

is a quick search for those

thanks @alexmiller

nice filter @alexmiller, thanks!

Running through that list, shouldn't http://dev.clojure.org/jira/browse/CLJ-1542 be closed since http://dev.clojure.org/jira/browse/CLJ-1038 is closed?

@slipset: re 1542, dunno thus left there for Rich to look at eventually