From nobody Mon Feb 28 21:06:47 2022 X-Original-To: dev-commits-doc-all@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 199DA19F027F for ; Mon, 28 Feb 2022 21:06:48 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4K6tGv6lWFz4rX5; Mon, 28 Feb 2022 21:06:47 +0000 (UTC) (envelope-from git@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1646082408; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=GvtbZNIJB/jlltyVK85kD+DM+buW/LJiAQ1BLeoFLRQ=; b=AZGvw74AoIsI+shSmwcCI7HzXVHxkO0DLQ7HiA5cPIakU4dAyFZ3fRHIfbCdd4POl6l8d5 D6MB+U8m0nag5xM9pLNoqPOIuoMMRnwXt/wFLNiHxlkIvz4o7LaYoyVqpWv61iJSIIaLr1 Jc/4xy4K/Z2hKB/galSvP2qRnFJZxx8LPCRD5dD/d4LY8bcVXCR+MQQgHHg5ut+3H2K/G4 pvT+uLA/Xcu8xyMJNhkc4XQevZ1rGh91czsSe2Ct8qqwXdFWeWgqQuwoIkbW1QWJpVeJX6 LTT53um5tn7elmBz8d9VFWFDakDNgcyRN2AE7ZrgVV+pp1IJP7PcaornGHa33Q== Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (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 did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id C212922A8B; Mon, 28 Feb 2022 21:06:47 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 21SL6lVI029012; Mon, 28 Feb 2022 21:06:47 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 21SL6lYH029011; Mon, 28 Feb 2022 21:06:47 GMT (envelope-from git) Date: Mon, 28 Feb 2022 21:06:47 GMT Message-Id: <202202282106.21SL6lYH029011@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Sergio Carlavilla Delgado Subject: git: d0407d9bac - main - Change Port Management Team to Ports Management Team. List-Id: Commit messages for all branches of the doc repository List-Archive: https://lists.freebsd.org/archives/dev-commits-doc-all List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-doc-all@freebsd.org X-BeenThere: dev-commits-doc-all@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: carlavilla X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: d0407d9baccd8e9d6bde1fcaf974e6d988141f5a Auto-Submitted: auto-generated ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1646082408; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=GvtbZNIJB/jlltyVK85kD+DM+buW/LJiAQ1BLeoFLRQ=; b=RHbqLWEzltdxyYKUc2dDbV+VohFv7OMOLzVT1InL16eMgNA0hVcYu/GMajf0EnrAD3/7FX wIkLPbMeFXk9Ho+1d0mHf6Ui1T/J1oLmD8q9ddkTTasqT5uMXc37DFMlKUKPSAwBAxR1P1 mSmrILHyyoDbGE7F5yueY83TFu6tIcHBLaXWHrZoOZOhE9HU9pJbb34zyhbZ5MmOkT8wQX 7aTVVcNvs54gw53Z2Iigf1KwCyUtJNoVA2oFxxzoNiSNONuD3mIt6o0dxd2qFotaBE8QnH wW7jF2YMQ5POfPP9bYSmLP3l5UVgjGYrIsPswA3pOYiJ4YpwzB3/CXLckUiUzg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1646082408; a=rsa-sha256; cv=none; b=Idu+OQIzF75cYHaTOUc/3+Yv0R51urDfMTB1n7npzotOVu2PzacyR0rWhRGiVmbkrNsjfv vMy/dl6yb8joFVc464ri/njONf7Csxpt9/05PuPDY3/wFqDjaqbCBddiyxa3K0bQGQN4D/ r3Azpymggo8cu9XbPzcT90elnZup8filKCR0i4lDLoBCMJK63k4LBT3U+u7ycJo+G3tuOc C6r6a1R3BcyAgwCDYy6knbq8JywezBHeYQvnRWMNTLzdoelgk4T0s2ZP2EguvsJYW1h3f7 ZqlPOjp3Rb/Dumcpz6z/wdf6NuZbSdGCp3CzexDNvaqj9N0z7/yqZOvfd/5mEg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N The branch main has been updated by carlavilla: URL: https://cgit.FreeBSD.org/doc/commit/?id=d0407d9baccd8e9d6bde1fcaf974e6d988141f5a commit d0407d9baccd8e9d6bde1fcaf974e6d988141f5a Author: Sergio Carlavilla Delgado AuthorDate: 2022-02-28 21:04:52 +0000 Commit: Sergio Carlavilla Delgado CommitDate: 2022-02-28 21:04:52 +0000 Change Port Management Team to Ports Management Team. Based on Ports Management Team charted the correct description of the Team is Ports Management Team PR: 261916 Submitted by: Graham Perrin --- .../content/en/articles/committers-guide/_index.adoc | 6 +++--- website/content/en/administration.adoc | 16 ++++++++-------- website/content/en/internal/clusteradm.adoc | 4 ++-- website/content/en/press/press-rel-9.adoc | 2 +- website/content/en/status/report-2010-04-2010-06.html | 4 ++-- website/content/en/status/report-2012-04-2012-06.html | 4 ++-- website/content/en/status/report-2012-07-2012-09.html | 2 +- website/content/en/status/report-2013-07-2013-09.html | 8 ++++---- website/content/en/status/report-2013-10-2013-12.html | 14 +++++++------- website/content/en/status/report-2014-01-2014-03.html | 10 +++++----- website/content/en/status/report-2014-04-2014-06.html | 6 +++--- website/content/en/status/report-2014-10-2014-12.html | 2 +- website/content/en/status/report-2015-01-2015-03.html | 2 +- 13 files changed, 40 insertions(+), 40 deletions(-) diff --git a/documentation/content/en/articles/committers-guide/_index.adoc b/documentation/content/en/articles/committers-guide/_index.adoc index 557630327b..e52393a258 100644 --- a/documentation/content/en/articles/committers-guide/_index.adoc +++ b/documentation/content/en/articles/committers-guide/_index.adoc @@ -3576,7 +3576,7 @@ Tiers are defined for both kernels and userland ABIs. In the common case, a plat === Tier 1: Fully-Supported Architectures Tier 1 platforms are the most mature FreeBSD platforms. -They are supported by the security officer, release engineering, and port management teams. +They are supported by the security officer, release engineering, and Ports Management Team. Tier 1 architectures are expected to be Production Quality with respect to all aspects of the FreeBSD operating system, including installation and development environments. The FreeBSD Project provides the following guarantees to consumers of Tier 1 platforms: @@ -3612,7 +3612,7 @@ Collectively, developers are required to provide the following to maintain the T === Tier 2: Developmental and Niche Architectures Tier 2 platforms are functional, but less mature FreeBSD platforms. -They are not supported by the security officer, release engineering, and port management teams. +They are not supported by the security officer, release engineering, and Ports Management Team. Tier 2 platforms may be Tier 1 platform candidates that are still under active development. Architectures reaching end of life may also be moved from Tier 1 status to Tier 2 status as the availability of resources to continue to maintain the system in a Production Quality state diminishes. @@ -3640,7 +3640,7 @@ Collectively, developers are required to provide the following to maintain the T === Tier 3: Experimental Architectures Tier 3 platforms have at least partial FreeBSD support. -They are _not_ supported by the security officer, release engineering, and port management teams. +They are _not_ supported by the security officer, release engineering, and Ports Management Team. Tier 3 platforms are architectures in the early stages of development, for non-mainstream hardware platforms, or which are considered legacy systems unlikely to see broad future use. Initial support for Tier 3 platforms may exist in a separate repository rather than the main source repository. diff --git a/website/content/en/administration.adoc b/website/content/en/administration.adoc index 3eff03abb9..821af45704 100644 --- a/website/content/en/administration.adoc +++ b/website/content/en/administration.adoc @@ -20,7 +20,7 @@ This page lists teams, groups and individuals within the FreeBSD project with de * Project Management ** <> ** <> -** <> +** <> ** <> * Release Engineering ** <> @@ -32,7 +32,7 @@ This page lists teams, groups and individuals within the FreeBSD project with de * Secretaries ** <> ** <> -** <> +** <> * Internal Administration ** <> ** <> @@ -83,11 +83,11 @@ The https://www.freebsd.org/internal/doceng/[doceng team charter] describes the * {0mp} (Secretary) [[t-portmgr]] -== FreeBSD Port Management Team +== FreeBSD Ports Management Team -The primary responsibility of the FreeBSD Port Management Team is to ensure that the FreeBSD Ports Developer community provides a ports collection that is functional, stable, up-to-date and full-featured. +The primary responsibility of the FreeBSD Ports Management Team is to ensure that the FreeBSD Ports Developer community provides a ports collection that is functional, stable, up-to-date and full-featured. Its secondary responsibility is to coordinate among the committers and developers who work on it. -The https://www.freebsd.org/portmgr/charter/[portmgr team charter] describes the duties and responsibilities of the Port Management Team in greater detail. +The https://www.freebsd.org/portmgr/charter/[portmgr team charter] describes the duties and responsibilities of the Ports Management Team in greater detail. * {antoine} * {bapt} (Core Team Liaison) @@ -185,10 +185,10 @@ The FreeBSD Documentation Engineering Team Secretary is a non-voting member of t * {0mp} [[t-portmgr-secretary]] -== Port Management Team Secretary +== Ports Management Team Secretary -The FreeBSD Port Management Team Secretary is a non-voting member of the Port Management Team, responsible for documenting the work done by portmgr, keeping track of voting procedures, and to be an interface to the other teams, especially the admin and Core teams. -The Port Management Team Secretary is also responsible for writing and sending out monthly status reports to the FreeBSD Developer community, containing a summary of portmgr's latest decisions and actions. +The FreeBSD Ports Management Team Secretary is a non-voting member of the Ports Management Team, responsible for documenting the work done by portmgr, keeping track of voting procedures, and to be an interface to the other teams, especially the admin and Core teams. +ThePorts Management Team Secretary is also responsible for writing and sending out monthly status reports to the FreeBSD Developer community, containing a summary of portmgr's latest decisions and actions. * {rene} diff --git a/website/content/en/internal/clusteradm.adoc b/website/content/en/internal/clusteradm.adoc index e62eabd512..e4e8feab3e 100644 --- a/website/content/en/internal/clusteradm.adoc +++ b/website/content/en/internal/clusteradm.adoc @@ -14,7 +14,7 @@ Lead cluster administrator is a delegated officer role (aka. "hat") that answers * Ensure that standard operating procedures, rules, guidelines etc are documented and understandable. * Take measures to ensure that a competent administrator would be expected to be able to adopt a predecessor's work in a reasonable amount of time. * Contingency planning and implementation to ensure continuity across site specific problems (including donated site withdrawal or outages). -* Keep the interested parties (Core Team, Security Team, FreeBSD Foundation, Port Management Team, etc), project members and community members appropriately informed. +* Keep the interested parties (Core Team, Security Team, FreeBSD Foundation, Ports Management Team, etc), project members and community members appropriately informed. * Give timely and authoritive answers to questions, or a direct referral to the appropriate party. * Aid other hat wearers and cluster administrators to get their job done. * Where practical and appropriate, use the Project's own product as a proving ground. @@ -31,7 +31,7 @@ Any of the following still require a sign-off from the Core Team: Notable interaction with other hats: * The lead cluster administrator will consult with the Security Officer and the Security Team where appropriate but will be responsible for making decisions. However, the Security Officer may respond to security emergencies involving project infrastructure as necessary. -* The Port Management Team has a large resource footprint and arrangements will be made with them to effectively operate their resources within the constraints of the overall cluster operation. +* The Ports Management Team has a large resource footprint and arrangements will be made with them to effectively operate their resources within the constraints of the overall cluster operation. Earmarked resources: diff --git a/website/content/en/press/press-rel-9.adoc b/website/content/en/press/press-rel-9.adoc index 1bc699753e..4568f639ac 100644 --- a/website/content/en/press/press-rel-9.adoc +++ b/website/content/en/press/press-rel-9.adoc @@ -8,7 +8,7 @@ loadPress: false *The FreeBSD Foundation received a donation of a blade system from Hewlett-Packard for use as a third-party software build cluster. This 20-node HP BladeSystem cluster triples the speed of the build process for i386 packages.* -_"With this generous donation from HP, we are able to continuously produce up-to-date packages from more than 13000 ports of third-party software available in the FreeBSD Ports Collection, at about three times the rate of the previous hardware cluster,"_ said Kris Kennaway, member of the FreeBSD Port Management Team. +_"With this generous donation from HP, we are able to continuously produce up-to-date packages from more than 13000 ports of third-party software available in the FreeBSD Ports Collection, at about three times the rate of the previous hardware cluster,"_ said Kris Kennaway, member of the FreeBSD Ports Management Team. _"This directly benefits the users of FreeBSD through the rapid availability of new and updated software packages, and through the increased testing and QA of FreeBSD that the new hardware allows."_ diff --git a/website/content/en/status/report-2010-04-2010-06.html b/website/content/en/status/report-2010-04-2010-06.html index b33bdda59a..56ad0808b1 100644 --- a/website/content/en/status/report-2010-04-2010-06.html +++ b/website/content/en/status/report-2010-04-2010-06.html @@ -292,7 +292,7 @@ utilities) meant to be included in the base system when it is done. It comes with built-in mass patch creation and application commands. It is funded by Google Summer of Code 2010.

-

Open tasks:

  1. Finish the project.
  2. Get some testing for it.
  3. Convince the Port Management Team it is actually a Good +

    Open tasks:

    1. Finish the project.
    2. Get some testing for it.
    3. Convince the Ports Management Team it is actually a Good Thing to have even as an experimental feature.
    4. Agree upon the policy on which package patches will be created (i.e. from which point in time to which point in time), assuming the "stable" package tree idea has still not gotten @@ -1493,7 +1493,7 @@

      alepulver's Licensing Framework Summer of Code project has made - it into the tree and the Port Management Team is currently + it into the tree and the Ports Management Team is currently assessing the fallout and it will come up with guidelines and documentation in due time.

      Open tasks:

      1. Looking for help fixing ports diff --git a/website/content/en/status/report-2012-04-2012-06.html b/website/content/en/status/report-2012-04-2012-06.html index a71dd542d2..f4b45bb520 100644 --- a/website/content/en/status/report-2012-04-2012-06.html +++ b/website/content/en/status/report-2012-04-2012-06.html @@ -277,7 +277,7 @@ relatively high number of new members. Note that this is the second of the four reports planned for 2012.

        Thanks to all the reporters for the excellent work! This report contains 17 entries and we hope you enjoy reading it.

        Please note that the deadline for submissions covering the period - between July and December 2012 is February 17th, 2013.

        Projects

          Userland Programs

          FreeBSD Team Reports

          Kernel

          Network Infrastructure

          Documentation

          Architectures