Open Services for Lifecycle Collaboration (OSLC) is a community of software developers, operations experts, and organizations that are working to standardize the way that software lifecycle tools can share data with one another.
From requirements to upgrades, from defects to patches, from planning to testing, from sprints to deployments, there is a stunning variety of applications from many vendors that support the phases of developing, deploying, and monitoring software. We want to make it easy and practical to integrate those tools.
We want software that easily integrates with other software, which will help you build your ideal development and operations environment, connect disjointed workflows, minimize frustration, and save time and money.
Development and operations tools should be able to work freely with similar products. With standardized methods to represent, access, and link to resources, you won't have to suffer with a legion of fragile, point-to-point integrations.
Software should be able to share and use linked data. When your tools can freely understand each others’ lifecycle data, you can better analyze, track, and explore that data to make better decisions.
We bring together experts from a variety of industries to form workgroups around common issues in software development and operations such as change management or performance monitoring.
Workgroup members explore and agree on the minimum amount of information and scenarios that are necessary to support the most common tasks and interactions.
We want OSLC to spread, so our specifications are freely available for anyone to adopt; our contributors even agree to not assert patents on any implementations.
We write just enough specification to address our scenarios. We do not address uncommon use cases, nor do we create specifications for their own sake.
Our specifications are based on Internet and linked-data standards. We use RESTful services, and any resource must be accessible to multiple tools via a URL.
Our specifications are not complete until we have a working implementation and a test suite. This makes sure our specifications are useful, achievable, and supportable.
Although we try to work fast and deliver a specification in a relatively short time, later versions of a specification can address more scenarios and issues.