[Openmcl-devel] how to move-on efficiently

R. Matthew Emerson rme at acm.org
Sun Jul 15 13:36:19 PDT 2018

> On Jul 15, 2018, at 1:29 PM, Ralf Stoye <stoye at stoye.com> wrote:
> Hello everyone,
> i just had a look on ccl-tests - nice!
> I would like you (folks at clozure) to create a guideline for participation
> - a recipe how to handle this situations in a well defined way.
> eg. fork ccl, fork ccl-tests, make a bug report, create a test referring to this bug, add a test to ccl-tests …

That’s a fair request.  Within the next few days, I’ll write up a CONTRIBUTING.md file with this sort of information in it.  (I just merged one of your pull requests, incidentally.)

> Please comment on this so we can move on ;-)
> I remember the times when a problemreport on this list was answered nearly in realtime
> and included some highly insightfull explanation by you all, specially by gary byers.
> I miss this ;-)

Me too.

More information about the Openmcl-devel mailing list