License policy

Regarding the license policy, this comes from the previous meeting where we discussed about the license of two crates.

Our project charter already allows usage of open source licenses for other repos that are not the main Servo one, if it's an open source license. See "7. Intellectual Property Policy".

So this point is just to verify everyone is fine with this.

Request : project top-3 or top-5 highest priorities to help focus development efforts, thanks

Request : project top-3 or top-5 highest priorities to help focus development efforts, thanks

To tag onto this, I've mentioned it on Zulip before but it would be nice to have some more visible tracking for the state of various API implementations. The idea I proposed was a pinned github issue that could act as a "meta-meta bug" showing which APIs are under development, each of which could in turn also have their own meta bug or bugs linked. Something else that could be useful (this would probably belong in the Servo book somewhere) would be an outline of how to approach implementing a new DOM API with the relevant in-tree documentation linked (for example, https://doc.servo.org/script/dom/index.html)

We have servo triage meeting to discuss issues and PRs: #104
However, it's only about the issues related to the participants for now.
We could take this chance to put some top priority issue and see how we push them more.

Request : project top-3 or top-5 highest priorities to help focus development efforts, thanks

To tag onto this, I've mentioned it on Zulip before but it would be nice to have some more visible tracking for the state of various API implementations. The idea I proposed was a pinned github issue that could act as a "meta-meta bug" showing which APIs are under development, each of which could in turn also have their own meta bug or bugs linked.

We have been using https://github.com/servo/servo/projects for some features, so probably that could be a way to group issues related to a particular feature we want to work on.

AI policy update

@delan has created a PR for the Servo book to update the policy: servo/book#27

Future of rust-url

I would like to add a point to the agenda where we discuss whether or not rust-url should spin out into a separate GitHub organization or not.