Skip to content
This repository was archived by the owner on Sep 3, 2020. It is now read-only.
This repository was archived by the owner on Sep 3, 2020. It is now read-only.

Gooey should be able to enable release management for a module #13

@Cervator

Description

@Cervator

When a module is born it starts unreleased and without belonging to any kind of grouping (unless we want to keep a name for "limbo" modules). When ready it should be possible to automatically enable release management via chat:

"Gooey: enable release management for x by y"

  • Creates a "role" on IRC/Slack (really in the back-end brain the bot uses) for x and adds y to it - Have Gooey manage a role/team approach on IRC/Slack for allowing further access to commands #5
    • If triggered on IRC the user needs to be registered first so they can have voice added (to avoid nick impersonation)
  • Possibly adds the module to a named grouping of some sort (could be what triggers other stuff)
  • Triggers the publishing of the module to the meta server, launcher, and automated summary docs
  • Possibly triggers the creation of a release job for the module in Jenkins (or whatever other process we go for)
  • Possibly adds the user to associated jobs in Jenkins to run releases that way (directly execute releases in Jenkins instead of asking Gooey)
  • Possibly adds/moves the job in Jenkins to a different view

After this point the target user should count as privileged to run official release management tasks and run other commands for that module in chat (and maybe via Jenkins)

Outstanding:

  • At this point should a user be added to the Contributors team under MovingBlocks and/or be added to the credits somewhere?
  • At this point should a forum thread be associated with the module? Either a dedicated thread or a "parent" thread (for small modules covered by larger modules to begin with)

Related:

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/36715684-gooey-should-be-able-to-enable-release-management-for-a-module?utm_campaign=plugin&utm_content=tracker%2F983091&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F983091&utm_medium=issues&utm_source=github).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions