Miguel Dantas
2db3825940
[CORE][COMPOSER] Added intervention/image
|
5 years ago | |
|---|---|---|
| .. | ||
| apereo | 5 years ago | |
| bin | 5 years ago | |
| composer | 5 years ago | |
| diogocomposer | 5 years ago | |
| embed | 5 years ago | |
| ezyang | 5 years ago | |
| guzzlehttp | 5 years ago | |
| hoa | 5 years ago | |
| intervention | 5 years ago | |
| masterminds | 5 years ago | |
| mf2 | 5 years ago | |
| michelf | 5 years ago | |
| openid | 5 years ago | |
| paragonie | 5 years ago | |
| pear | 5 years ago | |
| phpseclib | 5 years ago | |
| psr | 5 years ago | |
| ralouphie | 5 years ago | |
| stomp-php | 5 years ago | |
| README.md | 5 years ago | |
| autoload.php | 5 years ago | |
README.md
DO NOT "FIX" CODE IN THIS DIRECTORY.
ONLY UPSTREAM VERSIONS OF SOFTWARE GO IN THIS DIRECTORY.
This directory is provided as a courtesy to our users who might be unable or unwilling to find and install libraries we depend on.
If we "fix" software in this directory, we hamstring users who do the right thing and keep a single version of upstream libraries in a system-wide library. We introduce subtle and maddening bugs where our code is "accidentally" using the "wrong" library version. We may unwittingly interfere with other software that depends on the canonical release versions of those same libraries!
Forking upstream software for trivial reasons makes us bad citizens in the Open Source community and adds unnecessary heartache for our users. Don't make us "that" project.
Frequently Asked Questions
Q: What should we do when we find a bug in upstream software?
A: First and foremost, REPORT THE BUG, and if possible send in a patch.
Watch for a release of the upstream software and integrate with it when it's released.
In the meantime, work around the bug, if at all possible. Usually, it's quite possible, if slightly harder or less efficient.
Q: What if the bug can't be worked around?
A: If the upstream developers have accepted a bug patch, it's undesirable but acceptable to apply that patch to the library in the extlib dir. Ideally, use a release version for upstream or a version control system snapshot.
Note that this is a last resort.
Q: What if upstream is unresponsive or won't accept a patch?
A: Try again.
Q: I tried again, and upstream is still unresponsive and nobody's checked on my patch. Now what?
A: If the upstream project is moribund and there's a way to adopt it, propose having the GNU social dev team adopt the project. Or, adopt it yourself.
Q: What if there's no upstream authority and it can't be adopted?
A: Then we fork it. Make a new name and a new version. Include it in extlib/ instead of vendor/, and use the GNUsocial_* prefix to change the namespace to avoid collisions.
This is a last resort; consult with the rest of the dev group before taking this radical step.