├── _template.html ├── azure ├── microsoftforums.png ├── stackoverflow.png └── windowsazurelogo.png ├── contact.html ├── css ├── azureopensource.css ├── bootstrap-responsive.css ├── bootstrap-responsive.min.css ├── bootstrap.css └── bootstrap.min.css ├── docs └── Contribution License Agreement.pdf ├── guidelines.html ├── images ├── button-fork.jpg └── button-pull-request.jpg ├── img ├── glyphicons-halflings-white.png └── glyphicons-halflings.png ├── index.html ├── js ├── azure.js ├── bootstrap.js └── bootstrap.min.js ├── projects.html ├── robots.txt └── thanks.html /_template.html: -------------------------------------------------------------------------------- 1 | 2 | 3 |
4 | 5 |You'll find that the community on the Internet is probably the best 92 | way to engage and get answers to your questions.
93 | 94 |Forum Provider | 97 |Tags | 98 |Notes | 99 | 100 | 101 ||
---|---|---|---|
![]() |
104 | StackOverflow |
105 | azure | 106 |A friendly, open and fun community of developers. | 107 |
![]() |
111 | Microsoft forums |
112 | 113 | | A good place for support and feedback on Microsoft Azure features 114 | and services like Web Sites, Mobile Services, etc. | 115 |
There are support options available for your Microsoft Azure subscription - 121 | you can find more information & submit a support ticket at https://manage.windowsazure.com/?getsupport=true.
123 | 124 |All accounts include billing support at no cost and there are 125 | paid plans available for additional levels of support.
126 | 127 |You can read up on this and more on the Microsoft Azure 129 | Support section of the 130 | primary web site.
131 | 132 |Support for the Microsoft Azure SDK is not available direct from 134 | the Microsoft engineers working on the product in an official capacity.
135 | 136 |If you would like to discuss feature requests or bug fixes, please use 137 | GitHub Issues on the appropriate Microsoft Azure GitHub repository.
138 | 139 |You may find many members of the team active on Twitter, StackOverflow, 140 | and other venues. Recognize that these conversations and avenues are friendly but 141 | unofficial and do not represent the opinions of Microsoft.
142 | 143 | 144 | 145 |
150 | André Rodrigues151 |Software Development Engineer Follow @andremrodrigues 158 | 159 | |
160 |
161 | Jeff Wilcox162 |Software Development Lead Follow @jeffwilcox 169 | 170 | |
171 |
172 | Mohit Srivastava173 |
174 | Lead Program Manager 179 | Follow @mohit 182 | 183 | |
184 |
187 | Guang Yang188 |
189 | Program Manager 194 | Follow @guayan 197 | 198 | |
199 |
200 | Brady Gaster201 |
202 | Program Manager 207 | Follow @bradygaster 210 | 211 | |
212 |
213 | Larry Franks214 |
215 | Senior Programming Writer 220 | Follow @larry_franks 223 | 224 | |
225 |
228 | Albert Cheng229 |Software Engineer Follow @chengg1978 236 | 237 | |
238 |
239 | Abdelrahman Elogeel240 |Software Development Engineer Follow @Elogeel 247 | 248 | |
249 | 250 | |
259 | Abhishek Lal260 |Senior Program Manager Follow @AbhishekRLal 267 | 268 | |
269 |
270 | Will Perry271 |SDET Follow @willpe 278 | 279 | |
280 |
281 | Clemens Vasters282 |Principal Program Manager Follow @clemensv 289 | 290 | |
291 |
300 | John Deutscher301 |Principal Program Manager Follow @Johndeu 308 | 309 | |
310 |
311 | Mingfei Yan312 |Program Manager Follow @mingfeiy 319 | 320 | |
321 |
322 | Vishal Sood323 |Senior Program Manager Follow @vishalsood 330 | 331 | |
332 |
335 | George Trifonov336 |Developer Follow @GeorgeTrifonov 343 | 344 | |
345 |
346 | Milan Gada347 |Senior Program Manager Follow @gadamilan 354 | 355 | |
356 | 357 | |
366 | Josh Twist367 |Program Manager Follow @joshtwist 374 | 375 | |
376 |
377 | Yavor Georgiev378 |Program Manager Follow @theYavor 385 | 386 | |
387 | 388 | |
The Microsoft Azure SDK team maintains a number of specialized "insiders" 423 | programs for projects such as the Node.js SDK.
424 | 425 |The program is rather unofficial and relaxed in nature. Invitation 426 | is often granted as the team sees active community contributions, open 427 | source contributions or other impressive technology feats.
428 | 429 |107 | If you would like to become involved in the development of 108 | Windows Azure SDKs and Tools there are many different ways 109 | in which you can contribute. We strongly value your 110 | feedback, questions, bug reports, and feature requests. 111 |
112 | 113 |114 | Consider these options: 115 |
116 | 117 |139 | Our source is developed & published on GitHub.com 140 | (learn more). If you are 141 | new to Git, 142 | check out the 143 | Pro Git Book online or at 144 | your bookseller of choice. 145 |
146 |147 | We have based our development process for moving code 148 | around on the now-classic 149 | Successful Git Branching Model 150 | as well as using GitHub pull requests and forks between the 151 | central organization repository and developer accounts. 152 |
153 |154 | From any of the Windows Azure code repositories on GitHub, 155 | you can "Fork" the code to your own account. 156 |
157 | 158 |
159 | To get the source on your local development machine,
160 | simply clone the repo using Git:
161 | git clone https://github.com/USERNAME/PROJECT.git
163 |
162 | git checkout dev
166 | Each repository has a README that should be helpful to 167 | learn more about the specifics of the language, project 168 | and its development environment. 169 |
170 | 171 |176 | The easiest way to ask questions is to use the Windows Azure SDK and Tools forums 178 | on StackOverflow and MSDN. If your target language is .NET 179 | the most appropriate forums for discussion are on MSDN. 180 | 181 | For all other languages please use StackOverflow. 182 |
183 | 184 |Forum Provider | 187 |Tags | 188 |Notes | 189 | 190 | 191 ||
---|---|---|---|
![]() |
194 | StackOverflow |
195 | azure | 196 |A friendly, open and fun community of developers. | 197 |
![]() |
202 | Microsoft forums |
203 | 204 | | A good place for support and feedback on Windows Azure features 205 | and services like Web Sites, Mobile Services, etc. | 206 |
215 | Issues and feature requests are submitted through the project's
216 | Issues section on GitHub. Please use the following guidelines when
217 | you submit issues and feature requests:
218 |
242 | Issues are regularly reviewed and updated with additional 243 | information by the core team. Sometimes the core team may have 244 | questions about particular issue that might need clarifications 245 | so, please be ready to provide additional information. 246 |
247 |252 | Feature requests and Design Change Requests (DCRs) are an important part of 253 | the lifecycle of any software project. Please log these as Issues in the 254 | appropriate GitHub repository. 255 |
256 |257 | Although the team will consider any opened issues, please keep in mind 258 | that there is an extremely high bar when it comes to expanding the scope 259 | and functionality of a core product such as an SDK for Windows Azure. 260 |
261 |262 | When opening any feature requests, consider including as much information 263 | as possible, including: 264 |
265 |294 | From an engineering standpoint, please make sure that you can 295 | build and test the code. Familiarize yourself with our 296 | project guidelines and coding conventions. 297 |
298 | 299 |300 | The SDK team also recommends that you read these great 301 | posts about open source: 302 |
303 |310 | If you have ever considered contributing to the ASP.NET Web Stack, 312 | we have modeled much of this process on that project.
313 | 314 |315 | Before you start working on a feature or substantial code 316 | contribution please discuss it with 317 | the team and ensure it is an appropriate addition to the core 318 | product. 319 |
320 | 321 |322 | Note that code submissions will be rigorously reviewed and 323 | tested by the Windows Azure SDK Team (or the appropriate 324 | Azure service owners), and only contributions that meet 325 | an extremely high bar for both quality and design/roadmap 326 | appropriateness will be merged into the source.
327 | 328 |329 | In some situations Microsoft employees may engage with you 330 | to review design decisions and mitigate issues as part of 331 | the contribution process. Understand that in some situations, 332 | developers inside Microsoft may decide to decline your 333 | pull request and instead log the issue for a future 334 | product milestone or bug fix. The team will provide 335 | information in the pull in these situations and still 336 | thank you for your contribution. 337 |
338 | 339 |340 | For bug fixes, simply start a conversation in the related 341 | GitHub issue to notify the team and chat about the design of 342 | the fix if needed.
343 | 344 |345 | There are many opportunities to build value-add services and 346 | frameworks that do not need to direct alterations to the 347 | SDKs and products: NuGet packages for .NET or NPM modules 348 | for Node.js devs can easily take a dependency on the core 349 | SDK components, for example. 350 |
351 | 352 | 353 |In order to become a contributor to the Windows Azure 373 | open source projects on GitHub you must follow some 374 | legal requirements.
375 | 376 |Until you meet the legal requirements your pull requests / source 377 | contributions will not be considered or reviewed.
378 | 379 |As a community member you must sign the Contribution License Agreement (CLA) 391 | before you can contribute to Microsoft open source projects.
392 | 393 |You only need complete and submit the documentation once. Please 394 | carefully review the document; you may also need to have your 395 | employer sign the document.
396 | 397 |Signing the Contribution License Agreement (CLA) does not grant 398 | you rights to commit to the main repository but it does mean that 399 | the Windows Azure team will be able to review and consider your 400 | contributions and you will get credit if we do.
401 | 402 |You can download the Contribution License Agreement (CLA) by 403 | clicking the following link: http://windowsazure.github.com/docs/Contribution License Agreement.pdf.
405 | 406 |
409 | Download the Contribution License Agreement (CLA)
410 | 281 KB PDF
Please fill in, sign, scan & email the completed document 414 | to cla@microsoft.com. 416 |
417 | 418 |If you are currently employed as an active Full-Time Employee (FTE) 423 | at Microsoft you may be able to contribute through your job to 424 | the SDK without signing a CLA.
425 | 426 |You will need to clearly identify yourself as a Microsoft employee 427 | in your GitHub profile. You should also include your alias in any 428 | pull requests.
429 | 430 |As a courtesy you should have a conversation about contributing 431 | to the Azure open source projects with your manager, and remember 432 | to follow your business group's guidelines and policies.
433 | 434 |If your Microsoft team is looking to partner with the 439 | Windows Azure SDK team to ship new bits, create new 440 | open source projects & meet your shipping 441 | criteria, please start engaging the Windows Azure SDK 442 | triad early.
443 | 444 |Our SharePoint site contains plenty of information on 445 | the onboarding process, timelines and contacts.
446 | 447 |
449 | Open Windows Azure SDK SharePoint
450 | Requires corporate credentials
457 | Active contributors might be asked to join the core team or 458 | help with feature development. The ability to merge pull 459 | requests typically remains with the SDK team to ensure 460 | that contributions to master are thoroughly reviewed. 461 |
462 | 463 |464 | Please configure your Git client with a name and email 465 | address to use for your commits. This will also help the 466 | team validate your CLA status: 467 | 468 |
git config user.name Your Name 469 | git config user.email YourAlias@YourEmailDomain470 | 471 | 472 |
In order to obtain the source code you need to become familiar
479 | with Git (see http://progit.org/book/)
480 | and Github (see http://help.github.com/)
481 | and you need to have Git installed on your local machine. You can
482 | obtain the source code from Github and start a contributor environment by
483 | following the these steps on your local machine:
484 |
git clone git@github.com:[USERNAME]/[PROJECT]
git checkout dev
You can then start to make modifications to the code in your local Git repository.
502 | This can be done in your local dev branch or, if you prefer, in a branch out of dev.
503 | In the simplest scenario, working directly on dev, you can commit your work
504 | with following commands:
505 |
git commit -a
509 | git push
512 | Once your code is in your github fork, you can then submit a pull request
515 | for the team's review. You can do so with the following commands:
516 |
If there are conflicts between your fork and the main project one, github 527 | will warn you that the pull request cannot be merged. If that's the case, 528 | you can do the following: 529 |
530 |git remote add upstream -f
534 | git@github.com:WindowsAzure/[PROJECT]
git merge upstream/dev
git push
542 | Please keep in mind that not all requests will be approved.
545 | Requests are reviewed by the Core Team on a regular basis and will
546 | be updated with the status at each review. If your request is
547 | accepted you will receive information about the next steps and
548 | when the request will be integrated in the main branch. If your
549 | request is rejected you will receive information about the reasons
550 | why it was rejected.
551 |
557 | The Windows Azure SDK team has an active Microsoft discussion 558 | group used for submitting code reviews and discussing design 559 | changes, best practices, and other important topics. 560 |
561 |562 | Part of the code review process involves using a code review 563 | tool, and for most open source projects, the team uses the 564 | built-in Pull Request functionality on GitHub for enabling 565 | annotations and comments on code before accepting the pull 566 | request/s. 567 |
568 |569 | Expect a good amount of feedback as part of any pull request: 570 | not only which branch to merge to and from, but also 571 | consistency guidelines, matching existing code, and 572 | making targeted, smart changes when fixing bugs. 573 |
574 | 575 |577 | The SDK team is considering allowing for community code 578 | reviews as well. If you watch a repository of interest, 579 | you can make comments on any public pull request. The 580 | best time for providing feedback is during dev branch 581 | pulls into the primary WindowsAzure GitHub account. 582 |
583 | 584 |The best way to get in touch with the team regarding feature ideas, 590 | developer designs amd communicating about bug fixes is to use the Issues system 591 | built in to GitHub.
592 | 593 |If you are looking for support or to provide feedback, there are a lot of 594 | places to do this.
595 | 596 | 597 | 598 |605 | Huge thanks go to the contributors from the community who 606 | have been actively working with the Windows Azure SDK team. 607 |
608 |You can find a list of contributors here. 609 |
Microsoft is always hiring bright and talented students & 617 | professionals. Please consider submitting your resume and 618 | applying for open positions at 619 | //careers.microsoft.com.
620 | 621 |The Windows Azure SDK team is busy coding away frameworks and experiences to help 80 | make your projects successful.
81 |We create SDKs that connect to Windows Azure services through REST wrappers 82 | and interfaces in the language of your choice - including .NET, Java, Node.js, 83 | Python, and others.
84 |We accept your open source contributions, license our work with Apache 2.0, and use 85 | GitHub.
86 | 87 |Our frameworks & libraries are developed in agile dev branches on GitHub.
106 | 107 |We provide the low-level REST abstractions, sample code and documentation, and some higher-level functionality, hand-built in your language of choice.
111 | 112 |We strive to release our work under the permissive and open Apache 2.0 license.
116 | 117 |This page contains information about the open source aspect of many 81 | of the Windows Azure SDKs, frameworks & tools. If you want to use 82 | the released versions of these products to develop your applications, 83 | please visit //windowsazure.com/documentation/ 84 | to find official installers, documentation, package manager links, samples and videos.
85 | 86 |These products are actively developed by the Windows Azure SDK team in 87 | collaboration with our open source community.
88 | 89 |Together we are dedicated to creating the best possible experience for 90 | developers creating amazing experiences that are built on the world-class 91 | infrastructure, platforms and frameworks that make up Windows Azure.
92 | 93 |Here is an overview of all Windows Azure projects hosted on Github.
97 | For additional information about Windows Azure and the services it offers
98 | you can visit www.windowsazure.com
99 | If you are interested in contributing to any of the projects below please
100 | read the Contribution Guidelines first.
SDK | 107 |GitHub | 108 |Windows Azure Services | 109 ||
---|---|---|---|
.NET |
114 | 115 | | 116 | |
|
138 |
Java |
141 | 142 | | 143 | |
|
155 |
Node.js |
158 | 159 | | 160 | |
|
183 |
PHP |
186 | 187 | | 188 | |
|
194 |
Python |
197 | 198 | | 199 | |
|
205 |
Ruby |
208 | 209 | | 210 | |
211 |
|
216 |
Mobile Services |
219 | 220 | | 221 | |
|
228 |
This repository contains a set of PowerShell commandlets that let you 246 | deploy applications to Windows Azure using PowerShell.
247 |The cross-platform command line interface (xplat CLI) is written in 256 | Node.js (JavaScript) and lets you deploy apps to Windows Azure on 257 | your Mac, PC, or Linux box.
258 |This repository contains an IIS extension that allows you to host Node.js 273 | applications on Windows.
274 |Markdown-based documentation for the Windows Azure web site's developer 289 | content.
290 |This site.
299 |The Server & Tools business at Microsoft has a lot of great open source products 307 | that you might want to consider contributing to. Note that these products may have different 308 | guidelines for contributions of open source than the Windows Azure SDK.
309 | 310 |The open source home of ASP.NET MVC, Web API, and Web Pages.
312 | 313 |Open source developer-focused package management system for the .NET platform.
315 | 316 |The engine behind git deployments for the Windows Azure Web Sites feature.
318 | 319 | 322 | 323 |Thanks go to our community of developers who have helped improve the 90 | quality of the Windows Azure open source products by helping with 91 | code contributions.
92 | 93 | 94 | 95 |
100 | git log --pretty=format:"%aN <%aE>" | sort -u | node process-contributors.js
101 |
If you've contributed to Windows Azure open source and would like to
209 | be listed, please submit a pull request to thanks.html
in the
210 |
212 | https://github.com/windowsazure/windowsazure.github.com/ repo.