New theme pack for emacs

New theme pack for emacs

[Bruno Ciccarino]

[-- Attachment #1: Type: text/plain, Size: 471 bytes --]

Good evening, or morning, wherever you are reading, I recently created a
theme pack for Emacs, based on my existing one for Neovim, and I would like
to know, how can I do it so that it is accepted in Elpa/Melpa, now? I sent
the pull request, if anyone could review it and help me get it through, I
would be very grateful, the pull request link is this:

https://github.com/melpa/melpa/pull/9291

I would like to thank anyone who can help me in advance. reply, I'll wait.

[-- Attachment #2: Type: text/html, Size: 649 bytes --]

Re: New theme pack for emacs

[Philip Kaludercic]

Bruno Ciccarino <brunociccarinoo@gmail.com> writes:

> Good evening, or morning, wherever you are reading, I recently created a
> theme pack for Emacs, based on my existing one for Neovim, and I would like
> to know, how can I do it so that it is accepted in Elpa/Melpa, now? I sent
> the pull request, if anyone could review it and help me get it through, I
> would be very grateful, the pull request link is this:
>
> https://github.com/melpa/melpa/pull/9291

We have nothing to do with the MELPA archive.  If you want to, we can
add the package to GNU or NonGNU ELPA.  I would guess you want to add it
to NonGNU ELPA, as the code is licensed under MIT?

There is not much code to comment on, my only question is if
`nekonight-main-color' is supposed to be a user option, or if you could
even define it as a constant?

> I would like to thank anyone who can help me in advance. reply, I'll wait.

Re: New theme pack for emacs

[Richard Stallman]

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > We have nothing to do with the MELPA archive.  If you want to, we can
  > add the package to GNU or NonGNU ELPA.  I would guess you want to add it
  > to NonGNU ELPA, as the code is licensed under MIT?

I don't follow the inference here -- could you explain it?
Specifically, I don't see any reason why it could not be included in
GNU ELPA, if the developers want that and we want that.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)

Re: New theme pack for emacs

[Philip Kaludercic]

Richard Stallman <rms@gnu.org> writes:

> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
>   > We have nothing to do with the MELPA archive.  If you want to, we can
>   > add the package to GNU or NonGNU ELPA.  I would guess you want to add it
>   > to NonGNU ELPA, as the code is licensed under MIT?
>
> I don't follow the inference here -- could you explain it?
> Specifically, I don't see any reason why it could not be included in
> GNU ELPA, if the developers want that and we want that.

My inference is that since the package is not published under GPLv3, the
authors probably didn't intend to add the package to GNU ELPA.  But I
might be mistaken!

To the package author: If the package is to be added to GNU ELPA, all
significant contributors have to sign the FSF copyright assignment [0]
and the package must be relicensed to match that of Emacs.

[0] https://www.fsf.org/licensing/assigning.html

Re: New theme pack for emacs

[Richard Stallman]

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > My inference is that since the package is not published under GPLv3, the
  > authors probably didn't intend to add the package to GNU ELPA.  But I
  > might be mistaken!

If the authors assign the copyright, we would probably relicense it
under GPL-3-or-later -- unless there is some specific reason not to.
I can't think of what might be such a reason, but I don't want to
assert it can't possibly happen.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)