unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Grant Shangreaux <grant@churls.world>
To: emacs-devel@gnu.org
Subject: ruby mode additional packages
Date: Thu, 07 Jul 2022 08:50:02 -0500	[thread overview]
Message-ID: <85bku110qo.fsf@churls.world> (raw)


hello emacs-devel,

i've recently been re-rolling a configuration using only ELPA and
non-gnu ELPA package archives. i primarily work with ruby in my
day-to-day work, and was a bit surprised that many of the packages i've
grown accustomed to are not available, particularly inf-ruby.

i understand that much of it comes from copyright assignment issues, but
i was curious if there is any work to bring some of the ruby support
packages into non-gnu ELPA? i am sort of the de-facto maintainer of the
minitest-emacs package, though i did not write it. i would be
interested in organizing what it takes to get it into non-gnu ELPA.

in addition to that, i started trying to make my own inferior ruby based
off of comint-mode, and while its very basic right now, it does
work. would there be any desire to add a FSF assigned new version of
inferior ruby to ELPA or Emacs proper? what considerations are required
for something like that? i do not want to detract from the work people
put into the existing inf-ruby. i also do not want to cause any issues
with copyright or licensing, for example, using inf-ruby as a basis
to write a new package.

i do have my FSF paperwork in order, and i'd love to contribute what i
can. since i'm in ruby land most often i thought i would ask here to see
where the effort would best be placed. thank you!

-- 
Tokṡa ake
Grant Shangreaux



             reply	other threads:[~2022-07-07 13:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 13:50 Grant Shangreaux [this message]
2022-07-07 15:33 ` ruby mode additional packages Philip Kaludercic
2022-07-08  3:41   ` Grant Shangreaux
2022-07-08  1:10 ` Dmitry Gutov
2022-07-08  3:17   ` Grant Shangreaux
2022-07-10  1:18     ` Dmitry Gutov
2022-07-10 14:24       ` Stefan Monnier
2022-07-10 18:13         ` Bozhidar Batsov
2022-07-11  1:07           ` Dmitry Gutov
2022-07-11  6:28             ` Bozhidar Batsov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85bku110qo.fsf@churls.world \
    --to=grant@churls.world \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).