* Example code can be found using [https://github.com/search?q=tweak+extension%3A+.xm+&ref=searchresults&type=Code&utf8=%E2%9C%93 Github Search]. To read about flexible searching, please see [[Getting Started#Finding example projects]] for advice

+

* [[Advice for new developers#Choosing open vs. closed source|Advantages, Disadvantages of Open Sourcing]]

−

A bit of background information: If a project does not explicitly have a license that gives you the right to use its code, that means it is copyrighted by the developer and you can't use its code in your own projects - in other words, you can read it and learn from it, but don't copy and paste it. If you've published a project that does not have a free license, and you'd like people to be able to use your code if they want to, [http://www.gnu.org/licenses/license-recommendations.html How to choose a license for your own work] and [http://choosealicense.com/ Choose A License] may be helpful.

+

'''A note on licenses:''' If a project does not explicitly have a license that gives you the right to use its code, that means it is copyrighted by the developer and you can't use its code in your own projects - in other words, you can read it and learn from it, but don't copy and paste it. If you've published a project that does not have a free license, and you'd like people to be able to use your code if they want to, [http://www.gnu.org/licenses/license-recommendations.html How to choose a license for your own work] and [http://choosealicense.com/ Choose A License] may be helpful. GitHub has advice on [https://help.github.com/articles/open-source-licensing adding a license to your repository].

−

== Tweaks ==

+

'''A note on contributing:''' If you'd like to contribute improvements to one of these projects (or even just file a bug report), a great first step is to get in contact with the developer and talk to them about it - you can email them, tweet them, find them on IRC, open an issue on the project page, or whatever method of communication you can find. People are usually pretty happy to hear that another developer is interested enough in their project to want to add something to it. If you'd like to contribute code to a project that is on GitHub (like most of these), GitHub's [https://guides.github.com/activities/contributing-to-open-source/ guide to contributing to open source] has helpful advice for how to make a pull request (a formal way to propose your changes so they can be easily integrated). And yes, [http://openhatch.org/blog/2013/what-contributing-to-open-source-can-give-back-to-you/ contributing is worth your time].

−

Also check out [http://tweakweek.com/ TweakWeek] for a long list of relatively simple open source tweaks, organized by rpetrich.

+

= Tweaks =

+

+

Also check out [http://tweakweek.com/ TweakWeek] for a long list of relatively simple open source tweaks, organized by rpetrich. [[Tweak Battles]] is also a great resource.

A note on licenses: If a project does not explicitly have a license that gives you the right to use its code, that means it is copyrighted by the developer and you can't use its code in your own projects - in other words, you can read it and learn from it, but don't copy and paste it. If you've published a project that does not have a free license, and you'd like people to be able to use your code if they want to, How to choose a license for your own work and Choose A License may be helpful. GitHub has advice on adding a license to your repository.

A note on contributing: If you'd like to contribute improvements to one of these projects (or even just file a bug report), a great first step is to get in contact with the developer and talk to them about it - you can email them, tweet them, find them on IRC, open an issue on the project page, or whatever method of communication you can find. People are usually pretty happy to hear that another developer is interested enough in their project to want to add something to it. If you'd like to contribute code to a project that is on GitHub (like most of these), GitHub's guide to contributing to open source has helpful advice for how to make a pull request (a formal way to propose your changes so they can be easily integrated). And yes, contributing is worth your time.