MLPro Extension Hub

[detlefarend]

Description/Motivation
MLPro extensions are separate 3rd party GitHub repos that provide additional functionalities around/on top of MLPro. They can be created by everyone but please in a standardized way. A new Section Extensions or Marketeplace on RTD could list all public repos forked from this repo...

Task list

• 1. New template repository

  • New repo fhswf/MLPro-Extension as template (for the moment: private)
  • Template files
    • Readme.md
      • Various badges, in particular for download statistics (see also: Download statistics #494)
    • Issue templates
    • Python module
    • Python howto file
  • Default folder structure
  • PyPI deployment action
  • Anaconda deployment action

• 2. Cyclic detection of new repositories
  Github workflows can be triggered by schedules. This can be used to start a special workflow to determine new repositories

  • New subfolder "marketplace"
  • New file "whitelist" within (manual maintenance in branch main)
  • New file "blacklist" within (manual maintenance in branch main)
  • Templates for issue body/comment, owner and repo descriptions
  • Python module 'update_marketplace.py
    • Detect all extensions with topic "mlpro-extension"
    • If the repo is neither whitelisted nor blacklisted, an issue labelled "pending-extension" is to be created.
    • If the repo is blacklisted, it is to be removed from RTD
    • If the repo is whitelisted, it is to be added/updated to RTD
  • Workflow "Marketplace Update"

• 3. RTD MLPro: New section "Extension Hub"

  • Explanations/Tutorials for own extensions
  • Submenu for extensions, separated by organizations and single users, grouped by owners

Cross References
https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows
https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#schedule
https://github.com/orgs/community/discussions/26672