Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Bugs first, then features. Most users do not edit the issue type or severity fields, so most tickets start marked as bugs, and job 1 is to recategorize them.
  2. Focus on tickets with code. If there isn't code yet, you will have to write it, and have someone else screen it.
  3. No new features during Beta. The most a feature request can hope for during Beta is to be assigned the "Approved Backlog" release
  4. Do the important bugs first. There is no AI query to find these. One obvious criterion for importance is difficulty of workaround. Another is regression. Another is upvoted issues.
  5. Vote up issues you think important.

Fail Fast

Bounce bad tickets as quickly as possible.

...

Reasons to decline a ticket:

Want to Become a Screener?

...

  • Change does more than one thing. Break it up, submit individual problems and patches.
  • Enhancement belongs in a library instead. Be encouraging and redirect the person to an appropriate Contrib (or propose a new Contrib).

...

  • Does not comprehensively consider the root problem. 

The following are required in the ticket. Mark the ticket incomplete if any are missing (or fix the gap if you can):

  1. Clear description of the problem.
  2. For defects, a reproducing case in a basic repl (no gists, no external github projects, no jars, etc unless absolutely necessary due to AOT etc).
  3. For defects, a description of the cause of the problem.
  4. The approach to fixing the problem (or implementing the enhancement). This should explain (as a narrative) the change in the patch.
  5. For changes that have a performance impact, a performance analysis. Results should be in a table showing before and after timings. Example code to reproduce the timings should be either linked or included. Specify the Clojure and Java version used to take the timings.
  6. The name of the patch to consider (unless there is only one patch, and even then, it wouldn't hurt).
  7. Links to background discussions or other relevant material a screener should read.

The following are required in the patch. Mark the ticket incomplete if any are missing:

  1. Patch file should end in .patch or .diff.
  2. Commit message should start with the ticket id and have a brief 1 line description of the change. Optionally, it may have a longer description after that.
  3. Patch should be in proper format and include tests.

Want to Become a Screener?

Screeners are a subset of contributors who are responsible for moving tickets through a review process, and then funneling tickets to the BDFL.

It would be great to have more screeners. If you are interested, just do all the steps described in this document, without actually changing any ticket attributes. Instead, add a comment to the ticket explaining what you would have done to screen it. (Screeners: keep an eye out for such comments, and where sensible provide feedback so that we are grooming more screeners.)

...

Code Block
languagenone
$ git checkout -b freds_fixbug42
$ git am --keep-cr -s --ignore-whitespace < their-patch-file.diff
  • make sure you have a clean local checkout
  • no need to check on multiple OSes (unless the ticket is specific to this)
  • Please If you are committing i.e. you own the lib, please note the importance of -s above, it is important, as it indicates that you are the one accepting this patch.
  • The --keep-cr helps when files being patched contain DOS CR/LF line endings.  It seems to be harmless when it isn't needed, but leave it off or use --no-keep-cr if you suspect it is causing issues.
  • The --ignore-whitespace helps when the only changes made to master since the patch was created are to whitespace in the context lines.  Without this option, some patches will fail to apply.  With that option, screeners can help avoid making contributors update patches merely because some whitespace changed in master.

Once you have a working copy, you should take note of the following kinds of things:

  • Review the code in a diff tool to make sure that nothing extraneous snuck in
  • Make sure compile and tests pass
  • Test the functionality from the REPL
  • Does the patch accomplish the goals stated in the ticket (and any accompanying discuss in Confluence/email/IRC)
  • Is the code in proper style? But remember that Library Coding Standards are guidelines, not fixed laws of the Universe.
  • If questions were raised in the discussion, are they answered in the ticket?
  • Are you happy with the tests, can you follow what they're testing, is there anything missing?
  • Are the tests excessive (introducing dependency on implementation detail)?
  • Does the documentation still seem right to you?
  • Is the implementation idiomatic (if not, explain why, link to examples...)
  • Is the patch performance-sensitive? If so, is the approach appropriate?

...