This repository has been archived by the owner on Mar 24, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
Vision
Liam Morley edited this page Nov 14, 2015
·
1 revision
Pulse should be maintainable, scalable, and simple. These goals are often complimentary to one another.
- Developers elsewhere within Pivotal Labs should be able to pick up a story with minimal communication
- Someone from outside Pivotal should be able to contribute (clear documentation, good structure, not intimidating)
The client and server should be relatively isolated from one another both physically and contractually. A developer outside of the team or organization should be able to fork the repository and modify one of these to their own needs in isolation of the other.
It should be relatively easy and straightforward to add additional CI environments.
Consider how Pulse will be adopted into an organization. It may have to integrate with external SSO.
This is something that we as Pivots use every day; it needs to be easy for an anchor to set this up quickly.
- ...for a system administrator installing and setting it up
- ...for a project anchor managing a project over time