We are open to, and grateful for, any contributions made by the community. By contributing to pixie, you agree to abide by the code of conduct.
Before opening an issue, please search the issue tracker to make sure your issue hasn't already been reported.
We use the issue tracker to keep track of bugs and improvements to pixie itself, its examples, and the documentation. We encourage you to open issues to discuss improvements, architecture, theory, internal implementation, etc. If a topic has been discussed before, we will ask you to join the previous discussion.
As pixie is stable software, changes to its behavior are very carefully considered.
For support or usage questions like “how do I do X with pixie and “my code doesn't work”, please search and ask on StackOverflow with a pxi tag first.
We ask you to do this because StackOverflow does a much better job at keeping popular questions visible. Unfortunately good answers get lost and outdated on GitHub.
Some questions take a long time to get an answer. If your question gets closed or you don't get a reply on StackOverflow for longer than a few days, we encourage you to post an issue linking to your question. We will close your issue but this will give people watching the repo an opportunity to see your question and reply to it on StackOverflow if they know the answer.
Please be considerate when doing this as this is not the primary purpose of the issue tracker.
On both websites, it is a good idea to structure your code and question in a way that is easy to read to entice people to answer it. For example, we encourage you to use syntax highlighting, indentation, and split text in paragraphs.
Please keep in mind that people spend their free time trying to help you. You can make it easier for them if you provide versions of the relevant libraries and, if applicable, a runnable small project reproducing your issue. You can put your code on JSBin or, for bigger projects, on GitHub. Make sure all the necessary dependencies are declared in package.json so anyone can run npm install && npm start and reproduce your issue.
Visit the issue tracker to find a list of open issues that need attention.
Fork, then clone the pxi-pxi repo (make sure you backup your .pxi module):
git clone https://github.com/your-username/pxi-pxi.git ~/.pxiWrite your chunkers, deserializers, appliers, and serializers.
Make sure you have added the plugin in your .pxi module. The plugin's extensions should show up in pxi --help and can be used.
Please open an issue describing what your plugin does. Then, open a pull request that adds your plugin to pxi's README.
Visit the issue tracker to find a list of open issues that need attention.
Fork, then clone the repo:
git clone https://github.com/your-username/pxi.gitRun pixie with either of the following commands:
npm start -- --help
node index.js --helpTo only run linting:
npm run lintTo only run tests:
npm testImprovements to the documentation are always welcome.
Pixie comes with official examples to demonstrate its features. When adding a new example, please adhere to the style and format of the existing examples.
For non-trivial changes, please open an issue with a proposal for a new feature or refactoring before starting on the work. We don't want you to waste your efforts on a pull request that we won't want to accept.
On the other hand, sometimes the best way to start a conversation is to send a pull request. Use your best judgement!
In general, the contribution workflow looks like this:
- Open a new issue in the issue tracker.
- Fork the repository.
- Create a new feature branch based off the
developbranch. - Make sure all tests pass and there are no linting errors.
- Submit a pull request, referencing any issues it addresses.
Please try to keep your pull request focused in scope and avoid including unrelated commits.
After you have submitted your pull request, we'll try to get back to you as soon as possible. We may suggest some changes or improvements.
Thank you for contributing!