This repository has been archived by the owner on Nov 14, 2017. It is now read-only.
/
guidelines.html
655 lines (566 loc) · 34.2 KB
/
guidelines.html
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
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Open Source Contribution Guidelines - Windows Azure Open Source</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="Contribution guidelines for the Windows Azure open source SDKs and products.">
<meta name="author" content="Windows Azure SDK">
<!--[if lt IE 9]>
<script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
<link href="css/bootstrap.min.css" rel="stylesheet">
<link href="css/bootstrap-responsive.min.css" rel="stylesheet">
<link href="css/azureopensource.css" rel="stylesheet">
<link rel="shortcut icon" href="//az83882.vo.msecnd.net/favicon.ico">
</head>
<body data-spy="scroll" data-target=".sidebar-nav" data-x-offset-top="60">
<script type="text/javascript">
// MICROSOFT AZURE
window.location.href = "http://azure.github.io/guidelines.html";
</script>
<div class="navbar navbar-inverse navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
<button type="button" class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse">
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button><!-- style="padding:15px 15px 5px 15px;margin-top:-5px" -->
<a class="brand" href="//azure.microsoft.com/"><!-- img
src="azure/windowsazurelogo.png" style="width:218px;height:35px;border:0px"
alt="Microsoft Azure" title="Windows Azure" / -->Microsoft Azure</a>
<div class="nav-collapse collapse">
<ul class="nav">
<li><a href="index.html">Open Source Home</a></li>
<li class="active"><a href="guidelines.html">Contribute</a></li>
<li class="dropdown">
<a href="projects.html" class="dropdown-toggle" data-toggle="dropdown">Projects <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="projects.html">All projects</a></li>
<li class="nav-header">Software Dev Kits</li>
<li><a href="projects.html#dotnet">.NET SDK</a></li>
<li><a href="projects.html#nodejs">Node.js SDK</a></li>
<li><a href="projects.html#java">Java SDK</a></li>
<li><a href="projects.html#php">PHP SDK</a></li>
<li><a href="projects.html#python">Python SDK</a></li>
<li><a href="projects.html#ruby">Ruby SDK</a></li>
<li class="divider"></li>
<li class="nav-header">Command line</li>
<li><a href="projects.html#powershell">PowerShell</a></li>
<li><a href="projects.html#cli">x-plat CLI</a></li>
<li class="divider"></li>
<li class="nav-header">More Projects</li>
<li><a href="projects.html#iisnode">iisnode</a></li>
<li><a href="projects.html#teams">Other teams</a></li>
<li class="divider"></li>
<li class="nav-header">WindowsAzure.com</li>
<li><a href="//www.windowsazure.com/en-us/documentation/">Documentation Center</a></li>
<li><a href="//www.windowsazure.com/en-us/develop/reference/">REST Reference</a></li>
</ul>
</li>
<li><a href="contact.html">Contact</a></li>
<li><a href="thanks.html">Thanks</a></li>
</ul>
</div>
<!--/.nav-collapse -->
</div>
</div>
</div>
<div class="container">
<div class="row">
<div class="span3">
<div class="sidebar-nav">
<ul class="nav azure-nav-list nav-list affix">
<li class="active"><a href="#waystocontribute"><i class="icon-chevron-right"></i>Ways to contribute</a></li>
<li class="nav-header">Community member</li>
<li><a href="#source"><i class="icon-chevron-right"></i>Source code</a></li>
<li><a href="#forums"><i class="icon-chevron-right"></i>Q&A forums</a></li>
<li><a href="#issues"><i class="icon-chevron-right"></i>Opening issues</a></li>
<li><a href="#features"><i class="icon-chevron-right"></i>Feature requests</a></li>
<li class="nav-header">OSS Development</li>
<li><a href="#contributing"><i class="icon-chevron-right"></i>Contributing code</a></li>
<li><a href="#cla"><i class="icon-chevron-right"></i>Legal / CLA</a></li>
<li><a href="#stepbystep"><i class="icon-chevron-right"></i>Step-by-step</a></li>
<li><a href="#codereviews"><i class="icon-chevron-right"></i>Code reviews</a></li>
<li><a href="#contact"><i class="icon-chevron-right"></i>Contact the team</a></li>
<li><a href="#thanks"><i class="icon-chevron-right"></i> Our contributors</a></li>
<li class="nav-header">Join our team</li>
<li><a href="#jobs"><i class="icon-chevron-right"></i> Azure is hiring</a></li>
</ul>
</div>
</div>
<div class="span9">
<h1 style="margin-bottom: -20px">Let's work together.</h1>
<section id="waystocontribute">
<h2>Ways to contribute</h2>
<p>
If you would like to become involved in the development of
Windows Azure SDKs and Tools there are many different ways
in which you can contribute. We strongly value your
feedback, questions, bug reports, and feature requests.
</p>
<p>
Consider these options:
</p>
<ul>
<li><a href="//www.windowsazure.com/en-us/develop/downloads/">Use the products</a></li>
<li>Submit a
<a href="//github.com/windowsazure/">GitHub issue</a>
to the appropriate repo (for a guide on submitting good
bug reports, read
<a href="http://www.joelonsoftware.com/articles/fog0000000029.html">Painless Bug Tracking</a>).
</li>
<li>Verify fixes for bugs.</li>
<li>Submit a code fix for a bug.</li>
<li>Submit a new feature request (as a GitHub issue).</li>
<li>Help answer questions on forums such as StackOverflow.</li>
<li>Submit a unit test.</li>
<li>Submit another unit test.</li>
<li>Code review pending pull requests and bug fixes.</li>
<li>Tell others about these projects.</li>
</ul>
</section>
<section id="source">
<h2>Get the source code</h2>
<p>
Our source is developed & published on GitHub.com
(<a href="//help.github.com/">learn more</a>). If you are
new to <a href="//git-scm.com/">Git</a>,
check out the
<a href="//progit.org/book/">Pro Git Book</a> online or at
your bookseller of choice.
</p>
<p>
We have based our development process for moving code
around on the now-classic
<a href="http://nvie.com/posts/a-successful-git-branching-model/">Successful Git Branching Model</a>
as well as using GitHub pull requests and forks between the
central organization repository and developer accounts.
</p>
<p>
From any of the Windows Azure code repositories on GitHub,
you can "Fork" the code to your own account.
</p>
<p>
To get the source on your local development machine,
simply clone the repo using Git:<br />
<code>git clone https://github.com/USERNAME/PROJECT.git<br />
git checkout dev</code>
</p>
<p>
Each repository has a README that should be helpful to
learn more about the specifics of the language, project
and its development environment.
</p>
</section>
<section id="forums">
<h2>Q&A forums</h2>
<p>
The easiest way to ask questions is to use the <a
href="http://www.windowsazure.com/en-us/support/forums/">Windows Azure SDK and Tools forums</a>
on StackOverflow and MSDN. If your target language is .NET
the most appropriate forums for discussion are on MSDN.
For all other languages please use StackOverflow.
</p>
<table class="table">
<thead>
<th colspan="2">Forum Provider</th>
<th>Tags</th>
<th>Notes</th>
</thead>
<tbody>
<tr>
<td style="min-width: 83px"><a href="//stackoverflow.com/tagged/azure"><img
src="azure/stackoverflow.png" alt="StackOverflow" title="StackOverflow" style="width: 83px;height: 82px" /></a></td>
<td><a href="//stackoverflow.com/tagged/azure"><h2>StackOverflow</h2></a></td>
<td><a href="//stackoverflow.com/tagged/azure">azure</a></td>
<td>A friendly, open and fun community of developers.</td>
</tr>
<tr>
<td><a style="width: 83px" href="http://social.msdn.microsoft.com/Forums/en-US/category/windowsazureplatform,azuremarketplace,windowsazureplatformctp"><img
src="azure/microsoftforums.png" alt="Microsoft Forums for Windows Azure"
title="Microsoft forums" style="" /></a></td>
<td><a href="http://social.msdn.microsoft.com/Forums/en-US/category/windowsazureplatform,azuremarketplace,windowsazureplatformctp"><h2>Microsoft forums</h2></a></td>
<td></td>
<td>A good place for support and feedback on Windows Azure features
and services like Web Sites, Mobile Services, etc.</td>
</tr>
</tbody>
</table>
</section>
<section id="issues">
<h2>Reporting bugs & issues</h2>
<p>
Issues and feature requests are submitted through the project's
Issues section on GitHub. Please use the following guidelines when
you submit issues and feature requests:<br>
</p>
<ul>
<li>
Make sure the issue is not already reported by searching
through the list of issues
</li>
<li>
Provide detailed description of the issue including the
following information:
<ul>
<li>Which feature the issue appears in</li>
<li>Under what circumstances the issue appears</li>
<li>What is desired behavior</li>
<li>What is breaking</li>
<li>
What is the impact (things like loss or corruption of data,
compromizing security, disruption of service etc.)
</li>
<li>Any code that will be helpful to reproduce the issue</li>
</ul>
</li>
</ul>
<p>
Issues are regularly reviewed and updated with additional
information by the core team. Sometimes the core team may have
questions about particular issue that might need clarifications
so, please be ready to provide additional information.
</p>
</section>
<section id="features">
<h2>Feature requests</h2>
<p>
Feature requests and Design Change Requests (DCRs) are an important part of
the lifecycle of any software project. Please log these as Issues in the
appropriate GitHub repository.
</p>
<p>
Although the team will consider any opened issues, please keep in mind
that there is an extremely high bar when it comes to expanding the scope
and functionality of a core product such as an SDK for Windows Azure.
</p>
<p>
When opening any feature requests, consider including as much information
as possible, including:
</p>
<ul>
<li>Detailed scenarios enabled by the feature or DCR.</li>
<li>Information about your use case or additional value your
business or site will see from the feature.</li>
<li>Any design tips or estimation ideas you may have considered already.</li>
<li>Make note of whether you are opening an issue you would
like the Microsoft team or another community member to work on <em>or</em>
if you are looking to design & develop the feature
yourself.</li>
<li>Any potential caveats or concerns you may have already
thought about.</li>
<li>A miniature test plan or list of test scenarios is always
helpful.</li>
</ul>
</section>
<hr />
<div class="alert alert-info">
<!-- <a class="close">×</a> -->
<strong>Note:</strong> A Contribution Legal Agreement (CLA) is
required before the team can consider your contributions &
pull requests. Please read this entire page carefully.
</div>
<section id="contributing">
<h2>Contributing code</h2>
<p>
From an engineering standpoint, please make sure that you can
build and test the code. Familiarize yourself with our
project guidelines and coding conventions.
</p>
<p>
The SDK team also recommends that you read these great
posts about open source:
</p>
<ul>
<li><a href="http://tirania.org/blog/archive/2010/Dec-31.html">Open Source Contribution Etiquette</a> by Miguel de Icaza</li>
<li><a href="http://www.igvita.com/2011/12/19/dont-push-your-pull-requests/">Don't "Push" Your Pull Requests</a> by Ilya Grigorik</li>
<li><a href="http://nvie.com/posts/a-successful-git-branching-model/">A Successful Git Branching Model</a> by Vincent Driessen</li>
</ul>
<p><em>
If you have ever considered contributing to the <a
href="http://aspnetwebstack.codeplex.com/wikipage?title=Contributing">ASP.NET Web Stack</a>,
we have modeled much of this process on that project.</em></p>
<p>
Before you start working on a feature or substantial code
contribution please <a href="contact.html">discuss it</a> with
the team and ensure it is an appropriate addition to the core
product.
</p>
<p>
Note that code submissions will be rigorously reviewed and
tested by the Windows Azure SDK Team (or the appropriate
Azure service owners), and only contributions that meet
an extremely high bar for both quality and design/roadmap
appropriateness will be merged into the source.</p>
<p>
In some situations Microsoft employees may engage with you
to review design decisions and mitigate issues as part of
the contribution process. Understand that in some situations,
developers inside Microsoft may decide to decline your
pull request and instead log the issue for a future
product milestone or bug fix. The team will provide
information in the pull in these situations and still
thank you for your contribution.
</p>
<p>
For bug fixes, simply start a conversation in the related
GitHub issue to notify the team and chat about the design of
the fix if needed.</p>
<p>
There are many opportunities to build value-add services and
frameworks that do not need to direct alterations to the
SDKs and products: NuGet packages for .NET or NPM modules
for Node.js devs can easily take a dependency on the core
SDK components, for example.
</p>
<ul>
<li>You have properly documented any new functionality using the
documentation standards for the language (this includes clasees,
methods and functions, properties etc.)</li>
<li>For any change you make proper inline documentation is
included<br>
</li>
<li>For any new functionality you have written complete unit tests</li>
<li>You have ran all unit tests and they pass</li>
</ul>
In order to speed up the process of accepting your contributions, you
should try to make your checkins as small as possible, avoid any unnecessary
deltas and the need to rebase.
</section>
<section id="cla">
<h2>Contribution License Agreement (CLA)</h2>
<p>In order to become a contributor to the Windows Azure
open source projects on GitHub you must follow some
legal requirements.</p>
<p>Until you meet the legal requirements your pull requests / source
contributions will not be considered or reviewed.</p>
<div class="tabbable">
<ul class="nav nav-tabs">
<li class="active"><a href="#standardcla" data-toggle="tab">Community Member</a></li>
<li><a href="#ftecla" data-toggle="tab">Microsoft FTE</a></li>
<li><a href="#msftcla" data-toggle="tab">Microsoft Partner Team</a></li>
</ul>
<div class="tab-content well" style="margin-top: -20px">
<div class="tab-pane active" id="standardcla">
<p>As a community member you must sign the Contribution License Agreement (CLA)
before you can contribute to Microsoft open source projects.</p>
<p>You only need complete and submit the documentation once. Please
carefully review the document; you may also need to have your
employer sign the document.</p>
<p>Signing the Contribution License Agreement (CLA) does not grant
you rights to commit to the main repository but it does mean that
the Windows Azure team will be able to review and consider your
contributions and you will get credit if we do.</p>
<p>You can download the Contribution License Agreement (CLA) by
clicking the following link: <a href="docs/Contribution License Agreement.pdf"
title="Contribution License Agreement">http://windowsazure.github.com/docs/Contribution License Agreement.pdf</a>.</p>
<p><a href="docs/Contribution License Agreement.pdf"
title="Contribution License Agreement"
class="btn btn-primary"><i class="icon-download icon-white"></i>
Download the Contribution License Agreement (CLA)</a><br />
<small>281 KB PDF</small></p>
<p><strong>Please fill in, sign, scan & email the completed document
to <a href="mailto:cla@microsoft.com?subject=New CLA from Community Member"
title="Email signed Contribution License Agreement to Microsoft">cla@microsoft.com</a>.</strong>
</p>
</div>
<div class="tab-pane" id="ftecla">
<p>If you are currently employed as an active Full-Time Employee (FTE)
at Microsoft you may be able to contribute through your job to
the SDK without signing a CLA.</p>
<p>You will need to clearly identify yourself as a Microsoft employee
in your GitHub profile. You should also include your alias in any
pull requests.</p>
<p>As a courtesy you should have a conversation about contributing
to the Azure open source projects with your manager, and remember
to follow your business group's guidelines and policies.</p>
</div>
<div class="tab-pane" id="msftcla">
<p>If your Microsoft team is looking to partner with the
Windows Azure SDK team to ship new bits, create new
open source projects & meet your shipping
criteria, please start engaging the Windows Azure SDK
triad early.</p>
<p>Our SharePoint site contains plenty of information on
the onboarding process, timelines and contacts.</p>
<p><a href="https://microsoft.sharepoint.com/teams/azuresdk/"
class="btn btn-primary"><i class="icon-lock icon-white"></i>
Open Windows Azure SDK SharePoint</a><br />
<small>Requires corporate credentials</small></p>
</div>
</div>
</div>
<p>
Active contributors might be asked to join the core team or
help with feature development. The ability to merge pull
requests typically remains with the SDK team to ensure
that contributions to master are thoroughly reviewed.
</p>
<p>
Please configure your Git client with a name and email
address to use for your commits. This will also help the
team validate your CLA status:
<pre>git config user.name Your Name
git config user.email YourAlias@YourEmailDomain</pre>
</p>
</section>
<section id="stepbystep">
<h2>Step-by-step guide</h2>
<h4>Checkout the latest code</h4>
<p>In order to obtain the source code you need to become familiar
with Git (see <a href="http://progit.org/book/">http://progit.org/book/</a>)
and Github (see <a href="http://help.github.com/">http://help.github.com/</a>)
and you need to have Git installed on your local machine. You can
obtain the source code from Github and start a contributor environment by
following the these steps on your local machine:<br>
</p>
<ol>
<li>Go to https://github.com/WindowsAzure/[PROJECT]</li>
<li>Select <img src="images/button-fork.jpg" alt=""> and choose your own Github account as target</li>
<li>Clone the repository on your local machine with the following
Git command<br>
<code>git clone git@github.com:[USERNAME]/[PROJECT]</code><br>
</li>
<li>When you clone the repository you should see, at least, 2 branches: dev and master.
dev is the branch where the team does all the day to day development while master is
the branch that is always up to date with the latest release.<br/>
This means, before starting any work, you should switch to the dev branch. You can do so
with the following command:<br/>
<code>git checkout dev</code></li>
</ol>
<h4>Create bug fixes and features<br>
</h4>
<p>You can then start to make modifications to the code in your local Git repository.
This can be done in your local dev branch or, if you prefer, in a branch out of dev.
In the simplest scenario, working directly on dev, you can commit your work
with following commands:<br/>
</p>
<ol>
<li>Add and commit your local changes<br/>
<code>git commit -a</code>
</li>
<li>Push your changes from your local repository to your github fork<br/>
<code>git push</code>
</li>
</ol>
<p>Once your code is in your github fork, you can then submit a pull request
for the team's review. You can do so with the following commands:<br/>
</p>
<ol>
<li>In GitHub click on the Pull
Request button <img src="images/button-pull-request.jpg" alt=""></li>
<li>In the pull request select your fork as source and
WindowsAzure/[PROJECT] as destination for the request</li>
<li>Write detailed message describing the changes in the pull
request</li>
<li>Submit the pull request for consideration by the Core Team</li>
</ol>
<p>If there are conflicts between your fork and the main project one, github
will warn you that the pull request cannot be merged. If that's the case,
you can do the following:
</p>
<ol>
<li>Add remote to your local repository using the following Git
commands<br>
</code><code>git remote add upstream -f
git@github.com:WindowsAzure/[PROJECT]</code><br>
</li>
<li>Update your local repository with the changes from the remote
repository by using the following Git commands (make sure you're in
the branch you're submitting the code from)<br>
<code>git merge upstream/dev</code></li>
<li>Resolve any conflicts locally and finally do another push with the command<br/>
<code>git push</code>
</li>
</ol>
<p>Please keep in mind that not all requests will be approved.
Requests are reviewed by the Core Team on a regular basis and will
be updated with the status at each review. If your request is
accepted you will receive information about the next steps and
when the request will be integrated in the main branch. If your
request is rejected you will receive information about the reasons
why it was rejected.<br>
</p>
</section>
<section id="codereviews">
<h2>Code Reviews</h2>
<p>
The Windows Azure SDK team has an active Microsoft discussion
group used for submitting code reviews and discussing design
changes, best practices, and other important topics.
</p>
<p>
Part of the code review process involves using a code review
tool, and for most open source projects, the team uses the
built-in Pull Request functionality on GitHub for enabling
annotations and comments on code before accepting the pull
request/s.
</p>
<p>
Expect a good amount of feedback as part of any pull request:
not only which branch to merge to and from, but also
consistency guidelines, matching existing code, and
making targeted, smart changes when fixing bugs.
</p>
<h3>Community code reviews</h3>
<p>
The SDK team is considering allowing for community code
reviews as well. If you watch a repository of interest,
you can make comments on any public pull request. The
best time for providing feedback is during dev branch
pulls into the primary WindowsAzure GitHub account.
</p>
</section>
<section id="contact">
<h2>Contact the team</h2>
<p>The best way to get in touch with the team regarding feature ideas,
developer designs amd communicating about bug fixes is to use the Issues system
built in to GitHub.</p>
<p>If you are looking for support or to provide feedback, there are a lot of
places to do this.</p>
<p><a class="btn btn-primary" href="contact.html">Detailed support and contact information »</a></p>
</section>
<section id="thanks">
<h2>Thank you</h2>
<p>
Huge thanks go to the contributors from the community who
have been actively working with the Windows Azure SDK team.
</p>
<p>You can find a <a href="thanks.html">list of contributors here</a>.
</section>
<hr />
<section id="jobs">
<h2>Jobs</h2>
<p>Microsoft is always hiring bright and talented students &
professionals. Please consider submitting your resume and
applying for open positions at
<a href="//careers.microsoft.com/">//careers.microsoft.com</a>.</p>
</section>
</div>
</div>
<hr>
<footer>
<p class="pull-right"><a href="#top">Back to top</a></p>
<div class="links">
<a href="//www.windowsazure.com/">WindowsAzure.com</a> |
<a href="http://blogs.msdn.com/b/windowsazure/">Windows Azure Blog</a> |
<a href="https://twitter.com/windowsazure">@windowsazure</a> |
<a href="https://github.com/windowsazure/">GitHub</a> |
<a href="thanks.html">Thank you to our contributors</a>
</div>
<p>
<small>© Microsoft |
<a href="http://go.microsoft.com/fwlink/p/?linkid=131004&clcid=0x409">Privacy and Cookies</a> |
<a href="http://go.microsoft.com/fwlink/p/?linkid=222682&clcid=0x409">Trademarks</a>
</small>
</p>
</footer>
</div>
<!-- /container -->
<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.9.0/jquery.min.js"></script>
<script src="js/bootstrap.min.js"></script>
<script src="js/azure.js"></script>
</body>
</html>