From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: fthain@linux-m68k.org
Cc: corbet@lwn.net, dan.j.williams@intel.com,
gregkh@linuxfoundation.org, keescook@chromium.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
tech-board-discuss@lists.linux-foundation.org, tytso@mit.edu
Subject: Re: [PATCH] Documentation: Linux Contribution Maturity Model and the wider community
Date: Mon, 19 Jun 2023 07:32:50 -0400 [thread overview]
Message-ID: <e78eef83a50a558aae765baafcf9c571788a02a5.camel@HansenPartnership.com> (raw)
In-Reply-To: <cd1786eadd1ff05d9ca053b72eb5f06ceb0c470d.1687167717.git.fthain@linux-m68k.org>
On Mon, Jun 19, 2023 at 07:41:57PM +1000, Finn Thain wrote:
> The Linux Contribution Maturity Model methodology is notionally based
> on the Open source Maturity Model (OMM) which was in turn based on
> the Capability Maturity Model Integration (CMMI).
>
> According to Petrinja et al., the goal of the OMM was to extend the
> CMMI so as to be useful both for companies and for communities
> [1][2]. However, the Linux Contribution Maturity Model considers
> only companies and businesses.
That's not a correct characterization. The model is designed to
measure and be useful to businesses, but it definitely considers the
community because it's progress is built around being more useful to
and working more effectively with the community.
> This patch addresses this bias as it could hinder collaboration with
> not-for-profit organisations and individuals, which would be a loss
> to any stakeholder.
I don't really think changing 'Businesses' to 'Organizations' entirely
addresses what you claim is the bias because individuals would still be
excluded from the term 'Organizations'. I also don't really think it
matters. Part of the reason this whole thing doesn't matter is that
sometimes people do know who a contributor they work with works for,
but most of the time they don't. If you really want this to be
inclusive, you could change it to 'other contributors' but I'm still
not sure it's worth it.
>
> Level 5 is amended to remove the invitation to exercise the same bias
> i.e. employees rewarded indirectly by other companies.
I also wouldn't remove the bit about seeking upstream feedback on
employees; I know from personal experience it happens a lot.
Regards,
James
next prev parent reply other threads:[~2023-06-19 11:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 9:41 [PATCH] Documentation: Linux Contribution Maturity Model and the wider community Finn Thain
2023-06-19 9:55 ` Greg Kroah-Hartman
2023-06-20 3:48 ` Finn Thain
2023-06-20 13:00 ` James Bottomley
2023-06-19 11:32 ` James Bottomley [this message]
2023-06-20 3:50 ` Finn Thain
2023-06-20 22:52 ` [Tech-board-discuss] " James Bottomley
2023-06-19 19:42 ` Theodore Ts'o
2023-06-20 3:54 ` Finn Thain
2023-06-20 21:25 ` Theodore Ts'o
2023-06-21 1:51 ` Finn Thain
2023-06-21 12:41 ` Greg Kroah-Hartman
2023-06-22 7:02 ` Finn Thain
2023-06-22 7:10 ` Greg Kroah-Hartman
2023-06-22 7:24 ` Finn Thain
2023-06-22 17:39 ` Theodore Ts'o
2023-06-23 0:52 ` Finn Thain
2023-06-23 1:45 ` [Tech-board-discuss] " Mark Brown
2023-06-21 14:08 ` Steven Rostedt
2023-06-21 22:48 ` Finn Thain
2023-07-01 1:46 ` Measurement, was " Finn Thain
2023-07-01 7:04 ` [Tech-board-discuss] Measurement, was " Greg Kroah-Hartman
2023-07-01 22:54 ` Finn Thain
2023-06-21 22:44 ` Finn Thain
2023-06-23 2:32 ` Matthew Wilcox
2023-06-19 19:49 ` Kees Cook
2023-06-20 3:54 ` Finn Thain
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=e78eef83a50a558aae765baafcf9c571788a02a5.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=fthain@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tech-board-discuss@lists.linux-foundation.org \
--cc=tytso@mit.edu \
/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 NNTP newsgroup(s).