Add comprehensive development roadmap via GitHub Issues
Created 10 detailed GitHub issues covering: - Project activation and management UI (#1-2) - Worker node coordination and visualization (#3-4) - Automated GitHub repository scanning (#5) - Intelligent model-to-issue matching (#6) - Multi-model task execution system (#7) - N8N workflow integration (#8) - Hive-Bzzz P2P bridge (#9) - Peer assistance protocol (#10) Each issue includes detailed specifications, acceptance criteria, technical implementation notes, and dependency mapping. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
20
mcp-server/node_modules/lunr/CONTRIBUTING.md
generated
vendored
Normal file
20
mcp-server/node_modules/lunr/CONTRIBUTING.md
generated
vendored
Normal file
@@ -0,0 +1,20 @@
|
||||
Contributions are very welcome. To make the process as easy as possible please follow these steps:
|
||||
|
||||
* Open an issue detailing the bug you've found, or the feature you wish to add. Simplified working examples using something like [jsFiddle](http://jsfiddle.net) make it easier to diagnose your problem.
|
||||
* Add tests for your code (so I don't accidentally break it in the future).
|
||||
* Don't change version numbers or make new builds as part of your changes.
|
||||
* Don't change the built versions of the library; only make changes to code in the `lib` directory.
|
||||
|
||||
# Developer Dependencies
|
||||
|
||||
A JavaScript runtime is required for building the library.
|
||||
|
||||
Run the tests (using PhantomJS):
|
||||
|
||||
make test
|
||||
|
||||
The tests can also be run in the browser by starting the test server:
|
||||
|
||||
make server
|
||||
|
||||
This will start a server on port 3000, the tests are then available at `/test`.
|
||||
Reference in New Issue
Block a user