[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Development meeting notes, Feb 18
From: |
Ruben |
Subject: |
Development meeting notes, Feb 18 |
Date: |
Fri, 19 Feb 2021 16:45:52 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Icedove/68.10.0 |
* Libor sent an email about manifest v3. Some points are not set in
stone yet, there will be one year overlap for v2 and v3 to coexist.
* New API announced for page level scripts in chrome, provides a new way
to access the DOM, this could impact our possible methods for modifying
the environment. Georgio will keep an eye on this.
- We may want to advertise our extension as Firefox-only, in case the
chrome version ends up not being effective.
* Giorgio to push first PR on pagure. Improve the injection code to make
it possible to unify wrappers between browsers by modifying the
environment in which the wrapper works. This would make the wrapper code
browser-agnostic. Libor agrees with this approach. Similar code is
available on NoScript common library. It will be a big patch, it affects
both the injection code and the wrappers.
* Martin has improved the unit test system, it may help test Giorgio's
MR, maybe we may need to write specific tests for it.
* JSR 0.4.5 released, with new wrappers for media devices. Fixed some
bugs and improved handling of domains. Martin is working on the testing,
not yet finished. He will be also working on other related project from
university.
* Libor reported ticket about coding naming conventions. Currently using
conventions from APIManager. An alternative would be WebIDL files.
* Last week we discussed the doxygen documentation, Libor created a
branch on pagure with some more content in the documentation, for the
design team to work on. Also working on more license related information
on the doc. This batch of changes may conflict with Giorgio's change
(G's changes should not affect filename conventions, should add some
files, some changes to Makefile).
* We want to document the changes to geolocation API, media devices API
and mbs, and that should be an example on how other wrappers should be
documented. Libor would start a thread on this topic.
* For restructure of code, moving the wrappers into their own directory
and naming conventions (maybe categories), this should happen after
merging Giorgio's code, and contributions from FSFE (they want to add
machine readable license notification; https://reuse.software ; SPDX
headers for all relevant files; also to discuss contribution policy).
--
Ruben Rodriguez | Chief Technology Officer, Free Software Foundation
GPG Key: 05EF 1D2F FE61 747D 1FC8 27C3 7FAC 7D26 472F 4409
https://fsf.org | https://gnu.org
signature.asc
Description: OpenPGP digital signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Development meeting notes, Feb 18,
Ruben <=