public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: v <vsochat@gmail.com>
Cc: Ben Woodard <woodard@redhat.com>,
	Ben Woodard via Libabigail <libabigail@sourceware.org>
Subject: Re: Testing Setup - More Tests and Automation?
Date: Sat, 30 Apr 2022 23:48:39 +0200	[thread overview]
Message-ID: <20220430214839.GC11996@gnu.wildebeest.org> (raw)
In-Reply-To: <CAM=pu+KrCpekap71fEVPsS-Bg-mW8iW4t_uZjdQEMNi2aGn1Sw@mail.gmail.com>

Hi Vanessa,

On Sat, Apr 30, 2022 at 02:36:47PM -0600, v wrote:
> The links are private because this is Ben's personal repository for his
> account - given that libabigail was developed under a proper organization
> it would be public. You can look at example OSS projects (e.g., tensorflow
> https://github.com/tensorflow/tensorflow/runs/6241307726?check_suite_focus=true)
> to get a sense of what the UI looks like.

That shows the same thing "Sign in to view logs".

> I understand the desire to not use proprietary software, but if you needed
> to move the setup elsewhere that's not hard to do! Modern software
> developers use GitHub, and all major companies (including RedHat) grow
> strong communities of developers on there. Podman is a good example:
> https://github.com/containers/podman. Git is git, so you could develop on
> GitHub and keep a backup on sourceware, and have an automated workflow to
> do that. In other words, there are ways to have your cake and eat it too.

I have contributed to some projects that use github (see e.g. rpm or
gccrust) but found it a major pita to be honest. Their website
basically doesn't work without javascript. And you have to depend on
people having a github account to do pull requests or accept patches
for you. Maybe it works better if you are able to create an account
and don't mind running all this proprietary javascript. But the legal
language involved in creating one is so large that I cannot even tell
if it is acceptable or not.

I happen to work for Red Hat myself as day job. But not directly
on libabigail, nor on any project that uses github. I know it is
possible to extract some stuff from github, I do keep some mirrors in
my own git setup https://code.wildebeest.org/ so I can sent patches
or pull requests. But I don't find the experience of interacting with
github using projects great.

> You have *eighteen* contributors with over 5 commits in a project that is 8
> years old, and that includes repeated individuals using different
> alias/email. Out of those 18, it looks like there are maybe 3 that have
> contributed meaningfully (and recently), and talking with Ben (and seeing
> number of commits), I get a sense that the main developer is Dodji and he
> is overwhelmed. So (to me) for a library that is as important as
> libabigail, this is problematic. The bus factor is really high.

I agree it would be good to have more active developers. I doubt it
matters whether or not the project has a github webpage. For me
personally I stopped most contributions since the licence
change. Which might or might not be a factor to others. Personally I
like contributing to projects that use strong copyleft.

> Compare
> that to Podman https://github.com/containers/podman/graphs/contributors,
> which is also a niche technology / area of work, and the project has only
> been around since late 2017 (and I don't know when it went up on GitHub
> from perhaps being private at RedHat) and it has almost 400 contributors
> (just over 100 with >= 5 commits) and many others that haven't contributed
> directly to the code (myself included) but have contributed via issues and
> other interaction.

I am not sure that libabigail and podman are comparable projects. But
I get that there are ways to interact with the project on the github
website that you prefer to interacting with the libabigail project?

> So (to me) this is a problem that needs to be solved, and I don't think
> keeping things the way that they are is that solution, regardless of how
> you innovate a bit with adding automation. The cost of not changing your
> current setup is very high, and I worry about the future of libabigail.

So which changes would you like to see? Note that I don't mind a forge
like setup, I just think that github is a pretty bad one. But
something like sourcehut, self-hosted gitlab or pagure would be pretty
cool. I do think adding automated testing is a pretty valuable thing,
especially if contributors can use it as pre-commit gating, which is
why I am working on adding buildbot and container based automation to
sourceware for all project hosted there. So I am a bit surprised you
believe that isn't part of the solution.

> As
> a developer I want to contribute and champion the work, but in its current
> state I find the project feels very closed and not trying bring me in. The
> students I spoke to at CU Boulder were inspired, but they will stop their
> exploration when they realize it's not easy to ask questions or for help.

Is that because they don't use email, bugzilla or irc? Do you think we
should have some kind of web-forum for the project?

Would their opinion change if they realize libabigail is mirrored on
sourcehut already?

> In other words, you are 100% losing out in terms of new contributors and
> developers by not using these modern practices and services.

Which modern practices and services are those exactly?

> That is of
> course your choice (and I respect the choices you make generally) but I
> strongly suggest you have a conversation with your team about this issue,
> and action you can take to address it. I really have enjoyed using
> libabigail and I think it can be better in many ways, not just the library
> itself but supported tools, automation, and branding, and this burden
> cannot just be on one or two developers.

I hope you can help and I hope we can provide you with the tools to do so.

Thanks,

Mark

  reply	other threads:[~2022-04-30 21:48 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 [this message]
2022-04-30 22:38           ` v
2022-05-01 22:42             ` Mark Wielaard
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=20220430214839.GC11996@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=libabigail@sourceware.org \
    --cc=vsochat@gmail.com \
    --cc=woodard@redhat.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).