The pulp javascript Community
pulp strives to have a thriving user community by encouraging users to help users and to contribute suggestions, documentation, bug reports and patches.
User Support
Users can get help and support through pulp's support google group. Your help and feedback is appreciated.
Suggestions
Please submit suggestions on the development mailing list or through pulp's Google code issue tracker.
Documentation
pulp javascript has two types of documentation: automatically generated API reference and user documentation including examples, frequently asked questions, use cases, and tutorials. The documentation can be viewed in /trunk/docs/api/ and /trunks/docs/user/.
The API reference is automatically generated based on the source's inline documentation using JavaDoc-syntax comments. Inline documentation can be modified by checking out the source, making changes, and submitting a patch to pulp's Google code issue tracker. Once a change is committed and the API is regenerated, the new reference pages can be found in /trunk/docs/api/.
pulp's user documentation is also hosted in the SVN source package in /trunk/docs/user/. Please check out the source and post patches to make updates and additions.Bug Reports
To file a bug report, first search pulp's Google code issue tracker to see if one is already filed. If not, please create a new bug report.
Patches
One of our top priorities is to make contributing easy. We use Subversion and patches to manage our source. We hope you will find that Subversion is powerful but still friendly to new developers—especially in contrast to a distributed versioning system that leave many asking "Where's the source?" or "How do I create a patch?".
Please submit SVN patches through pulp's Google code issue tracker.
More Information
New to Subversion? Check out these resources:
- Tortoise SVN Client Home, Manual, and Checkout guide
- Definitive guide to Subversion
- Rice University Subversion tutorial
New to JavaScript? Check out these resources: