d582a66bea
When a password was set for a mail share an e-mail was sent to the recipient with the password. Now the e-mail is no longer sent if the password is meant to be sent by Talk. However, before the e-mail was not sent when the share was updated but the password was not changed. Now an e-mail is sent in that case too if switching from a password sent by Talk to a password sent by mail. On the other hand, when switching from a password sent by mail to a password sent by Talk it is mandatory to change the password; otherwise the recipient would already have access to the share without having to call the sharer to verify her identity. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> |
||
---|---|---|
.github | ||
.idea | ||
.tx | ||
3rdparty@4b46a9176e | ||
apps | ||
build | ||
config | ||
contribute | ||
core | ||
lib | ||
ocm-provider | ||
ocs | ||
ocs-provider | ||
resources | ||
settings | ||
tests | ||
themes | ||
.bowerrc | ||
.codecov.yml | ||
.drone.yml | ||
.gitignore | ||
.gitmodules | ||
.htaccess | ||
.jshintrc | ||
.mailmap | ||
.scrutinizer.yml | ||
.tag | ||
.user.ini | ||
AUTHORS | ||
autotest-checkers.sh | ||
autotest-external.sh | ||
autotest-hhvm.sh | ||
autotest-js.sh | ||
autotest.sh | ||
bower.json | ||
buildjsdocs.sh | ||
CHANGELOG.md | ||
CODE_OF_CONDUCT.md | ||
composer.json | ||
console.php | ||
CONTRIBUTING.md | ||
COPYING | ||
COPYING-README | ||
cron.php | ||
index.html | ||
index.php | ||
issue_template.md | ||
occ | ||
public.php | ||
README.md | ||
remote.php | ||
robots.txt | ||
status.php | ||
version.php |
Nextcloud Server
A safe home for all your data.
Why is this so awesome?
- 📁 Access your Data You can store your files, contacts, calendars and more on a server of your choosing.
- 📦 Sync your Data You keep your files, contacts, calendars and more synchronized amongst your devices.
- 🔄 Share your Data …by giving others access to the stuff you want them to see or to collaborate with.
- 🚀 Expandable with dozens of Apps ...like Calendar, Contacts, Mail and all those you can discover in our App Store
- 🔒 Security with our encryption mechanisms, HackerOne bounty program and two-factor authentication.
You want to learn more about how you can use Nextcloud to access, share and protect your files, calendars, contacts, communication & more at home and at your Enterprise? Learn about all our Features.
Get your Nextcloud
- Install a server by yourself on your own hardware or by using one of our ready to use Appliances
- Buy one of the awesome devices coming with a preinstalled Nextcloud
- Find a service provider who is hosting Nextcloud for you or your company
Enterprise? Public Sector or Education user? You may want to have a look into the Enterprise Support Subscription provided by the Nextcloud GmbH
Get in touch
…learn more about how to get support for Nextcloud here!
Contribution Guidelines
All contributions to this repository from June, 16 2016 on are considered to be licensed under the AGPLv3 or any later version.
Nextcloud doesn't require a CLA (Contributor License Agreement). The copyright belongs to all the individual contributors. Therefore we recommend that every contributor adds following line to the header of a file, if they changed it substantially:
@copyright Copyright (c) <year>, <your name> (<your email address>)
Please read the Code of Conduct. This document offers some guidance to ensure Nextcloud participants can cooperate effectively in a positive and inspiring atmosphere, and to explain how together we can strengthen and support each other.
Please review the guidelines for contributing to this repository.
More information how to contribute: https://nextcloud.com/contribute/
Running master checkouts
Third-party components are handled as git submodules which have to be initialized first. So aside from the regular git checkout invoking git submodule update --init
or a similar command is needed, for details see Git documentation.
Several apps that are included by default in regular releases such as firstrunwizard or gallery are missing in master
and have to be installed manually.
That aside Git checkouts can be handled the same as release archives.
Note they should never be used on production systems.