emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Samuel Banya" <sbanya@fastmail.com>
To: Bastien <bzg@gnu.org>, "Corwin Brust" <corwin@bru.st>
Cc: Charles Berry <emacs-orgmode@gnu.org>
Subject: Re: Request For Approval To Contribute To Org Mode
Date: Fri, 11 Feb 2022 08:13:37 -0500	[thread overview]
Message-ID: <41319b25-9792-4a3e-8c75-c6af7746c25f@www.fastmail.com> (raw)
In-Reply-To: <878ruhztyd.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]

Hey Bastien,

Sounds good!

I'll take a look at the current issues to see if there are any low hanging fruit.

Also, I'll try looking on the page for any guides for how to submit patches as I have never done anything like that before, but I have seen it done in terms of related emails being sent to the org mailing list and the main Emacs mailing list.

Probably is built into Emacs so it should be cool to learn.

Thanks again Bastien :)

~ Sam

On Fri, Feb 11, 2022, at 3:30 AM, Bastien wrote:
> Hi Samuel,
> 
> sorry for the late answer.  
> 
> To contribute to Org, you can send patches to the mailing list:
> maintainers will review and hopefully accept them.
> 
> Once you have several patches accepted and are comfortable pushing
> changes directly to the Org repository, we will consider giving you
> write access.  But for occasional bug fixing, this is not needed.
> 
> See https://orgmode.org/worg/org-contribute.html for more and let
> us know if this answers your question.
> 
> Best,
> 
> -- 
> Bastien
> 

[-- Attachment #2: Type: text/html, Size: 1748 bytes --]

      reply	other threads:[~2022-02-11 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-06 19:27 Request For Approval To Contribute To Org Mode Samuel Banya
2022-02-06 19:35 ` Corwin Brust
2022-02-08 14:19   ` Samuel Banya
2022-02-11  8:30   ` Bastien
2022-02-11 13:13     ` Samuel Banya [this message]

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.orgmode.org/

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

  git send-email \
    --in-reply-to=41319b25-9792-4a3e-8c75-c6af7746c25f@www.fastmail.com \
    --to=sbanya@fastmail.com \
    --cc=bzg@gnu.org \
    --cc=corwin@bru.st \
    --cc=emacs-orgmode@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/org-mode.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).