All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Squashing bugs!
Date: Tue, 4 Jun 2019 18:22:14 -0400	[thread overview]
Message-ID: <20190604222214.GA20929@chatter.i7.local> (raw)
In-Reply-To: <4bc7ff3c-d190-f9a0-5088-9dc99ab7741d@linuxfoundation.org>

On Tue, Jun 04, 2019 at 04:02:21PM -0600, Shuah Khan wrote:
>>>>May I recommend using a project like git-bug [1] instead of a 
>>>>mailing
>>>>list?
>>>
>
>I experimented with git-bug a bit. Doesn't look like it is mature enough
>for our use. It depends on golang-go
>
>I would like to have the option to build from sources, the instructions
>are rather poor and couldn't build following those.
>
>Is there another git-bug like option we can look into?

If there exists one, I'm unaware of it, unfortunately. The right person 
to talk to about developing something like this would be the author of 
Public-Inbox (Eric Wong), who digs distributed systems and would 
probably love working on something like this.

However, I have been unsuccessful in getting LF to fund such development 
projects, and he's certainly not in a position to work on something like 
this for free.

Hey, you work at LF now. Maybe you'll have more luck convincing The 
Right People that this is important work that would greatly benefit the 
Linux community? :)

-K

  reply	other threads:[~2019-06-04 22:22 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 23:30 [Ksummit-discuss] [MAINTAINERS SUMMIT] Squashing bugs! Shuah Khan
2019-05-31 12:01 ` Laura Abbott
2019-05-31 15:56   ` Shuah Khan
2019-06-03  5:01     ` Leon Romanovsky
2019-05-31 22:15   ` Kees Cook
2019-06-03 10:42     ` Jan Kara
2019-06-04 18:29       ` Laura Abbott
2019-06-03 16:48     ` Shuah Khan
2019-06-02 18:09   ` Sasha Levin
2019-06-03 17:25     ` Shuah Khan
2019-06-03 18:09       ` Konstantin Ryabitsev
2019-06-03 19:32         ` Shuah Khan
2019-06-03 20:48         ` Linus Torvalds
2019-06-03 21:10           ` Sasha Levin
2019-06-03 21:15             ` Jiri Kosina
2019-06-03 21:23               ` Linus Torvalds
2019-06-03 21:28                 ` Jiri Kosina
2019-06-03 22:11             ` Mark Brown
2019-06-04 17:16               ` Shuah Khan
2019-06-05  9:27                 ` Mark Brown
2019-06-05 11:48                   ` Geert Uytterhoeven
2019-06-05 18:16                     ` Shuah Khan
2019-06-05 13:19                 ` Sasha Levin
2019-06-05 19:05                   ` Shuah Khan
2019-06-04 18:09             ` Laura Abbott
2019-06-05 12:49               ` Sasha Levin
2019-06-04 21:43           ` Konstantin Ryabitsev
2019-06-04 22:02             ` Shuah Khan
2019-06-04 22:22               ` Konstantin Ryabitsev [this message]
2019-06-05 17:54                 ` Shuah Khan
2019-06-03 20:59       ` Sasha Levin
  -- strict thread matches above, loose matches on Subject: below --
2019-05-29 22:34 Shuah Khan

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=20190604222214.GA20929@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=skhan@linuxfoundation.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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.