There is a lot of potential for dev transparency when using the druid cloud platform. Individual stakeholders could subscribe to specific notifications. For example, project manager might be interested in the progress of a specific issue. They could maybe subscribe to issue changes/comments, commits related, data changes?, etc. On the other hand a director might be interested only in closed issues, blocked issues, dev deployments, prod deployments, prod build failures, dev build failures, etc. Customers are another group that might be interested in specific types of progress towards an end goal. The concept would really be to foster an ecosystem that favors, promotes transparency and collaboration from everyone dev to stakeholder.
Another idea is subscribing to updates on specific objects inside a repo. Even the idea of guarding promotion of objects to prod with a review process. This would come into play perhaps with panel page changes. Where changes to pages on a site need to be reviewed before promoted.
The distributed repo model per site has potential to really foster this nicely.
site (dev & prod)
site-objects (dev)
rules for specific objects - matches
this could also be used for notifications in the app level for subscribing to matches like real estate ads matching criteria.
There is a lot of potential for dev transparency when using the druid cloud platform. Individual stakeholders could subscribe to specific notifications. For example, project manager might be interested in the progress of a specific issue. They could maybe subscribe to issue changes/comments, commits related, data changes?, etc. On the other hand a director might be interested only in closed issues, blocked issues, dev deployments, prod deployments, prod build failures, dev build failures, etc. Customers are another group that might be interested in specific types of progress towards an end goal. The concept would really be to foster an ecosystem that favors, promotes transparency and collaboration from everyone dev to stakeholder.
Another idea is subscribing to updates on specific objects inside a repo. Even the idea of guarding promotion of objects to prod with a review process. This would come into play perhaps with panel page changes. Where changes to pages on a site need to be reviewed before promoted.
The distributed repo model per site has potential to really foster this nicely.