From: ng0 <ng0@we.make.ritual.n0.is>
To: Pjotr Prins <pjotr.public12@thebird.nl>, David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Feedback, ideas, discussion: tracking patches, discussions, bugs.
Date: Sun, 14 Aug 2016 09:14:39 +0000 [thread overview]
Message-ID: <87lgzzr9ts.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <20160814054130.GA13054@thebird.nl>
Hi,
Pjotr Prins <pjotr.public12@thebird.nl> writes:
> I hope this will be a topic in Rennes though I won't be there.
I won't be there as well, it's currently too expensive for me.
> Savannah is nice but limited in scope (and notably does not provide
> 100% uptime).
>
> The E-mail patch system is archaic and is certainly noisy. I think we
> should have an additional system that is more friendly. I use github a
> lot to collaborate, and while it is not acceptable to a GNU project
> (mostly because it is closed source), it certainly proves to have good
> functionality and improves collaboration.
>
> Also, I think reviewers should become mentors - i.e., help rather than
> be only critical. The current system is unfriendly, though it appears
> to be hard to appreciate that problem from the 'inside'. The main
> problem appears to be we have too few reviewers to make them
> mentors...
>
> I am not contributing my work as it stands. Maybe my contributions do
> not matter in the greater scheme of things - but, believe me, I am not
> happy about it. I just updated a critical bug in OpenBLAS and bumped
> scipy and numpy in production. Someone else will have to do that work
> over again.
>
> Maybe some people here can form a working group and come up with
> recommendations?
I'd be happy to join or work in such a group.
> Pj.
--
♥Ⓐ ng0
For non-prism friendly talk find me on http://www.psyced.org
next prev parent reply other threads:[~2016-08-14 9:14 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 10:46 Feedback, ideas, discussion: tracking patches, discussions, bugs David Craven
2016-08-13 11:11 ` David Craven
2016-08-13 11:23 ` ng0
2016-08-14 5:41 ` Pjotr Prins
2016-08-14 9:14 ` ng0 [this message]
2016-08-15 1:39 ` David Craven
2016-08-15 4:55 ` Pjotr Prins
2016-08-15 9:11 ` David Craven
2016-08-16 13:17 ` Ricardo Wurmus
2016-08-16 13:29 ` Pjotr Prins
2016-08-15 11:53 ` Hartmut Goebel
2016-08-15 13:30 ` Danny Milosavljevic
2016-08-15 15:18 ` Alex Vong
2016-08-16 7:20 ` Hartmut Goebel
2016-08-16 14:06 ` Alex Vong
2016-08-18 11:47 ` Hartmut Goebel
2016-09-01 6:32 ` ng0
2016-09-01 11:19 ` ng0
2016-09-02 0:27 ` John Darrington
2016-09-02 0:58 ` ng0
2016-09-02 5:50 ` Alex Vong
2016-09-02 8:21 ` ng0
2016-09-02 10:54 ` Alex Vong
2016-09-03 16:44 ` Pjotr Prins
2016-09-03 16:55 ` David Craven
2016-09-03 19:19 ` Brendan Tildesley
2016-09-03 19:53 ` David Craven
2016-09-03 20:42 ` Efraim Flashner
2016-09-02 12:39 ` Tracking package submissions with Debbugs Ludovic Courtès
2016-09-02 14:29 ` Ricardo Wurmus
2016-09-03 0:35 ` Alex Vong
2016-09-03 13:47 ` Ludovic Courtès
2016-09-04 2:21 ` Alex Vong
2016-09-03 21:00 ` Efraim Flashner
2016-09-04 2:37 ` Alex Vong
2016-09-04 7:05 ` Andreas Enge
2016-09-04 16:57 ` ng0
2016-09-04 17:00 ` ng0
2016-09-04 17:09 ` David Craven
2016-09-05 12:52 ` Alex Kost
2016-09-05 20:22 ` Ludovic Courtès
2016-09-05 20:39 ` David Craven
2016-09-05 23:12 ` ng0
2016-09-07 20:38 ` Ludovic Courtès
2016-09-05 23:17 ` ng0
2016-09-05 23:54 ` David Craven
2016-09-06 0:01 ` Ben Woodcroft
2016-09-06 7:57 ` ng0
2016-09-06 11:26 ` David Craven
2016-09-06 1:24 ` Alex Vong
-- strict thread matches above, loose matches on Subject: below --
2016-08-16 8:37 Feedback, ideas, discussion: tracking patches, discussions, bugs David Craven
2016-08-16 9:01 ` David Craven
2016-08-13 10:18 ng0
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=87lgzzr9ts.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=david@craven.ch \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.