Skip to content

Rescope cookiecutter

No due date 87% complete

An ever growing user-base across a wider range of projects and skill-sets that cannot be centrally accomodated necessitates rescoping of the cookiecutter.

  • It should have a leaner core that is:

    • Easier to maintain
    • Easier for users to understand and extend to their own ends
    • Relies on fewer dependencies
    • Less prone to breakages, e.g. due to it's dependencie…

An ever growing user-base across a wider range of projects and skill-sets that cannot be centrally accomodated necessitates rescoping of the cookiecutter.

  • It should have a leaner core that is:

    • Easier to maintain
    • Easier for users to understand and extend to their own ends
    • Relies on fewer dependencies
    • Less prone to breakages, e.g. due to it's dependencies (which are user-managed and we cannot pin) making breaking changes
  • It should provide scripts/instructions - "recipes" - to setup functionality that is either:

    • Not suitable in every situation
    • Not generically configurable for every situation
    • Too complex to be a Cookiecutter default
    • We do not have a good standard approach for yet
  • Documentation should be split into

    1. Requirements - you MUST do this
    2. Recommendations - you are highly encouraged to do this
Loading