Skip to content

Commit c5884ef

Browse files
kuba-moodavem330
authored andcommitted
docs: netdev: offer performance feedback to contributors
Some of us gotten used to producing large quantities of peer feedback at work, every 3 or 6 months. Extending the same courtesy to community members seems like a logical step. It may be hard for some folks to get validation of how important their work is internally, especially at smaller companies which don't employ many kernel experts. The concept of "peer feedback" may be a hyperscaler / silicon valley thing so YMMV. Hopefully we can build more context as we go. Signed-off-by: Jakub Kicinski <kuba@kernel.org> Signed-off-by: David S. Miller <davem@davemloft.net>
1 parent 931ae86 commit c5884ef

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

Documentation/process/maintainer-netdev.rst

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -319,3 +319,13 @@ unpatched tree to confirm infrastructure didn't mangle it.
319319
Finally, go back and read
320320
:ref:`Documentation/process/submitting-patches.rst <submittingpatches>`
321321
to be sure you are not repeating some common mistake documented there.
322+
323+
My company uses peer feedback in employee performance reviews. Can I ask netdev maintainers for feedback?
324+
---------------------------------------------------------------------------------------------------------
325+
326+
Yes, especially if you spend significant amount of time reviewing code
327+
and go out of your way to improve shared infrastructure.
328+
329+
The feedback must be requested by you, the contributor, and will always
330+
be shared with you (even if you request for it to be submitted to your
331+
manager).

0 commit comments

Comments
 (0)