Date: Thu, 29 Apr 2021 19:06:57 GMT From: Rene Ladan <rene@FreeBSD.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org Subject: git: 646b610c49 - main - Mention Git instead of Subversion on the internal web pages. Message-ID: <202104291906.13TJ6v2h008519@gitrepo.freebsd.org>
next in thread | raw e-mail | index | archive | help
The branch main has been updated by rene: URL: https://cgit.FreeBSD.org/doc/commit/?id=646b610c49db90a36b71b6a37f9c11b1783079b6 commit 646b610c49db90a36b71b6a37f9c11b1783079b6 Author: Rene Ladan <rene@FreeBSD.org> AuthorDate: 2021-04-29 18:57:24 +0000 Commit: Rene Ladan <rene@FreeBSD.org> CommitDate: 2021-04-29 19:06:44 +0000 Mention Git instead of Subversion on the internal web pages. --- website/content/en/internal/about.adoc | 2 +- website/content/en/internal/developer.adoc | 4 ++-- website/content/en/internal/doceng.adoc | 2 +- website/content/en/internal/new-account.adoc | 6 +++--- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/website/content/en/internal/about.adoc b/website/content/en/internal/about.adoc index 79b96eac19..3bab403728 100644 --- a/website/content/en/internal/about.adoc +++ b/website/content/en/internal/about.adoc @@ -37,7 +37,7 @@ The original page design was done by Megan McCormack. == link:{fdp-primer}#the-website-build[Building and updating the FreeBSD Web Pages] -This document describes how to build and update the FreeBSD Web pages from the Subversion repository by hand. +This document describes how to build and update the FreeBSD Web pages from the Git repository by hand. == Update of the FreeBSD Web Pages diff --git a/website/content/en/internal/developer.adoc b/website/content/en/internal/developer.adoc index 421d73c7b2..43cc11fe27 100644 --- a/website/content/en/internal/developer.adoc +++ b/website/content/en/internal/developer.adoc @@ -9,7 +9,7 @@ include::shared/en/urls.adoc[] == link:{committers-guide}[Committers Guide] -This document is an overall guide for all new committers, including both technical details and policy details. For the former, see the chapters on link:{committers-guide}#subversion-primer[the Subversion VCS], the link:{committers-guide}#bugzilla[Bugzilla] bug tracking system, and the link:{committers-guide}#ssh.guide[SSH Quick-Start Guide]. +This document is an overall guide for all new committers, including both technical details and policy details. For the former, see the chapters on link:{committers-guide}#git-primer[the Git VCS], the link:{committers-guide}#bugzilla[Bugzilla] bug tracking system, and the link:{committers-guide}#ssh.guide[SSH Quick-Start Guide]. It contains almost everything a new committer to the FreeBSD Project needs to know. See the Documentation Project Primer and the Ports Guide, below, for more info. @@ -23,7 +23,7 @@ A guide for FreeBSD ports committers. This includes the canonical link:{porters- == link:{fdp-primer}#the-website-build[How to build the FreeBSD Web Pages]. -This document describes how to build and update the FreeBSD Web pages from the SVN repository by hand. +This document describes how to build and update the FreeBSD Web pages from the Git repository by hand. == FreeBSD Projects diff --git a/website/content/en/internal/doceng.adoc b/website/content/en/internal/doceng.adoc index 1c393df1aa..d5ab9a97aa 100644 --- a/website/content/en/internal/doceng.adoc +++ b/website/content/en/internal/doceng.adoc @@ -12,7 +12,7 @@ The doceng@ team is a body to handle some of the meta-project issues associated * To grant approval for new documentation committers. Documentation includes articles and books, website pages, manual pages, release notes and translations of the above. There are two kinds of doc commit bits: translator commit bit, which is limited to translations in a particular language and full commit bit, which is only granted to aspirants, who have shown enough English writing skills. * To maintain the doc project primer, which documents best practices for the FreeBSD Documentation Project. * To manage the doc/ release process. This includes coordinating the release documentation updates with the various translation teams, coordinating with the release engineering team to tag the doc/ tree during the release cycle, and documenting these procedures. -* To ensure that the generated documentation (PDF, HTML, etc.) on the Web site and FTP site are up to date with respect to the versions of the documents in the SVN tree. This includes making sure the Web site build is functioning correctly, and also involves working with the admin team to ensure that the primary Web server has all of the requisite software installed (including build scripts). +* To ensure that the generated documentation (PDF, HTML, etc.) on the Web site and FTP site are up to date with respect to the versions of the documents in the Git tree. This includes making sure the Web site build is functioning correctly, and also involves working with the admin team to ensure that the primary Web server has all of the requisite software installed (including build scripts). * To act as MAINTAINER (when necessary) or to work in coordination with existing MAINTAINERs, to ensure that the documentation toolchains (DocBook, groff, etc.) are in good working order. * To maintain the sanctity of the FreeBSD doc/ tree. Due to the visibility of these files and documents to the outside world, doceng@ reserves the right to immediately backout (or fix without waiting for response from the original committer) changes that introduce broken links, cause the Web site build to break, or otherwise degrade the accessibility of the FreeBSD Web site and documentation. * To appoint and oversee a FreeBSD Webmaster Team that carries out daily maintenance of the Project web servers in collaboration with other teams. diff --git a/website/content/en/internal/new-account.adoc b/website/content/en/internal/new-account.adoc index 76d1f06ae5..530db544c1 100644 --- a/website/content/en/internal/new-account.adoc +++ b/website/content/en/internal/new-account.adoc @@ -55,7 +55,7 @@ accounts@ creates the new account with the above information on the FreeBSD.org == Mentor Activates New Committer's Commit Bit -After the new committer confirms that the account works, the mentor adds the new committer to the correct `access` file, using an appropriate commit message. The commit message should at least contain the committer's full name and username, the mentor's name and what area the new committer will start to work in. An entry should also be added to the `mentors` file in the respective Subversion repository to indicate the mentor relationship. Having done all that, the new committer and mentor jointly go through the first commit operations. +After the new committer confirms that the account works, the mentor adds the new committer to the correct `access` file, using an appropriate commit message. The commit message should at least contain the committer's full name and username, the mentor's name and what area the new committer will start to work in. An entry should also be added to the `mentors` file in the respective Git repository to indicate the mentor relationship. Having done all that, the new committer and mentor jointly go through the first commit operations. == Additional Services @@ -65,8 +65,8 @@ Reading the link:{committers-guide}[Committer's Guide] is considered a good firs == End Of Mentorship -There is no pre-set duration for a mentorship. Once the mentor feels the mentee is ready to 'fly solo' the mentor notifies the developer community by removing the entry from the `mentors` file in SVN. +There is no pre-set duration for a mentorship. Once the mentor feels the mentee is ready to 'fly solo' the mentor notifies the developer community by removing the entry from the `mentors` file in Git. == Transfer Of Mentorship -Should a need arise to transfer mentorship for a committer please email the responsible party, as described for a new account proposal. Typically this request is rubberstamped as-is. In Subversion, the `mentors` file should be updated. +Should a need arise to transfer mentorship for a committer please email the responsible party, as described for a new account proposal. Typically this request is rubberstamped as-is. In Git, the `mentors` file should be updated.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202104291906.13TJ6v2h008519>