author | marclaporte <marc@marclaporte.com> | 2011-10-03 17:40:54 (UTC) |
---|---|---|
committer | marclaporte <marc@marclaporte.com> | 2011-10-03 17:40:54 (UTC) |
commit | 148f8b07a622ecc95b72759b5d92216bab269c82 (patch) (unidiff) | |
tree | e47c2289bd868744c0841b9235f4ef39f6c400c5 | |
parent | 541bb378ddece2eab135a8066a16994e94436dea (diff) | |
download | clipperz-148f8b07a622ecc95b72759b5d92216bab269c82.zip clipperz-148f8b07a622ecc95b72759b5d92216bab269c82.tar.gz clipperz-148f8b07a622ecc95b72759b5d92216bab269c82.tar.bz2 |
typo
-rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -18,25 +18,25 @@ But why would you prefer running Clipperz Community Edition from your own server | |||
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 | ||