profile
viewpoint
Tobie Langel tobie UnlockOpen Geneva, Switzerland http://www.tobie.me

prototypejs/prototype 3491

Prototype JavaScript framework

EthicalSource/ethicalsource.dev 114

Home of the Organization for Ethical Source

ampproject/meta 48

Information about the AMP open source project.

ampproject/meta-ac 23

The AMP Advisory Committee

savetheclocktower/prototype 14

Prototype JavaScript framework (forked for some disruptive changes)

madrobby/sprockets 8

JavaScript dependency management and concatenation

tobie/async-it 6

Generic asynchronous iterators for node.js.

ampproject/wg-foundation-onboarding 2

Responsible for work/coordination related to AMP completing the OpenJS Foundation onboarding

tobie/async-memoizer 2

A memoizer for asynchronous methods obeying node.js conventions.

PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent

Pull request review commentw3ctag/ethical-web-principles

Intro: add paragraph about balancing principles, for #62

 (for example, with strong privacy protections).  The web should also support human rights, dignity and personal agency.-We need to put internationally recognized human rights at the core of the web platform. [[?UDHR]]+We need to put internationally recognized human rights at the core of the web platform [[?UDHR]]. And we need to promote ethical thinking across the web industry to reinforce this approach. +The principles in this document are deliberately unordered,+and many are interconnected with each other.+While all of the principles together aim to provide pillars that collectively support+a web that is beneficial for society, there are cases where upholding one principle+may diminish the efficacy of another principle.+Thus in applying these principles, there are benefits and tradeoffs+that may need to be carefully balanced. When faced with principles+which appear to be in conflict with one another,+it is important to consider the context in which a particular technology+is being applied, the expected audience(s) for the technology,+who the technology benefits and who it may disadvantage,+and any power dynamics involved.

I don't think it's instead of though, as you could conceivably end up with competing principles applying to the same constituent,[…]

Ha! That’s a great point I hadn’t thought about. That sounds like the right way to go about this!

rhiaro

comment created time in 12 days

PullRequestReviewEvent

Pull request review commentw3ctag/ethical-web-principles

Intro: add paragraph about balancing principles, for #62

 (for example, with strong privacy protections).  The web should also support human rights, dignity and personal agency.-We need to put internationally recognized human rights at the core of the web platform. [[?UDHR]]+We need to put internationally recognized human rights at the core of the web platform [[?UDHR]]. And we need to promote ethical thinking across the web industry to reinforce this approach. +The principles in this document are deliberately unordered,+and many are interconnected with each other.+While all of the principles together aim to provide pillars that collectively support+a web that is beneficial for society, there are cases where upholding one principle+may diminish the efficacy of another principle.+Thus in applying these principles, there are benefits and tradeoffs+that may need to be carefully balanced. When faced with principles+which appear to be in conflict with one another,+it is important to consider the context in which a particular technology+is being applied, the expected audience(s) for the technology,+who the technology benefits and who it may disadvantage,+and any power dynamics involved.

This seems very reminiscent of the priority of constituencies. Referencing it here does create somewhat of a circular dependency problem, though.

Curiously, the priority of constituencies seems to be both a concrete implementation of some of these principles in the platform and (as you describe here) a sort of meta principle that sits as an arbiter between said principles. I feel like @mnot addresses this tension well in RFC 8890 by tying the end-user focus to IETF's mission. Maybe we need something similar for W3C, to your point in #37 and @torgo's comment in #58?

In the meantime, I'd suggest either merging as is (and making a note of that tension in an issue) or replacing most of the selected text by a reference to the priority of constituencies (and filing an issue to come back and deal with the circularity of it all).

rhiaro

comment created time in 12 days

PullRequestReviewEvent
PullRequestReviewEvent

delete branch ampproject/meta-ac

delete branch : tobie-membership-update

delete time in 15 days

push eventampproject/meta-ac

Tobie Langel

commit sha e3977fc2f54a53478bb4bae5bfc00f943a3f8712

Update AC membership (#213)

view details

push time in 15 days

PR merged ampproject/meta-ac

Update AC membership
+5 -5

1 comment

1 changed file

tobie

pr closed time in 15 days

pull request commentampproject/meta-ac

Update AC membership

Approved during AC meeting #214.

tobie

comment created time in 15 days

issue openedampproject/meta-ac

AC Meeting 2021-11-15/16

Logistics

Meeting time

<!-- Watch out to fix UTC times depending on daylights savings.

Currently, the Americas & EMEA meetings shifts to accomodate daylight savings. So meetings are held:

  • at 5pm UTC during the northern hemisphere summer months and
  • at 6pm UTC during the northern hemisphere winter months.

The EMEA & APAC meetings do NOT change with daylight savings. Meetings are held at 11am UTC all year round. -->

Region Date Time (UTC) Local time
Americas & EMEA Monday, November 15 6pm UTC See it in your timezone
EMEA & APAC CANCELED -- --

Video conferencing details

Zoom Meeting: https://us02web.zoom.us/j/88232401009?pwd=NnRiNTFZeFAvMU5uMnVGZk5tNi9Tdz09 Meeting ID: 88232401009 Password: 301196 Find your local number: https://zoom.us/u/avfhv6bQL

Note: We use the same conferencing details for both meetings.

Agenda

  • Approve pull request #213
  • Welcome Dan Walmsley as interim member (as per process).
  • Update on the last TSC meeting
    • Resignation of two members
    • Proposal: online TSC/AC "workshop" to clarify the direction of the project and role of the different governing bodies in light of external changes (see Long-Term Vision TF Report)
  • Check roster for TSC meeting.
  • Check roster for Design reviews.

Note: Add a comment on this issue to propose items for the agenda.

Minutes

created time in 15 days

issue openedw3ctag/ethical-web-principles

Offer a framework to handle conflicts between principles

What happens when improving privacy increases your environment footprint or makes controlling the spread of disinformation more difficult?

Which principle should you favor and why?

Is there a priority of principles likes there is a priority of constituencies?

Can you make tradeoff and if so, based on what?

Can the TAG help and if so how do you get their help?

Building on #62 would be great to have a framework to navigate conflicts between principles, or at least a set of suggestions to do so.

created time in 17 days

issue openedw3ctag/ethical-web-principles

Acknowledge that principles can come in conflict with one another

For example transparency ("We will always make sure it is possible to determine how a web application was built and how the code works.") can conflict with reducing the web's environmental footprint (shipping binary data would probably be more efficient), preventing the spread of misinformation may conflict with privacy, enabling users to render their content as they please may conflict with security concerns, etc.

Some principles acknowledge this tension, for example in §2.6 The web must enable freedom of expression: "Our work should not enable state censorship, surveillance or other practices that seek to limit this freedom. This principle must be balanced with respect for other human rights […]".

It would be good to acknowledge this in general, maybe right after the introduction or in conclusion.

created time in 17 days

PullRequestReviewEvent

PR opened ampproject/meta-ac

Update AC membership
+5 -5

0 comment

1 changed file

pr created time in 23 days

create barnchampproject/meta-ac

branch : tobie-membership-update

created branch time in 23 days

issue openedampproject/meta-ac

AC Meeting 2021-11-01/02

Logistics

Meeting time

<!-- Watch out to fix UTC times depending on daylights savings.

Currently, the Americas & EMEA meetings shifts to accomodate daylight savings. So meetings are held:

  • at 5pm UTC during the northern hemisphere summer months and
  • at 6pm UTC during the northern hemisphere winter months.

The EMEA & APAC meetings do NOT change with daylight savings. Meetings are held at 11am UTC all year round. -->

Region Date Time (UTC) Local time
Americas & EMEA Monday, November 1 <!-- summer --> 5pm UTC <!-- summer --> See it in your timezone
EMEA & APAC Tuesday, November 2 11am UTC See it in your timezone

Video conferencing details

Zoom Meeting: https://us02web.zoom.us/j/88232401009?pwd=NnRiNTFZeFAvMU5uMnVGZk5tNi9Tdz09 Meeting ID: 88232401009 Password: 301196 Find your local number: https://zoom.us/u/avfhv6bQL

Note: We use the same conferencing details for both meetings.

Agenda

Note: Add a comment on this issue to propose items for the agenda.

Minutes

created time in a month

issue commentopenjs-foundation/cross-project-council

OpenJS Foundation Cross Project Council Meeting 2021-10-26

Sending regrets. Really not feeling well.

mhdawson

comment created time in a month

issue openedampproject/meta-ac

AC Meeting 2021-10-18/19

Logistics

Meeting time

<!-- Watch out to fix UTC times depending on daylights savings.

Currently, the Americas & EMEA meetings shifts to accomodate daylight savings. So meetings are held:

  • at 5pm UTC during the northern hemisphere summer months and
  • at 6pm UTC during the northern hemisphere winter months.

The EMEA & APAC meetings do NOT change with daylight savings. Meetings are held at 11am UTC all year round. -->

Region Date Time (UTC) Local time
Americas & EMEA Monday, October 18 5pm UTC See it in your timezone
EMEA & APAC Tuesday, October 19 11am UTC See it in your timezone

Video conferencing details

Zoom Meeting: https://us02web.zoom.us/j/88232401009?pwd=NnRiNTFZeFAvMU5uMnVGZk5tNi9Tdz09 Meeting ID: 88232401009 Password: 301196 Find your local number: https://zoom.us/u/avfhv6bQL

Note: We use the same conferencing details for both meetings.

Agenda

Note: Add a comment on this issue to propose items for the agenda.

Minutes

created time in a month

push eventopenjs-foundation/cross-project-council

Tobie Langel

commit sha d92430f037ddf22bec85cd0e6a78c881591e687f

Add reminder to review issues labeled cpc-quartely-review

view details

push time in 2 months

PR opened openjs-foundation/cross-project-council

Track issues outside of Dates-and-Reminders.md

Moving issues we want to revisit out of the Dates-and-Reminders.md document and track them with the cpc-quartely-review label instead.

+0 -5

0 comment

1 changed file

pr created time in 2 months

IssuesEvent

issue commentopenjs-foundation/cross-project-council

Build stronger ties between At Large maintainers and their CPC Rep

Reopening for assessing outcomes in next quarterly review.

tobie

comment created time in 2 months

issue closedopenjs-foundation/cross-project-council

Dojo report link in Code of Conduct is broken

The link to the report form for Dojo in the Code of Conduct now leads to a 404 page

closed time in 2 months

OLD-and-changed

issue commentopenjs-foundation/cross-project-council

Dojo report link in Code of Conduct is broken

Thanks for fixing this @dylans! <3

OLD-and-changed

comment created time in 2 months

issue commentw3c/manual-of-style

Update inclusive terminology guidance

Oh yeah, “he or she” is awful. I’m certainly not advocating for that.

LJWatson

comment created time in 2 months

more