Re: Defining GNOME software (finally)
- From: Michael Catanzaro <mcatanzaro gnome org>
- To: Sriram Ramkrishna <sri ramkrishna me>
- Cc: Allan Day <aday gnome org>, Gnome Release Team <release-team gnome org>, board <board gnome org>
- Subject: Re: Defining GNOME software (finally)
- Date: Wed, 22 Apr 2020 17:46:32 -0500
Using issue tracking to handle some decisions (especially freeze
breaks) makes sense to me.
On Wed, Apr 22, 2020 at 1:20 pm, Sriram Ramkrishna <sri ramkrishna me>
wrote:
Thanks for that. Do you care about external dependencies - meaning we
add things to our toolchain - are they scrutinized? For instance,
picking up some library that has one person supporting it might raise
eyebrows. Curious if those are things the board would be interested in
knowing or a power that the release team should wield or does in fact
wield. (I'm not sure how on-topic this part is so if you want to
answer maybe that is worth a separate thread)
So new deps are usually handled on a case-by-case basis. Generally they
go into core-deps whenever required, though. We usually are not picky
about what we put there. Most of our core modules are, realistically,
maintained by just one-person, so I wouldn't be surprised if several of
our core-deps also have bus factor of 1.
We are much stricter about what goes into sdk, since that is exposed in
the flatpak runtime.
Michael
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]