Re: New Package for NonGNU-ELPA: clojure-ts-mode

[Danny Freeman <danny@dfreeman.email>]

Eli Zaretskii <eliz@gnu.org> writes:
> Don't agree because they oppose that as a matter of principle, or
> don't agree because they think it's too much work?

A matter of principle.

> I'm suggesting to look at the numbers and see who of the contributors
> really needs to sign the legal paperwork.  The results might surprise
> us, but even if they don't, what possible harm could it do to collect
> those LOC counts for each contributor, so that we all are on the same
> page regarding the magnitude of the problem?
>
> Or let me turn the table ans ask: suppose no CA paperwork was needed:
> would they still oppose adding these modes to Emacs?

Yes.

> Maybe the people involved don't really want to see this in core even
> if possible.  But if so, I guess they are unwilling to contribute the
> package to Emacs, which makes this whole discussion futile and
> pointless to begin with.

Even if it's possible, I know the consensus is that we do not want the
package in the core right now. I don't see that consensus changing.

>> Clojure-mode and cider were never moved to the core for the same
>> reason. I have already had this conversation with them a number of
>> times but was unable to make a convincing argument.
>
> What are the counter-arguments?

I will try to re-summarize the arguments in my own words:

1. Copy right assignment paper work is a barrier to contribution.
2. Cider/clojure-mode/inf-clojure/clojure-ts-mode are all developed by
the same group of people. Keeping them under the same development model
is easier to manage and facilitates coordinating changes across all the
packages. Putting one of these in the core would make this harder.
3. Non-GNU ELPA makes it easy for people to get these packages without
much trouble, since it one of the default package repositories the Emacs
ships with.

I agree with the second/third points. We would like to eventually
have clojure-ts-mode be able to take the place of clojure-mode as a
dependency of the other packages like cider. Keeping it under the same
development model is the right choice to reach that goal IMO. Non-GNU
ELPA and licensing with GPL3 is a good compromise, where we keep the
clojure emacs development model, but still have things relatively easy
to get started with out of the box.

Thank you,
-- 
Danny Freeman