From: Mark Wielaard <mark@klomp.org>
To: v <vsochat@gmail.com>
Cc: Ben Woodard via Libabigail <libabigail@sourceware.org>
Subject: Re: Testing Setup - More Tests and Automation?
Date: Mon, 2 May 2022 00:42:38 +0200 [thread overview]
Message-ID: <20220501224238.GD30898@gnu.wildebeest.org> (raw)
In-Reply-To: <CAM=pu+L+KRM6fH3sasRqxHv76-8Zuwdx1i5=8Lz365LfS7pvOg@mail.gmail.com>
Hi Vanessa,
On Sat, Apr 30, 2022 at 04:38:52PM -0600, v via Libabigail wrote:
> I appreciate you keeping your opinion about GitHub and dislike separate
> from an overall evaluation of what is best for the project. There are
> things that I don't like too, but I recognize the value for other
> developers or (in this case) growing a community.
I am aware of my biases and preferences, which might be different from
other developers based on our experiences. And I certainly want to
learn from other experiences. But I do believe software freedom comes
first and there are real negatives to a community for relying on some
proprietary centralized hosting facility. I am happy to learn and
adopt free software replacements to get a similar experience though.
I am a little disappointed you seem to brush away any concerns by
saying github is currently really popular in some groups of
developers. Just because something is popular doesn't mean it is good
or appropriate in all circumstances. It would also be nice if you
could at least acknowledge that there are (possibly better?)
alternative forges which support "modern practices" that aren't
proprietary. Or that you would at least be willing to look at
them. They might not be exactly what you are personally accustomed to,
but if you evaluate them honestly we can at least see whether we can
adapt them. They are free software platforms after all, which we can
improve together.
Cheers,
Mark
next prev parent reply other threads:[~2022-05-01 22:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAM=pu++-JdBdizXQ9dj8eUypXg7fpPOTDzN6BL1NY-TFvk++kQ@mail.gmail.com>
2022-04-28 0:55 ` Fwd: " Ben Woodard
2022-04-28 1:57 ` v
2022-04-30 19:55 ` Mark Wielaard
2022-04-30 20:36 ` v
2022-04-30 21:48 ` Mark Wielaard
2022-04-30 22:38 ` v
2022-05-01 22:42 ` Mark Wielaard [this message]
2022-05-01 22:46 ` v
2022-06-09 11:31 ` Thinking different (was Re: Testing Setup - More Tests and Automation?) Dodji Seketeli
2022-06-09 19:48 ` v
2022-06-15 14:21 ` Dodji Seketeli
2022-06-09 11:18 ` Testing Setup - More Tests and Automation? Dodji Seketeli
2022-06-09 11:11 ` Dodji Seketeli
2022-06-14 10:05 ` Mark Wielaard
2022-04-28 8:06 ` Fwd: " Mark Wielaard
2022-04-29 21:13 ` Mark Wielaard
2022-04-29 22:02 ` Mark Wielaard
2022-05-03 19:08 ` Ben Woodard
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=20220501224238.GD30898@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=libabigail@sourceware.org \
--cc=vsochat@gmail.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.
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).