... | ... | @@ -243,17 +243,28 @@ NB: there is a node using the alias /blog and it's breaking the blog view. We sh |
|
|
|
|
|
# Extension directory
|
|
|
|
|
|
Review:
|
|
|
Drupal7 setup to port to Drupal8:
|
|
|
|
|
|
* [ ] Extension node
|
|
|
* [ ] Extension release
|
|
|
* [ ] Extension views
|
|
|
* [ ] Jenkins job that runs a drush script: https://test.civicrm.org/view/All/job/Extdir%20Scan%20(civicrm.org)/
|
|
|
* [ ] Relies on a Drush command (`sudo -u aegir -H drush @civicrm.org extdir-scan`)
|
|
|
* [ ] Stats
|
|
|
* [ ] Stats extraction (for stats.c.o)
|
|
|
* [ ] JSON feeds for the in-app extension browser / Symfony app
|
|
|
* [ ] Views for generating the data used by the Symfony app
|
|
|
|
|
|
Things to consider:
|
|
|
|
|
|
* The most important bit is the drush script that Jenkins run.
|
|
|
* There is a fair amount of code for allowing manual creation of releases, and we could probably disable that option (only allow it for admins, for now, without validation, since it's rarely used and clunky).
|
|
|
* Porting the views that produces the json feeds should be fairly straight forward. They had not been very much customized?
|
|
|
|
|
|
In mid-2020, as we shift our focus on Comex:
|
|
|
|
|
|
* Comex would generate the feed required for Composer
|
|
|
* Comex could feed itself off c.o, or it could feed itself from a repo with json files. Adding an extension would require doing a merge-request on the repo to add the json file.
|
|
|
* If it helps, adding an extension node on c.o might auto-create the Gitlab project under /extensions. It would ensure that the namespace is reserved there too, and avoid dependency on ext-wg leads for creating those repos.
|
|
|
|
|
|
# Time tracking
|
|
|
|
... | ... | |