Difference between revisions of "Headlights2014"

From W3C Wiki
Jump to: navigation, search
(Proposals)
Line 4: Line 4:
  
 
See also [[Headlights2013]].
 
See also [[Headlights2013]].
 
==Instructions for W3C Members and Staff==
 
 
# Create a new page '''in this wiki''' for each proposal. The content of the page should follow the template below.
 
# Add a link to your topic in the list of proposals below.
 
<!--
 
# Add a link to the one page version at [[Headlights2013Transcluded]].
 
-->
 
  
 
=== Schedule ===
 
=== Schedule ===
Line 25: Line 17:
 
== Proposals ==
 
== Proposals ==
  
Add link to your proposal here:
+
=== Webizen Program ===
 +
 
 +
Led by: Jeff Jaffe
 +
 
 +
It was proposed [https://www.w3.org/wiki/TPAC2013 during TPAC 2013]
 +
that we should have an Individual Membership program at W3C. W3C
 +
management concluded that we did not need a program which conferred
 +
the participation rights of Membership to individuals, since we
 +
already have [http://www.w3.org/2004/08/invexp.html Invited Experts].
 +
 
 +
Instead, we are looking to explore a "Webizen" program.  For a nominal
 +
fee (e.g. $100 US per annum), the individual would get some benefits of
 +
comparable value.  This project will explore whether such a program is
 +
viable and want the benefits should be.
 +
 
 +
Sample benefits could include: user groups, user conferences, T-shirts,
 +
ID-cards, a path to provide user input to Working Groups, recognition as
 +
a Webizen for participants in W3C Working Groups and Community Groups.
 +
 
 +
To join: [mailto:public-webizen-request&#64;w3.org?subject=subscribe subscribe to public-webizen@w3.org]
 +
 
 +
=== W3C Community On-Boarding ===
 +
 
 +
Led by: Dominique Hazaël-Massieux.
 +
 
 +
As the scope of Web technologies increases, and as the communities
 +
impacted by the Web grows, it becomes critical that a wider variety of
 +
people can come on board of the W3C train and become effective
 +
participants in W3C groups. This headlight will explore the various
 +
existing and new approaches that would let W3C newcomers get integrated
 +
in our community better and faster.
 +
 
 +
To join: Visit [https://www.w3.org/wiki/OnBoarding the OnBoarding wiki] and [mailto:public-onboarding-request&#64;w3.org?subject=subscribe subscribe to public-onboarding@w3.org]
  
# [[Headlights2014/OnBoarding|W3C Community On-Boarding]] Making it easier for new participants to contribute
+
=== Security and Privacy Internal Consulting ===
# [[Headlights2014/HTML3D|3D as a native element for HTML using CSS Style (similar to CSS3 animations)]]
+
# [[Headlights2014/EasyAccesstoSpec|Easy Access to W3C Specs]]
+
# [[Headlights2014/HTTP2|HTTP2]]
+
# [[Headlights2014/Webizen|Webizen]]
+
# [[Headlights2014/W3C_Workshop_on_Web_Apps_and_Marketplaces|W3C Workshop on Web Apps and Marketplaces]]
+
# [[Headlights2014/Security and Privacy Consulting|Security and Privacy Consulting]]
+
# [[Headlights2014/Data gathering on existing Web usages|Data gathering on existing Web usages]]
+
# [[Headlights2014/Developers voice|Developers voice]]
+
  
 +
Led by: Wendy Seltzer
  
For those who like to scroll or print, all proposals on one page: [[Headlights2014/all]]
+
To improve the quality of of W3C recommendations with regards to privacy
(Needs manual update if new proposals are added.)
+
and security, we want to provide internal consultation on security and
 +
privacy issues at the request of a Working Group. The aim is to help WGs
 +
throughout all phases of their work to identify, discuss and resolve
 +
specific privacy and security questions. Along with review of finalized
 +
specs, this service will focus on collaborative work earlier in the WG's
 +
progress.
  
==Template==
+
To join: Discussion will take place in a joint task force of the
 +
[https://www.w3.org/wiki/Privacy Privacy Interest Group] and
 +
[http://www.w3.org/Security/wiki/IG Web Security Interest Group].
  
''To use this template, please copy the following subsections to the wiki page for your idea and complete them. See also the [[Headlights2014/ExampleProposal|Example Proposal to help you organize your proposal]]''
+
=== Easy Access to W3C Specifications ===
  
===Name of idea===
+
Led by:  Xiaoqian (Cindy) Wu
  
IDEA NAME HERE
+
Many developers have strong willingness to understand W3C's standards,
 +
to comment on the drafts or participant in our other activities, but
 +
quite a few of them might give up at the very beginning because the
 +
specs are not easy to read.  To make it easier for the developers to
 +
get access to our specs, we hope to invite editors or other experts in
 +
each working groups to write articles about how to read the specs, and
 +
to translate these articles into other languages if necessary. By
 +
these kind of introduction, more developers will get involved in the
 +
process, which will help increase the consistency of our
 +
specification, and allow us to develop new technologies for more
 +
people.
  
===Submitter name===
+
To join: Visit the [https://www.w3.org/wiki/EasyAccesstoSpec Easy Access to Specs wiki] and subscribe to  [mailto:public-accesstospec-request&#64;w3.org?subject=subscribe subscribe to public-accesstospec@w3.org]
  
YOUR NAME HERE
+
=== Data-backed Operations ===
  
===Classification===
+
Led by: Alan Bird
This idea is (CHOOSE ONE):
+
<ul class="show_items">
+
* An area of web standardization that arises from the increased application of web technology to a new business segment (e.g. entertainment, publishing, health, energy, government).
+
* A trend in information technology that requires new standardizations (e.g. cloud computing, social networking, a search platform, a gaming platform)
+
* A specific technology area that requires new standardization (e.g. structured vocabularies, privacy, REST)
+
* A new scope of work for W3C for an existing technology area (e.g. education, testing, validation, certification, profiles)
+
*      None of the above
+
</ul>
+
  
===One Hundred Word Description of the Idea===
+
This project will be primarily internal to the W3C Team. The project
 +
goal is to identify data we have available and and to determine how we
 +
ma analyze it to better serve our Members and other parts of
 +
community.
  
YOUR DESCRIPTION HERE
+
Please contact Alan Bird <abird@w3.org> with any questions.
  
===Benefit(s) to Web or W3C===
+
=== HTTP2 ===
YOUR DESCRIPTION HERE
+
  
===Which of our stakeholders would be the most enthusiastic in supporting===
+
The IETF is defining HTTP2. Proponents point out that the improved
YOUR LIST HERE
+
architecture will have far greater performance, and we can build
 +
stronger security requirements into it. We need to explore further the
 +
impact: What aspects of Web architecture need to be made more
 +
efficient to leverage HTTP2? How do we build security into the Web
 +
layer? What new applications will be developed?
  
=== Feedback/Questions on the idea===
+
More information coming soon.
Feedback provided by people reviewing the ideas
+

Revision as of 19:33, 14 February 2014

W3C management reviews W3C priorities and resources on an ongoing basis, and annually (typically mid-year) explores major re-allocations of resources to align with important trends. W3C Members and W3C Staff use this wiki to identify some potential directions for W3C (technical, organizational, etc.).

These are proposals for discussion. Do not assume that W3C endorses these ideas or has allocated any resources to pursuing them beyond initial discussion.

See also Headlights2013.

Schedule

  • October 2013 - January 2014: Proposals from W3C Members and Staff added to this page
  • Jan 2014: W3C management prioritization of headlights ideas
  • Feb 2014: Announcement of topics selected for further development and start of task forces
  • Feb - May 2014: Idea Development
  • June 2014: AC meeting discussion
  • June-July 2014: further development
  • July 2014: W3M evaluation of proposals and assignment of resources

Proposals

Webizen Program

Led by: Jeff Jaffe

It was proposed during TPAC 2013 that we should have an Individual Membership program at W3C. W3C management concluded that we did not need a program which conferred the participation rights of Membership to individuals, since we already have Invited Experts.

Instead, we are looking to explore a "Webizen" program. For a nominal fee (e.g. $100 US per annum), the individual would get some benefits of comparable value. This project will explore whether such a program is viable and want the benefits should be.

Sample benefits could include: user groups, user conferences, T-shirts, ID-cards, a path to provide user input to Working Groups, recognition as a Webizen for participants in W3C Working Groups and Community Groups.

To join: subscribe to public-webizen@w3.org

W3C Community On-Boarding

Led by: Dominique Hazaël-Massieux.

As the scope of Web technologies increases, and as the communities impacted by the Web grows, it becomes critical that a wider variety of people can come on board of the W3C train and become effective participants in W3C groups. This headlight will explore the various existing and new approaches that would let W3C newcomers get integrated in our community better and faster.

To join: Visit the OnBoarding wiki and subscribe to public-onboarding@w3.org

Security and Privacy Internal Consulting

Led by: Wendy Seltzer

To improve the quality of of W3C recommendations with regards to privacy and security, we want to provide internal consultation on security and privacy issues at the request of a Working Group. The aim is to help WGs throughout all phases of their work to identify, discuss and resolve specific privacy and security questions. Along with review of finalized specs, this service will focus on collaborative work earlier in the WG's progress.

To join: Discussion will take place in a joint task force of the Privacy Interest Group and Web Security Interest Group.

Easy Access to W3C Specifications

Led by: Xiaoqian (Cindy) Wu

Many developers have strong willingness to understand W3C's standards, to comment on the drafts or participant in our other activities, but quite a few of them might give up at the very beginning because the specs are not easy to read. To make it easier for the developers to get access to our specs, we hope to invite editors or other experts in each working groups to write articles about how to read the specs, and to translate these articles into other languages if necessary. By these kind of introduction, more developers will get involved in the process, which will help increase the consistency of our specification, and allow us to develop new technologies for more people.

To join: Visit the Easy Access to Specs wiki and subscribe to subscribe to public-accesstospec@w3.org

Data-backed Operations

Led by: Alan Bird

This project will be primarily internal to the W3C Team. The project goal is to identify data we have available and and to determine how we ma analyze it to better serve our Members and other parts of community.

Please contact Alan Bird <abird@w3.org> with any questions.

HTTP2

The IETF is defining HTTP2. Proponents point out that the improved architecture will have far greater performance, and we can build stronger security requirements into it. We need to explore further the impact: What aspects of Web architecture need to be made more efficient to leverage HTTP2? How do we build security into the Web layer? What new applications will be developed?

More information coming soon.