unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Hugo Thunnissen <devel@hugot.nl>
Cc: emacs-devel@gnu.org
Subject: Re: Developing a PHP package
Date: Sat, 04 Sep 2021 15:46:22 -0400	[thread overview]
Message-ID: <jwvo898dtcd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87fsuk41vu.fsf@hugot.nl> (Hugo Thunnissen's message of "Sat, 04 Sep 2021 18:44:05 +0000")

>> I'll let Emacs maintainers decide whether they want it in the core, but
>> I'd be happy to add it to GNU ELPA.  In both cases we'd first need you
>> to sign some copyright paperwork anyway.  If you're OK with that, please
>> fill the form after my sig and send it to the FSF as instructed so they
>> can send you the appropriate paperwork to sign.
> Great, elpa is probably the best place to start anyways :).
> That papwerwork won't be a problem.

Excellent.  Let me know when the paperwork is done.

> It is my understanding from reading back a bit in in the mailing list
> archives that php-mode cannot be merged into Emacs, so I thought that
> maybe it would make sense use this as the base for a new PHP mode.
> I would still have to see whether implementing that is actually practical
> though.

Indeed, there are some issues.  This said, `php-mode` is now in NonGNU
ELPA, so an GNU ELPA package is now allowed to depend on `php-mode`.

But that's not necessarily what I had in mind.  I was just thinking of
making sure that the two package collaborate.  E.g. maybe the code in
the current `php-mode` could be split into a part (call it `php-core`)
for which we could get the paperwork (and hence put into GNU ELPA) and
which both packages can use, and try and move as much code as possible
into that `php-core`.

BTW, you might also want to take a look at `phps-mode` which is in GNU ELPA.

>> Do you have a Git repository for your code somewhere?
> I do now! https://git.sr.ht/~hugot/phpinspect.el. Excuse the lack of
> documentation, I haven't found time to write much of that yet.

Thanks.  I'll try and take a quick look at it when I find the time.


        Stefan




  reply	other threads:[~2021-09-04 19:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-04 16:37 Developing a PHP package Hugo Thunnissen
2021-09-04 16:51 ` Stefan Monnier
2021-09-04 18:44   ` Hugo Thunnissen
2021-09-04 19:46     ` Stefan Monnier [this message]
2021-09-05  7:40   ` Lars Ingebrigtsen
2021-09-05  8:44     ` Juri Linkov
2021-09-05  9:19     ` Eli Zaretskii
2021-09-04 17:21 ` Dmitry Gutov
2021-09-04 17:26 ` Eli Zaretskii
2021-09-04 18:52   ` Hugo Thunnissen

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=jwvo898dtcd.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=devel@hugot.nl \
    --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).