From nobody Sun Nov 30 09:06:20 2025 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 4dK1Ns0m0qz6Hyyf for ; Sun, 30 Nov 2025 09:06:21 +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 "R12" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4dK1Nr6ZZLz3YJw for ; Sun, 30 Nov 2025 09:06:20 +0000 (UTC) (envelope-from git@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1764493580; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=rcdMtEYUN37wH1GLI7zBuq+Yr3mGurMZ/I+2VvUpWOM=; b=pu6TowA7Xnm/eUC6bn3zUweqIpvAOGVz/7l8XXSgS5dJ2fedtp8sTiFOwCIm9Gu4XPVHap /mnaZE+cgQ7AZLJWwjRG0w0b8YlOgBNo3yoM4Qmp94O7eD2H0PU4fzSdT/Bpuq291hvwwC HRnKit/KCTIPmIgwu5E62O6jFaK4OEJHy72R8LwU1LDhNVbnmBu1mfSV/jUdvPyvpbvOKx FQaI7CRCUfSUD3SDRNDraAoCGiA66z/AOgw+BzZdtKvV6/ulPqHGw/sqVL6PPRMjNAeDc1 3rDhGeUDa3aMU+Y1NWvBK+MwX8TLV94Iwz0Q9Vk6SSjGSk7ftPFcxf58CWeV1A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1764493580; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=rcdMtEYUN37wH1GLI7zBuq+Yr3mGurMZ/I+2VvUpWOM=; b=cyhedVykUwgTwuw2C3vLd9g7A0kColGRP3UshLdQ8OhNB3DTQwNN64nNi9R8qE7Dpfl+Kh 6OWO+GSYcT2pIGeJzR/Nx8dFILEIto2Eb2zVp0gq5frrCtoLU6daXzPcx7D2My+7XYnGnC fFUeEJXyMfKMfzXK/TKmpA36Ria+79OOql4CfvZu+2AMuH/3j11bSsmEvBPM7zpsGOfB67 ESmqnWTNqYIN8FYMOCQfPBAQFWCRLiY2/0CrldazRGSdKFrcVKox2sYGUiqwthUWyNhJY6 3FtwT1ehJQ7tpRZJ7eMYrNOLGbVgIhOYamCIpTs+YwM2uFNZfG2+JAwF8Egruw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1764493580; a=rsa-sha256; cv=none; b=vYEewLYAVpxBeOrRaqF5oRZwb4FoYwYVP+MYSLYDksvQsH/ny/b2NXprMwKUFpqn8otyVk gc7SpqWUB8EpgQozxMZw1RlDIj8OcfUDVGodCfcWIV1bGLFBIPUW2kqFSF4zt/8pZAYI47 htevMob0+SqJoVR5F+w+fVkjeuZD9PyTTIe0BZHAETYQis6ZaLpjhHmsvY2KTBCGJxdaNM X0Fsu492Xh/gQZbLrjQnQgrujAD4peYEk9jfNRu9yfUyAzTMBdBLEpa+QLTFlSro8OqoRD BiwRebn2dHcpdsI9x5CsC9/y8IVgySE1XvxgrB/jv42JDiTrR7L+F2FWMXaMJw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) by mxrelay.nyi.freebsd.org (Postfix) with ESMTP id 4dK1Nr5MgnzCxL for ; Sun, 30 Nov 2025 09:06:20 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from git (uid 1279) (envelope-from git@FreeBSD.org) id 2e24d by gitrepo.freebsd.org (DragonFly Mail Agent v0.13+ on gitrepo.freebsd.org); Sun, 30 Nov 2025 09:06:20 +0000 To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org Cc: Li-Wen Hsu From: Lorenzo Salvadore Subject: git: 56f2b9189a - main - Status/2025Q3/core.adoc: Add report 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: X-BeenThere: dev-commits-doc-all@freebsd.org Sender: owner-dev-commits-doc-all@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: salvadore X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 56f2b9189a765d7cfd430b037c9ab611ee061bf3 Auto-Submitted: auto-generated Date: Sun, 30 Nov 2025 09:06:20 +0000 Message-Id: <692c090c.2e24d.6e58a864@gitrepo.freebsd.org> The branch main has been updated by salvadore: URL: https://cgit.FreeBSD.org/doc/commit/?id=56f2b9189a765d7cfd430b037c9ab611ee061bf3 commit 56f2b9189a765d7cfd430b037c9ab611ee061bf3 Author: Li-Wen Hsu AuthorDate: 2025-11-30 08:59:34 +0000 Commit: Lorenzo Salvadore CommitDate: 2025-11-30 09:05:18 +0000 Status/2025Q3/core.adoc: Add report Co-authored-by: René Ladan --- .../en/status/report-2025-07-2025-09/core.adoc | 69 ++++++++++++++++++++++ 1 file changed, 69 insertions(+) diff --git a/website/content/en/status/report-2025-07-2025-09/core.adoc b/website/content/en/status/report-2025-07-2025-09/core.adoc new file mode 100644 index 0000000000..fe2afa17ab --- /dev/null +++ b/website/content/en/status/report-2025-07-2025-09/core.adoc @@ -0,0 +1,69 @@ +=== FreeBSD Core Team + +Contact: FreeBSD Core Team + +The FreeBSD Core Team is the governing body of FreeBSD. + +==== Completed Items + +Core completed the following items: + +* EuroBSDCon core session + - dch, glebius, hrs, rene were present at the conference. + - dch had a talk with title "Core Team: Personal Perspective" + +* Removing links to X/Twitter from the project website. + - Core received a question if it is OK to remove links to X/Twitter from the project website. + - As the handle is not being used, core thinks this is fine. + - The Project still needs to control the handle to avoid abuse by others. + - The link can be re-added if someone in the project or Foundation can use those SNS accounts well. + +* Privacy-friendly web analytics, proposed by the Foundation. + - An idea is to compare traffic flows between freebsd.org and freebsdfoundation.org + - Collaborated with doceng and deployed. + +* Core and the FreeBSD Foundation were working on publishing the 2025 edition of the Community survey result. + +==== Work in Progress + +Core is currently working on the following items: + +* Core is creating a working group to restructure doceng. + +* Committer mentorship guideline/rule + - Brought up by inquirers from the developers. + - Core idendified there are some existing documentations but should ask doceng/portmgr/srcmgr for more input. + +* Core election and term changes + - From the feedback of the community, the preferred way is staggered core terms. + - One idea is to rate half of core every year instead of rotating possibly. + all of core every two years, so that in-progress work and experience do not get lost. + - Some developers have strong ideas about this (like rotating a third of core each year instead of all of core every two years) and would like to be involved. + - We need to have the bylaws changed for this, the standard is high. + - There are suggestions from the community for we just change the bylaws as core does not legally represent anybody. + Is that really a good idea? + - This discussed at core session at BSDCan developer summit 2025. + - Core is continuously working on this toward to setup staggered core terms. + +* Project continuity + - Brought up by an inquriy from a developer + - We need (updated) documentation on how to rebuild the critical systems to ensure business continuity of the FreeBSD Project. + This encompasses three aspects: + - Our own project business continuity (loss of key personnel or infrastructure) + - Replication for end consumers of FreeBSD + - How does our release engineering work, and which of the various teams are impacted. + - Currently too much knowledge depends on tribal memory, need to collect, sort and documented. + - An artifact of the STA work is that release documentation is written (next to the releng article in doc repository). + Some corner cases are currently missing. + +* Committer GECOS fields and pseudonyms + - A question came from a developer about whether pseudonyms can be used as committer names. + - There is a higher concern about how to deal with any copyright issues. + - Core however does not feel that using pseudonyms is endorsed as it makes paperwork and restoring cluster access more difficult, and suggests mentioning the advantages of using real names. + - Another way pseudonyms could cause problems is when the identity is shared, e.g. in case of a vendor commit bit, who will be the spokesperson? + +* AI policy + - The Core Team is in the process of drafting a policy on using AI and LLMs. + - For this effort, it also plans to consult with other groups, such as the Foundation's legal counsel and people in the Linux and other open source communities who are working on related topics. + - There are various questions about copyright, guaranteeing code provenance, best practices and "common sense" by both developers and external contributors, and what can and cannot be done with AI (assisted) tools. + - There have been many follow-up discussions after BSDCan and EuroBSDCon, and core is organizing and summarizing them.