This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-12
Channels
- # beginners (63)
- # boot (3)
- # braveandtrue (153)
- # cider (19)
- # cljdoc (2)
- # clojure (80)
- # clojure-dev (25)
- # clojure-italy (73)
- # clojure-losangeles (1)
- # clojure-nl (4)
- # clojure-spec (67)
- # clojure-sweden (1)
- # clojure-uk (83)
- # clojurescript (56)
- # clojutre (11)
- # core-logic (37)
- # cursive (18)
- # datomic (14)
- # editors (10)
- # emacs (13)
- # figwheel-main (11)
- # fulcro (62)
- # graphql (11)
- # jobs (3)
- # klipse (1)
- # leiningen (6)
- # off-topic (91)
- # onyx (7)
- # pedestal (3)
- # portkey (5)
- # re-frame (14)
- # reagent (13)
- # remote-jobs (1)
- # shadow-cljs (111)
- # tools-deps (4)
- # yada (10)
New contributors don't seem to be able to have tickets assigned to them in JIRA. (Or even assign them to themselves.) Have we hit a user-count limit with our JIRA license?
they have to have roles added
I kind of do that on demand or sometimes when we get CAs
who needs it?
I don't think it is critical, but there is a - Martin Kučera with a patch in https://dev.clojure.org/jira/browse/CLJS-2868 (he has a CA signed) - Julio Berina with a patch in https://dev.clojure.org/jira/browse/CLJS-2849 (CA status unknown) - Eugene Kostenko with a patch in https://dev.clojure.org/jira/browse/CLJS-2729 and https://dev.clojure.org/jira/browse/CLJ-2332 (CA status unknown) Just trying to help with validating that CAs are done, and follow up on patches, etc. and ran into this inability to communicate with contributors via the JIRA tickets.
@mfikes I’ve given all of them rights to edit tickets, which I’m happy to do to anyone doing actual work on tickets, even if their CA status is unknown. CA is important at the point where we accept a patch (and generally knowing that before you review a patch is preferred as if they don’t have signed CA, you should be developing a clean patch, not one informed by their patch)
also! I have made you a jira admin so you can do this yourself now
There is something sophisticated that Google is doing to robotically manage CAs (see https://github.com/google/closure-library/pulls)
you click the Administration link in the upper right, then Users, then search. Or you can click on a user’s name in the ticket to get specifically to that user. Once you get to the user, click Edit Groups. Then select “clojure-dev” and “jira-developers” in the list on the left and click the “Join” button
clojure-dev is a group used in confluence and jira-developers is a group used in jira (they share a SSO Crowd directory)
if you want to figure out how that works, write it down and let me know :)
I think there might be a note about this admin stuff somewhere…
Yeah, perhaps we can automate CLAs a bit more. I can dig and see if what they are using is open source.
https://dev.clojure.org/display/community/Adding+a+new+contributor
Whatever googlebot
is doing here is pretty cool: https://github.com/google/closure-library/pull/877#issuecomment-364798253
only scalability issues :)
Parallelism factor has just been increased by 1 by adding Mike as a JIRA admin +1
Bah! It seems that all of the CLA management systems only work with this newfangled system the kool kids are using, which is based in PRs.
never heard of it
as a grumpy old programmer, I assume that’s probably crap. rcs or death.