From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: easy tasks ?
Date: Sun, 16 Jul 2017 11:41:35 +0900 [thread overview]
Message-ID: <E2EBBDC7-DEE4-4286-B54F-016648A9ABEA@gmail.com> (raw)
In-Reply-To: <CAM-tV-_YfCSdN=tFkHZR_4k_gCvZjc1bUxvjHtaarf0w340+vQ@mail.gmail.com>
> On Jul 16, 2017, at 11:07, Noam Postavsky <npostavs@users.sourceforge.net> wrote:
>
> On Sat, Jul 15, 2017 at 9:56 PM, Jean-Christophe Helary
> <jean.christophe.helary@gmail.com> wrote:
>> A lot of FOSS projects have a list of tasks for potential contributors that are split between easy/moderate/hard or easy/medium/big. It makes entry into the project easier. Is there such a catalogue for emacs development ?
>
> I tagged a few bugs as "easy", you can see the current list here:
> https://debbugs.gnu.org/cgi/pkgreport.cgi?include=tags%3Aeasy;package=emacs
> So far nobody else has done such tagging, as far as I know, so the
> list is pretty short.
Thank you Noam. I'm guessing there is no general "task" or "rfe" system for emacs development?
In my email, I'm tagging tasks that I said I'd handle or I want to get involved with. But it only covers topics discussed in the past months. I've not yet "discovered" the system that documents where to look for issues I can tackle.
Jean-Christophe
next prev parent reply other threads:[~2017-07-16 2:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 1:56 easy tasks ? Jean-Christophe Helary
2017-07-16 2:07 ` Noam Postavsky
2017-07-16 2:41 ` Jean-Christophe Helary [this message]
2017-07-16 2:54 ` Noam Postavsky
2017-07-16 2:59 ` Jean-Christophe Helary
2017-07-16 3:14 ` Noam Postavsky
2017-07-16 4:02 ` Jean-Christophe Helary
2017-07-16 22:09 ` Noam Postavsky
2017-07-17 0:23 ` Jean-Christophe Helary
2017-07-17 6:29 ` Michael Albinus
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=E2EBBDC7-DEE4-4286-B54F-016648A9ABEA@gmail.com \
--to=jean.christophe.helary@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 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).