# gitcvt Meetings (https://meet.google.com/njw-rsdg-vbf)

## Meeting 2
2023-08-10 1400 UTC

### Agenda
https://hackmd.io/9zFPQirwTByQY6S93g9qiA

## Meeting 1
2023-07-27 13:00 UTC

### Agenda
Not defined for this meeting

### Attendees:
- Li-Wen Hsu
- Warner Losh
- Ed Maste
- Muhammad Moinur Rahman (moin)
- Ihor Antonov

### Takeaway Action Items

1. Standup external gitea instance for collaboration and hacking.
2. Hackmd notes of meeting minutes (done)
3. Decision Record document:
- Needs to be finialized to asciidoc
- https://asciidoclive.com/
- https://wang-yan-hao.github.io/FreeBSD-Online-Document-Editor/root/
- Google docs is a good place to collaborate on it in the meenwhile

### Minutes

#### Ihor

Welcomes everyone. Asks about the agenda of the meeting and the purpuse of the working group.

#### Moin

Agenda is to what to do with our tools.

#### Li-Wen

Shares his thoughs: was working on SVN to GIT conversion.
This was phase 1. Phase 2 is how to use git the right way and to reduce
the friction to contribution.

Li has a feeling that people would like to have PR based contribution model.
What people want is easier merge model and less painful experience.
Pre-merge/pre-commit CI, secondary - better code review experience.

Gitlab/Github is opposed to Phab in their workflow/contribution style.

One reason that tipted the scale into gitlab/github side.

Phabricator is not a very friendly user experience.
Should we go with Phab/Phorge?
What we should do in the following months for this WG:

Formalize what a next generation system cover. What features/properties we value?
- SSO system.
- CI/ CD system (needs a lot of help)
- Easier merge.

Postpone bugzilla migration bugs migration as CI work has more value and impact.

#### Warner

We need to have an agenda ahead of time. Use HackMD to post the agenda.
This is how graphics team works and it works well for them.

Recaps of what LiWen said:

1. Improve CI/CD and contribution experience
2. Requirements/Design doc to explain decison tradeoffs

Ass Li - Do we have a set of tools in mind to meet the criteria?
Is this GitLab? Something else?

#### Li-Wen

If we want a self-hosted solution the only good options:
- Gitalb
- Gitea (preferred)

Self-hosted is preferred option for the FBSD Project.

note: Gitbox - bidirectional sync mechanism between github and self-hosted isntance, may be interesting to look into later.

Forgejo/Gitea - no preference at the moment.
There is a prototype instance of gitea but access is complicated.

Private beta will be hosted on internal resources and will eventually become our new prod instance.

#### Moin

(noise)
.. does not prefer gitlab anymore

#### Li-Wen

Gitlab is difficult to deploy/update due to complicated dependencies
but it can be worked around. Also having staging system helps.

#### Ihor

Prefers gitea due to easier development/deployment and better programming language and better performance.

#### Ed Maste

There is merit to setup external gitea instance.
..don't like the idea of factions within package community. Not easy to resolve.

We need to be transparent about setting up external test instance

#### Warner

Use what is best for the project.
Public stuff is good - getting feedback is good. Even negative one.
This effort will need to attract more interested contributors to help.
Even outside of coding: documentation, communication.
Writing docs ahead of time is important.
The more public and transparent it is the less POLA violation :D

There is a risk of astonishment with this:
- redocument review process
- new CI system
We need to communicate early and often to avoid astonishing users.

Our problems are not too unique. It is ok to use a popular tool which
has some flaws. It is worse to use a custom/unique tool that nobody uses.

#### LiWen

It is important to write down features we need.
Decision Record(DR) document.
SVN-GIT process used WIKI.
Start in hackmd or wiki. Use it as homework for next meeting.

#### Warner

We need 2 paragraphs summary on what we are trying to do
and send it to core team to align with them.
Will(maybe) come up with a draft to the next meeting.

#### LiWen

Has desire to present something at EuroBSDCon on September and/or
on DevSummit in November.

#### Moin/Warner

Next meeting in 2 weeks. 2 weeks is a good cadence