[
  {
    "path": ".github/CONTRIBUTING.md",
    "content": "### 1. The issues list is for development purposes only.\n\nAll issues reported here should result in **code being changed, added, or removed**.\n\nFor support requests, please use [limetext/support](https://github.com/limetext/support) instead.\n\n\n### 2. Issues should be opened up in the correct repository.\n\nIssues should only be reported here if they cover the project as a whole. If the issue relates to a specific package, please file it there instead. Lime Text is made up of a number of packages, which can be found [here](https://github.com/limetext).\n\n\n### 3. If you would like to help but do not know how.\n\nThere is plenty of work that needs to be done, requiring a wide variety of skills and skill levels. The [Contributing wiki page](https://github.com/limetext/lime/wiki/Contributing) is a good place to start for some ideas.\n\nThere is no roadmap with well staked out milestones, where we can just give you a specific task to work on, and the few volunteers who are actively involved at the moment are already having a hard time managing everything. This is a community-run project, without any commercial backing, and any time spent here by our volunteers is their own spare time that they kindly donate to the project instead of spending time with friends, family, and other interests.\n\nWe do need your help. Even 5 minutes spent fixing a typo is valuable to us, and if you can spare more time, even better.\n"
  },
  {
    "path": ".github/ISSUE_TEMPLATE.md",
    "content": "> Replace me with your issue!\n\n\n##### Disclaimer:\n\n - [ ] I have read the guidelines for contributing linked to above.\n - [ ] This issue is related to the limetext project as a whole and would not belong better in one of the individual package repositories found [here](https://github.com/limetext).\n - [ ] I have checked for duplicate issues.\n - [ ] This is not a [support request](https://github.com/limetext/support).\n"
  },
  {
    "path": "LICENSE",
    "content": "Copyright (c) 2013 The lime Authors\nAll rights reserved.\n\nRedistribution and use in source and binary forms, with or without\nmodification, are permitted provided that the following conditions are met:\n\n1. Redistributions of source code must retain the above copyright notice, this\n   list of conditions and the following disclaimer.\n2. Redistributions in binary form must reproduce the above copyright notice,\n   this list of conditions and the following disclaimer in the documentation\n   and/or other materials provided with the distribution.\n\nTHIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS \"AS IS\" AND\nANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED\nWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE\nDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR\nANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES\n(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;\nLOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND\nON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT\n(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS\nSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.\n"
  },
  {
    "path": "README.md",
    "content": "[![Bountysource Bounties](https://www.bountysource.com/badge/team?team_id=8742&style=bounties_received)](https://www.bountysource.com/teams/limetext/issues?utm_source=limetext&utm_medium=shield&utm_campaign=bounties_received)\n[![Bountysource Raised](https://www.bountysource.com/badge/team?team_id=8742&style=raised)](https://www.bountysource.com/teams/limetext?utm_source=limetext&utm_medium=shield&utm_campaign=raised)\n\n[![Gitter](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/limetext/lime)\n\n\n# lime\n\nWelcome to the meta project for Lime.\n\nFor the backend, please see [limetext/lime-backend](https://github.com/limetext/lime-backend).\n\nThere are also three frontends currently in development: [limetext/lime-qml](https://github.com/limetext/lime-qml), [limetext/lime-termbox](https://github.com/limetext/lime-termbox), and [limetext/lime-html](https://github.com/limetext/lime-html).\n\n\n# Status\n\nThe frontends are **not** ready to replace your favourite editor, but the backend isn't too far away.\n\nIf you want to help us build Lime, great! We'd love your help. See [here](https://github.com/limetext/lime#contributing) for how you could be most useful.\n\nThis project is not yet ready for daily use, and we currently lack the resources to support users. If you need help building, running, or otherwise using Lime, try the [wiki](https://github.com/limetext/lime/wiki/_pages) or your favorite search engine. If you still need help, consider opening an issue in [limetext/support](https://github.com/limetext/support). Issues opened in this project that don't relate to bugs or improvements will be closed.\n\nYour help is needed to move the project forward! Claim an [issue](https://github.com/limetext/lime/issues) and submit a pull request!\n\n\n# What is Lime?\n\n> I love the [Sublime Text](http://www.sublimetext.com) editor. [I have](https://github.com/quarnster/SublimeClang) [created](https://github.com/quarnster/SublimeJava) [several](https://github.com/quarnster/CompleteSharp) [plugins](https://github.com/quarnster/SublimeGDB) [to make](https://github.com/quarnster/ADBView) it even better. One thing that scares me though is that it is not open sourced and the [pace of nightly releases](http://www.sublimetext.com/nightly) have recently been anything but nightly, even now that version 3 is out in Beta.\n>\n> There was a period of about 6 months after the Sublime Text 2 \"stable\" version was released where pretty much nothing at all was communicated to the users about what to expect in the future, nor was there much support offered in the forums. People including myself were wondering if the product was dead and I personally wondered what would happen to all the bugs, crashes and annoyances that still existed in ST2. This lack of communication is a dealbreaker to me and I decided that I will not spend any more money on that product because of it.\n>\n> As none of the other text editors I've tried come close to the love I had for Sublime Text, I decided I had to create my own.\n>\n> -- @quarnster\n\n\n### Why API compatibility?\n\nSublime Text has a good plugin architecture and a [large collection of existing plugins](https://sublime.wbond.net/) created for it. We want users to be able to take advantage of these extensions without requiring developers to support multiple APIs.\n\n\n# Goals\n\nPlease refer to the [Goals](https://github.com/limetext/lime/wiki/Goals) page in the [wiki](https://github.com/limetext/lime/wiki/_pages).\n\n\n# Build instructions\n\nPlease refer to the [Building](https://github.com/limetext/lime/wiki/Building) page in the [wiki](https://github.com/limetext/lime/wiki/_pages).\n\n\n# Contributing\n\nWant to help build Lime? Awesome! We are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it.\n\nIf your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve.\n\nWhere is a good place to start? The [Contributing](https://github.com/limetext/lime/wiki/Contributing) page in the wiki has some suggestions. Think the [wiki](https://github.com/limetext/lime/wiki/_pages) needs clarifying, or something is missing? Go ahead and make the change.\n\nGuidelines for making contributions can be found in [CONTRIBUTING.md](.github/CONTRIBUTING.md).\n\nWant to chat? Find us on [Gitter](https://gitter.im/limetext/lime).\n\n\n# License\n\nThe license of the project is the [2-clause BSD license](LICENSE).\n"
  }
]