From 6b3c829e4e973820a3433f13eff910e5071e8007 Mon Sep 17 00:00:00 2001 From: Valmik Date: Thu, 28 Apr 2016 10:28:32 +0530 Subject: [PATCH] Delete Contributing.md Existing file in .github folder --- CONTRIBUTING.md | 68 ------------------------------------------------- 1 file changed, 68 deletions(-) delete mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index ed2d7c56a6..0000000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,68 +0,0 @@ -# Contributing to Frappe / ERPNext - -## Questions - -If you have questions on how to use ERPNext or want help in customization or debugging of your scripts, please post on https://discuss.erpnext.com. This is only for bug reports and feature requests. - -## Reporting issues - -We only accept issues that are bug reports or feature requests. Bugs must be isolated and reproducible problems. Please read the following guidelines before opening any issue. - -1. **Search for existing issues:** We want to avoid duplication, and you'd help us out a lot by first checking if someone else has reported the same issue. The issue may have already been resolved with a fix available. -1. **Report each issue separately:** Don't club multiple, unreleated issues in one note. -1. **Mention the version number:** Please mention the application, browser and platform version numbers. - -### Issues - -1. **Share as much information as possible:** Include operating system and version, browser and version, when did you last update ERPNext, how is it customized, etc. where appropriate. Also include steps to reproduce the bug. -1. **Include Screenshots if possible:** Consider adding screenshots annotated with what goes wrong. -1. **Find and post the trace for bugs:** If you are reporting an issue from the browser, Open the Javascript Console and paste us any error messages you see. -1. **Security Issues:** If you are reporting a security issue, please send a private email to . - - -### Feature Requests - -1. We need as much information you can to consider a feature request. -1. Think about **how** you want us to build the feature. Consider including: - 1. Mockups (wireframes of features) - 1. Screenshots (annotated with what should change) - 1. Screenshots from other products if you want us to implement features present in other products. -1. Basically, the more you help us, the faster your request is likely to be completed. -1. A one line feature request like **Implement Capacity Planning** will be closed. - -## Pull Requests - -General guidelines for sending pull requests: - -#### Don't Repeat Yourself (DRY) - -We believe that the most effective way to manage a product like this is to ensure that -there is minimum repetition of code. So before contributing a function, please make sure -that such a feature or function does not exist else where. If it does, the try and extend -that function to accommodate your use case. - -#### Don't create new DocTypes Unless Absolutely Necessary - -DocTypes are easy to create but hard to maintain. If you find that there is a another DocType with a similar functionality, then please try and extend that functionality. For example, by adding a "type" field to classify the new type of record. - -#### Tabs or spaces? - -Tabs! - -#### Release Checklist - -- Describe, in detail, what is in the pull request -- How to use the new feature? -- Test cases -- Change log -- Manual Pull Request Link -- Screencast. Should include: - - New Forms - - Linked Forms - - Linked Reports - - Print Views - -### Copyright - -Please see README.md -