Bug 196961

Summary: articles/committers-guide: introduction step has unclear destination
Product: Documentation Reporter: Jan Beich <jbeich>
Component: Books & ArticlesAssignee: freebsd-doc (Nobody) <doc>
Status: Closed Feedback Timeout    
Severity: Affects Only Me CC: bcr
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   

Description Jan Beich freebsd_committer freebsd_triage 2015-01-21 06:13:12 UTC
While reading the following paragraph and then checking with the rest of the guide I can't figure out *where* to mail my introduction.

6.2. For Everyone

  1. Introduce yourself to the other developers, otherwise no one will
  have any idea who you are or what you are working on. The
  introduction need not be a comprehensive biography, just write a
  paragraph or two about who you are, what you plan to be working on
  as a developer in FreeBSD, and who will be your mentor. Email this
  to the FreeBSD developers mailing list and you will be on your way!

Developers maillist is mentioned several times later but never how to properly construct its mail address. Is one supposed to wait for discussions to happen there before knowing for certain?
Comment 1 Jan Beich freebsd_committer freebsd_triage 2015-01-21 06:27:43 UTC
Ah, found. In the first chapter as Internal Mailing Lists. Given there're many developers lists it's not clear how to choose one.
Comment 2 Benedict Reuschling freebsd_committer freebsd_triage 2015-06-15 21:39:23 UTC
I think it is save to close this one without action. Mentors should provide their mentees with the proper mailing-list as part of the first steps for a new mentee. Do you agree or should we make it more explicit?
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:44:25 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.