Take the OSLC 2012 Community Survey
and encourage your colleagues to do the same, because it is good for
the Open Services for Lifecycle Collaboration community and it is good
Services for Lifecycle Collaboration (OSLC). Have you heard about it before?
Even if you’ve never heard of OSLC before now, you may already be using
software that depends on it.
is both “a community of software developers and organizations that is working
to standardize the way that software lifecycle tools can share data” , and
the set of specifications describing how that data is actually shared. Perhaps
the most famous use of OSLC specifications is the IBM Rational Jazz Platform
, and the associated set of products . These Jazz products use OSLC
specifications to integrate with each other to provide a complete CLM
(Collaborative Lifecycle Management) solution . Since OSLC specifications
are available under the Creative Commons Attribution License , however, it
isn’t just Jazz-based products that are using OSLC to solve the integration
problem. Open source software, such as FusionForge Tracker, Jenkins, and the
Eclipse Lyo project; “traditional” IBM Rational products, such as ClearQuest
and DOORS; IBM Rational competitor products, such as Oracle Team Productivity
Center; and even software from outside the traditional CLM space, such as IBM
Tivoli Service Request Manager; have all implemented OSLC specifications .
Third party solutions have also popped up that provide OSLC adapters that
enable OSLC integrations with software that doesn’t support it natively, such
as HP Quality Center and Atlassian JIRA . Even companies whose main business
isn’t software are choosing OSLC as the standard integration technology for
connecting homegrown and open source tools with the commercial software they
purchase  .
(If you really have never heard of OSLC before now, be sure to check out open-services.net, beginning with the About page, then check out some of the materials from the OSLC Community Webcast Series.)
using software integrated with OSLC and experiencing increased visibility and
simplified traceability across integration boundaries, OSLC is also really
interesting from both technical and business perspectives. From a technical
perspective, the application of Linked Data to application data is a novel idea
with lots of potential. From a business perspective, open specifications offer
hope to all those feeling “locked in” by one vendor or another. More, whether driven
by technical or business concerns, that there is an active specification
development community interested in new integration scenarios is a huge step
forward for the industry.
there is a lot to be gained by participating in OSLC workgroups, to
clarify and prioritize new scenarios, to create and review new
specification revisions, and to implement the initial implementations
that prove the specification is complete . Even if you're just the
end user of what the community produces (either by implementing
specifications to create integrations that matter to you, or by using
integrations developed by others), you can gain a lot from OSLC. But all
of that takes effort on your part (whether you've done it already, or
might do it in the future), and if you're going to put some effort into
OSLC, why not maximize your return?
there is a simple (and painless) way for you to influence the OSLC
Community so that future returns are maximized: the OSLC 2012 Community Survey!
The survey can be completed in less than 5 minutes (though if you have
participated in an OSLC workgroup, implemented an OSLC specification, or
used software integrated by OSLC, please take an extra minute, or two,
to complete those optional sections as well). The survey is also
feedback is so important to OSLC, and the effort to provide it is so
minimal, why not encourage your colleagues to take the survey too? Use #OSLCSurvey to discuss on Twitter, and join the OSLC Group on LinkedIn.