Source

Weavver® source and installers are not currently available for public download. The project is under heavy development.
Recommended Clients:
PC: Tortoise SVN
Weavver is open source and free. We recognize that limiting our code base to one licensing model may not meet and serve all needs therefore we also take care to maintain different models of distribution of our products, code, and services. Please read more on our licensing page.

1. You may download Weavver source code from http://svn.weavver.com/source using any standard SVN client.
  • No password is necessary as anonymous read-only login is enabled.
2. Not all of our source code is public yet. We are working on it but please be patient.

*Note: The repo is currently unpopulated. We have a large amount of code in our private repository that we will migrate to the /source repository as soon as we can perform a data scrub to remove Weavver, Inc. specific data.


How do I become a contributor?


There are several ways to contribute:

a. Patches
b. Bounties
c. Commit access
d. Join our team!

Before you do any of the above, you must fill out and agree to the contributor agreement.

"Wait!! -- I'm not a programmer?" That's okay! Don't be scared. Think of it this way.. Subversion keeps track of files. That means word documents.. Excel.. Etc. And p.s. we need help with everything, not just code. :) If you would like, you can also help out by supporting other users like you in our public forum, or spread the word.


How do I make patches?


1. Download our source via the Subversion link above.
2. Modify the files on your local file system.
3. Use your Subversion client to generate a patch.
4. Submit your patch.


Commit Access


Commit access is considered a privilege and a responsibility. This is not the easiest or quickest way to get your changes into our repository. If you are looking for something quicker, please consider submitting your work as patches.

To earn this access:

1. Become an active and positive member of our community.
2. Earn karma by submitting patches.
3. Pass a background check.
4. Have solid references.
5. Be a team player.
6. Follow our design standards, patterns, and goals.


Repositories


Currently, we maintain a few repositories. Mainly we have a couple for private use and one for public use. Code that can not be released without comprimising the security and integrity of our website and customers will be kept in our private repository until we can publicly cleanse it of security issues (such as hardcoded passwords) and clear up any intellectual property issues.