From owner-freebsd-hackers@freebsd.org Sun Apr 25 18:58:34 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AD0B25E35ED for ; Sun, 25 Apr 2021 18:58:34 +0000 (UTC) (envelope-from mason@blisses.org) Received: from yangtze.blisses.org (yangtze.blisses.org [144.202.50.44]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4FSy3Y5Pp1z3vhr for ; Sun, 25 Apr 2021 18:58:33 +0000 (UTC) (envelope-from mason@blisses.org) Received: from cocytus.blisses.org (cocytus.blisses.org [64.223.129.151]) by yangtze.blisses.org (Postfix) with ESMTP id C987C17B288 for ; Sun, 25 Apr 2021 14:58:32 -0400 (EDT) Date: Sun, 25 Apr 2021 14:58:31 -0400 From: Mason Loring Bliss To: freebsd-hackers@freebsd.org Subject: Mentoring framework? Message-ID: <20210425185831.GS18217@blisses.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="nWEzmRaGLXxZdI3i" Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspamd-Queue-Id: 4FSy3Y5Pp1z3vhr X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of mason@blisses.org designates 144.202.50.44 as permitted sender) smtp.mailfrom=mason@blisses.org X-Spamd-Result: default: False [-4.40 / 15.00]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[144.202.50.44:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[144.202.50.44:from:127.0.2.255]; DMARC_NA(0.00)[blisses.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:20473, ipnet:144.202.48.0/20, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; MAILMAN_DEST(0.00)[freebsd-hackers]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Apr 2021 18:58:34 -0000 --nWEzmRaGLXxZdI3i Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I just wrote about some bugs that nettle me in my "bug bounties" post, sent just prior to my writing this. I'd like to throw out another idea as well. In the post I listed a number of things that I'd encountered that bother me, and in each case I've put some time into trying to either correct or work around the bugs. Between work and family my time is way more limited than I'd like, but I'd like to contribute, and something that occurs to me is the notion of formal mentoring. At work one of my roles involves mentoring junior engineers. We'll either tackle things they're working on, wherein I show them how I'd approach the issues they're trying to untangle and maybe highlight tools and techniques that might be new to them, or I'll share what I'm doing and narrate my actions and ideas as I work through puzzles that have landed on my plate. Either way, the end result is that they end up with more tools and techniques at their disposal, making them feel more powerful and competent. This would be a bit heavyweight for a volunteer project, but for FreeBSD, I can envision folks volunteering as mentors and corresponding via email about particular projects or bug hunts, or occasionally via IRC or somesuch. The underlying idea is that a hands-on donation of time from the folks in the mentoring role would be enough to energize folks like me to the point where bugs get fixed and the mentees start building up momentum on their own. As an example, for the bug I noted where a platform won't reliably boot the kernel, or for the bug that came up on the list a week or two ago where Vultr VMs hang on reboot, a mentor might help identify data collection tools and techniques and some idea of how to determine if a line of inquiry is producing usable results, after which the mentee could dig in with some notion of the short-term goal for the current stage of the investigation. I'd love thoughts and opinions. --=20 Mason Loring Bliss mason@blisses.org Ewige Blumenkraft! awake ? sleep : random() & 2 ? dream : sleep; -- Hamlet, Act III, Scene I --nWEzmRaGLXxZdI3i Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEEXtBZz1axB5rEDCEnrJXcHbvJVUFAmCFu9QACgkQnrJXcHbv JVXawBAA0lKHpiHwH2lHmuhMxK0uSPiU+XsfxphrsbkSX540oC65shFAK/bRkQzc 838y3k+J9oTQTucQxlSOy7Kyj35hAYs4jOGxsbUwWnLUKvy5F1KWZ2AR4Huit7XL lgtbptL68mFmVm87PlvvtSJwWiiw/VNa8QbRmCnIEvRl3R4IGeH0dFvG9JV/A4Sh /OlG9tq/lQGRr6LyJfT5JmDEXv6AGTipUJCY5up3aSkCVhaQUcDWjfNMxwF7SYZY Qe5tmBPLlO5/nQwUX8sFvFOBaDQjyxoGRJ0CopwF3dAoVr8mSbDYnq9iuI35hc19 avQYv3K6nH/FVfTyREzbrGUfL7D6cea53dFgS1BoG85Jv+UOIXvJax9isH56DEub 6GK4cUb3ydGc7S8uV00cQ7ywIlpG3DIOAgGC7WbNLKgBxSDN6W0M9VRf/x/paCvp 8fuYxvUO2JbuimW0sdoz4jJoZj3kpy0R58GLz3glougINTi1bJkcrzEbugxbyhsF VBJ8UWnN2Fo83LR7YYpyupfCRV1OnrkL8Wf9T0gSW2H+tCT9XDKomMXgF1qY5jCn iwUhOdjw6DSaIWqSpUYt+MPbPoZIJW+CGrpO8tnzaXADoCji1ys27FWsS/eN1lhm +aNsfK4gixscT5rSNksFrvuFEV+sAZ8wLkGJqpKYy3vcHMEZLQc= =VBC4 -----END PGP SIGNATURE----- --nWEzmRaGLXxZdI3i--