Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 391103

Summary: Getting started with CDO is a frustrating experience
Product: [Modeling] EMF Reporter: Aaron Digulla <digulla>
Component: cdo.docsAssignee: Project Inbox <emf.cdo-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: stepper
Version: 4.1   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Aaron Digulla CLA 2012-10-04 05:39:50 EDT 
Follow me on a short trip while I tried to get started with CDO.

First, I went to http://wiki.eclipse.org/CDO (Google suggestion for "eclipse cdo").

Nice overview. Then the page suggested to go to http://www.eclipse.org/cdo which I did. How do I get started? Documentation (http://www.eclipse.org/cdo/documentation) ... nope. Just some longer overview. Dead end. What now?

Okay, back to the Wiki page. Documentation ... poster ... architecture ... configuration ... presentations ... webinar ... nothing useful ... ah, tutorials.

No, I don't want to prepare EMF models, user interfaces is a long way off, performance will be an issue in a few months but not now ... nothing.

Maybe the internal Eclipse help is better. But which features should I install? ... one hour later ...

Programmer's Guide sounds good - I just hope this isn't for people developing the framework. Okay, "Developing Client Applications". Architecture ... view providers ... no tutorial either.

That's the point when most people give up. Is there a working "How to get started with CDO" tutorial somewhere? As I said in another bug report, http://wiki.eclipse.org/Getting_started_with_CDO_Helios is outdated. Right now, I'm not sure it's worth to spend more time on it.

Conclusion: I can understand that there are many important things to do in a project but a decent, working tutorial how to get started should be one of the topmost priorities (unless your goal is to keep people away from your project) and not something which "the community" should provide.
Comment 1 Eike Stepper CLA 2012-10-04 05:56:23 EDT 
(In reply to comment #0)
> [...] I can understand that there are many important things to do in a
> project but a decent, working tutorial how to get started should be one of
> the topmost priorities (unless your goal is to keep people away from your
> project) and not something which "the community" should provide.

It would be good to have a version-controlled Getting Started tutorial. And many more tutorials and documents. But unless someone's paying me for writing all the documents it's simply not among my top priorities. Especially given that the community has already provided a bunch of tutorials, which you've found in the wiki. Of course I'd also accept patches for the shipped documentation and review it carefully and maintain it later. Interestingly the community doesn't seem to be more keen on writing docs.

*** This bug has been marked as a duplicate of bug 297142 ***