by doug
on August 19, 2008
Just thinking out loud here…
- What’s it really take for a community to start and evolve?
- Who must participate?
- Who shouldn’t participate?
- Who should facilitate?
- How does the “What’s in it for me” get addressed?
- Is this really what a community serves? Free support, free tools, utilities, open access to information?
- If this is true, can “real” relationships ever be realized?
- How transparent should the community be?
- Does transparency/openness help/hinder participation?
- Should everyone be able to see who’s participating, where they work, their background and motives?
- Should companies incent/encourage/mandate participation by their SMEs and practitioners?
- How should they?
- Who has the best community and what makes it so good?
- What’s an example of a bad community?
Thoughts?
by doug
on August 19, 2008
** Edited at request of IBM Development **
Check out this OPAL whitepaper from one of our ATG folks for our TSRM – Netcool/OMNIbus integration.
As an alternative to this approach, if you own Netcool/Impact you can look at this OPAL paper which uses WebServices.
by delicious
on August 19, 2008
Links that I have found interesting for August 18th:
- EMC on IT Infrastructure Library (ITIL) – Join Glenn O’Donnell, EMC principal product marketing manager, as he offers some practical, well-informed guidance on achieving a successful IT Infrastructure Library (ITIL) implementation. ITIL has become enormously popular as a definition of best practices for IT operations, due to the increased need for operational discipline in IT. Find out how your organization can benefit from ITIL.
- Jitterbit – Jitterbit creates open source integration software that aims to overcome the challenges of cost and complexity associated with connecting applications, data and systems.
Jitterbit’s open source integration solution is a graphical platform for connecting legacy, enterprise and On-Demand applications, including Business Process Fusion, ETL, SaaS, and SOA.
The Jitterbit Open Source Integration Platform also makes use of sharable integration templates called Jitterpaks that allow the community to reuse common integrations with the most popular web services, application APIs, and databases.
