emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "James R Miller" <james.ryland.miller@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: issue tracker?
Date: Tue, 19 May 2020 18:22:46 -0500	[thread overview]
Message-ID: <6bc12cfc-b55c-429e-8e50-59769fb51023@www.fastmail.com> (raw)
In-Reply-To: <ra1h8d$2ij$1@ciao.gmane.io>

> This idea that the tools used by a potential contributor are inadequate
> misses the point. If the intention is to keep a project going, or better
> yet increase the number of contributors, tools have to be used that will
> be convenient and familiar to those thinking about contributing.
> 
> For better or worse, the workflows embodied by Github and Gitlab are
> familiar to the current generation of potential contributors upon which
> sustaining a project will depend.
> 
> Holding up the 'Linux uses email for development and thus any project
> doing similar is right' fails to recognize the peculiar nature of the
> Linux kernel (and its developers) and neglects the thousands of projects
> that have increased their visibility and participation by using tools
> such as Github. I agree that Github/Gitlab may not be the best choice
> owing to their stance or implementation related to software freedom, but
> an honest discussion of alternatives seems prudent.

This is the point I am trying to (un-eloquently) make. I'm seeing a bunch of 
younger coders interested in emacs (mostly spacemacs and doom); but, 
they get frustrated with the ancient (to them) dev practices.  I'm not 
advocating any rash decisions; simply, whether the project would benefit
from incorporating some sort of simple issue tracker, so that new 
contributors could readily see open tasks / issues / submit bug reports.

My biggest issue with a ML only approach is that it's not easy to see what's 
an open issue unless you spend a long time searching and reading the ML. 
And I feel that that time could be better spent learning the code base
instead of reading the ML. 

-- 
 James Miller
james.ryland.miller@gmail.com


  reply	other threads:[~2020-05-19 23:23 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18 21:24 issue tracker? Anthony Carrico
2020-05-18 22:21 ` Nick Dokos
2020-05-18 23:13   ` James R Miller
2020-05-19  7:33     ` tomas
2020-05-19 14:02       ` James R Miller
2020-05-19 14:05         ` James R Miller
2020-05-19 14:53           ` tomas
2020-05-19 14:58       ` Bruce D'Arcus
2020-05-19 16:45         ` Timothy
2020-05-19 16:57         ` Russell Adams
2020-05-19 17:03           ` Timothy
2020-05-19 17:29             ` Russell Adams
2020-05-19 18:50               ` James R Miller
2020-05-19 19:42                 ` Eric Abrahamsen
2020-05-19 20:17                   ` Roland Everaert
2020-05-19 20:47                     ` Diego Zamboni
2020-05-19 21:28                     ` Eric Abrahamsen
2020-05-19 19:48                 ` Russell Adams
2020-05-19 20:14                   ` Trey Ethan Harris
2020-05-19 20:57                   ` gyro funch
2020-05-19 23:22                     ` James R Miller [this message]
2020-05-20  9:22           ` Eric S Fraga
2020-05-20  9:40             ` Detlef Steuer
2020-05-20 11:12               ` Stefan Nobis
2020-05-20 16:41                 ` Jud Taylor
2020-05-20 18:55                   ` gennady.uraltsev
2020-05-20 22:05                     ` Bob Newell
2020-05-21  8:10               ` Nicolas Goaziou
2020-05-21 11:21                 ` Bruce D'Arcus
2020-05-21 14:46                 ` Kévin Le Gouguec
2020-05-21 16:31                   ` Eric Abrahamsen
2020-05-22  8:17                     ` Roland Everaert
2020-05-22 14:53                       ` Anthony Carrico
2020-05-23 12:57                         ` Roland Everaert
2020-05-23 13:14                           ` Russell Adams
2020-05-25 11:20                             ` Roland Everaert
2020-05-26 12:34                               ` Robert Pluim
2020-06-01 14:40                       ` Bastien
2020-06-01 14:36                     ` Bastien
2020-05-26 19:17               ` Matthew Lundin
2020-06-01 14:43                 ` Bastien
2020-05-27 17:59         ` Mario Frasca
2020-05-27 18:12           ` Russell Adams
2020-05-27 18:48             ` Eric Abrahamsen
2020-05-31  8:49           ` Russell Adams
2020-06-01 14:45           ` Bastien
2020-06-01 15:46             ` Mario Frasca
2020-06-01 15:53               ` Bastien
2020-06-01 16:28                 ` Mario Frasca
2020-06-01 16:54                   ` Russell Adams
2020-06-02 11:57                   ` Bastien
2020-06-05 22:44                     ` Mario Frasca
2020-06-06  7:57                       ` Bastien
2020-06-06 16:15                         ` Mario Frasca
2020-06-07  9:38                           ` Bastien
2020-06-07 13:50                             ` Mario Frasca
2020-06-08  9:11                               ` Bastien
2020-05-21  2:35 ` Anthony Carrico
2020-05-21  3:12   ` James R Miller
2020-05-21  5:33     ` Russell Adams
2020-05-21  7:31     ` Kévin Le Gouguec
2020-05-21 14:18       ` Anthony Carrico
2020-05-21 14:38         ` tomas
2020-05-21 14:38         ` Anthony Carrico
2020-05-21 15:05           ` Kévin Le Gouguec
2020-05-22 16:56   ` Ken Mankoff
2020-05-26 19:36   ` Matthew Lundin
2020-06-01 14:59 ` Bastien
2020-09-14  5:23   ` Bastien
  -- strict thread matches above, loose matches on Subject: below --
2020-06-02 11:38 Vladimir Nikishkin
2020-06-02 11:55 ` Bastien

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=6bc12cfc-b55c-429e-8e50-59769fb51023@www.fastmail.com \
    --to=james.ryland.miller@gmail.com \
    --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).