[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cross-project-issues-dev] Reorg of the callisto site
- From: "Richard Gronback" <Richard.Gronback@xxxxxxxxxxx>
- Date: Fri, 17 Mar 2006 12:11:39 -0800
- Delivered-to: email@example.com
- Thread-index: AcZJ5PMGFDabqXHvTCy5Cs1zB5oqHgAGHfvw
- Thread-topic: [cross-project-issues-dev] Reorg of the callisto site
I believe David started out in this direction, right?
Perhaps we can just maintain 2 site manifests and give users the option to view
by project or by functional category?
Regarding this organization, I like it and would recommend
some slight changes:
1. Data Tools Project includes "Project" while others are
functional categories, so why not "Database Development
2. Why not lump EMF, GMF, XSD, SDO, and JEM into a
"Modeling Tools" category?
3. Remove (CDT) from C/C++ Development
4. This leaves just GEF in the 'Bits and pieces'
category... not sure where else it might go.
Today, the content of the callisto site reflects the
organization of the projects at the foundation. This is fine for all of us who
are familiar with the ecosystem, but probably meaningless to "new comers".
Moreover it makes things like EMF, GEF, etc. prominent whereas they should be
hidden from the user since they are mainly infrastructural pieces. Based on that
I created a more function oriented site.xml that is attached to this email. The
pro of this proposal is that it makes the site clearer for end users, but the
con is that it makes callisto looks more like a product and less like a
What do you