all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: kristofer@hjelmtorp.se
To: Philip Kaludercic <philipk@posteo.net>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Maintenance of cobol-mode.el on ELPA
Date: Sun, 5 May 2024 21:22:35 +0200 (CEST)	[thread overview]
Message-ID: <1112921232.105999.1714936955847@office.mailbox.org> (raw)
In-Reply-To: <87wmo8nyd1.fsf@posteo.net>


> 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?

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



  reply	other threads:[~2024-05-05 19:22 UTC|newest]

Thread overview: 16+ 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 [this message]
2024-05-05 19:32         ` Philip Kaludercic
2024-05-06 19:44           ` kristofer
2024-05-06 20:00             ` Philip Kaludercic
2024-05-20  6:42               ` Philip Kaludercic
2024-05-20  6:57                 ` Andrea Corallo
2024-05-20 10:51                   ` kristofer
2024-06-05 19:46                   ` kristofer--- via Emacs development discussions.
2024-06-06  5:48                     ` Eli Zaretskii
2024-06-06  6:22                     ` Philip Kaludercic
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

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

  git send-email \
    --in-reply-to=1112921232.105999.1714936955847@office.mailbox.org \
    --to=kristofer@hjelmtorp.se \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.