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

[Po Lu <luangruo@yahoo.com>]

João Távora <joaotavora@gmail.com> writes:

> So the lure of the "GitHub-model" is deceptive. More likely some devs
> of some successful projects there are just sticking to it because they
> happen to already know it very well and resist changing.  Just like
> many devs in "our" camp.  More likely those "GitHub model" devs just
> don't dig the vibe around these parts that much -- perfectly
> legitimate -- but are a bit afraid to say so, so they say it's the CA
> requirement and the patches model.
>
> After all, this mailing list, for all the talk of obsolete mails etc,
> is very heavily participated and even more heavily read.  Just the
> fact of having one's work scrutinized in such a big forum is not to
> everyone's liking.  And that's perfectly legitimate, too.  Developing
> a package outside Emacs is a liberating experience by comparison.
> Inside, there is a completely new set of concerns, completely
> independent of the forge you use.  The format of manuals, coding
> style, commands you can and cannot add, even the upgrade options you
> offer to your user base are affected.  As I've recently learned,
> moving a package from the outside to the inside is a bit like getting
> married: you better be prepared to give some things up and fight
> actively for others.  You have to love Emacs very much to make it work
> ;-)
>
> In my personal case I find no significant difference in working with
> either model.  I find certain GitHub discussions and issue threads
> just as pleasant or toxic as the things I find here.  I find email
> reviews of patches no more complicated than those sophisticated boxes.
> Trivial patches to typos and stuff are indeed a little harder to apply
> here compared with the the big green button.  But then trivial patches
> aren't the things moving a project forward anyway.  I could switch to
> SourceHut, of course, or anything -- including GitHub.  It won't make
> that big of a difference I think.

Very well said, thanks.

Compounding all of this is the additional impediment imposed by GitHub's
demand that all users of their system register an account irrespective
of their intent, whether it be to merely report a bug or to create a new
repository.  This has undoubtedly played the role of a deterrent to the
detriment of users and developers alike.