all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Vardhamann B E <be.vardhamann@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Willing to Contribute to Emacs NS-Port Development
Date: Tue, 06 Aug 2024 15:08:18 +0200	[thread overview]
Message-ID: <m2a5hp94u5.fsf@pro2.fritz.box> (raw)
In-Reply-To: <CAKQC1kOSQpuMb4MwWXeRkTT=jUj2Mg1eZxnzFY9Rjv3t7+GOag@mail.gmail.com> (Vardhamann B. E.'s message of "Tue, 6 Aug 2024 16:08:24 +0530")

Vardhamann B E <be.vardhamann@gmail.com> writes:

> Hello devs,
>
> I have had the pleasure of using Emacs on macOS over the past few
> years and have greatly enjoyed it. I recently came across a post on
> Sacha Chua’s blog mentioning the need for more testers and
> contributors for the NS-port. I am willing to contribute my time (2-3
> hours a week) to help with the development of Emacs, as I wish to give
> back to the community.
>
> Although I am not very well-versed in how to test the program, I am
> eager to learn and be of help. Could you please guide me on how I can
> assist or point me towards any resources I need to learn in order to
> contribute effectively?
>
> Thank you,
> Vardhamann

Hi Vardhamann.

I'm not an Emacs maintainer. I'm a macOS user, exclusively, and
sometimes I'm contributing this or that.

From my POV, what is missing are Cocoa (macOS GUI) developers. The Cocoa
port is unmaintained and has serious stability problems, i.e. it freezes
and crashes much too frequently on macOS.

Without someone familiar with Cocoa who can fix things, testing won't
help much.

My 2 cents only, of course.



  reply	other threads:[~2024-08-06 13:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06 10:38 Willing to Contribute to Emacs NS-Port Development Vardhamann B E
2024-08-06 13:08 ` Gerd Möllmann [this message]
2024-08-06 20:28   ` Charles Choi
2024-08-07  0:55     ` Po Lu
2024-08-07  2:53       ` Charles Choi
2024-08-22 20:19         ` chad
2024-08-06 22:00 ` Andrea Corallo
2024-08-17  9:20 ` Eli Zaretskii

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=m2a5hp94u5.fsf@pro2.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=be.vardhamann@gmail.com \
    --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 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.