From owner-freebsd-hackers@freebsd.org Mon Apr 26 23:11:11 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 0BE945F3D8C for ; Mon, 26 Apr 2021 23:11:11 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ultimatedns.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FTgcZ5l19z4gqJ; Mon, 26 Apr 2021 23:11:10 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 13QNBHeY046705; Mon, 26 Apr 2021 16:11:23 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) MIME-Version: 1.0 Date: Mon, 26 Apr 2021 16:11:17 -0700 From: Chris To: Li-Wen Hsu Cc: "linimon@portsmon.org linimon@portsmon.org" , FreeBSD Hackers Subject: Re: Mentoring framework? In-Reply-To: References: <20210425185831.GS18217@blisses.org> <1866645852.215610.1619467279581@privateemail.com> User-Agent: UDNSMS/17.0 Message-ID: X-Sender: bsd-lists@bsdforge.com Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4FTgcZ5l19z4gqJ X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] 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: Mon, 26 Apr 2021 23:11:11 -0000 On 2021-04-26 13:33, Li-Wen Hsu wrote: > On Tue, Apr 27, 2021 at 4:01 AM linimon@portsmon.org > linimon@portsmon.org wrote: >> >> >> > On 04/25/2021 1:58 PM Mason Loring Bliss wrote: >> > I'd like to contribute, and something that occurs to me is the notion of >> > formal mentoring. >> >> Here are my observations: email is a pretty slow way of doing this kind of >> thing. Yes, us old-timers are quite used to it, but it kind of lacks a >> "collaborative" feel. >> >> A lot of time this kind of work gets done on various IRC channels. They at >> least (usually) give quicker feedback. >> >> But koobs@ has been putting a lot of effort into getting Discord to be a >> first- >> class interactivity space for FreeBSD. So, let me suggest trying out one >> of >> the channels there, as see if it's more like what you are looking for. >> >> (disclaimer: I am not saying "this will solve all our problems". I'm >> saying that >> right now it has momentum and seems worth supporting.) > > Yes there is no silver bullet, and IRC and discord are great tools for > fast respon time. > > But please remember, they are not very good to keep things permanent, > to let knowledge accumulated. > > So, my suggestion is, trying to use mailing list as possible, because > the archived mails can also help others, not just two or few people, > it can maximize the impact of the people who answer the questions. > > I like to use IRC, but sometimes I found that the "right people" are > not always available, and it is more difficult when it comes to time > zone issues. If it happens to find the right person, and get the issue > resolved. It is awesome and it will be good to have those experiences > be kept. For that purpose, the document is still the best thing, I > think in the open source world, things are more in an asynchronized > way, and documents can solve the issue that the mentor and mentee > can't be in the same time and space. And I believe that's also a good > way to make contributions. > > In short, the "mentoring program" begins when you send a mail to a > mailing list, you just need to describe your issues more clear, and be > a bit patient to wait for others to reply. And once the issue has been > resolved, sort it and put it to the official documents, we have > docs.freebsd.org, wiki.freebsd.org, and man pages, all for different > (and may overlap) purposes. +100% I would have to agree that mailing list(s) are probably the best approach 1) Those with any real tenure are already on them because "hey, that's they way we did everything back then" 2) base/ports/bugs already have lists So maybe add some flag to bugzilla? Add an additional (bounty) list? --Chris > > Best, > Li-Wen > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"