From: Shuah Khan <skhan@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Sasha Levin <sashal@kernel.org>,
Laura Abbott <labbott@redhat.com>,
ksummit <ksummit-discuss@lists.linuxfoundation.org>,
skhan@linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Squashing bugs!
Date: Wed, 5 Jun 2019 11:54:40 -0600 [thread overview]
Message-ID: <93cb1eea-fe5e-2ea7-a3b7-8fbea8769583@linuxfoundation.org> (raw)
In-Reply-To: <20190604222214.GA20929@chatter.i7.local>
On 6/4/19 4:22 PM, Konstantin Ryabitsev wrote:
> 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.
>>
I was able to compile with "go" under my home directory finally and run
a few commands on git-bug repo. There is the next step of trying to see
if it works for other repos.
I still have my concerns about dependency on "go" and I would like to
get this to work under a non-home directory structure.
>> 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.
>
Okay.
> 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? :)
>
:)
My thoughts on this are: "we needed a solution yesterday" and we can't
start building a shelter for rain while its raining. We need some
interim solution, even if we choose to explore a long term project
development idea.
thanks,
-- Shuah
next prev parent reply other threads:[~2019-06-05 17:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 23:30 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
2019-06-05 17:54 ` Shuah Khan [this message]
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=93cb1eea-fe5e-2ea7-a3b7-8fbea8769583@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=labbott@redhat.com \
--cc=sashal@kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox