14. Status
Where we were: Where we are now:
Releases on SourceForge
Semi-Yearly releases
No public source
Few public contributors
15. Status
Where we were: Where we are now:
Releases on SourceForge Source on GitHub
Semi-Yearly releases
No public source
Few public contributors
16. Status
Where we were: Where we are now:
Releases on SourceForge Source on GitHub
Semi-Yearly releases Daily Builds
No public source
Few public contributors
17. Status
Where we were: Where we are now:
Releases on SourceForge Source on GitHub
Semi-Yearly releases Daily Builds
No public source YUI 2 & 3 full source
Few public contributors
18. Status
Where we were: Where we are now:
Releases on SourceForge Source on GitHub
Semi-Yearly releases Daily Builds
No public source YUI 2 & 3 full source
Few public contributors Released 4 other tools
19. Status
Where we were: Where we are now:
Releases on SourceForge Source on GitHub
Semi-Yearly releases Daily Builds
No public source YUI 2 & 3 full source
Few public contributors Released 4 other tools
YUIDoc
20. Status
Where we were: Where we are now:
Releases on SourceForge Source on GitHub
Semi-Yearly releases Daily Builds
No public source YUI 2 & 3 full source
Few public contributors Released 4 other tools
YUIDoc
Builder
21. Status
Where we were: Where we are now:
Releases on SourceForge Source on GitHub
Semi-Yearly releases Daily Builds
No public source YUI 2 & 3 full source
Few public contributors Released 4 other tools
YUIDoc
Builder
PHPLoader
22. Status
Where we were: Where we are now:
Releases on SourceForge Source on GitHub
Semi-Yearly releases Daily Builds
No public source YUI 2 & 3 full source
Few public contributors Released 4 other tools
YUIDoc
Builder
PHPLoader
Compressor
23. Status
Where we were: Where we are now:
Releases on SourceForge Source on GitHub
Semi-Yearly releases Daily Builds
No public source YUI 2 & 3 full source
Few public contributors Released 4 other tools
YUIDoc
Builder
PHPLoader
Compressor
Several public contributors
72. How?
What is Git?
Git is a free & open source, distributed version control
system designed to handle everything from small to
very large projects with speed and efficiency.
Every Git clone is a full-fledged repository with
complete history and full revision tracking capabilities,
not dependent on network access or a central server.
Branching and merging are fast and easy to do.
73. How?
What is Git?
Git is a free & open source, distributed version control
Git is a distributed
system designed to handle everything from small to
very large projects with speed and efficiency.
version control system.
Every Git clone is a full-fledged repository with
complete history andis a full tracking capabilities,
Every clone full revision
not dependent on network access or a central server.
repository.
Branching and merging are fast and easy to do.
92. How?
Forking is the preferred way of collaboration on GitHub and it
works quite well with git. You get your own public repository which
contains exactly the same history as the main repository at the time
you forked it. You will later push your contributions into this
repository and the maintainers of the main repository will pull your
commits into the main branch.
93. How?
Forking is the preferred way of collaboration on GitHub and it
works quite well with git. You get your own public repository which
contains exactly the same history as the mainbranching time
Forking on GitHub is like repository at the
you forked it. You will later push your contributions into this
on steriods.
repository and the maintainers of the main repository will pull your
commits into the main branch.
107. How?
General Guidelines:
• Sign & Submit a CLA
• Have a Use Case
• Create a Ticket
• Have a working Test Case
108. How?
General Guidelines:
• Sign & Submit a CLA
• Have a Use Case
• Create a Ticket
• Have a working Test Case
• Make an Example
109. How?
General Guidelines:
• Sign & Submit a CLA
• Have a Use Case
• Create a Ticket
• Have a working Test Case
• Make an Example
• Be Open to Suggestions
111. How?
Why a CLA?
Contributor License Agreement
The CLA ensures that everyone who commits intellectual
property to the YUI Library is contributing work that is
their own.
112. How?
Why a CLA?
Contributor License Agreement
The CLA ensures that everyone who commits intellectual
property to the YUI Library is contributing work that is
their own.
More Information:
http://developer.yahoo.com/yui/community/
114. How?
Use Case
Test Case
Make sure you have a valid use case for
your issue. Cover your bases.
115. How?
Use Case
Test Case
Make sure you have a valid use case for
your issue. Cover your bases.
Test cases are very important, but make
sure that your test actually tests what you
think it does!
117. How?
Pull Requests..
Pull Requests are how we know what
and when you want us to pull your
code and start the process of getting it
merged into the code line.
118. How?
Pull Requests..
Pull Requests are how we know what
and when you want us to pull your
code and start the process of getting it
merged into the code line.
129. How?
Submitting a Pull Request
Steps from here:
• A Ticket is Created.
• Owner:
• Determines if valid.
130. How?
Submitting a Pull Request
Steps from here:
• A Ticket is Created.
• Owner:
• Determines if valid.
• Merges in changes.
131. How?
Submitting a Pull Request
Steps from here:
• A Ticket is Created.
• Owner:
• Determines if valid.
• Merges in changes.
• Creates a build.
132. How?
Submitting a Pull Request
Steps from here:
• A Ticket is Created.
• Owner:
• Determines if valid.
• Merges in changes.
• Creates a build.
• Build system pushes to GitHub
137. How?
Other ways to Contribute
•
Examples
•
Creating new
•
Updating current
138. How?
Other ways to Contribute
•
Examples
•
Creating new
•
Updating current
•
Support
139. How?
Other ways to Contribute
•
Examples
•
Creating new
•
Updating current
•
Support
•
Submitting Tickets
140. How?
Other ways to Contribute
•
Examples
•
Creating new
•
Updating current
•
Support
•
Submitting Tickets
•
Answering Forum Posts
141. How?
Other ways to Contribute
•
Examples
•
Creating new
•
Updating current
•
Support
•
Submitting Tickets
•
Answering Forum Posts
•
Writing Tests
142. How?
Other ways to Contribute
•
Examples
•
Creating new
•
Updating current
•
Support
•
Submitting Tickets
•
Answering Forum Posts
•
Writing Tests
•
New Modules
145. YUI 3 Gallery
http://yuilibrary.com/gallery/
Your code on our CDN!
146. YUI 3 Gallery
http://yuilibrary.com/gallery/
Your code on our CDN!
Gallery allows all YUI developers to extend
the library rapidly, adding modules that
are accessible from any YUI 3 use()
statement.
153. YUI 3 Gallery
Add Add your module and pick a name.
We will try to approve new modules as
Get Approved
fast as we can.
154. YUI 3 Gallery
Add Add your module and pick a name.
We will try to approve new modules as
Get Approved
fast as we can.
Fork the yui3-gallery project on
Fork It!
GitHub.
155. YUI 3 Gallery
Add Add your module and pick a name.
We will try to approve new modules as
Get Approved
fast as we can.
Fork the yui3-gallery project on
Fork It!
GitHub.
Commit Commit your code to your fork.
156. YUI 3 Gallery
Add Add your module and pick a name.
We will try to approve new modules as
Get Approved
fast as we can.
Fork the yui3-gallery project on
Fork It!
GitHub.
Commit Commit your code to your fork.
Submit a CDN Request for your
CDN Request
module from the Gallery.
157. YUI 3 Gallery
Give us some time to approve the CDN
Request. It takes a little time.
158. YUI 3 Gallery
Once approved, it will be deployed to our
CDN and available to anyone.
159. YUI 3 Gallery
And that's more awesome than
Captain James T. Kirk.