From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] Ticket tracking system for LTP
Date: Tue, 24 Apr 2018 10:48:38 +0200 [thread overview]
Message-ID: <20180424084838.GA18678@rei> (raw)
In-Reply-To: <20180423133840.cj5vah2xlm3urly6@xps>
Hi!
> > * GitHub issues
> > - probably the easiest solution
> > - we can create a specific labels to sort these out
> > - needs GitHub account which everybody has already
> > - some operations could be done only by LTP project members
> > I'm not sure if random users can add labels for example
>
> +1. It meets the requirements (except open source), and is already
> established. To be successful, LTP's github probably needs more
> curation. I see a lot of pull requests and issues opened for a long time
> without any action. This is true of any solution, of course.
Well I should be a bit more proactive there, most of the issues that
stay open for long time are these where the original author lost
interest in getting the changes upstream, quite a few of them could be
closed with "no response" at this point.
> Also, importantly, github is where the developers are (like it or not).
True.
There were two responses so far with two +1 for GitHub so I suppose that
this is the way forward.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2018-04-24 8:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 15:17 [LTP] Ticket tracking system for LTP Cyril Hrubis
2018-04-11 13:15 ` Sebastian Chlad
2018-04-23 13:38 ` Dan Rue
2018-04-24 8:48 ` Cyril Hrubis [this message]
2018-04-24 13:42 ` Petr Vorel
2018-04-24 13:44 ` Cyril Hrubis
2018-04-24 14:04 ` Petr Vorel
2018-04-25 14:29 ` Cyril Hrubis
2018-04-26 1:44 ` Sandeep Patil
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=20180424084838.GA18678@rei \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox