Skip to content

Latest commit

 

History

History
37 lines (29 loc) · 2.44 KB

TODOS.md

File metadata and controls

37 lines (29 loc) · 2.44 KB
Raw

TODOS

This file contains outstanding tasks that someone on the project team must complete. As items are accomplished, they can be removed from this file.

(This is a good place to record information about long-term technical debt.)

  • Project Codebase Ownership: The project team owns all the code in this repo. Assign a team member to perform the following:

    • Read all the generated documentation.
      • README.md, CONTRIBUTING.md, docs/*
    • Be familiar with the configuration for Grunt, Docker, Outrigger, Drupal, and Drush
      • Gruntconfig.json
      • docker-compose.yml, docker-compose.override.yml, build.yml, build.devcloud.yml, and jenkins.yml
      • .outrigger.yml
      • src/sites/settings.common.php
      • env/build/etc/drush/drushrc.php
    • Note all the utility scripts in ./bin
    • Ensure everyone on the team understands what they need to know.

  • Test the Site Setup: Confirm the build and site installation works.

    • Install and start Outrigger.
    • Run docker-compose pull && docker-compose -f build.yml pull to ensure you have the latest Docker images for local development.
    • Run rig project setup to confirm the code works and setup your project.
    • Move any code generated in src/sites/default/settings.php after the include of src/sites/settings.common.php into the latter file.
    • If git can add a file, please add it to the code repository. Your src/sites/default/settings.php file should be committed.

  • Adapt the Code to the Project: This is only a starting place.

    • Modify scripts to suite your needs, or remove scripts you will not use and maintain as it will simply be clutter.
    • Rewrite codebase documentation to suite the audience. Make sure future onboarding will work.

  • Engage with the Community

    • Report on any changes made to get the environment working, improve documentation, or automate development processes.
    • Phase2 staff should join the #devtools-support flow to get help. Ask for one-on-one time for troubleshooting or additional coaching.
    • Tweet @outrigger_sh with the big ideas.
    • Collaborate in issue queues such as Outrigger Drupal, Outrigger Docs, [Rig CLI]((https://github.com/phase2/rig), and others.