On 4/18/07, haleh mahbod <[EMAIL PROTECTED]> wrote:
These are done now:
> 1) Using SDO Java could move to 'user guide' on this page.
+1
2) Code structure can move to get involved or even to the architecture doc
+1 to moving to "get involved"
On 4/17/07, kelvin goodson <[EMAIL PROTECTED]> wrote:
>
> I replied to this thread on the tuscany-user list
>
> On 12/04/07, haleh mahbod < [EMAIL PROTECTED]> wrote:
> >
> > Kelvin,
> > Thanks for your review. You mentioned that scopes should be the same
> when
> > on a given page.
> > I agree. I fixed it. We now have a sdo cpp FAQ and a sdo Java FAQ.
I
> > also moved text from some of the mentioned threads to the FAQ. The
ones
> I
> > did not is because I did not know how to net it down to a question and
> an
> > answer.
> >
> > You mentioned General heading can be called Tuscany or SDO General
> > heading. The General heading is more a collection of things that I
> couldn't
> > find a good title for on that page :) It is not intended to be general
> for
> > Tuscany.
> >
> > Some suggestion for the SDO Java page:
> >
> > 1) Using SDO Java could move to 'user guide' on this page.
> > 2) Code structure can move to get involved or even to the architecture
> doc
> >
> > If there is agreement, I go ahead and make the changes.
> > Haleh
> >
> >
> > On 4/12/07, kelvin goodson <[EMAIL PROTECTED]> wrote:
> > >
> > > Haleh,
> > >
> > > thanks for addressing these issues. One concern I have after a
> quick
> > > look
> > > is that on arriving at a pages such as
> > > http://cwiki.apache.org/TUSCANY/sdo-java.html some of the links on
the
> > > left
> > > under a given heading go off to a scope that is not intuitive from
the
> > > page
> > > that you were on. E.g. under the "General" sidebar heading, the
FAQ
> > > link
> > > for Java SDO goes to a page that I think is intended to contain
> generic
> > > cross language SDO questions, i.e. up one level of abstraction from
> the
> > > page
> > > heading. It's been that way since version 3 of the file, and I
can't
> > > work
> > > out whether it's intended that way, or just a result of copying the
> > > content
> > > from an existing C++ page.
> > >
> > > The next sidebar heading below FAQ --- "Downloads" --- relates to
> > > downloading SDO Java ( i.e. at the same level of abstraction of the
> > > current
> > > page). I think it would be good if the sidebar headings grouped
links
> > > at
> > > the same level of abstraction and made this clear from the heading
> name
> > > -
> > > e.g. "Tuscany General", or "SDO General"
> > >
> > >
> > > BTW, FWIW, this prompted me to just catalogue the set of
tuscany-dev
> > > notes
> > > that I have put an "FAQ" label against when reading the list. I had
> the
> > > intention of reviewing this list to see what was worth refining into
> > > well
> > > formed info snippets some time, but haven't got to it yet. Maybe
we
> > > can
> > > divide and conquer to add to the website's FAQ set. Does anyone
else
> > > have
> > > anything like this?
> > >
> > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg00469.html
> > > http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg13291.html
> > > Ron Gavlin's response to tuscany-user of 5th of Jan (cant find a
very
> > > good
> > > archive URL for this one)
> > > My response to Alexander Pankov of the 26th of Jan on t-user
> > > (again URL
> > > not readily found)
> > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg00560.html
> > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg00610.html
> > > The thread started by Adriano Crestani on 15th Feb "mvn problem?"
> > > Unanswered thread from Ignacio on 16th Feb
> > > Frank's responses to Murtaza Goga in the thread started 20th March
> > >
> > >
>
http://mail-archives.apache.org/mod_mbox/ws-tuscany-user/200703.mbox/[EMAIL
PROTECTED]
> > > The thread entitled "Root property that is not containment" started
> 29th
> > > of
> > > Jan
> > > The thread entitled "Getting started with Tuscany databinding"
started
> > > on
> > > 10th April
> > >
> > > Regards, Kelvin.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On 12/04/07, haleh mahbod < [EMAIL PROTECTED]> wrote:
> > > >
> > > > Hi,
> > > >
> > > > As mentioned in [1] I started working on the website and the first
> > > phase
> > > > is
> > > > ready for review.
> > > >
> > > > My first attempt ended up with something other than what I had
> > > originally
> > > > planned; which was to move content. Instead, I worked on the
> > > readability
> > > > of
> > > > the website.
> > > > I have tried to use a consistent look and feel across the
pages to
> > > make
> > > > it
> > > > easier to find information. In addition, I tried to make
> > > the information
> > > > available progressively ( allowing the user to decide if they want
> to
> > > > learn
> > > > more).
> > > >
> > > > Here is the layout at a high level for the Tuscany Website (
> > > > http://cwiki.apache.org/TUSCANY/)
> > > >
> > > > - Home page - On this page you will find the general stuff that
> > > apply
> > > > to the whole Tuscany as well as links to each subproject and
> > > Downloads.
> > > > - Each subproject has an overview page, for example SCA
overview
> > > or
> > > > DAS overview. On the overview page you find a brief
introduction
> to
> > > the
> > > > subproject and links to resources which are introductory
> > > information on
> > > > the
> > > > subproject, for example white papers, articles, webinar links
if
> > > any.
> > > > - Each subproject also has a more detailed page for those who
> want
> > > to
> > > > get more info about that particular subproject. For example,
SCA
> > > Java,
> > > > SDO
> > > > C++, DAS RDB or DAS LDAP.
> > > > - Each detailed subproject page's navigation bar looks the same
> and
> > >
> > > > provides more detailed information on the project. For example,
> > > FAQ,
> > > > Documentation, How to get involved, Downloads, etc.
> > > > - I tried to keep each page's navigation information to the
> minimum
> > >
> > > > information that is needed for that stage in order to make it
> > > easier to
> > > > find
> > > > information.
> > > >
> > > > I'd like your feedback on this phase before we go ahead and put
all
> > > the
> > > > content in place.
> > > > - Is the navigation intuitive?
> > > > - Do we need additional information?
> > > >
> > > > If everyone is happy with the look and feel, let's try to keep
the
> > > > consistency across the pages as we add content.
> > > >
> > > > For the next step, I am trying to capture content from the old
> > > website,
> > > > the
> > > > old wiki and mailing threads.
> > > > Please review the content on the overview pages (already
there) and
> > > > correct
> > > > it if needed.
> > > > There is a lot to be done and any help or feedback is very
welcomed
> :)
> > > >
> > > > Thanks,
> > > > Haleh
> > > >
> > > > [1] -
> > > >
> > > >
> > >
>
http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200704.mbox/[EMAIL
PROTECTED]
> > > >
> > >
> >
> >
>
Hi
I'm starting to like the shape of it. Some comments. Apologies now if I
stray into content comments. I know at the moment we are commenting on the
shape of it but I'll note what I see as I go through. Also I've fixed small
things as I've looked at them and noted things here that people may disagree
with.
- General Comments
- Need diagrams - we had some nice ones from sebastien and from the old
site that we can use in various places
- Home
- Move the page round to make the first thing the statement about what it
does rather than about incubation.
- Have a a breaking new section on the bottom of the first page to report
the last 3 or so significant events, i.e. provide links directly to the
latest releases.
- News and Events
- Appears in General and Community
- Separate "upcoming events and news" into events and news
- SCA
- Java SCA
- Java SCA Subproject? Why subproject in the title of this page.
- I like the list of modules I think we should go with the module name
from the code and link to a separate
page for each one. (take a look I've made an example). We can then use
URLs such as
http://cwiki.apache.org/confluence/display/TUSCANY/binding-ws to refer
directly to the module description(*)
- Downloads
- centre alignment looks strange
- Architecture Guide
- still pointing to the old one
- JavaDoc
- shouldn;t be under the guides section
- DeveloperGuide
- I still think there should be a developer guide as it fits well under
the guide section. So how about
Guides
User Guide
Architecture Guide
Developer Guide
Resources
Source code
Java Doc
- SDO
- SDO Java
- has an issue management section under development
- DAS
- seems to be in a slighlty different format. We have Java and C++
implementations underway so we could follow the patter of SCA and SDO.
(*) - I took a look at how we can refer back to the website from the poms.
We could include the URL of a modules web page in the <url/> tag of each
module pom. This url is used during site generation by maven. I'm not
suggesting we do maven site generation now (I saw someone previously doing
this for some modules and the issue was how to integrate with confluence). I
think for the time being it will be easier/quicker/more inclusive to collect
module information on the wiki.
If we want, in the future, to generate a maven site, for example, if we want
to ship it with a release, then the information on the wiki provides a good
homepage for each module and hence the <url/> in the pom provides that link.
My concern is for visioning on the wiki. I guess we can either generate
released focused spaces or export the relevant pages to HTML and check into
svn when we cut a release.
Regards
Simon
