Re: The Jakarta Site Was: [Discussion] (Fake)Forrest for Jakarta!

2003-01-30 Thread dion
Henri Yandell [EMAIL PROTECTED] wrote on 31/01/2003 02:28:59 PM:

[snip]
 However, a consistent skin might actually be the best way to get a
 consistently labelled and functional site together.
 
 Now I get to disagree with Dion :) His list of important things, the 
ones
 Maven produce, are by and large not important. The important things are
 the ones the user cares about:
They're important to me as a developer. As a user, yeah it's a different 
list.

How about we give these items some names:

 1) Where do I download?
Downloads
 2) Has their been a release?
Release Notes
 3) Where are the tutorials/documentation?
Documentation
 4) How do I complain about a bug?
Bugs
 5) Where do I ask a question?
Mailing Lists

 and then more minor questions like:
 
 6) So who is behind Project X?
Team Members
 7) What Apache community does Project X belong to?
What's an Apache community? Do you mean 'top-level project'?

[snippage]
 Those who can't do, complain. But I'm happy to be a member of both sets. 
I
 believe the first step is to actually try to cross-manage the site. Tbh, 
I
What's cross-management?

 Once a site-wide contract for labelling and minimum functionality is
 ironed out, each particular look and feel, project and generational tool
 are free to enhance it as much as they want, as long as they:
 
 eg) Provide a link called 'Download nightly build'  or whatever.
Cool.

Let's take a stab at it then.

--
dIon Gillard, Multitask Consulting
Blog:  http://www.freeroller.net/page/dion/Weblog
Work:  http://www.multitask.com.au



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: The Jakarta Site Was: [Discussion] (Fake)Forrest for Jakarta!

2003-01-30 Thread Henri Yandell


On Fri, 31 Jan 2003 [EMAIL PROTECTED] wrote:

 Henri Yandell [EMAIL PROTECTED] wrote on 31/01/2003 02:28:59 PM:

 How about we give these items some names:

Sounds good.

  1) Where do I download?
 Downloads
  2) Has their been a release?
 Release Notes

Possibly this should be 'Status' as projects may not have had a release.
I'm thinking that this section is more:

Status: We are working on version 3.0. It's aimed to contain blah blah,
world peace, profitable websites and no arguments.

  3) Where are the tutorials/documentation?
 Documentation
  4) How do I complain about a bug?
 Bugs
  5) Where do I ask a question?
 Mailing Lists

  and then more minor questions like:
 
  6) So who is behind Project X?
 Team Members
  7) What Apache community does Project X belong to?
 What's an Apache community? Do you mean 'top-level project'?

Nope. Like, Jakarta should point to the Apache front page somewhere, Ant
should too. BSF should point to Jakarta.

ie) Apache projects are a hierarchy. If the idea of a project being in
multiple communities occurs, then it would list these.


 [snippage]
  Those who can't do, complain. But I'm happy to be a member of both sets.
 I
  believe the first step is to actually try to cross-manage the site. Tbh,
 I
 What's cross-management?

Management's obviously a bad word, but I'm thinking of some form of
structure that Apache sites have to fit into. Like saying that every
subsite has to show the Apache logo etc. Basically trying to create a
site-contract that sub-projects agree to, hopefully helping to make the
site more usable to users without forcing anything too painful on
projects.

  Once a site-wide contract for labelling and minimum functionality is
  ironed out, each particular look and feel, project and generational tool
  are free to enhance it as much as they want, as long as they:
 
  eg) Provide a link called 'Download nightly build'  or whatever.
 Cool.

 Let's take a stab at it then.

Okay. I'd like to start a document, I guess Wiki would be a good choice
for this, and evolve the document. Wiki, Mailing list, jakarta-site2 cvs?

Hen


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




RE: The Jakarta Site Was: [Discussion] (Fake)Forrest for Jakarta!

2003-01-30 Thread Christoph Wilhelms
Hi!

Sorry! Just picking one point, but :)!

   7) What Apache community does Project X belong to?
  What's an Apache community? Do you mean 'top-level project'?
 
 Nope. Like, Jakarta should point to the Apache front page 
 somewhere, Ant
 should too. BSF should point to Jakarta.

Agrreed 100% - and this is what the forrest skin does in the header line
(http://ant.apache.org, http://xml.apache.org/forrest) Of course this
feature is part of FakeForrest :)

 ie) Apache projects are a hierarchy. If the idea of a project being in
 multiple communities occurs, then it would list these.

If you mean Ant for example: As you might have missed, Ant was promoted from
a Jakarta to a toplevel Apache project, so the link on Jakarta is just there
to redirekt to the correct page, because hundreds for websites, programs,
manuals etc. point to the jakarta website talking about Ant! Probably the
link can be removed from project.xml but the redirecting page has to remain
:)!

Additionally:
I think it's pretty important to know how old some information is. For this
reason (Fake)Forrest generates the deploy/generation date in the footer
row...

Just my 2 cents :)

Cheers,
Chris

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




RE: The Jakarta Site Was: [Discussion] (Fake)Forrest for Jakarta!

2003-01-30 Thread Henri Yandell


On Fri, 31 Jan 2003, Christoph Wilhelms wrote:

 Sorry! Just picking one point, but :)!

Slice it all apart, one point at a time :)

7) What Apache community does Project X belong to?
   What's an Apache community? Do you mean 'top-level project'?
 
  Nope. Like, Jakarta should point to the Apache front page
  somewhere, Ant
  should too. BSF should point to Jakarta.

 Agrreed 100% - and this is what the forrest skin does in the header line
 (http://ant.apache.org, http://xml.apache.org/forrest) Of course this
 feature is part of FakeForrest :)

Good. Hopefully all technologies used to fuel the sites will be able to do
the same. :)

  ie) Apache projects are a hierarchy. If the idea of a project being in
  multiple communities occurs, then it would list these.

 If you mean Ant for example: As you might have missed, Ant was promoted from
 a Jakarta to a toplevel Apache project, so the link on Jakarta is just there
 to redirekt to the correct page, because hundreds for websites, programs,
 manuals etc. point to the jakarta website talking about Ant! Probably the
 link can be removed from project.xml but the redirecting page has to remain
 :)!

Not necessarily. Even though Ant, James etc have left Jakarta, ASF
discussions a while back [started off by Brian Behlendorf's email on
having categories/communities] suggest that Ant and James may still belong
to the Jakarta community, as well as being top-level projects. I think
this entire concept is still quite in the air.

 Additionally:
 I think it's pretty important to know how old some information is. For this
 reason (Fake)Forrest generates the deploy/generation date in the footer
 row...

Ah, definitely good. I'll add it to the 'contract'. Am writing up a first
one now.

Hen


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]