[cmucl-imp] Reverting changes to listen (Fixes #143)

[Jon Boone]

Thanks for the response, Carl.

I’m struggling to build the appropriate context in which to understand a number of things about this particular project, such as:

• Who are the known user communities?
• What are their primary use cases?
• What platform(s) do they use?
• What is the most important principle to consider in attempting to fix a reported bug?
• What is the most important principle to consider in attempting to add a feature?
• What is the most important principle to consider when proposing an architectural change to the project?


— jb
On May 29, 2023 at 15:26 -0400, Carl Shapiro <carl.shapiro at gmail.com>, wrote:
> Hi Jon,
>
> I do not recall there ever being a discussion about this.  Small projects tend to be less structured so that might not be a surprise
>
> What are your interests?
>
> Carl
>
> > On Mon, May 29, 2023 at 11:37 AM Jon Boone <ipmonger at delamancha.org> wrote:
> > > I understand the rationale for reverting the merge associated with closing  Issue #143 — Listen doesn’t signal error when given more than one argument ( gitlab.common-lisp.net/cmucl/cmucl/-/issues/143).
> > >
> > > I’m hoping we can articulate some prioritized principles for the project to assist folks such as myself who are interested in participating in the project.
> > >
> > > Is this a topic that has been discussed before?
> > >
> > > — jb
> > >
> > > — jb
> > > _______________________________________________
> > > cmucl-imp mailing list
> > > cmucl-imp at cmucl.cons.org
> > > https://lists.zs64.net/mailman/listinfo/cmucl-imp