* Friendly reminder
@ 2019-05-06 13:31 Mimi Zohar
0 siblings, 0 replies; only message in thread
From: Mimi Zohar @ 2019-05-06 13:31 UTC (permalink / raw
To: linux-integrity; +Cc: Jarkko Sakkinen, Shuah Khan
Hi -
A number of people have recently joined this mailing list wanting to
contribute - participate in discussions, provide bugs fixes, and/or
add new features. This is also a good reminder for seasoned kernel
developers as well. Like with any community, Linux kernel development
defines certain conventions. At minimum to participate in the
discussions, please find a mailer that doesn't mangle posts; and
remember to trim and inline/bottom post responses.
To fix bugs or submit new features to the linux-integrity subsystem
please read the kernel documentation [1,2] to understand the
process and expectations. Patches pertaining to IMA, EVM, "trusted"
keys and "encrypted" keys, are upstreamed via the linux-security
tree. Please make sure any patches posted, apply cleanly to the next-
integrity branch [3] or the next-queued-testing branch immediately
before, during, and after the open window.
For those submitting new features, please pay special attention to the
section titled "3) Separate your changes". [1] Before posting patches
to the mailing list, please review your patches line by line, just as
people reviewing patches do. The easier it is to read and review the
patches, the more likely they will be reviewed/upstreamed.
Before extending IMA/EVM, please consider the security/integrity
implications of the proposed new feature, not only in the context of
your environment, but the bigger picture - how others are currently
using existing features. Remember changes may never break userspace
[4] and, additionally for the linux-integrity subsystem, userspace
expectations.
Most importantly, reviewing patches should not only be the
maintainer's responsibility, it simply doesn't scale very well, but is
the community's responsibility. You don't need to be a subject expert
to review/comment on patches. Patches can be reviewed at multiple
levels - patch descriptions, coding style, security, integrity, etc.
Please take the time to review and comment on other people's patches.
Thanks!
Mimi
[1] Documentation/process/submitting-patches.rst
[2] Documentation/process/submit-checklist.rst
[3] next-integrity branch (https://git.kernel.org/pub/scm/linux/kernel
/git/zohar/linux-integrity.git)
[4] Linus' edict "Never break userspace"
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-05-06 13:32 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-05-06 13:31 Friendly reminder Mimi Zohar
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.