diff --git a/site/blog/2024-02-07-community-call/README.md b/site/blog/2024-02-07-community-call/README.md new file mode 100644 index 000000000..e275422f0 --- /dev/null +++ b/site/blog/2024-02-07-community-call/README.md @@ -0,0 +1,42 @@ +--- +title: Frictionless Data Community Call January 2024 +date: 2024-02-07 +tags: ["events", "community-hangout"] +category: events +image: /img/blog/Specs-Update-February-Call.png +description: At our last monthly call continued talking about the specs update... +author: Sara Petti +--- +On our last community call was on January 25th, we continued discussing the [Frictionless Specs](https://specs.frictionlessdata.io/) update with community members. As a reminder, thanks to the generous support of [NLnet](https://nlnet.nl/), the Frictionless core team, together with a working group composed of members of the community, is now working on a v2 of the Specs. Read the [announcement blog](https://frictionlessdata.io/blog/2023/11/15/frictionless-specs-update/) to know more about it. + +## Working group discussion + +The first thing we discussed was ways to prioritise candidate features for future Specs updates (beyond v2). At the moment, our idea is to prioritise those issues that get more votes (aka thumbs up), among the [issues in the Specs repository](https://github.com/frictionlessdata/specs/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc). + +Note, the reference for the v2 update is still [the one we initially published as a roadmap](https://github.com/frictionlessdata/specs/milestone/6) in the update announcement blog. For the v2 release we will stick to that list of issues. + +Anyone is welcome to open a Pull Request to address any of those issues. The PR will then be reviewed by the working group, according to the [decision-making process](https://frictionlessdata.io/blog/2023/11/15/frictionless-specs-update/#decision-making) we have agreed upon. + +In case of neutral response from a high number of members of the working group which prevents the achievement of the consensus, the issue gets deprioritised. In case someone has a strong interest for a certain issue that gets deprioritised, they can bring it to discussion during one of the calls. + +Evgeny also brought up that on top of the Specs themselves, there are many non-functional things that need to be updated too. For example, the Specs navigation needs to be improved, with a clear structure of the metadata properties. Since all this non-functional stuff is still part of the Specs, and should therefore follow a defined process, it was proposed that this part would be led by OKFN, and reviewed at the end by working group members. + +The last thing that we discussed during the calls were `patterns`. The purpose of the `patterns` has not been super well defined within the Frictionless project, and it is now unclear to some. The idea at the time they were introduced, was for them to be best practices, but not refined enough to be part of the Specs quite yet. It was also a way to share a certain approach. But there was no clearly defined mechanism to promote the `patterns` to be part of the Specs. + +Since the approach with this Specs update is to simplify as much as possible and cut out what is not needed, it was decided to include the `patterns` in the Specs documentation (as some kind of Cook Book) and not in the Specs themselves, and rename them as their current name suggests a certain formality. + +# Join us in February! +Next community call is on February 22tnd, join us to hear all the exciting news about the [Frictionless specs](https://specs.frictionlessdata.io/) update! + +Do you have something you would like to present to the community at one of the upcoming calls? Let us know via [this form](https://forms.gle/AWpbxyiGESNSUFK2A), or come and tell us on our [community chat on Slack](https://join.slack.com/t/frictionlessdata/shared_invite/zt-17kpbffnm-tRfDW_wJgOw8tJVLvZTrBg)(also accessible via a [Matrix bridge](https://matrix.to/#/#frictionlessdata:matrix.okfn.org) if you prefer to use an open protocol). + +You can sign up for the call already [here](https://docs.google.com/forms/d/e/1FAIpQLSeuNCopxXauMkrWvF6VHqOyHMcy54SfNDOseVXfWRQZWkvqjQ/viewform?usp=sf_link). Do you want to share something with the community? Let us know when you sign up. + +# Call Recording +Here is the recording of the full call: + + + +# Thank you +On a final note, we would like to thank all community members that joined the call and that keep all these discussions alive, and particularly to those who are putting a lot of thinking and hard work into the specs working group. Without you, all of this would not be possible. +