# 8th March 2023, 21:00 - 22:00 UTC+0
Attendees: Thomas, Prakhar, Anastasia
## Decision summary
* We will be using CreativeCommons license for documentation, CC-BY-4.0 * 26th April on this meeting will be a “development guidelines brainstorming session”. Everyone with ideas on how to improve development guidelines is welcome to join. * 3 weeks break for meetings between 22th March and 12th April. And then every 2 weeks as usual.
## Agenda
* [aklm] We wanted to have a “development guidelines brainstorming session” after the release. Seems the time has come? We can allocate the next meeting for this? Or maybe the next meeting in April, depending on who wants to join. * Yes we can do it on 26th of April. We can create a doc for brainstorming, and everyone will edit it. Once the text is composed, then it can be added to documentation. * [Thomas] How should we license the new documentation? GPL / CreativeCommons / something else * GPL is optimised for code/software * and then CreativeCommons is for everything, not just code/software * what is the level of CreativeCommons license that would be equivalent to what we have now? CC-BY -> do everything that you want, but have to name the original authors. * [https://doc.coreboot.org/documentation_license.html%5D(https://doc.coreboot....) coreboot has different license for code vs documentation. * that would enable people to write a tutorial based on new docs. * Do we need to add a line to every doc? * (..|//| #) SPDX-License-Identifier: CC-BY-4.0 * we can add git hook to check for this one line * The one-line can be used for code too, with the existing license. Would save repetition of the same text in every file. * [aklm] can we do a 3 week gap between the last meeting in March and first in April? and then 2 weeks as usual. * Yes, we will have a meeting on the 22nd of March as usual, and then 12th April, and then every 2 weeks as usual.