2001 and published to developers@ and ports@ to the internal handbook.
Portmgr has been operating under this charter since then, but people
were having problems finding this in the email archives. Add it to
our internal page so that people no longer have this problem.
I'll also note that core.2 intended to give a very borad range of
powers to portmgr@ to manage the ports tree, while retaining the
ability to clarify and refine the charter over time.
Mark and Hiroki are doing good jobs as new member, so I can pass
all my (especially Japanese/localization specific) doceng hats
to Hiroki and other doceng members.
I'll focus to use my FreeBSD time for activities in other area
(like core, *master, ...).
And I hope I can find time to do actual translation works, not
management nor engineering works. :-)
file is from so@. We dropped the SSHv1 info as well as adding or
otherwise adjusting the existing machine info (couple new machines,
plus ref4 wound up rebuilt and we didn't have access to the old
machine's SSH info any more).
Signed by: des (with so@ hat)
several goals:
1. Make the pages more consistent with the style of the other FreeBSD
www pages.
2. Reorganize the top-level Internal page into four subheadings:
Projects, Policies, People, and Resources. This helps make the
page 'flow' a lot better.
3. Create a new, second-level, Policies page to hold one subgrouping
of the links that used to live on the main page, which had too many
links as it was.
4. Remove the Contacting, Copyright, and Search links, which had
been promoted to the top-level FreeBSD page some time ago in another
cleanup.
Note: all of the links (except in #4) from the original page remain
either in pages committed -- this is essentially a reorganization of
the existing links to present them in a more logical -- and legible --
context.
Discussed without objection on: freebsd-www
Reviewed by: trhodes
Approved by: trhodes
- Remove the requirement for mentors to send PGP keys of new
committers to admins@.
committers-guide/article.sgml:
- Update copyright year.
- Emphasize that new committers should add their PGP key to the
Handbook, since it might be needed for identification, e.g. for
account recovery.
teams.ent:
- Add an entiry for admins@.
Discussed with: admins (joe, kensmith)
the US Senate, Canadian Parliament and Australian Senate, it was
causing some confusion. After some consultation with Mark Murray,
change this to 'without objection' since often times a plain-speaking
term is preferable to a regionally used term.
Also, clarify that this procedure is to be used when for more mundane
matters that need a sanity check, but don't need the whole, ponderous
voting proceedure that more difficult issues require. Core members
that read email in any given 48 hour period are trusted enough to know
the difference and to provide the sanity check as necessary.
Reviewed by: markm
definition of 'Unanimous Consent' that is used by the US Senate to
mean 'without objection' in routine matters. Also say as in this
document for non-US folks who may be unfamiliar with the term and
confused by its use.
PR: www/60171 (the 'be' -> 'may' change)
