Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate with W3C mission statement #163

Open
cwilso opened this issue Mar 27, 2024 · 6 comments
Open

Integrate with W3C mission statement #163

cwilso opened this issue Mar 27, 2024 · 6 comments
Assignees
Labels
Project Vision Vision and Principles

Comments

@cwilso
Copy link
Collaborator

cwilso commented Mar 27, 2024

We should ensure eventually that this is closely aligned (in both directions) with w3.org/Mission and the branding there.

@cwilso cwilso added Project Vision Vision and Principles needed for Statement Probably needs to be resolved prior to Statement vote labels Mar 27, 2024
@tantek
Copy link
Member

tantek commented Sep 25, 2024

The editor and chair of the Vision Task Force met with W3C team members working on a proposed update to the W3C mission statement and we (VisionTF) are currently waiting on an updated proposal for presentation to the Task Force. We hope to see this proposed update sometime this month or next month.

(Originally published at: https://tantek.com/2024/269/t4/)

@cwilso cwilso removed the needed for Statement Probably needs to be resolved prior to Statement vote label Sep 25, 2024
@cwilso
Copy link
Collaborator Author

cwilso commented Sep 25, 2024

At this point, based on the conversation we had, I'm removing "needed for statement" as I'm confident we are aligned well enough between the two, and I don't think there will be action items needed for an initial Statement. There may be additional tweaking needed in the future, of course, but I don't think it should block going to Statement.

@fantasai
Copy link
Contributor

Should we just close this issue then? Since at this point it's just a reminder to the Team to keep things in sync as needed, and I think we can let them handle such tracking.

@tantek
Copy link
Member

tantek commented Sep 30, 2024

Should we just close this issue then?

No, because this issue as named is to “integrate” which is still a pending task separate from the Team task of “updated proposal”.

just a reminder to the Team to keep things in sync as needed

No, that is missing half the point of this issue. By “in both directions” (per issue description) I believe it means that the chair/editor of the Vision have explicit work to do in the direction of incorporating content into the Vision document.

I disagree with “Candidate to Close” and do not think it needs AB time to discuss closing at this time, thus am removing that label.

If you believe this issue needs explicit sync-discussion by the AB at this time, please add “Agenda+” instead with your goals for discussion.

(Originally published at: https://tantek.com/2024/274/t1/)

@koalie
Copy link
Contributor

koalie commented Oct 2, 2024

The editor and chair of the Vision Task Force met with W3C team members working on a proposed update to the W3C mission statement and we (VisionTF) are currently waiting on an updated proposal for presentation to the Task Force.

The Comm Team has a proposal.
Edit 2024-10-17: "That proposal uses ingredients of a strong mission statement: who, what, how, for whom, why."

We'll ask for AB meeting agenda time in the coming week(s). \o/

@chaals
Copy link
Contributor

chaals commented Oct 4, 2024

The abstract claims this document "articulates the W3C's mission".

First it is not obvious that it does that. It explains the vision that underpins the mission. As mentioned in #188 (I'm fine with closing that as a subset), there is a specific web page that articulates the mission.

Second, I think that gettig the abstract a bit more right is worth doing Before making this a W3C statement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Project Vision Vision and Principles
Projects
None yet
Development

No branches or pull requests

6 participants