Skip to content

Commit

Permalink
Merge pull request #17 from onebeyond/chore/meeting-notes
Browse files Browse the repository at this point in the history
feat: added meeting notes 13-12-2022
  • Loading branch information
UlisesGascon committed Jan 10, 2023
2 parents 6283d9e + 0735c89 commit 6212984
Showing 1 changed file with 67 additions and 0 deletions.
67 changes: 67 additions & 0 deletions meetings/2022-12-13.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
# One Beyond Open Source Admins Meeting 2022-12-13

## Links
* **recording:** Available in [Sharepoint](https://dcslsoftwareltd.sharepoint.com/:v:/s/Architecture-team/EaISqXNk2dhHgYgrUKBVIncBL_w1wNAvObpTtxt8c3MzGw?e=kFJ9kc). Please contact Ulises/Iñigo if you don’t have access
* **Github issue:** [#11](https://github.com/onebeyond/admin/issues/11)
* **Minutes Google Doc:** (https://docs.google.com/document/d/1vasPDzesFxTe4LHgu5MTV9qSdriAN4zmmjSYDI1Bgb8/edit?usp=sharing)


## Present
__Use github alias__
* Admins team: @onebeyond/admins
* Maintainers team: @onebeyond/maintainers
* Ulises Gascón: @ulisesgascon
* Iñigo Marquinez: @inigomarquinez
* Carlos Jimenez: @betisman
* Carlos Serrano: @carpasse
* Javier G. Leal: @jgleal
* Cesar Demicheli: @CesarD

## Announcements

## Agenda

### Define Org teams in Github
- [see](https://github.com/onebeyond/admin/issues/5)
- We created the organic teams (admins, maintainers, triage..)
- We created the first specific teams and “Pills team” will be removed
- We will create teams when is needed.
- Ulises will provide a clear documentation on how to manage the teams and the relationship with the repos.

### Define migration strategy and start the process
- [see](https://github.com/onebeyond/admin/issues/6)
- More than 25 repositories were already migrated from Guidesmiths Org
Jaystack can start the migration at any moment. Ulises will provide support to Peter Z. and Peter N. in January.
- Possible second round to migrate more repositories outside of the current backlog

### Define contribution policies
- [see](https://github.com/onebeyond/admin/issues/4)
- We agreed in the need to separate the open source communication and create a Public (by invitation) Slack that can help us to community with the community and the include automation.
- Iñigo will ask for the new Slack (One Beyond Open Source)

### Repo template as baseline
- [see](https://github.com/onebeyond/admin/issues/1)
- CoC added waiting for a clear contact form (Open Source Slack)
- Github actions added
- Settings like protecting branched are not properly copied from the template to the new repository. This will require additional research (Create an issue to track, Ulises lead)
- Possibility to use metafiles for license, contributing.md. To centralize this information in a single point (Ulises will lead it)


### Define License policies
- [see](https://github.com/onebeyond/admin/issues/3)
- We should use MIT licenses for all the repos (currently and in the future).


## Q&A, Other

- Great Resource: [opensource.guide](https://opensource.guide)
- Open Source metrics
- We can start the discussion in the next meeting.
- Roadmap definition
- There is a need to manage a roadmap for some projects
- We are not in a stage to define how this will be defined as organization process, so we are not taking any decision now.


## Upcoming Meetings

- Next week, same day and hour

0 comments on commit 6212984

Please sign in to comment.