Note:2: Difference between revisions
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
This note includes questions about the current state of installing extensions. | This note includes questions about the current state of installing extensions. | ||
* | * Auxiliary files (e.g. composer.json, Gruntfile.js, package.json, CODE_OF_CONDUCT.md) are getting added to extensions. | ||
** Are they documented anywhere? (https://www.mediawiki.org/wiki/Continuous_integration/Entry_points) | |||
** Is there a way to generate them automatically? | |||
** Who is responsible for adding them/keeping them up-to-date? (extension maintainer? somebody else?) | |||
** How are they kept up-to-date? | |||
** Is there redundancy? | |||
* When an extension has a composer.json file, should it be added to composer.local.json? | * When an extension has a composer.json file, should it be added to composer.local.json? | ||
Revision as of 16:23, 2 September 2017
| Author | |
|---|---|
| Created | 2 September 2017 21:08:02 |
| Last Modified | 4 September 2017 16:30:44 |
| Tags | Extensions |
This note includes questions about the current state of installing extensions.
- Auxiliary files (e.g. composer.json, Gruntfile.js, package.json, CODE_OF_CONDUCT.md) are getting added to extensions.
- Are they documented anywhere? (https://www.mediawiki.org/wiki/Continuous_integration/Entry_points)
- Is there a way to generate them automatically?
- Who is responsible for adding them/keeping them up-to-date? (extension maintainer? somebody else?)
- How are they kept up-to-date?
- Is there redundancy?
- When an extension has a composer.json file, should it be added to composer.local.json?
- Doing so for some of the "Semantic" extensions causes issues.
- Doing some is required for some extensions.
- What about other extensions?