-
Notifications
You must be signed in to change notification settings - Fork 97
docs: officially disband Dev Team Enablement #781
Conversation
TEAM_STRUCTURES.md
Outdated
- Set the guidelines for writing, maintaining and managing codebases, test suites, and contributions. | ||
- Define process and help achieve high quality sustainable open source modules. | ||
- Automating tasks for things such as: release cycle, ensuring code quality, activity reports. | ||
- Automate tasks for things such as: release cycle, ensuring code quality, activity reports. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about wording this:
Configure automation for defined development policies like release cycles and code quality reporting
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated 👍
TEAM_STRUCTURES.md
Outdated
|
||
**Responsibilities include**: | ||
- Enable developers to develop faster by reducing friction from dev. | ||
- Upgrade and build dev tools (i.e AEgir and gx). | ||
- Create a sound testing infrastructure for all the IPFS projects. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sounds like "we will run testing infrastructure" when I think our responsibility is more around Enable dev teams to run reliable, efficient tests and manage continuous deployment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated 👍
This PR follows conversations with the multiple stakeholders, including the Infra Team.