---
# System prepended metadata

title: 2020Q3 Report
tags: [FreeBSD]

---

# 2020Q3 Report

FreeBSD Core Status Report

Months:                        July, August, September 2020

Status:                        DRAFT
Prepared by:                   bofh
Reviewed by:			       jhb

Table of Contents
-----------------

1. Introduction
.. 1. Meetings
2. Completed Items
.. 1. Fast Response to CONDUCT issues
.. 2. privacy@ and GDPR requests
.. 3. CORE Town Hall Meetings
..... 1. CORE 11 Town Hall 1 - FreeBSD Office Hours 6
..... 2. CORE 11 Town Hall 2 - FreeBSD Office Hours 7
..... 3. CORE 11 Town Hall 3 - FreeBSD Office Hours 11
.. 4. conduct@ issue
..... 1. bapt@ handled one conduct issue
.. 5. AWS Credits replenished
.. 6. New toys for postmaster@
.. 7. Digital legacy of bde@
.. 8. Extra meeting with lwhsu@ for CI improvement
.. 9. Restoring the src bit for qingli@
.. 10. Revamping ports-secteam@
.. 11. Change in RE Deputy Lead
3. Commit Bits
.. 1. Rob Wing
4. Closed Items
.. 1 markj to write a proposal for Foundation funding to work on Network epoch
.. 2 Git working group followup
.. 3 jrm@ proposed to merge 800+ chromium patches upstream
.. 4 Possible git client in base
5. Summary of Items Discussed Since 2020-04/05/06 Report
.. 1 bapt@ proposed about splitting port-mgr@

1 Introduction
==============

1.1 Meetings
July

2020-07-14: bofh emaste gnn hrs imp markj scottl seanc
2020-07-28: bapt bofh emaste gnn imp kevans markj

August

2020-08-11: bapt bofh emaste gnn hrs imp kevans seanc
2020-08-25: bapt bofh emaste gnn hrs imp kevans markj

September

2020-09-08: bapt bofh emaste gnn imp kevans seanc
2020-09-16: bofh emaste gnn imp lwhsu scottl seanc
2020-09-22: bapt bofh emaste gnn imp kevans scottl seanc

2. Completed Items

2.1. Fast Response to CONDUCT issues
Owner:      CORE
Completed:  2020-07-14
Resolution: gnn will work as the pager for FAST reponse to CONDUCT issues.
Source:     Internal


2.2. privacy@ and GDPR requests
Owner:      CORE
Completed:  2020-07-14
Resolution: privacy@ and GDPR requests are forwarded to core@ for further
            discussions.
Source:     Internal

2.3. CORE Town Hall Meetings
The FreeBSD CORE 11 team has decided to arrange regular Town Hall Meetings for the community; Which will give The CORE Team to work more closely with the developers. As an attempt towards that the CORE team arranged 3 Virtual Town Hall meetings.

2.3.1. CORE 11 Town Hall 1 - FreeBSD Office Hours 6
This Town Hall took place on 7th July 2020 on 1800 UTC and was targeted mainly towards the Europe and Americas. The agenda is available in the following:
https://wiki.freebsd.org/CoreIntro2020

The recorded video is available from Youtube in the following link:
https://www.youtube.com/watch?v=exxgZoephis

2.3.2. CORE 11 Town Hall 2 - FreeBSD Office Hours 7

This Town Hall took place on 8th July 2020 on 0200 UTC and was targeted mainly towards the Asia and Africa. The agenda is available in the following:
https://wiki.freebsd.org/CoreIntro2020

The recorded video is available from Youtube in the following link:
https://www.youtube.com/watch?v=_gS9YDySvGI

2.3.3. CORE 11 Town Hall 3 - FreeBSD Office Hours 11

This Town Hall took place on 23rd September 2020 on 1800 UTC and was targeted mainly towards the Asia and Africa. The agendas were discussion about git transition, recruiting for project teams and publishing CORE TODO lists.

The recorded video is available from Youtube in the following link:
https://www.youtube.com/watch?v=2k0Gz3kKbbs

2.4 conduct@ issue
2.4.1. bapt@/kevans@ handled two conduct issue

We have been reported a conduct issue. Due to the nature and non-english language barrier bapt@ had to intervene and has been solved accordingly. Besides that there were one more conduct@ issue that has been escalated to core@ which was also handled by bapt@ and kevans@.

2.5. AWS Credits replenished

We were running short of AWS credits. emaste@ had a discussion with collins@ who has confirmed that nothing to worry about that as AWS will replenish or add credits when needed.

2.6. New toys for postmaster@

postmaster@ requires new toys for upgrading our mail infrastructure. gnn@ will take care of this issue as the Foundation has necessary fundings available. Once postmaster@ informs about their requirement gnn@ will pickup from there and complete the necessary work to avail the hardwares for postmaster@.

2.7. Digital legacy of bde@

Owner:        imp
Completed:    2020-09-08
After the sad demise of bde@; imp@ stepped up to sort out his digital legacy. bde@ has been a significant contributor towards FreeBSD src tree and there might be that he had some unfinished work in his home. imp@ decided to sort it through as it might also contain some personal info. Based on the sorting imp@ will decide what to publish.

2.8. Extra meeting with lwhsu@ for CI improvement

Owner:        core
Completed:    2020-09-16

An out of schedule meeting took place between core@ and lwhsu@ to understand the current standing of the FreeBSD CI system and how it can be evolved to a better standing in terms of Release Artifact reproducibility.

2.9. Restoring the src bit for qingli@

Owner:        gnn/imp
Completed:    2020-09-16

qingli@ requested src commit back. After some discussion imp@ took the initiative to restore his bit back while gnn@ stepped up to mentor.

2.10. Revamping ports-secteam@

Owner:        core
Completed:    2020-08-25

We received a dissatisfaction from the ports-secteam@ that noone was responsive and was working except joneum@ and gjb@. So core@ decided to handover the responsibitility of ports-secteam@ over to joneum@ so that the team can be revamped with fresh bloods.

2.11. Change in re@ Deputy Lead

Owner:        core
Completed:    2020-08-23

marius@ decided to step down from the re@ Deputy role. Based on involvement and free cycle gjb@ proposed cperciva@ to step up as the Deputy Lead. Core acknowledged and approved the changes.

2.12. Change in clusteradm@ Lead

Owner:        core
Completed:    2020-07-17

peter@ decided to stand down from the clusteradm@ Lead role. So core@ requested zi@ to accept the Lead role which was well accepted by other members of the team.

3. Commit Bits

3.1 Rob Wing
kevans@ proposed a src Commit Bit for Rob Wing. And the bit was awarded with the following votes

Yes: bapt, emaste, gnn, imp, markj, scottl, seanc
No:
Abstain: kevans, hrs

4. Closed Items

4.1 markj to write a proposal for Foundation funding to work on Network epoch

Owner:      markj/gnn
Completed:  2020-07-14
Resolution: markj will followup with FF under his current contract
Source:     Internal

markj: I don't think that's really a core related item. I could probably do some of that work under my existing contract. So I'm not really not too worried about that. It's more about establishing a technical direction for that problem.

4.2 Git working group followup

Owner:      emaste/imp
Completed:  2020-08-11

emaste@ and imp@ will ensure that the git migration schedule is completed and published in the git working group meeting. With this marks the completion of the followup with the git working group.

imp@ will also followoup on the updates of the docs@ for git migration and git primer documentation.

emaste@ mentioned that the git conversion will take place in between after the release of 12.2 and before the release of 13.0.

In the future releases we will also try to phaseout portsnap.

4.3 jrm@ proposed to merge 800+ chromium patches upstream

Owner:      bapt
Completed:  2020-08-25

jrm@ proposed whether if anyone has any connection in Google who can help us merge 800+ patches in chromium upstream. bapt@ has notified that this has been attempted multiple times without any result so this should be a waste of time. So suggested jrm@ to try it by himself again. Unless otherwise nothing more to do as previously many have notified about connection in Google who can help land the patches; which eventually didn't happen.

4.4 Possible git client in base

Owner:        bapt/emaste/imp
Completed:    2020-09-08

There was a discussion about the possibility of integrating a git client in the base system. Unfortunately at this stage there were no implementation of git available in C which can be integrated/vendor imported into the system. OpenBSD team is working on such a client and it's not clear at this stage how long it might take to achieve a production state.

5. Summary of Items Discussed Since 2020-04/05/06 Report

5.1. bapt@ proposed about splitting port-mgr@

Owner:          bapt
Created:        2020-08-25

bapt@ proposed about splitting into two different teams one working actually on ports management and defining ports infrastructure while the other naming pkg-mgr@ will work on the infrastructure level creating necessary hosts and jails and pkg sets as we roll new version of FreeBSD and update those regularly. This is still under discussion with the port-mgr@

Updates:        2020-09-08

bapt@ mentioned the some of the port-mgr@ wants a voting member from the Core Team.

# vim: ft=txt : columns=72