Permalink
Browse files

README, LICENSE: Add note about contributing

License the software under MIT license, and write a small document
about making changes.

Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
  • Loading branch information...
1 parent 658eb8f commit bf946fea1609828473bab8b891641267ec59dfc5 @artagnon artagnon committed Aug 29, 2011
Showing with 51 additions and 0 deletions.
  1. +22 −0 LICENSE
  2. +29 −0 README.mkd
View
22 LICENSE
@@ -0,0 +1,22 @@
+Copyright (c) 2011 Kharagpur Linux Users' Group
+
+Permission is hereby granted, free of charge, to any person
+obtaining a copy of this software and associated documentation
+files (the "Software"), to deal in the Software without
+restriction, including without limitation the rights to use,
+copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the
+Software is furnished to do so, subject to the following
+conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
+HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+OTHER DEALINGS IN THE SOFTWARE.
View
@@ -0,0 +1,29 @@
+klug.github.com Website
+=======================
+
+How to make changes to the website, and get it merged into upstream:
+
+1. Fork the project on GitHub, so that you have your own copy of the
+project to play with.
+
+2. Make the changes that you want and split the changes up into
+logical commits. Don't forget to signoff on them.
+
+3. Please read and try to follow
+[Documentation/SubmittingPatches](http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob_plain;f=Documentation/SubmittingPatches).
+Since 'git-send-email' will not work from behind a restrictive
+firewall, either send one of the website maintainers an email with the
+patches attached, or send a "Pull Request" on GitHub if there are >10
+commits.
+
+4. Alternatively, if you think the changes will impact KLUG
+siginificantly, or you feel that your changes require discussion,
+please post the patches to the mailing list.
+
+5. The website maintainers will download the patches from their email
+inboxes, and apply them with git-am. They might choose to make minor
+changes or drop a few patches before pushing them to upstream. They
+will reply to your email with a rationale if necessary. Please pull
+the latest code from upstream to see your commits.
+
+Thanks, and enjoy contributing!

0 comments on commit bf946fe

Please sign in to comment.