| /plugin/webdav/vendor/sabre/dav/ |
| H A D | CONTRIBUTING.md | 11 We may not want to accept every feature that comes our way. Sometimes
14 We don't want to waste your time, so by having a quick chat with us first,
29 We are often on [IRC][5], in the #sabredav channel on freenode. If there's
68 Any new feature or change requires unittests. We use [PHPUnit][7] for all our
75 We may have to write the tests ourselves, which can increase the time it takes
|
| /plugin/davcal/vendor/sabre/dav/ |
| H A D | CONTRIBUTING.md | 11 We may not want to accept every feature that comes our way. Sometimes
14 We don't want to waste your time, so by having a quick chat with us first,
29 We are often on [IRC][5], in the #sabredav channel on freenode. If there's
68 Any new feature or change requires unittests. We use [PHPUnit][7] for all our
75 We may have to write the tests ourselves, which can increase the time it takes
|
| /plugin/statdisplay/pchart/ |
| H A D | README | 2 1.x library. We can't use the pChart 2.x library because of unclear license
8 We're currently at this commit (master branch):
|
| /plugin/webcode/_test/data/pages/ |
| H A D | display.txt | 29 * We should not see the cached code block (Only the bullet point of the list)
34 * We should see the code block below
|
| /plugin/findologicxmlexport/vendor/hoa/ustring/ |
| H A D | README.md | 63 We propose a quick overview of two usages: manipulate UTF-8 strings and one
70 `\IteratorAggregate` interfaces. We will use the following examples:
91 We note that it cares about text **direction**. Look at `$arabic[0]`, it returns
118 We are also able to iterate over the string:
148 We can also transform any text into ASCII:
187 We will found `AGATA`, `GATAA`, `ATAAG` and `GAGAA`.
|
| /plugin/editonlink/ |
| H A D | LICENSE | 10 software to the public domain. We make this dedication for the benefit
12 successors. We intend this dedication to be an overt act of
|
| /plugin/elasticsearch/vendor/elasticsearch/elasticsearch/docs/ |
| H A D | breaking-changes.asciidoc | 9 every time you use a deprecated parameters for {es}. We decided to add this
44 We require using PHP 7.1+ for elasticsearch-php. PHP 7.0 is not supported since
|
| H A D | php_json_objects.asciidoc | 37 `"content" : []`, which is no longer valid {es} DSL. We need to tell PHP that
57 <1> We use the generic PHP stdClass object to represent an empty object. The
153 We can build it using the following PHP code:
|
| /plugin/cookiebanner/lang/en/ |
| H A D | intro.txt | 1 …rack visitors anonymously. It doesn't hurt you, but helps us tremendously. We'd be grateful if you…
|
| /plugin/csv/_test/ |
| H A D | README | 1 We're using test files from various projects here:
|
| /plugin/authgooglesheets/vendor/google/apiclient-services/ |
| H A D | SECURITY.md | 7 We use g.co/vulnz for our intake, and do coordination and disclosure here using GitHub Security Adv…
|
| /plugin/authgooglesheets/vendor/psr/http-message/ |
| H A D | README.md | 13 We'll certainly need some stuff in here.
|
| /plugin/authgooglesheets/vendor/google/auth/ |
| H A D | SECURITY.md | 7 We use g.co/vulnz for our intake, and do coordination and disclosure here using GitHub Security Adv…
|
| /plugin/authgooglesheets/vendor/google/apiclient/ |
| H A D | SECURITY.md | 7 We use g.co/vulnz for our intake, and do coordination and disclosure here using GitHub Security Adv…
|
| /plugin/findologicxmlexport/vendor/jms/metadata/ |
| H A D | CONTRIBUTING.md | 28 We automatically run your pull request through [Travis CI](https://www.travis-ci.org)
42 We will give our best to review everything as fast as possible, but cannot always live up to our ow…
|
| /plugin/findologicxmlexport/vendor/jms/serializer/ |
| H A D | CONTRIBUTING.md | 20 We're using [`composer/composer`](https://github.com/composer/composer) to manage dependencies
52 We automatically run your pull request through [Travis CI](https://www.travis-ci.org)
69 We will give our best to review everything as fast as possible, but cannot always live up to our ow…
|
| /plugin/findologicxmlexport/vendor/hoa/visitor/ |
| H A D | README.md | 62 We propose to explain the basis of this library. We have two entities: an
68 contain the visitor computations. We will find several examples in Hoa
|
| /plugin/icons/assets/ |
| H A D | LICENSE.md | 50 We have made these icons available for you to incorporate into your products under the [Apache License Version 2.0](https://www.apache.org/licenses/LICENSE-2.0.txt). Feel free to remix and re-share these icons and documentation in your products.
51 We'd love attribution in your app's *about* screen, but it's not required. The only thing we ask is that you not re-sell these icons.
|
| /plugin/combo/resources/theme/default/pages/templates/ |
| H A D | landing.css | 10 * We may also just put it completely in the offcanvas
|
| /plugin/move/lang/pl/ |
| H A D | move.txt | 10 We wszystkich linkach z i do zmienianej strony będzie użyta nowa lokalizacja.
|
| /plugin/elwikiupgrade/lang/nl/ |
| H A D | step0.txt | 7 We raden aan vóór je verder gaat een backup van je wiki te maken.
|
| /plugin/elwikiupgrade/lang/en/ |
| H A D | step0.txt | 7 We recommend that you create a backup of your wiki before continuing.
|
| /plugin/upgrade/lang/en/ |
| H A D | step0.txt | 7 We recommend that you create a backup of your wiki before continuing
|
| /plugin/upgrade/lang/nl/ |
| H A D | step0.txt | 7 We raden aan vóór je verder gaat een backup van je wiki te maken
|
| /plugin/pgn4web/pgn4web/ |
| H A D | pgn-standard-proposed-supplement.txt | 76 We also propose the addition of a tag to the header to handle the state of the
113 on any single character as an unambiguous opening delimiter. We have chosen to
123 We are *not* proposing any fixed canonical list of commands. The idea is to
127 We *are* proposing a set of commands to deal with time handling. "clk" in the
166 We have thus departed from the epd opcode specification in two ways:
189 We propose the following commands for time handling The first is the command
244 We propose that this information should be encoded in a new header tag.
346 We ruled out the use of < > as delimiters specified in the BIF format because if
351 does envisage the specification of new optional tags. We have taken advantage of
|