author | Giulio Cesare Solaroli <giulio.cesare@solaroli.it> | 2011-10-03 21:18:47 (UTC) |
---|---|---|
committer | Giulio Cesare Solaroli <giulio.cesare@solaroli.it> | 2011-10-03 21:18:47 (UTC) |
commit | 101c3d3de142b4467d5b217ac056a301b0d857d5 (patch) (unidiff) | |
tree | e47c2289bd868744c0841b9235f4ef39f6c400c5 | |
parent | 541bb378ddece2eab135a8066a16994e94436dea (diff) | |
parent | 148f8b07a622ecc95b72759b5d92216bab269c82 (diff) | |
download | clipperz-101c3d3de142b4467d5b217ac056a301b0d857d5.zip clipperz-101c3d3de142b4467d5b217ac056a301b0d857d5.tar.gz clipperz-101c3d3de142b4467d5b217ac056a301b0d857d5.tar.bz2 |
Merge pull request #2 from marclaporte/patch-1
Thanks for the fix. For this time I will ask you to sign the contribution agreement. :)
-rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -14,33 +14,33 @@ ALL the code included in this project, if not otherwise stated, is released with | |||
14 | 14 | ||
15 | But why would you prefer running Clipperz Community Edition from your own server instead of using the free and anonymous online service provided by its developers? | 15 | But why would you prefer running Clipperz Community Edition from your own server instead of using the free and anonymous online service provided by its developers? |
16 | 16 | ||
17 | * “Clipperz security architecture is great, but I prefer to store my data on my hardware. I just feel better this way!” | 17 | * “Clipperz security architecture is great, but I prefer to store my data on my hardware. I just feel better this way!” |
18 | * “Clipperz is cool, but it would be even cooler it it had a Scala backend. I'm going to write it!" | 18 | * “Clipperz is cool, but it would be even cooler it it had a Scala backend. I'm going to write it!" |
19 | * “I would like to modify the look & feel of Clipperz and embed this powerful password manager within my family intranet.” | 19 | * “I would like to modify the look & feel of Clipperz and embed this powerful password manager within my family intranet.” |
20 | * “Clipperz works nicely, but I would love to play with the source code in order to improve feature X and add new features Y and Z.” | 20 | * “Clipperz works nicely, but I would love to play with the source code in order to improve feature X and add new features Y and Z.” |
21 | * … | 21 | * … |
22 | 22 | ||
23 | Whatever is your motivation, we would love to hear from you about how and where you use Clipperz Community Edition. [Get in contact!][contact] | 23 | Whatever is your motivation, we would love to hear from you about how and where you use Clipperz Community Edition. [Get in contact!][contact] |
24 | 24 | ||
25 | 25 | ||
26 | ## Warnings | 26 | ## Warnings |
27 | 27 | ||
28 | Please note that Clipperz Community Edition may not be suitable for mass deployments, depending on how robust is the backend you select. | 28 | Please note that Clipperz Community Edition may not be suitable for mass deployments, depending on how robust is the backend you select. |
29 | 29 | ||
30 | As an example, the current PHP backend lacks several critical capabilities such as bot protection and cuncurrent sessions management. | 30 | As an example, the current PHP backend lacks several critical capabilities such as bot protection and concurrent sessions management. |
31 | 31 | ||
32 | 32 | ||
33 | ## Community Edition vs Workgroup Edition | 33 | ## Community Edition vs Workgroup Edition |
34 | 34 | ||
35 | This Community Edition is aimed to **individual users**, but you may be interested to know that we are working on a **Workgroup Edition** targeting organizations that need a | 35 | This Community Edition is aimed to **individual users**, but you may be interested to know that we are working on a **Workgroup Edition** targeting organizations that need a |
36 | password manager for their workforce (creating and managing employees accounts, defining groups and sharing policies, ...). | 36 | password manager for their workforce (creating and managing employees accounts, defining groups and sharing policies, ...). |
37 | 37 | ||
38 | The Workgroup Edition development is quite challenging and, while the overall design is already in place, it will still require a fairly large amount of resources for analysis and implementation. | 38 | The Workgroup Edition development is quite challenging and, while the overall design is already in place, it will still require a fairly large amount of resources for analysis and implementation. |
39 | 39 | ||
40 | If your organization is interested in such edition, you can subscribe a "pledge" to sustain its development in exchange for a very generous user license with unlimited upgrades and other benefits. Again, [get in contact][contact]! | 40 | If your organization is interested in such edition, you can subscribe a "pledge" to sustain its development in exchange for a very generous user license with unlimited upgrades and other benefits. Again, [get in contact][contact]! |
41 | 41 | ||
42 | 42 | ||
43 | ## Contributions | 43 | ## Contributions |
44 | 44 | ||
45 | Your contributions to Clipperz Community Edition are very welcome! In order to avoid jeopardizing the ownership of the code base, we will require every developer to sign the Clipperz [Contributor Agreement][CA] | 45 | Your contributions to Clipperz Community Edition are very welcome! In order to avoid jeopardizing the ownership of the code base, we will require every developer to sign the Clipperz [Contributor Agreement][CA] |
46 | 46 | ||