Re: [NonGNU ELPA] New package: project-store

Lin Jian <[email protected]> writes:

> Philip Kaludercic <[email protected]> writes:
>
>>>> I've just pushed the package specification to nongnu.git
>>>> and the package should appear in the coming hours.
>>>
>>> Since I get a lot of HTTP 502 from cgit[1] of NonGNU ELPA repo, I choose
>>> to check it by cloning the repo with:
>>>
>>>   git clone --single-branch git://git.git.savannah.gnu.org/emacs/nongnu.git
>>>
>>> The latest commit is the one adding codex-ide and hermes.  Also, I do not
>>> see project-store in the repo.  Is something wrong?
>>
>> Ah, something must have gone wrong yesterday as I was trying to push the
>> package (I was experiencing some networking issues yesterday, it is
>> likely that might have interrupted the "git push")
>
> I just checked again and still project-store is not added to nongnu.git.
>
> Is it just that you forgot to push it again?
>
> Or is the addition postponed due to Stéphane insisting on avoiding
> "store" in the name?  To be clear, I am fine if ELPA maintainers decide
> to reject my first package submission due to that, even if
> contributing.html clearly states that naming, as a soft criteria, is not
> a reason to reject a package.

Yes, I haven't pushed it, because the discussion is still ongoing.  We
can change most things after adding a package, but it is always annoying
to rename a package.

You are right that we don't want to reject a name just based on a
package (except if the package name were something vulgar or vague), but
we never said that we'll at least not _try_ to change your mind and/or
find a compromise if we think that there is a good reason to ;)

> Anyway, I can just distribute my project-store through NixOS, which
> should already cover the majority of targeted users.  Adding it to
> NonGNU ELPA can help a few more other users.  But those a few more users
> being harder to use project-store is not an issue to me.

If you are thereby saying that you are committing to the name, and don't
foresee any chance that you'll change your mind, then I guess we might
as well add the package spec to nongnu.git.  As soon as you add the
package to Nix it will effectively be a reserved name in the global
Elisp namespace anyway.  TBH think that would be regrettable, since
Stéphane did raise good points that -- regardless of where the package
is hosted -- indicate that it would be better to use a less generic
name.

Just to know: Is there a rush in publishing this package, such as an
upcoming release of Nix where this package would either be added to the
distribution before some cutoff date?