unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: kristofer@hjelmtorp.se
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Maintenance of cobol-mode.el on ELPA
Date: Mon, 06 May 2024 20:00:37 +0000	[thread overview]
Message-ID: <87le4m7lsq.fsf@posteo.net> (raw)
In-Reply-To: <981312274.219842.1715024685288@office.mailbox.org> (kristofer@hjelmtorp.se's message of "Mon, 6 May 2024 21:44:45 +0200 (CEST)")

kristofer@hjelmtorp.se writes:

>> On 05/05/2024 9:32 PM CEST Philip Kaludercic <philipk@posteo.net> wrote:
>> 
>>  
>> kristofer@hjelmtorp.se writes:
>> 
>> >> On 05/05/2024 4:10 PM CEST Philip Kaludercic <philipk@posteo.net> wrote:
>> >> 
>> >>  
>> >> kristofer@hjelmtorp.se writes:
>> >> 
>> >> >> On 05/03/2024 7:42 AM CEST Philip Kaludercic <philipk@posteo.net> wrote:
>> >> >> 
>> >> >>  
>> >> >> kristofer@hjelmtorp.se writes:
>> >> >> 
>> >> >> > Greetings Emacs maintainers.
>> >> >> >
>> >> >> > I noticed in the last update to the Elpa package; cobol-mode.el,
>> >> >> > that is now orphaned and that you are looking for someone to step
>> >> >> > up and maintain it.
>> >> >> >
>> >> >> > I would be willing to take over that role if you would let me. I
>> >> >> > work with COBOL (IBM Enterprise COBOL) in my in daily work and use
>> >> >> > Emacs
>> >> >> > together with cobol-mode.el to do it. My emacs-lisp skills are
>> >> >> > mediocre at best but I will do my best to fix bugs and keep it
>> >> >> > working. But my ambition is to work on the missing features listed in
>> >> >> > the package, update it to include changes in the COBOL standards,
>> >> >> > improve the indentation and maybe in the future work on a tree-sitter
>> >> >> > implementation.
>> >> >> 
>> >> >> That sounds great!
>> >> >> 
>> >> >> > I do have very little knowledge about how a Elpa package like this is
>> >> >> > usually developed and how the commit process works so any information
>> >> >> > and tips are welcomed.
>> >> >> 
>> >> >> Currently the repository is part of elpa.git itself, but if someone else
>> >> >> were to take over maintenance, we could switch it to mirroring some
>> >> >> external repository that you would create.  You can use any Git forge
>> >> >> you like (I'd personally recommend Codeberg or Sourcehut).
>> >> >> 
>> >> >> Any changes you push to that repository will automatically be
>> >> >> synchronised upstream.  To release a new package, you just have to bump
>> >> >> the ";; Version: ..." header at the top of the file.
>> >> >> 
>> >> >> How does that sound like to you?
>> >> >> 
>> >> >
>> >> > That sounds great!
>> >> > I'm in the process of setting up a repository on Sourcehut. I will let
>> >> > you know when it's ready!
>> >> >
>> >> > I guess I just take the files from Elpa (just "cobol.el" from what I
>> >> > can see) and commit it to my new repo?
>> >> 
>> >> I think it would be better if you preserved the history by basing your
>> >> modifications on the branch in elpa.git:
>> >> 
>> >>   git clone -b externals/cobol-mode https://git.savannah.gnu.org/cgit/emacs/elpa.git
>> >> 
>> >> and then pushing that to SourceHut.
>> >> 
>> >
>> > Thanks for the instructions!
>> >
>> > I have created a new repository not at sourcehut; https://git.sr.ht/~hjelmtech/cobol-mode, and made one commit to change the maintainer. 
>> >
>> > Does it look good, or should I change something?
>> 
>> It looks good to me, and the ELPA build system isn't complaining either.
>> If you are ready and there are do objections, I can update elpa.git to
>> mirror your repository.
>> 
>
> I'm ready! Though I still have not received confirmation from FSF on the paperwork, but I do have signed and sent them in.

Oh, I misunderstood that.  In that case we have to wait anyway.  Ping me
when it's done, I assume that anyone with comments on the issue will
have had enough time to send a message until then.

>
>> >> >
>> >> >> > I have recently signed and sent in my FSF papers.
>> >> >> >
>> >> >> > Best Regards
>> >> >> > Kristofer Hjelmtorp
>> >> >> 
>> >> >> -- 
>> >> >> 	Philip Kaludercic on peregrine
>> >> 
>> >> -- 
>> >> 	Philip Kaludercic on icterid
>> 
>> -- 
>> 	Philip Kaludercic on peregrine

-- 
	Philip Kaludercic on peregrine



  reply	other threads:[~2024-05-06 20:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 19:57 Maintenance of cobol-mode.el on ELPA kristofer
2024-05-03  5:42 ` Philip Kaludercic
2024-05-05 10:27   ` kristofer
2024-05-05 14:10     ` Philip Kaludercic
2024-05-05 19:22       ` kristofer
2024-05-05 19:32         ` Philip Kaludercic
2024-05-06 19:44           ` kristofer
2024-05-06 20:00             ` Philip Kaludercic [this message]
2024-05-20  6:42               ` Philip Kaludercic
2024-05-20  6:57                 ` Andrea Corallo
2024-05-20 10:51                   ` kristofer
2024-05-03  6:15 ` Eli Zaretskii
2024-05-05 10:24   ` kristofer

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=87le4m7lsq.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=kristofer@hjelmtorp.se \
    /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).