Put DKAN on drupal.org

[janette]

• Goals:
  • Mirror code from github project (this one) to the drupal.org DKAN project gitlab repo.
  • Allow users to see available updates from Drupal updates module.
  • Higher visibility from more Drupal users.
  • Benefit from d.o maintainer tools such as download stats.
  • Benefit from d.o security team work.
  • In the future, leverage Drupal autoupdates project.
• MVP (Phase 1):
  • Continue work as we do: Issues, PRs on github, nothing on d.o except releases.
  • Github action to mirror main branches from github to d.o.
  • Tasks:
    • Add CONTRIBUTING.md file.
    • Add license checker tooling to CI (Maybe https://github.com/dominikb/composer-license-checker ?)
    • Create github action to mirror github repo to d.o gitlab.
      • This should happen on push/merge to main branch (2.x at this time)
      • Should change the name in composer.json on push.
      • Example? https://git.drupalcode.org/project/drupalpod/-/blob/main/.github/workflows/mirror.yml?ref_type=heads
    • Update README.md
    • Determine release process for DKAN.
      • Strategy 1: Github releases are transformed into d.o releases somehow.
      • Strategy 2: Use D.O release API to create releases as github actions.
      • Strategy 3: Use D.O to make releases without any special scripting.
  • Notes:
    • D.O Project module docs: https://www.drupal.org/node/114618
    • How do release nodes get packaged into downloadable files? https://www.drupal.org/node/289662
• Phase 2:
  • All the things for D.O security policy approval. Add to this list.
    • Requirements for security policy approval https://www.drupal.org/node/1011698
    • phpcs --standard=Drupal,DrupalPractice
    • Probably consolidate external libraries as much as possible.
    • Might require shifting to DrupalCI.
      • Determine subset of tests that can/should/must be run on DrupalCI.
  • Mark getdkan/dkan as deprecated in favor of drupal/dkan.
  • Determine desirability/feasibility of turning past releases into d.o-based releases.
  • Determine desirability/feasibility of allowing d.o issues in addition to/replacing github issues.
    • Might be required for d.o security coverage.
    • Would require mirroring d.o issue branches to github, for CI.
    • Probably not practical at this phase.
  • Tasks:
    • TBD