-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathtemp.html
More file actions
145 lines (126 loc) · 8.1 KB
/
temp.html
File metadata and controls
145 lines (126 loc) · 8.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content="">
<meta name="author" content="">
<title>Chapters.io : Tightening the Standards Feedback Loop</title>
<!-- Bootstrap Core CSS -->
<link href="css/bootstrap.min.css" rel="stylesheet">
<!-- Custom CSS -->
<link href="css/grayscale.css" rel="stylesheet">
<!-- Custom Fonts -->
<link href="font-awesome/css/font-awesome.min.css" rel="stylesheet" type="text/css">
<link href="http://fonts.googleapis.com/css?family=Lora:400,700,400italic,700italic" rel="stylesheet" type="text/css">
<link href="http://fonts.googleapis.com/css?family=Montserrat:400,700" rel="stylesheet" type="text/css">
<!-- HTML5 Shim and Respond.js IE8 support of HTML5 elements and media queries -->
<!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
<!--[if lt IE 9]>
<script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
<script src="https://oss.maxcdn.com/libs/respond.js/1.4.2/respond.min.js"></script>
<![endif]-->
</head>
<body id="page-top" data-spy="scroll" data-target=".navbar-fixed-top">
<!-- Intro Header -->
<header class="intro">
<div class="intro-body">
<div class="container">
<div class="row">
<div class="col-md-8 col-md-offset-2">
<h1 class="brand-heading">Chapters</h1>
<p class="intro-text">A grassroots, global effort to help change the model of how web standards work.</p>
<a href="#about" class="btn btn-circle page-scroll">
<i class="fa fa-angle-double-down animated"></i>
</a>
</div>
</div>
</div>
</div>
</header>
<!-- About Section -->
<section id="about" class="container content-section text-center">
<div class="row">
<div class="col-lg-8 col-lg-offset-2">
<h2>What are Chapters?</h2>
<p>Chapters are local or regional groups set up with the general goal of discussing standards, best described in
the <a href="https://medium.com/@briankardell/web-standards-we-want-part-i-chapters-ca71985bf914">original post</a> about it.
The general goal is, to dramatically increase participation in, and education about standards in new and manageble ways - in the words of
<a href="https://extensiblewebmanifesto.org">The Extensible Web Manifesto</a>: To tighten the feedback loop between the editors
of web standards and developers. Essentially:
<ol style="text-align: left;">
<li>Bring people together in local forums to discuss developing standards </li>
<li>Create a ‘safer’ and ‘easier’ place for lesser skilled developers to learn with mentoring </li>
<li>Get help reviewing both standards and human documentation around them</li>
<li>To enlist help in looking at/reviewing and developing prollyfills and tests with an eye toward the standard</li>
<li>To introduce people to new technology and get them to try to use it </li>
<li>Most importantly perhaps, to help figure out a way to coalesce this feedback and information and feed it back into standards bodies to manage noise and channels productively.</li>
</ol>
</p>
</div>
</div>
</section>
<!-- Download Section -->
<section class="content-section text-center">
<div class="how-section">
<div class="container">
<div class="col-lg-8 col-lg-offset-2">
<h2>How do they work?</h2>
<p>There's no formal definition of how a chapter has to work, it's up to participants to determine what
they discuss or do, and how. At a very basic level, we simply ask that chapters try to "keep track" of their work or discussions,
create very simple distilled notes or summaries and share <em>something</em> with the wider world where possible.
This can be in any form or medium that works - a github org or gist, a blog post, a post on <a href="https://discourse.specifiction.org">specifiction</a>, or some social media like G+ or Facebook. The pilot group has found G+ to be a nice way for them to schedule meetups
and reminders and post some notes, and it uses Google Hangouts for remote participation, but your mileage may vary.
If you setup a group, let us know at <a href="https://plus.google.com/u/0/108958737038911231850/about">the main G+ org</a>
and we'll link you up and help you let people know about it.
</p>
<p>Our pilot partnered with the University of Vermont, who donated a dedicated space for 3 hours, one evening per week.
This isn't the only time or place where folks can talk, and not everyone can come every week or stay for the whole 3 hours,
but having a place where you <em>can</em> get together for some dedicated and substantial face-time seems helpful.
</p>
<p>Initially, we introduced newer people to the world of standards and helpful resources.
The model that eventually followed was simply to have people start reading about new or intersting things, and bring them to the group's attention.
They would talk about it until they thought they understood it, and
they would see what state of implementation it was in. If none, they'd look for a polyfill and, if it wasn't listed on
helpful resources like MDN or Web Platform Docs, they might submit it. They'd try it out and discuss it some more.
In some cases they were interested in potentially contributing Web Platform tests.
</p>
<!-- a href="url" class="btn btn-default btn-lg">Sample link</a -->
</div>
</div>
</div>
</section>
<!-- Contact Section -->
<section id="contact" class="container content-section text-center">
<div class="row">
<div class="col-lg-8 col-lg-offset-2">
<h2>Interested in Starting a Chapter?</h2>
<p>If you do, all that we ask is that you let us know about it and link you up via our main G+ org...</p>
</p>
<ul class="list-inline banner-social-buttons">
<!-- we don't have this yet... li>
<a href="https://twitter.com/chapters.io" class="btn btn-default btn-lg"><i class="fa fa-twitter fa-fw"></i> <span class="network-name">Twitter</span></a>
</li>
-->
<!-- we don't really have something useful here atm... li>
<a href="https://github.com/chapters" class="btn btn-default btn-lg"><i class="fa fa-github fa-fw"></i> <span class="network-name">Github</span></a>
</li -->
<li>
<a href="https://plus.google.com/u/0/108958737038911231850/about" class="btn btn-default btn-lg"><i class="fa fa-google-plus fa-fw"></i> <span class="network-name">Google+</span></a>
</li>
</ul>
<p>Feel free to email <a href="mailto:bkardell@gmail.com">Brian Kardell</a> or <a href="mailto:robin@berjon.com">Robin Berjon</a> if you have any private questions or media inquiries.</p>
</div>
</div>
</section>
<!-- Map Section -->
<div id="map"></div>
<!-- Footer -->
<footer>
<div class="container text-center">
<p>Copyright © Your Website 2014</p>
</div>
</footer>
</body>
</html>