emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Avdi Grimm" <avdi@avdi.org>
To: Manish <mailtomanish.sharma@gmail.com>
Cc: Bernt Hansen <bernt@norang.ca>,
	emacs-orgmode@gnu.org, Richard Riley <rileyrgdev@googlemail.com>,
	Ben Alexander <bva@alexanderonline.org>
Subject: Re: Re: How you can help
Date: Fri, 24 Oct 2008 14:41:32 -0400	[thread overview]
Message-ID: <ecbcf0fb0810241141hb114931n4afb7bd8aa791f71@mail.gmail.com> (raw)
In-Reply-To: <e7cdbe30810240927p51634ad4g925a85dfbd4268c3@mail.gmail.com>

On Fri, Oct 24, 2008 at 12:27 PM, Manish <mailtomanish.sharma@gmail.com> wrote:
> Let me take a step back and think aloud why we need a bug-tracking and
> testing system (if only to clarify my understanding) and who/when does
> it help.  Following scenarios come to mind (and how they can be
> handled best (again only my limited understanding)):

First of all, bug tracking are completely separate beasts, and should
be considered separately.  You can have either one without the other.

Second:  I don't care as much about bug tracking, except for the
following case: if there is a bug tracker and I'm feeling bored and
want to contribute a little, I'll check it for something that I think
I can fix.  If there is no such list, I won't do this, and I'll
contribute less.  I do *not* follow the mailing list closely enough to
pick up bugs from there except by sheer chance, and this is not going
to change.  I really don't care where or how the list is kept, so long
as there is a list.

Third, regarding testing.  I'm a coder, I know some ELisp, I *love*
org-mode, and I would like to contribute.  That said, I am completely
uninterested in doing manual QA for Org.  I am not going to go
clicking around just to look for broken behavior.  I have neither the
time nor the interest.  However, if there is an automated test suite I
can promise you that a) I will run it before submitting any change I
make; and b) I will add new tests to cover any functionality I add.

However, you should take all of this with a grain of salt because I
haven't submitted any code at all yet.

-- 
Avdi

Home: http://avdi.org
Developer Blog: http://avdi.org/devblog/
Twitter: http://twitter.com/avdi
Journal: http://avdi.livejournal.com

  reply	other threads:[~2008-10-24 18:41 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23 12:04 How you can help Ben Alexander
2008-10-23 13:43 ` Bernt Hansen
2008-10-23 15:04   ` Sebastian Rose
2008-10-23 15:49     ` Richard Riley
2008-10-23 16:22       ` Ben Alexander
2008-10-23 17:02       ` Sebastian Rose
2008-10-24 12:13         ` Richard Riley
2008-10-24 15:39           ` Sebastian Rose
2008-10-24 16:27           ` Manish
2008-10-24 18:41             ` Avdi Grimm [this message]
2008-10-23 19:13       ` Avdi Grimm
2008-10-24 12:19         ` Richard Riley
2008-10-23 16:19     ` Bernt Hansen
2008-10-24  5:05       ` Carsten Dominik
2008-10-23 17:01   ` Jason F. McBrayer
2008-10-23 23:46     ` Eric Schulte
2008-10-23 14:20 ` Sebastian Rose
2008-10-23 14:50   ` Manish
2008-10-23 15:46     ` Eric Schulte
2008-10-23 16:18       ` Avdi Grimm
2008-10-23 14:55   ` Ben Alexander
2008-10-23 16:26     ` Sebastian Rose
2008-10-23 16:42       ` Avdi Grimm
2008-10-23 17:33         ` Sebastian Rose
2008-10-23 19:10           ` Avdi Grimm
2008-10-24 21:09           ` Tom Breton (Tehom)
2008-10-24 18:33         ` Ben Alexander
2008-10-24 18:44           ` Avdi Grimm
2008-10-24 19:02             ` Jeff Mickey
2008-10-26 19:49             ` org-cycle broken when cursor is at ellipses Ben Alexander
2008-10-26 21:31               ` Cameron Horsburgh
2008-10-27  8:47                 ` Carsten Dominik
2008-10-27  8:47               ` Carsten Dominik
     [not found]       ` <D43ED86C-EFD4-4BA8-8528-4F82DB11D625@alexanderonline.org>
2008-10-23 17:12         ` How you can help Sebastian Rose
2008-10-23 15:08 ` Sebastian Rose

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=ecbcf0fb0810241141hb114931n4afb7bd8aa791f71@mail.gmail.com \
    --to=avdi@avdi.org \
    --cc=bernt@norang.ca \
    --cc=bva@alexanderonline.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mailtomanish.sharma@gmail.com \
    --cc=rileyrgdev@googlemail.com \
    /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).