Hi,
1) Would [1] be a better format & content for each download page of than
what we have today [2]?
If yes, I'll start upgrading the pages.
2) We currently use the same page to record download info for technologies.
For example, SCA Native and Java download pages are the same.
It would be cle
My understanding is that you moved the release name and date from the
"download section" to the "download table". If they are always same
for a group of downloads, won't it take space from the page by
repeating it on each table row ?
Also, do we want to keep all past releases available on the ma
haleh mahbod wrote:
Hi,
1) Would [1] be a better format & content for each download page of
than
what we have today [2]?
If yes, I'll start upgrading the pages.
2) We currently use the same page to record download info for
technologies.
For example, SCA Native and Java download pages are
I agree it would be good to not duplicate things for each downloadable
artifact associated with a release. Not sure it really needs the day of the
release or the assembly spec info either.
And +1 to having old release downloads on a separate page. I'm not sure if
this is the proposal but could th
The idea of a single download page sounds good, but if we are thinking
about tracking page visitors to correlate to the number of downloads,
we won't be able to identify if the person is visiting the page to
download SCA, SDO or DAS.
On 5/29/07, ant elder <[EMAIL PROTECTED]> wrote:
I agree it wo
Tracking page visitors is a bit meaningless due to things like caching isn't
it? While the incubator downloads aren't being mirrored we could just count
those though (but I think they may be about to start mirroring them)
...ant
On 5/29/07, Luciano Resende <[EMAIL PROTECTED]> wrote:
The idea
On 5/29/07, ant elder <[EMAIL PROTECTED]> wrote:
Tracking page visitors is a bit meaningless due to things like caching isn't
it?
Well, if the tracking is done via a js embedded on the page, cache
won't affect it, will it ?
While the incubator downloads aren't being mirrored we could just coun
I am including tuscany-users to get their opinion if interested.
Here are my thoughts influenced by your comments :)
- Separate the download information for latest release from the old
releases.
- Having the text of the change file/read me on the front page of the
download page is good. This mak
Hi
What we are attempting to do now it really far better than cluttering all
the downloads together on one page. Here is what I think about this
- for every Release (SCA / SDO / DAS) have a separate page whose first
section talks about what comprises of that release (including spec levels
etc.)
There doesn't seem to been much distance between the last two suggestions.
It feels to me like people are starting to talk about the same structure.
Let me try and summarize...
Home
Downloads
SCA Java ---> SCA Java Releases
SCA Native -> SCA Native Releases
SDO Java --> SDO Ja
Ok, I've added a new download page for the SCA Java 0.90 release which
hopefully isn't to far away from whats been talked about:
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
Its not linked to from anywhere yet as I'm not sure after all this
discussion where to put
HI Ant,
This looks in line with what I am imagining. I have linked up this page to
a SCA Releases page
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Releases. The SCA
Releases pages is futher linked to a Menu Item called 'SCA Releases' under
the Tuscany SCA menu box.
On the SCA Releas
I made the following updates:
Tuscany Download page, 'SCA Java' is linked to [1]
on [1], Other release DOWNLOAD is linked to the old Java SCA Download page
(old releases)
To do:
[1] could be renamed to SCA Java Latest Release. This page could always hold
info about the latest release.
[2] could b
I've changed the home page to include a box highlighting the latest
releases. Let me know if it seems ok
- Venkat
On 5/31/07, haleh mahbod <[EMAIL PROTECTED]> wrote:
I made the following updates:
Tuscany Download page, 'SCA Java' is linked to [1]
on [1], Other release DOWNLOAD is linked to th
Why it shows in [1] and not in [2] ?
[1] http://cwiki.apache.org/TUSCANY/home.html
[2] http://cwiki.apache.org/TUSCANY/
On 5/31/07, Venkata Krishnan <[EMAIL PROTECTED]> wrote:
I've changed the home page to include a box highlighting the latest
releases. Let me know if it seems ok
- Venkat
O
I'll run a manual autoexport to fix it.
You should see the changes in about 2 mins
Cheers!
Hernan
Luciano Resende wrote:
Why it shows in [1] and not in [2] ?
[1] http://cwiki.apache.org/TUSCANY/home.html
[2] http://cwiki.apache.org/TUSCANY/
On 5/31/07, Venkata Krishnan <[EMAIL PROTECTED]> wr
Done!
Cheers!
Hernan
Hernan Cunico wrote:
I'll run a manual autoexport to fix it.
You should see the changes in about 2 mins
Cheers!
Hernan
Luciano Resende wrote:
Why it shows in [1] and not in [2] ?
[1] http://cwiki.apache.org/TUSCANY/home.html
[2] http://cwiki.apache.org/TUSCANY/
On 5/3
Hi Venkat,
It looks like we posted a response to Ant's message at the same time and
missed each other's email and my changes show up on the site. Is the flow of
information OK?
Basically the old releases page linked to from the .90 page would be the
page that you have suggested.
Haleh
On 5/31/0
Hi Haleh, yes it seems so :). Let me look up and then post back.. thanks.
- Venkat
On 6/1/07, haleh mahbod <[EMAIL PROTECTED]> wrote:
Hi Venkat,
It looks like we posted a response to Ant's message at the same time and
missed each other's email and my changes show up on the site. Is the flow
19 matches
Mail list logo
