---
# System prepended metadata

title: Making Collection development easier

---

# Making Collection development easier



## Objective

## Make it easier to move content out of community.(general,network)
(Also applies to promoting content from Community to Support)

  * Document process better
  * Include moving history (i.e, https://gist.github.com/dmsimard/283578ae9ff03b45cc8625e4c639acf4)
  * ACTION: Review existing doc, what's missing
    * Remove moving from ansible/ansible 


## Make it easier to setup branch new collections


## Migrating role into a Collection

* Can we improve `ansible-galaxy collection init`
  * How does this relate to [collection_template](https://github.com/ansible-collections/collection_template)
  * Can we use something like [Cookiecutter](https://github.com/ansible-collections/overview/issues/122)
  * Basic `assert True` type of tests for units & integration so that all of the `ansible-test` subcommands work / pass from the beginning


## Make Collection Owners lives easier

* Lets talk to different collection owners
* Which
  * Maybe people not on IRC, so we get different views
* How
  * Video call, needs lots of discussion
  * Not surveys
  * Maybe small(ish) groups
  * Aims and objectives need to be framed well so people can come prepared with ideas and problems

## General

* When use FQCNs be used
  * Docs
  * Inventory Plugins
* DOCS: Deprecation vs tombstone vs redirect
* PROCESS: When to `git rm`
* Actively reduce the number of steps

## Improving testing Collections

* `Makefile`
    * Do we want want `make install
    * Do we want `make test` target in each collection?
        * Validation (and meaningful guidance) of directory name
        * run ansible-test sanity/units/integration
        * Link to online docs
        * Possibly have individual make targets for sanity,unit,test,lint, molecule 
* GitHub Action to be extended to include:
  * Same set of checks as Galaxy Import
* Make it easier to write integration tests
* Default Molecule ?
* Should we make the ansible-test Action something in GitHub Market Place
  * Variables:
    * Ansible versions
    * Python Versions
    * Run units: Y/N
    * Run integration tests: Y/N


# ACTIONS
* Review all PRs from recent content migrations
  * For every review comment, and question think: How can we improve docs to make this clearer


* ACTION: Copy collection_moving doc into hackmd and iterate on it
* Can we use something like Cookiecuter
* 

## Questions

- Can collections specify their own action group?
  - Is a PR to `module_common.py` the right way?
  - Can the collection specify any arbitrary action group via the `runtime.yml` or something similar?
- What are the criterias or the policy for including a collection into the ansible community package/tarball ?
