On 7/12/24 09:25, Mark Brown wrote:
On Fri, Jul 12, 2024 at 07:49:03AM -0700, Jakub Kicinski wrote:
+Open development
+----------------
+
+Discussions about user reported issues, and development of new code
+should be conducted in a manner typical for the larger subsystem.
+It is common for development within a single company to be conducted
+behind closed doors. However, maintainers must not redirect discussions
+and development related to the upstream code from the upstream mailing lists
+to closed forums or private conversations. Reasonable exceptions to this
+guidance include discussions about security related issues.
Reviewed-by: Mark Brown <broonie@xxxxxxxxxx>
I do think it's fine for people to have open places like github as an
option as well, so long as they're optional for contributors and things
pass through the lists in a normal fashion at some point. Directing
people towards existing relevant discussions/reviews can work well. The
main issues are taking things out of all visibility and blocking
contributors.
+1 It is important to point out the prior open conversations if any
that took place when patches go through reviews on kernel mailing
lists. This is the practice for the most part for work stemming from
discussions at conferences such as LPC.
Reviewed-by: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
thanks,
-- Shuah
