You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Jonathan Robie <jo...@redhat.com> on 2010/06/08 14:13:24 UTC
Prototype web site - now with most of the content
Here's the current version of the new web site:
http://ci.apache.org/projects/qpid/
Does this seem basically right? What needs to happen before we make this
live?
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Prototype web site - now with most of the content
Posted by Jonathan Robie <jo...@redhat.com>.
On Tue, 2010-06-08 at 08:38 -0400, Rajith Attapattu wrote:
> First of all good job Jonathan !
>
> I would like to see the following before we push our website into the live site.
>
> 1. Under documentation could we have the following right at the top.
>
> . Work-in-progress (or something that conveys the same meaning) -
> point to an upload of the current docs in trunk
Given the resources we have, I think we should promise to create
consistent docs for 0.7, and apologize for the hodge-podge we currently
have without promising to fix it.
Is that about right?
> 2. Wiki - this link should point to the wiki proper instead of the old
> confluence export. However I don't know what the URL for that :)
Yup.
But going forward, I think we should set a date for one final export,
point to it as archives, and point to that. I think we should pretty
much retire the Wiki.
Going forward, perhaps we should move to this approach?
* Design documentation is checked in with the source code, and kept up
to date for the current version
* Proposals, etc. are submitted in JIRAs or on the mailing list
* Documentation lives in DocBook.
* API docs are generated for a given version
* Other website content is created in vanilla HTML and wrapped using the
Python script
If we agree on something like this, we should document it on the web
site.
> 3. Also once we remove the old website, you might have to tweak the
> links in the new site, to point to the proper location in the wiki.
Yeah.
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Prototype web site - now with most of the content
Posted by Rajith Attapattu <ra...@gmail.com>.
First of all good job Jonathan !
I would like to see the following before we push our website into the live site.
1. Under documentation could we have the following right at the top.
. Work-in-progress (or something that conveys the same meaning) -
point to an upload of the current docs in trunk
2. Wiki - this link should point to the wiki proper instead of the old
confluence export. However I don't know what the URL for that :)
3. Also once we remove the old website, you might have to tweak the
links in the new site, to point to the proper location in the wiki.
Regards,
Rajith
On Tue, Jun 8, 2010 at 8:13 AM, Jonathan Robie
<jo...@redhat.com> wrote:
> Here's the current version of the new web site:
>
> http://ci.apache.org/projects/qpid/
>
> Does this seem basically right? What needs to happen before we make this
> live?
>
> Jonathan
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Prototype web site - now with most of the content
Posted by Jonathan Robie <jo...@redhat.com>.
On Tue, 2010-06-08 at 08:37 -0400, Alan Conway wrote:
> On 06/08/2010 08:13 AM, Jonathan Robie wrote:
> > Here's the current version of the new web site:
> >
> > http://ci.apache.org/projects/qpid/
> >
> > Does this seem basically right? What needs to happen before we make this
> > live?
> >
>
> Looks very nice.
>
> The getting started page has a link to the FAQ which links to the old cwiki.
> The FAQ (and pages it links to) needs to move to the new site, but I don't think
> that needs to hold up putting this live as long as the links to the old pages
> remain valid till they've been moved.
I'm inclined to move the old Wiki into a subdirectory and point to it,
but not reflect further updates. The FAQ is a bit problematic because it
pulls in pretty much everything, including things that belong to various
versions that we no longer support, and it's not terribly well
organized. I think we should probably create a new FAQ with current
content, well organized, that contains mostly the responses to questions
that are actually frequently asked. Perhaps we can start by identifying
the FAQ entries that we want, and create a new FAQ using them.
I also left out the road map, which currently goes up to M4. We need to
create a new road map. I'll start a new thread on that ...
There's other material that still needs to be converted - "Getting
Involved" especially, it needs some reorganization at the same time, in
my opinion. I'd like to move to the new site quickly, and move these
things incrementally, reorganizing as we go.
IMHO, the next big steps for me are to (1) work on the "getting
involved" section, (2) get version numbers and stable link names into
generated docs, (3) write a script to generate the entire site,
including calls to epydoc and doxygen, docbook builds, and the wrapper
(about half of this was done by hand this time around), and (4) dump
material we've been planning to contribute into the C++ broker docs,
concentrating on the 0.6 portion. I'd like to go forward, not backwards.
The Java Broker docs need some massaging from the Java Broker team, I
think.
In Qpid 0.5, the C++ API docs didn't build for me cleanly using Doxygen.
Those are the issues I'm aware of ....
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Prototype web site - now with most of the content
Posted by Alan Conway <ac...@redhat.com>.
On 06/08/2010 08:13 AM, Jonathan Robie wrote:
> Here's the current version of the new web site:
>
> http://ci.apache.org/projects/qpid/
>
> Does this seem basically right? What needs to happen before we make this
> live?
>
Looks very nice.
The getting started page has a link to the FAQ which links to the old cwiki.
The FAQ (and pages it links to) needs to move to the new site, but I don't think
that needs to hold up putting this live as long as the links to the old pages
remain valid till they've been moved.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: Results: VOTE: Take the web prototype live?
Posted by Steve Huston <sh...@riverace.com>.
Great - thanks!
> -----Original Message-----
> From: Jonathan Robie [mailto:jonathan.robie@redhat.com]
> Sent: Wednesday, June 16, 2010 2:38 PM
> To: dev@qpid.apache.org
> Subject: Results: VOTE: Take the web prototype live?
>
>
> I count 8 votes in favor, none against - I'm going to take
> this live in
> the next day or so.
>
> Jonathan
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Results: VOTE: Take the web prototype live?
Posted by Jonathan Robie <jo...@redhat.com>.
I count 8 votes in favor, none against - I'm going to take this live in
the next day or so.
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: VOTE: Take the web prototype live?
Posted by Jonathan Robie <jo...@redhat.com>.
So far, all votes have been positive.
On another thread, though, Marnie expressed some concern. I notice she
has not actually voted.
Marnie - can I declare the vote closed, or do you still need to weigh in?
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: VOTE: Take the web prototype live?
Posted by Alan Conway <ac...@redhat.com>.
On 06/10/2010 10:55 AM, Jonathan Robie wrote:
> On Tue, 2010-06-08 at 14:27 +0100, Robbie Gemmell wrote:
>
>> Overall looks good, I echo Gordon's thoughts, lets get this live ASAP
>> and improve as we go rather than spending too much time polishing it
>> beforehand: anythings better than what we have now and everything is
>> still reachable as long as we link to the wiki.
>
> I propose to fix things that I can fix quickly (based on the thread from
> the last few days) and make this site live:
>
> http://ci.apache.org/projects/qpid/
>
> This feels like a significant enough step that a vote seems appropriate.
> Support, anyone?
>
+1
Great job.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: VOTE: Take the web prototype live?
Posted by Gordon Sim <gs...@redhat.com>.
On 06/10/2010 03:55 PM, Jonathan Robie wrote:
> On Tue, 2010-06-08 at 14:27 +0100, Robbie Gemmell wrote:
>
>> Overall looks good, I echo Gordon's thoughts, lets get this live ASAP
>> and improve as we go rather than spending too much time polishing it
>> beforehand: anythings better than what we have now and everything is
>> still reachable as long as we link to the wiki.
>
> I propose to fix things that I can fix quickly (based on the thread from
> the last few days) and make this site live:
>
> http://ci.apache.org/projects/qpid/
>
> This feels like a significant enough step that a vote seems appropriate.
> Support, anyone?
+1
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: VOTE: Take the web prototype live?
Posted by Robbie Gemmell <ro...@gmail.com>.
72hrs seems ample time, so let's call it <checks original email> 67.5hrs
from now. :p
I am happy to be railroaded however, it's been over 6 months since the
original prototype and the current site has been somewhat busted for over a
month. I don't think a single negative thing has been said other than around
subjective colour choices, so....anyone who hasn't voiced their concerns by
now, has 67.5hrs to do so... :)
Robbie
> -----Original Message-----
> From: Steve Huston [mailto:shuston@riverace.com]
> Sent: 10 June 2010 20:12
> To: dev@qpid.apache.org
> Subject: RE: VOTE: Take the web prototype live?
>
> Hi Jonathan,
>
> > How long should we let this vote run? I'm hearing people
> > suggest we get this up as quickly as possible, but I also
> > don't want to railroad this decision.
>
> The vote should run 72 hours:
> http://apache.org/foundation/voting.html
>
> -Steve
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: VOTE: Take the web prototype live?
Posted by Steve Huston <sh...@riverace.com>.
Hi Jonathan,
> How long should we let this vote run? I'm hearing people
> suggest we get this up as quickly as possible, but I also
> don't want to railroad this decision.
The vote should run 72 hours:
http://apache.org/foundation/voting.html
-Steve
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: VOTE: Take the web prototype live?
Posted by Jonathan Robie <jo...@redhat.com>.
How long should we let this vote run? I'm hearing people suggest we get
this up as quickly as possible, but I also don't want to railroad this
decision.
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: VOTE: Take the web prototype live?
Posted by Jonathan Robie <jo...@redhat.com>.
On Thu, 2010-06-10 at 16:22 +0100, Robbie Gemmell wrote:
>
> (PS, im assuming you just havent prodded infra to update the
> ci.apache.org version manually and that the current version in our
> repo will be what gets made live? I still seem to be getting the old
> version using ids instead of classes....assuming of course it isnt
> just my friendly local proxy server refusing to show me the latest
> code hehe.)
Yeah. I've prodded a little, but it's not set up yet.
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: VOTE: Take the web prototype live?
Posted by Robbie Gemmell <ro...@gmail.com>.
+1
(PS, im assuming you just havent prodded infra to update the
ci.apache.org version manually and that the current version in our
repo will be what gets made live? I still seem to be getting the old
version using ids instead of classes....assuming of course it isnt
just my friendly local proxy server refusing to show me the latest
code hehe.)
On 10 June 2010 15:55, Jonathan Robie <jo...@redhat.com> wrote:
> On Tue, 2010-06-08 at 14:27 +0100, Robbie Gemmell wrote:
>
>> Overall looks good, I echo Gordon's thoughts, lets get this live ASAP
>> and improve as we go rather than spending too much time polishing it
>> beforehand: anythings better than what we have now and everything is
>> still reachable as long as we link to the wiki.
>
> I propose to fix things that I can fix quickly (based on the thread from
> the last few days) and make this site live:
>
> http://ci.apache.org/projects/qpid/
>
> This feels like a significant enough step that a vote seems appropriate.
> Support, anyone?
>
> Jonathan
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: VOTE: Take the web prototype live?
Posted by Rajith Attapattu <ra...@gmail.com>.
On Thu, Jun 10, 2010 at 11:12 AM, Robert Godfrey
<ro...@gmail.com> wrote:
> On 10 June 2010 16:55, Jonathan Robie <jo...@redhat.com> wrote:
>> On Tue, 2010-06-08 at 14:27 +0100, Robbie Gemmell wrote:
>>
>>> Overall looks good, I echo Gordon's thoughts, lets get this live ASAP
>>> and improve as we go rather than spending too much time polishing it
>>> beforehand: anythings better than what we have now and everything is
>>> still reachable as long as we link to the wiki.
>>
>> I propose to fix things that I can fix quickly (based on the thread from
>> the last few days) and make this site live:
>>
>> http://ci.apache.org/projects/qpid/
>>
>> This feels like a significant enough step that a vote seems appropriate.
>> Support, anyone?
>>
>> Jonathan
>>
>
> Is this supposed to be an official vote thread, or just asking if we
> should have a vote? :-)
>
> I'm +1 on both counts anyway
+1 - lets get this live.
> -- Rob
>
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: VOTE: Take the web prototype live?
Posted by Robert Godfrey <ro...@gmail.com>.
On 10 June 2010 16:55, Jonathan Robie <jo...@redhat.com> wrote:
> On Tue, 2010-06-08 at 14:27 +0100, Robbie Gemmell wrote:
>
>> Overall looks good, I echo Gordon's thoughts, lets get this live ASAP
>> and improve as we go rather than spending too much time polishing it
>> beforehand: anythings better than what we have now and everything is
>> still reachable as long as we link to the wiki.
>
> I propose to fix things that I can fix quickly (based on the thread from
> the last few days) and make this site live:
>
> http://ci.apache.org/projects/qpid/
>
> This feels like a significant enough step that a vote seems appropriate.
> Support, anyone?
>
> Jonathan
>
Is this supposed to be an official vote thread, or just asking if we
should have a vote? :-)
I'm +1 on both counts anyway
-- Rob
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: VOTE: Take the web prototype live?
Posted by Ken Giusti <kg...@redhat.com>.
Big improvement! Nice work.
+1
-K
----- "Sorin S." <ss...@gmail.com> wrote:
> Hi,
> To me, it looks much better than what we have, so:
> +1
>
> Cheers,
> Sorin
>
>
> On Thu, Jun 10, 2010 at 3:55 PM, Jonathan Robie
> <jo...@redhat.com> wrote:
> > On Tue, 2010-06-08 at 14:27 +0100, Robbie Gemmell wrote:
> >
> >> Overall looks good, I echo Gordon's thoughts, lets get this live
> ASAP
> >> and improve as we go rather than spending too much time polishing
> it
> >> beforehand: anythings better than what we have now and everything
> is
> >> still reachable as long as we link to the wiki.
> >
> > I propose to fix things that I can fix quickly (based on the thread
> from
> > the last few days) and make this site live:
> >
> > http://ci.apache.org/projects/qpid/
> >
> > This feels like a significant enough step that a vote seems
> appropriate.
> > Support, anyone?
> >
> > Jonathan
> >
> >
> >
> ---------------------------------------------------------------------
> > Apache Qpid - AMQP Messaging Implementation
> > Project: http://qpid.apache.org
> > Use/Interact: mailto:dev-subscribe@qpid.apache.org
> >
> >
>
>
>
> --
> Sorin S
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: VOTE: Take the web prototype live?
Posted by "Sorin S." <ss...@gmail.com>.
Hi,
To me, it looks much better than what we have, so:
+1
Cheers,
Sorin
On Thu, Jun 10, 2010 at 3:55 PM, Jonathan Robie
<jo...@redhat.com> wrote:
> On Tue, 2010-06-08 at 14:27 +0100, Robbie Gemmell wrote:
>
>> Overall looks good, I echo Gordon's thoughts, lets get this live ASAP
>> and improve as we go rather than spending too much time polishing it
>> beforehand: anythings better than what we have now and everything is
>> still reachable as long as we link to the wiki.
>
> I propose to fix things that I can fix quickly (based on the thread from
> the last few days) and make this site live:
>
> http://ci.apache.org/projects/qpid/
>
> This feels like a significant enough step that a vote seems appropriate.
> Support, anyone?
>
> Jonathan
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
--
Sorin S
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: VOTE: Take the web prototype live?
Posted by Steve Huston <sh...@riverace.com>.
+1
-Steve
> -----Original Message-----
> From: Jonathan Robie [mailto:jonathan.robie@redhat.com]
> Sent: Thursday, June 10, 2010 10:56 AM
> To: dev@qpid.apache.org
> Subject: VOTE: Take the web prototype live?
>
>
> On Tue, 2010-06-08 at 14:27 +0100, Robbie Gemmell wrote:
>
> > Overall looks good, I echo Gordon's thoughts, lets get this
> live ASAP
> > and improve as we go rather than spending too much time polishing it
> > beforehand: anythings better than what we have now and
> everything is
> > still reachable as long as we link to the wiki.
>
> I propose to fix things that I can fix quickly (based on the
> thread from the last few days) and make this site live:
>
> http://ci.apache.org/projects/qpid/
>
> This feels like a significant enough step that a vote seems
> appropriate. Support, anyone?
>
> Jonathan
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
VOTE: Take the web prototype live?
Posted by Jonathan Robie <jo...@redhat.com>.
On Tue, 2010-06-08 at 14:27 +0100, Robbie Gemmell wrote:
> Overall looks good, I echo Gordon's thoughts, lets get this live ASAP
> and improve as we go rather than spending too much time polishing it
> beforehand: anythings better than what we have now and everything is
> still reachable as long as we link to the wiki.
I propose to fix things that I can fix quickly (based on the thread from
the last few days) and make this site live:
http://ci.apache.org/projects/qpid/
This feels like a significant enough step that a vote seems appropriate.
Support, anyone?
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Prototype web site - now with most of the content
Posted by Robbie Gemmell <ro...@gmail.com>.
Now checked and fixed for IE6 too.
Robbie
On 25 June 2010 13:38, Jonathan Robie <jo...@redhat.com> wrote:
> Thanks or the IE fix!
>
> Jonathan
>
> On 06/24/2010 06:59 PM, Robbie Gemmell wrote:
>>
>> Forgot about this, I just took a look at it now.
>>
>> The feature_box div was wider than its parent and the older IE's don't
>> seem
>> to like that. I reduced its size locally, and once it fits in the parent
>> it
>> doesn't drop down the page to sit below the menu, so I've just committed
>> that change to the repo.
>>
>> Robbie
>>
>>> -----Original Message-----
>>> From: Robbie Gemmell [mailto:robbie.gemmell@gmail.com]
>>> Sent: 08 June 2010 14:28
>>> To: dev@qpid.apache.org
>>> Subject: Re: Prototype web site - now with most of the content
>>>
>>
>> <snip>
>>>
>>> One minor nit, the bullet pointed feature box things on the front page
>>> dont display in the right place in IE6 and IE7 (or 8 in compatibility
>>> mode), the entire containing div drops down the page to where the menu
>>> stops. I imagine its just a margin/padding+float CSS bug, ill try to
>>> take a look tonight if I get a chance, they are still around 1/3rd of
>>> all used browsers afterall..now, back to Firefox ;)
>>>
>>> Robbie
>>
>> </snip>
>>
>>
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Prototype web site - now with most of the content
Posted by Jonathan Robie <jo...@redhat.com>.
Thanks or the IE fix!
Jonathan
On 06/24/2010 06:59 PM, Robbie Gemmell wrote:
> Forgot about this, I just took a look at it now.
>
> The feature_box div was wider than its parent and the older IE's don't seem
> to like that. I reduced its size locally, and once it fits in the parent it
> doesn't drop down the page to sit below the menu, so I've just committed
> that change to the repo.
>
> Robbie
>
>> -----Original Message-----
>> From: Robbie Gemmell [mailto:robbie.gemmell@gmail.com]
>> Sent: 08 June 2010 14:28
>> To: dev@qpid.apache.org
>> Subject: Re: Prototype web site - now with most of the content
>>
>
> <snip>
>>
>> One minor nit, the bullet pointed feature box things on the front page
>> dont display in the right place in IE6 and IE7 (or 8 in compatibility
>> mode), the entire containing div drops down the page to where the menu
>> stops. I imagine its just a margin/padding+float CSS bug, ill try to
>> take a look tonight if I get a chance, they are still around 1/3rd of
>> all used browsers afterall..now, back to Firefox ;)
>>
>> Robbie
> </snip>
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: Prototype web site - now with most of the content
Posted by Robbie Gemmell <ro...@gmail.com>.
Forgot about this, I just took a look at it now.
The feature_box div was wider than its parent and the older IE's don't seem
to like that. I reduced its size locally, and once it fits in the parent it
doesn't drop down the page to sit below the menu, so I've just committed
that change to the repo.
Robbie
> -----Original Message-----
> From: Robbie Gemmell [mailto:robbie.gemmell@gmail.com]
> Sent: 08 June 2010 14:28
> To: dev@qpid.apache.org
> Subject: Re: Prototype web site - now with most of the content
>
<snip>
>
> One minor nit, the bullet pointed feature box things on the front page
> dont display in the right place in IE6 and IE7 (or 8 in compatibility
> mode), the entire containing div drops down the page to where the menu
> stops. I imagine its just a margin/padding+float CSS bug, ill try to
> take a look tonight if I get a chance, they are still around 1/3rd of
> all used browsers afterall..now, back to Firefox ;)
>
> Robbie
</snip>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Documentation for Java Broker Implementation
Posted by Rajith Attapattu <ra...@gmail.com>.
On Fri, Jun 11, 2010 at 11:31 AM, Marnie McCormack
<ma...@googlemail.com> wrote:
> Jonathan,
>
> Points 1, 2 & 3 - yes I agree.
>
> There are lots of people on this dev list who could opt in to help on the
> docs for the Java side. I know why I don't have time - because the 0-10
> broker is taking #1 priority and represents a substantial investment in
> Qpid.
Myself and Joanthan have taken care of the Java client to a certain extent.
I am planning to add a few more docs there.
Sadly I don't have enough knowledge on the Java broker side to review
all the docs, but I will help where I can.
> I'm not the 'plan' person for Qpid - I share what I'm doing/what I know is
> going on. So I guess if there's not enough community input on the doc
> migration thats a separate issue. I don't have time right now, but maybe
> other people do ?
> I don't really follow why you want to move the wiki URL - that would be
> quite inconvenient for the links we use. I don't object to moving to the new
> website, but I'd like to keep a reference to any docs that have not been
> taken over.
The current qpid.apache.org points to the old wiki.
The community has voted to move to a new website which will occupy that URL.
There will be a link from that website called "Wiki" which will point
to the old wiki proper.
Also from the documentation page we could point to the old java wiki
docs in addition to the pdf/html versions.
However I think it's good if all components use svn docs when we do
the next release.
The goal is to release html/pdf docs along with the bits.
Hopefully the Java broker docs will be in a reasonable shape by then.
> Marnie
>
> On Fri, Jun 11, 2010 at 3:09 PM, Jonathan Robie
> <jo...@redhat.com>wrote:
>
>> On Fri, 2010-06-11 at 08:56 +0100, Marnie McCormack wrote:
>> > Hi Jonathan,
>> >
>> > I'm not asking for updates on the wiki, but for it to stay up and linked
>> to
>> > until the docs have been converted from it/moved over.
>>
>> I think we agree that:
>>
>> 1. The Wiki needs to be kept available for archival purposes
>> 2. It needs to be possible to link into the pages of the Wiki archives
>> 3. We will not update the archives
>>
>> I think you're asking that we keep the archives precisely where they
>> are, and not use qpid.apache.org for the new web site until the Java
>> broker docs have been converted. I'd like to give the archived Wiki a
>> URL that let's us reference it from the main qpid.apache.org pages, e.g.
>>
>> qpid.apache.org/wiki/archives
>>
>> I did an initial conversion of the Java broker docs months ago and have
>> been asking for feedback and help. So far, no dice. Those converted docs
>> are available on the new site, I'd be glad to point to the Wiki archives
>> for the Java broker instead if you prefer.
>>
>> > The 0-10 broker implementation is the main priority for now and requiring
>> > much effort, the docs will need to wait a while until thats in good
>> shape.
>> > Realistically, a few weeks more work on the broker I think.
>> > I understand you want the java team to work on this - there are other
>> Java
>> > devs on this list who might have time to do this though ?
>> >
>> > From a time point of view, I'm not objecting to your plans just asking
>> for
>> > the wiki to stay put a while.
>>
>> Reading that, I don't hear any plan to have anyone do any work on the
>> Java broker docs in any specified time frame. If nobody has done that in
>> the last six months, what's going to change to make them do that now?
>>
>> The material in the Java broker docs I posted came directly from the
>> Wiki, I tried to organize it a little. Ideally, I'd like someone to
>> spend some time fixing that up and make it more usable, I spent time
>> creating a book out of the Wiki documentation for the Java broker
>> because I had hoped it would be helpful, but I'd also be happy to link
>> to the Wiki archives for the Java broker docs instead.
>>
>> Jonathan
>>
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>
>>
>
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Documentation for Java Broker Implementation
Posted by Marnie McCormack <ma...@googlemail.com>.
Jonathan,
Points 1, 2 & 3 - yes I agree.
There are lots of people on this dev list who could opt in to help on the
docs for the Java side. I know why I don't have time - because the 0-10
broker is taking #1 priority and represents a substantial investment in
Qpid.
I'm not the 'plan' person for Qpid - I share what I'm doing/what I know is
going on. So I guess if there's not enough community input on the doc
migration thats a separate issue. I don't have time right now, but maybe
other people do ?
I don't really follow why you want to move the wiki URL - that would be
quite inconvenient for the links we use. I don't object to moving to the new
website, but I'd like to keep a reference to any docs that have not been
taken over.
Marnie
On Fri, Jun 11, 2010 at 3:09 PM, Jonathan Robie
<jo...@redhat.com>wrote:
> On Fri, 2010-06-11 at 08:56 +0100, Marnie McCormack wrote:
> > Hi Jonathan,
> >
> > I'm not asking for updates on the wiki, but for it to stay up and linked
> to
> > until the docs have been converted from it/moved over.
>
> I think we agree that:
>
> 1. The Wiki needs to be kept available for archival purposes
> 2. It needs to be possible to link into the pages of the Wiki archives
> 3. We will not update the archives
>
> I think you're asking that we keep the archives precisely where they
> are, and not use qpid.apache.org for the new web site until the Java
> broker docs have been converted. I'd like to give the archived Wiki a
> URL that let's us reference it from the main qpid.apache.org pages, e.g.
>
> qpid.apache.org/wiki/archives
>
> I did an initial conversion of the Java broker docs months ago and have
> been asking for feedback and help. So far, no dice. Those converted docs
> are available on the new site, I'd be glad to point to the Wiki archives
> for the Java broker instead if you prefer.
>
> > The 0-10 broker implementation is the main priority for now and requiring
> > much effort, the docs will need to wait a while until thats in good
> shape.
> > Realistically, a few weeks more work on the broker I think.
> > I understand you want the java team to work on this - there are other
> Java
> > devs on this list who might have time to do this though ?
> >
> > From a time point of view, I'm not objecting to your plans just asking
> for
> > the wiki to stay put a while.
>
> Reading that, I don't hear any plan to have anyone do any work on the
> Java broker docs in any specified time frame. If nobody has done that in
> the last six months, what's going to change to make them do that now?
>
> The material in the Java broker docs I posted came directly from the
> Wiki, I tried to organize it a little. Ideally, I'd like someone to
> spend some time fixing that up and make it more usable, I spent time
> creating a book out of the Wiki documentation for the Java broker
> because I had hoped it would be helpful, but I'd also be happy to link
> to the Wiki archives for the Java broker docs instead.
>
> Jonathan
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
Re: Documentation for Java Broker Implementation
Posted by Jonathan Robie <jo...@redhat.com>.
On Fri, 2010-06-11 at 08:56 +0100, Marnie McCormack wrote:
> Hi Jonathan,
>
> I'm not asking for updates on the wiki, but for it to stay up and linked to
> until the docs have been converted from it/moved over.
I think we agree that:
1. The Wiki needs to be kept available for archival purposes
2. It needs to be possible to link into the pages of the Wiki archives
3. We will not update the archives
I think you're asking that we keep the archives precisely where they
are, and not use qpid.apache.org for the new web site until the Java
broker docs have been converted. I'd like to give the archived Wiki a
URL that let's us reference it from the main qpid.apache.org pages, e.g.
qpid.apache.org/wiki/archives
I did an initial conversion of the Java broker docs months ago and have
been asking for feedback and help. So far, no dice. Those converted docs
are available on the new site, I'd be glad to point to the Wiki archives
for the Java broker instead if you prefer.
> The 0-10 broker implementation is the main priority for now and requiring
> much effort, the docs will need to wait a while until thats in good shape.
> Realistically, a few weeks more work on the broker I think.
> I understand you want the java team to work on this - there are other Java
> devs on this list who might have time to do this though ?
>
> From a time point of view, I'm not objecting to your plans just asking for
> the wiki to stay put a while.
Reading that, I don't hear any plan to have anyone do any work on the
Java broker docs in any specified time frame. If nobody has done that in
the last six months, what's going to change to make them do that now?
The material in the Java broker docs I posted came directly from the
Wiki, I tried to organize it a little. Ideally, I'd like someone to
spend some time fixing that up and make it more usable, I spent time
creating a book out of the Wiki documentation for the Java broker
because I had hoped it would be helpful, but I'd also be happy to link
to the Wiki archives for the Java broker docs instead.
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Documentation for Java Broker Implementation
Posted by Marnie McCormack <ma...@googlemail.com>.
Hi Jonathan,
I'm not asking for updates on the wiki, but for it to stay up and linked to
until the docs have been converted from it/moved over.
The 0-10 broker implementation is the main priority for now and requiring
much effort, the docs will need to wait a while until thats in good shape.
Realistically, a few weeks more work on the broker I think.
I understand you want the java team to work on this - there are other Java
devs on this list who might have time to do this though ?
>From a time point of view, I'm not objecting to your plans just asking for
the wiki to stay put a while.
For anyone labouring under the misapprehension that docs don't matter to me,
I wrote quite a few of the Java user docs ;-)
Marnie
On Thu, Jun 10, 2010 at 10:37 PM, Jonathan Robie
<jo...@redhat.com>wrote:
> Hi Marnie,
>
> I think we need to have the archives available, but we also need to be
> able to use qpid.apache.org for the main website.
>
> OK if we move the existing wiki to qpid.apache.org/archives?
>
> Also, I converted quite a bit of the Java broker documentation here:
>
>
> http://ci.apache.org/projects/qpid/books/0.6/AMQP-Messaging-Broker-Java-Book/html/index.html
>
> http://ci.apache.org/projects/qpid/books/0.6/AMQP-Messaging-Broker-Java-Book/pdf/AMQP-Messaging-Broker-Java-Book.pdf
>
> The source files for this are in qpid/doc/book, you can make it using
>
> $ make java
>
> Someone really needs to go over that and determine what is really
> needed, what is outdated, etc. The content was taken directly from the
> Wiki. The main cleanup needed is probably:
>
> * Make sure tables, examples, etc. all have titles
> * Fix links (the error messages show you which ones are broken)
> * Apply updates that have been made since the original conversion
>
> I'm happy enough to have a pointer to the Wiki archives as of a given
> date - in fact, the site already has those pointers. I'm not as happy
> about continuing to reflect updates, for several reasons:
>
> 1. I've already done quite a bit of work to get the Java documentation
> mostly converted, and I would really like to see someone from the Java
> broker team take that over and finish it. Nobody has even reviewed this
> in any depth. If this documentation is out of date, it needs to be
> fixed.
>
> 2. If we keep making our updates to the Wiki instead of to the
> documentation, that's building a backlog of work for someone to do
> eventually. I think it would be better to get the existing Java
> documentation up to date and maintain it. That also has the advantage
> that it always corresponds to a specific version of the software.
>
> 3. I think it's confusing for users to have substantially the same
> information in two places, with minor differences depending on what's
> been updated.
>
> 4. I've already said I don't want to do more work to maintain the Wiki,
> which is a little broken, since we're moving to the new system.
>
> If the documentation for the Java Broker isn't the "real" documentation,
> we should probably just yank it from the documentation page and point to
> the Wiki. But I think that would tend to make the Java broker look like
> a second class citizen, especially as we contribute documentation to the
> C++ broker from Red Hat docs.
>
> Would it be realistic for someone from your team review the Java broker
> docs that have already been converted, and start to think about how much
> effort would be required to move to the new system?
>
> Jonathan
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
Documentation for Java Broker Implementation
Posted by Jonathan Robie <jo...@redhat.com>.
Hi Marnie,
I think we need to have the archives available, but we also need to be
able to use qpid.apache.org for the main website.
OK if we move the existing wiki to qpid.apache.org/archives?
Also, I converted quite a bit of the Java broker documentation here:
http://ci.apache.org/projects/qpid/books/0.6/AMQP-Messaging-Broker-Java-Book/html/index.html
http://ci.apache.org/projects/qpid/books/0.6/AMQP-Messaging-Broker-Java-Book/pdf/AMQP-Messaging-Broker-Java-Book.pdf
The source files for this are in qpid/doc/book, you can make it using
$ make java
Someone really needs to go over that and determine what is really
needed, what is outdated, etc. The content was taken directly from the
Wiki. The main cleanup needed is probably:
* Make sure tables, examples, etc. all have titles
* Fix links (the error messages show you which ones are broken)
* Apply updates that have been made since the original conversion
I'm happy enough to have a pointer to the Wiki archives as of a given
date - in fact, the site already has those pointers. I'm not as happy
about continuing to reflect updates, for several reasons:
1. I've already done quite a bit of work to get the Java documentation
mostly converted, and I would really like to see someone from the Java
broker team take that over and finish it. Nobody has even reviewed this
in any depth. If this documentation is out of date, it needs to be
fixed.
2. If we keep making our updates to the Wiki instead of to the
documentation, that's building a backlog of work for someone to do
eventually. I think it would be better to get the existing Java
documentation up to date and maintain it. That also has the advantage
that it always corresponds to a specific version of the software.
3. I think it's confusing for users to have substantially the same
information in two places, with minor differences depending on what's
been updated.
4. I've already said I don't want to do more work to maintain the Wiki,
which is a little broken, since we're moving to the new system.
If the documentation for the Java Broker isn't the "real" documentation,
we should probably just yank it from the documentation page and point to
the Wiki. But I think that would tend to make the Java broker look like
a second class citizen, especially as we contribute documentation to the
C++ broker from Red Hat docs.
Would it be realistic for someone from your team review the Java broker
docs that have already been converted, and start to think about how much
effort would be required to move to the new system?
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Prototype web site - now with most of the content
Posted by Rajith Attapattu <ra...@gmail.com>.
On Thu, Jun 10, 2010 at 4:39 PM, Marnie McCormack
<ma...@googlemail.com> wrote:
> Hi Rajith,
>
> On the wiki - it has been suggested on this thread that the wiki be retired
> and/or updates not reflected on the new website.
The old documentation will not be deleted.
There will be a link from the website to the wiki.
> Most of the java devs are very busy working on the 0-10 broker
> implementation which is a major effort. Does anyone out there have the
> bandwidth to convert/rewrite the Java content on the wiki ?
I think Jonathan has already converted the existing docs in the wiki
into the doc book format.
However if you are adding anything new, please add it to the svn docs.
It's unfair to expect him to continue to sync the svn docs with any
new additions to the wiki.
We as a community took this decision and it requires support from
everybody to ensure we provide good documentation for end users.
> My team have the knowledge, but not the time just now.
> For the .Net, is there a reason why you want to delete the 0-8 code,
> given we still have users ?
But there is nobody apart Aidan who has made any effort to answer any
user queries related to these clients on the user list.
I don't understand why we need to keep the old 0-8, 0-10 .NET clients
on trunk when there is no active development or anybody willing to
champion it ?
I really don't think anybody is interested in maintaining this code.
Many have pointed that they will not be comfortable with releasing
these clients again as they are buggy and unsupported.
> When we have something better I'd think that's
> the right thing, but imho better to keep the code we have out there on trunk
> until we can gracefully retire it.
We already have a better solution in WCF and a .NET binding, all
though they are targeted at 0-10.
With 1.0 coming out I don't think any new users will really care about 0-8.
And we as a community needs to ensure we steer them clear off these
unmaintained and unsupported clients.
> I didn't think it was causing any issues
> where it is ?
There is a serious issue.
Every we do a release we are effectively releasing (via the source
release) unmaintained buggy code that no one is willing to support !
That is an automatic -1 from me come the next release cycle.
Also every time anybody does a checkout we are effectively downloading
dead code.
We shouldn't be keeping unmaintained code in trunk. There has been
several discussions on the list about this already.
Several users have downloaded the old clients from the website and
have run into issues and there is nobody to answer their questions.
That is why I suggested to remove those clients from our download page.
> Regards,
> Marnie
>
> On Thu, Jun 10, 2010 at 5:46 PM, Rajith Attapattu <ra...@gmail.com>wrote:
>
>> On Thu, Jun 10, 2010 at 11:58 AM, Marnie McCormack
>> <ma...@googlemail.com> wrote:
>> > All,
>> >
>> > Sorry to chip in a little late - I've been on vacation.
>> >
>> > So, the wiki should definitely stay ! A lot of the Java docs are linked
>> from
>> > end user stuff I use and I'd be very unhappy to see those docs disappear
>> > (and you really won't like me when I'm angry) including the java FAQs
>> drawn
>> > from support questions etc. I promote all docs I write to Apache and link
>> > from there so the wiki links are in use.
>>
>> Nobody is going to remove anything in the wiki !
>> However any new documentation should be in the svn docs directory.
>> As agreed by the community the docs will be maintained in svn and will
>> be released along with the code.
>> At some point we need to convert the FAQ's into the docbook format as
>> well, since the content could change according to the release.
>> I believe it will ensure the FAQ is current at least for each release.
>>
>> > On the .Net, I have no interest in the 0-10 version but the 0-8 version
>> > should stay (docs, code the lot) as it matters and is in production use,
>> at
>> > least until we have a 0-10 Java broker and an alternative .Net client to
>> > interop with it.
>>
>> In ASF code is never deleted.
>> However I strongly feel we should remove links to the old 0-8 and 0-10
>> .NET clients from the download page.
>> Also we should remove the old .NET client code from the *trunk* as it
>> is dead code that is not going to be maintained.
>> If anybody needs them, we have release tags that corresponds to each
>> release.
>> We could also tag the current trunk version before we remove it from the
>> tree.
>>
>> > Bye for now,
>> > Marnie
>> >
>> > On Wed, Jun 9, 2010 at 5:32 PM, Rajith Attapattu <ra...@gmail.com>
>> wrote:
>> >
>> >> I would also remove the links to the old .NET clients from the download
>> >> page.
>> >> These clients are buggy and unsupported.
>> >> It's best we not provide anything at all, rather then providing
>> >> something that is known to be buggy and unsupported.
>> >>
>> >> This is not to disrespect the individuals who have put a lot of effort
>> >> into these clients, but rather being pragmatic about what we are able
>> >> to do as a community.
>> >> With the WCF client and the new .NET binding (over c++) it is unlikely
>> >> that the old clients will receive any TLC.
>> >> So lets get rid of them from the download pages and the code tree (You
>> >> could always get it from the svn history if needed).
>> >>
>> >> Rajith
>> >>
>> >> On Tue, Jun 8, 2010 at 10:41 AM, Jonathan Robie
>> >> <jo...@redhat.com> wrote:
>> >> > On Tue, 2010-06-08 at 14:27 +0100, Robbie Gemmell wrote:
>> >> >> On the same page, the link to the wiki should point to
>> >> >> http://cwiki.apache.org/confluence/display/qpid
>> >> >>
>> >> >> Overall looks good, I echo Gordon's thoughts, lets get this live ASAP
>> >> >> and improve as we go rather than spending too much time polishing it
>> >> >> beforehand: anythings better than what we have now and everything is
>> >> >> still reachable as long as we link to the wiki.
>> >> >>
>> >> >> One minor nit, the bullet pointed feature box things on the front
>> page
>> >> >> dont display in the right place in IE6 and IE7 (or 8 in compatibility
>> >> >> mode), the entire containing div drops down the page to where the
>> menu
>> >> >> stops. I imagine its just a margin/padding+float CSS bug, ill try to
>> >> >> take a look tonight if I get a chance, they are still around 1/3rd of
>> >> >> all used browsers afterall..now, back to Firefox ;)
>> >> >
>> >> > Nice catch - and there's a CSS validation error for feature_box in
>> >> > the .css stylesheet. I fixed that, I'm asking #asfinfra to refresh
>> (it's
>> >> > not yet set up for me to do that automagically).
>> >> >
>> >> > We'll see if that fixes the problem ...
>> >> >
>> >> > Jonathan
>> >> >
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > Apache Qpid - AMQP Messaging Implementation
>> >> > Project: http://qpid.apache.org
>> >> > Use/Interact: mailto:dev-subscribe@qpid.apache.org
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Regards,
>> >>
>> >> Rajith Attapattu
>> >> Red Hat
>> >> http://rajith.2rlabs.com/
>> >>
>> >> ---------------------------------------------------------------------
>> >> Apache Qpid - AMQP Messaging Implementation
>> >> Project: http://qpid.apache.org
>> >> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> Regards,
>>
>> Rajith Attapattu
>> Red Hat
>> http://rajith.2rlabs.com/
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>
>>
>
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Prototype web site - now with most of the content
Posted by Marnie McCormack <ma...@googlemail.com>.
Hi Rajith,
On the wiki - it has been suggested on this thread that the wiki be retired
and/or updates not reflected on the new website.
Most of the java devs are very busy working on the 0-10 broker
implementation which is a major effort. Does anyone out there have the
bandwidth to convert/rewrite the Java content on the wiki ?
My team have the knowledge, but not the time just now.
For the .Net, is there a reason why you want to delete the 0-8 code,
given we still have users ? When we have something better I'd think that's
the right thing, but imho better to keep the code we have out there on trunk
until we can gracefully retire it. I didn't think it was causing any issues
where it is ?
Regards,
Marnie
On Thu, Jun 10, 2010 at 5:46 PM, Rajith Attapattu <ra...@gmail.com>wrote:
> On Thu, Jun 10, 2010 at 11:58 AM, Marnie McCormack
> <ma...@googlemail.com> wrote:
> > All,
> >
> > Sorry to chip in a little late - I've been on vacation.
> >
> > So, the wiki should definitely stay ! A lot of the Java docs are linked
> from
> > end user stuff I use and I'd be very unhappy to see those docs disappear
> > (and you really won't like me when I'm angry) including the java FAQs
> drawn
> > from support questions etc. I promote all docs I write to Apache and link
> > from there so the wiki links are in use.
>
> Nobody is going to remove anything in the wiki !
> However any new documentation should be in the svn docs directory.
> As agreed by the community the docs will be maintained in svn and will
> be released along with the code.
> At some point we need to convert the FAQ's into the docbook format as
> well, since the content could change according to the release.
> I believe it will ensure the FAQ is current at least for each release.
>
> > On the .Net, I have no interest in the 0-10 version but the 0-8 version
> > should stay (docs, code the lot) as it matters and is in production use,
> at
> > least until we have a 0-10 Java broker and an alternative .Net client to
> > interop with it.
>
> In ASF code is never deleted.
> However I strongly feel we should remove links to the old 0-8 and 0-10
> .NET clients from the download page.
> Also we should remove the old .NET client code from the *trunk* as it
> is dead code that is not going to be maintained.
> If anybody needs them, we have release tags that corresponds to each
> release.
> We could also tag the current trunk version before we remove it from the
> tree.
>
> > Bye for now,
> > Marnie
> >
> > On Wed, Jun 9, 2010 at 5:32 PM, Rajith Attapattu <ra...@gmail.com>
> wrote:
> >
> >> I would also remove the links to the old .NET clients from the download
> >> page.
> >> These clients are buggy and unsupported.
> >> It's best we not provide anything at all, rather then providing
> >> something that is known to be buggy and unsupported.
> >>
> >> This is not to disrespect the individuals who have put a lot of effort
> >> into these clients, but rather being pragmatic about what we are able
> >> to do as a community.
> >> With the WCF client and the new .NET binding (over c++) it is unlikely
> >> that the old clients will receive any TLC.
> >> So lets get rid of them from the download pages and the code tree (You
> >> could always get it from the svn history if needed).
> >>
> >> Rajith
> >>
> >> On Tue, Jun 8, 2010 at 10:41 AM, Jonathan Robie
> >> <jo...@redhat.com> wrote:
> >> > On Tue, 2010-06-08 at 14:27 +0100, Robbie Gemmell wrote:
> >> >> On the same page, the link to the wiki should point to
> >> >> http://cwiki.apache.org/confluence/display/qpid
> >> >>
> >> >> Overall looks good, I echo Gordon's thoughts, lets get this live ASAP
> >> >> and improve as we go rather than spending too much time polishing it
> >> >> beforehand: anythings better than what we have now and everything is
> >> >> still reachable as long as we link to the wiki.
> >> >>
> >> >> One minor nit, the bullet pointed feature box things on the front
> page
> >> >> dont display in the right place in IE6 and IE7 (or 8 in compatibility
> >> >> mode), the entire containing div drops down the page to where the
> menu
> >> >> stops. I imagine its just a margin/padding+float CSS bug, ill try to
> >> >> take a look tonight if I get a chance, they are still around 1/3rd of
> >> >> all used browsers afterall..now, back to Firefox ;)
> >> >
> >> > Nice catch - and there's a CSS validation error for feature_box in
> >> > the .css stylesheet. I fixed that, I'm asking #asfinfra to refresh
> (it's
> >> > not yet set up for me to do that automagically).
> >> >
> >> > We'll see if that fixes the problem ...
> >> >
> >> > Jonathan
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > Apache Qpid - AMQP Messaging Implementation
> >> > Project: http://qpid.apache.org
> >> > Use/Interact: mailto:dev-subscribe@qpid.apache.org
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Regards,
> >>
> >> Rajith Attapattu
> >> Red Hat
> >> http://rajith.2rlabs.com/
> >>
> >> ---------------------------------------------------------------------
> >> Apache Qpid - AMQP Messaging Implementation
> >> Project: http://qpid.apache.org
> >> Use/Interact: mailto:dev-subscribe@qpid.apache.org
> >>
> >>
> >
>
>
>
> --
> Regards,
>
> Rajith Attapattu
> Red Hat
> http://rajith.2rlabs.com/
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
Re: Prototype web site - now with most of the content
Posted by Rajith Attapattu <ra...@gmail.com>.
On Thu, Jun 10, 2010 at 11:58 AM, Marnie McCormack
<ma...@googlemail.com> wrote:
> All,
>
> Sorry to chip in a little late - I've been on vacation.
>
> So, the wiki should definitely stay ! A lot of the Java docs are linked from
> end user stuff I use and I'd be very unhappy to see those docs disappear
> (and you really won't like me when I'm angry) including the java FAQs drawn
> from support questions etc. I promote all docs I write to Apache and link
> from there so the wiki links are in use.
Nobody is going to remove anything in the wiki !
However any new documentation should be in the svn docs directory.
As agreed by the community the docs will be maintained in svn and will
be released along with the code.
At some point we need to convert the FAQ's into the docbook format as
well, since the content could change according to the release.
I believe it will ensure the FAQ is current at least for each release.
> On the .Net, I have no interest in the 0-10 version but the 0-8 version
> should stay (docs, code the lot) as it matters and is in production use, at
> least until we have a 0-10 Java broker and an alternative .Net client to
> interop with it.
In ASF code is never deleted.
However I strongly feel we should remove links to the old 0-8 and 0-10
.NET clients from the download page.
Also we should remove the old .NET client code from the *trunk* as it
is dead code that is not going to be maintained.
If anybody needs them, we have release tags that corresponds to each release.
We could also tag the current trunk version before we remove it from the tree.
> Bye for now,
> Marnie
>
> On Wed, Jun 9, 2010 at 5:32 PM, Rajith Attapattu <ra...@gmail.com> wrote:
>
>> I would also remove the links to the old .NET clients from the download
>> page.
>> These clients are buggy and unsupported.
>> It's best we not provide anything at all, rather then providing
>> something that is known to be buggy and unsupported.
>>
>> This is not to disrespect the individuals who have put a lot of effort
>> into these clients, but rather being pragmatic about what we are able
>> to do as a community.
>> With the WCF client and the new .NET binding (over c++) it is unlikely
>> that the old clients will receive any TLC.
>> So lets get rid of them from the download pages and the code tree (You
>> could always get it from the svn history if needed).
>>
>> Rajith
>>
>> On Tue, Jun 8, 2010 at 10:41 AM, Jonathan Robie
>> <jo...@redhat.com> wrote:
>> > On Tue, 2010-06-08 at 14:27 +0100, Robbie Gemmell wrote:
>> >> On the same page, the link to the wiki should point to
>> >> http://cwiki.apache.org/confluence/display/qpid
>> >>
>> >> Overall looks good, I echo Gordon's thoughts, lets get this live ASAP
>> >> and improve as we go rather than spending too much time polishing it
>> >> beforehand: anythings better than what we have now and everything is
>> >> still reachable as long as we link to the wiki.
>> >>
>> >> One minor nit, the bullet pointed feature box things on the front page
>> >> dont display in the right place in IE6 and IE7 (or 8 in compatibility
>> >> mode), the entire containing div drops down the page to where the menu
>> >> stops. I imagine its just a margin/padding+float CSS bug, ill try to
>> >> take a look tonight if I get a chance, they are still around 1/3rd of
>> >> all used browsers afterall..now, back to Firefox ;)
>> >
>> > Nice catch - and there's a CSS validation error for feature_box in
>> > the .css stylesheet. I fixed that, I'm asking #asfinfra to refresh (it's
>> > not yet set up for me to do that automagically).
>> >
>> > We'll see if that fixes the problem ...
>> >
>> > Jonathan
>> >
>> >
>> > ---------------------------------------------------------------------
>> > Apache Qpid - AMQP Messaging Implementation
>> > Project: http://qpid.apache.org
>> > Use/Interact: mailto:dev-subscribe@qpid.apache.org
>> >
>> >
>>
>>
>>
>> --
>> Regards,
>>
>> Rajith Attapattu
>> Red Hat
>> http://rajith.2rlabs.com/
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>
>>
>
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Prototype web site - now with most of the content
Posted by Marnie McCormack <ma...@googlemail.com>.
All,
Sorry to chip in a little late - I've been on vacation.
So, the wiki should definitely stay ! A lot of the Java docs are linked from
end user stuff I use and I'd be very unhappy to see those docs disappear
(and you really won't like me when I'm angry) including the java FAQs drawn
from support questions etc. I promote all docs I write to Apache and link
from there so the wiki links are in use.
On the .Net, I have no interest in the 0-10 version but the 0-8 version
should stay (docs, code the lot) as it matters and is in production use, at
least until we have a 0-10 Java broker and an alternative .Net client to
interop with it.
Bye for now,
Marnie
On Wed, Jun 9, 2010 at 5:32 PM, Rajith Attapattu <ra...@gmail.com> wrote:
> I would also remove the links to the old .NET clients from the download
> page.
> These clients are buggy and unsupported.
> It's best we not provide anything at all, rather then providing
> something that is known to be buggy and unsupported.
>
> This is not to disrespect the individuals who have put a lot of effort
> into these clients, but rather being pragmatic about what we are able
> to do as a community.
> With the WCF client and the new .NET binding (over c++) it is unlikely
> that the old clients will receive any TLC.
> So lets get rid of them from the download pages and the code tree (You
> could always get it from the svn history if needed).
>
> Rajith
>
> On Tue, Jun 8, 2010 at 10:41 AM, Jonathan Robie
> <jo...@redhat.com> wrote:
> > On Tue, 2010-06-08 at 14:27 +0100, Robbie Gemmell wrote:
> >> On the same page, the link to the wiki should point to
> >> http://cwiki.apache.org/confluence/display/qpid
> >>
> >> Overall looks good, I echo Gordon's thoughts, lets get this live ASAP
> >> and improve as we go rather than spending too much time polishing it
> >> beforehand: anythings better than what we have now and everything is
> >> still reachable as long as we link to the wiki.
> >>
> >> One minor nit, the bullet pointed feature box things on the front page
> >> dont display in the right place in IE6 and IE7 (or 8 in compatibility
> >> mode), the entire containing div drops down the page to where the menu
> >> stops. I imagine its just a margin/padding+float CSS bug, ill try to
> >> take a look tonight if I get a chance, they are still around 1/3rd of
> >> all used browsers afterall..now, back to Firefox ;)
> >
> > Nice catch - and there's a CSS validation error for feature_box in
> > the .css stylesheet. I fixed that, I'm asking #asfinfra to refresh (it's
> > not yet set up for me to do that automagically).
> >
> > We'll see if that fixes the problem ...
> >
> > Jonathan
> >
> >
> > ---------------------------------------------------------------------
> > Apache Qpid - AMQP Messaging Implementation
> > Project: http://qpid.apache.org
> > Use/Interact: mailto:dev-subscribe@qpid.apache.org
> >
> >
>
>
>
> --
> Regards,
>
> Rajith Attapattu
> Red Hat
> http://rajith.2rlabs.com/
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
Re: Prototype web site - now with most of the content
Posted by Rajith Attapattu <ra...@gmail.com>.
I would also remove the links to the old .NET clients from the download page.
These clients are buggy and unsupported.
It's best we not provide anything at all, rather then providing
something that is known to be buggy and unsupported.
This is not to disrespect the individuals who have put a lot of effort
into these clients, but rather being pragmatic about what we are able
to do as a community.
With the WCF client and the new .NET binding (over c++) it is unlikely
that the old clients will receive any TLC.
So lets get rid of them from the download pages and the code tree (You
could always get it from the svn history if needed).
Rajith
On Tue, Jun 8, 2010 at 10:41 AM, Jonathan Robie
<jo...@redhat.com> wrote:
> On Tue, 2010-06-08 at 14:27 +0100, Robbie Gemmell wrote:
>> On the same page, the link to the wiki should point to
>> http://cwiki.apache.org/confluence/display/qpid
>>
>> Overall looks good, I echo Gordon's thoughts, lets get this live ASAP
>> and improve as we go rather than spending too much time polishing it
>> beforehand: anythings better than what we have now and everything is
>> still reachable as long as we link to the wiki.
>>
>> One minor nit, the bullet pointed feature box things on the front page
>> dont display in the right place in IE6 and IE7 (or 8 in compatibility
>> mode), the entire containing div drops down the page to where the menu
>> stops. I imagine its just a margin/padding+float CSS bug, ill try to
>> take a look tonight if I get a chance, they are still around 1/3rd of
>> all used browsers afterall..now, back to Firefox ;)
>
> Nice catch - and there's a CSS validation error for feature_box in
> the .css stylesheet. I fixed that, I'm asking #asfinfra to refresh (it's
> not yet set up for me to do that automagically).
>
> We'll see if that fixes the problem ...
>
> Jonathan
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Prototype web site - now with most of the content
Posted by Jonathan Robie <jo...@redhat.com>.
On Tue, 2010-06-08 at 14:27 +0100, Robbie Gemmell wrote:
> On the same page, the link to the wiki should point to
> http://cwiki.apache.org/confluence/display/qpid
>
> Overall looks good, I echo Gordon's thoughts, lets get this live ASAP
> and improve as we go rather than spending too much time polishing it
> beforehand: anythings better than what we have now and everything is
> still reachable as long as we link to the wiki.
>
> One minor nit, the bullet pointed feature box things on the front page
> dont display in the right place in IE6 and IE7 (or 8 in compatibility
> mode), the entire containing div drops down the page to where the menu
> stops. I imagine its just a margin/padding+float CSS bug, ill try to
> take a look tonight if I get a chance, they are still around 1/3rd of
> all used browsers afterall..now, back to Firefox ;)
Nice catch - and there's a CSS validation error for feature_box in
the .css stylesheet. I fixed that, I'm asking #asfinfra to refresh (it's
not yet set up for me to do that automagically).
We'll see if that fixes the problem ...
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Prototype web site - now with most of the content
Posted by Robbie Gemmell <ro...@gmail.com>.
On the same page, the link to the wiki should point to
http://cwiki.apache.org/confluence/display/qpid
Overall looks good, I echo Gordon's thoughts, lets get this live ASAP
and improve as we go rather than spending too much time polishing it
beforehand: anythings better than what we have now and everything is
still reachable as long as we link to the wiki.
One minor nit, the bullet pointed feature box things on the front page
dont display in the right place in IE6 and IE7 (or 8 in compatibility
mode), the entire containing div drops down the page to where the menu
stops. I imagine its just a margin/padding+float CSS bug, ill try to
take a look tonight if I get a chance, they are still around 1/3rd of
all used browsers afterall..now, back to Firefox ;)
Robbie
On 8 June 2010 14:03, Gordon Sim <gs...@redhat.com> wrote:
> On 06/08/2010 01:13 PM, Jonathan Robie wrote:
>>
>> Here's the current version of the new web site:
>>
>> http://ci.apache.org/projects/qpid/
>>
>> Does this seem basically right?
>
> "Documentation for Qpid 0.6 (development branch)" - 0.6 is a released and
> stable version (like 0.5). The current development version is 0.7 and that
> is what I think these docs (at least the programming guide and API
> references refer to).
>
>> What needs to happen before we make this
>> live?
>
> Other than the above it looks good to me. My view would be to get it live
> asap and allow changes to be made through the repo to fix any issues we spot
> (or even just for general improvements).
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Prototype web site - now with most of the content
Posted by Gordon Sim <gs...@redhat.com>.
On 06/08/2010 01:13 PM, Jonathan Robie wrote:
> Here's the current version of the new web site:
>
> http://ci.apache.org/projects/qpid/
>
> Does this seem basically right?
"Documentation for Qpid 0.6 (development branch)" - 0.6 is a released
and stable version (like 0.5). The current development version is 0.7
and that is what I think these docs (at least the programming guide and
API references refer to).
> What needs to happen before we make this
> live?
Other than the above it looks good to me. My view would be to get it
live asap and allow changes to be made through the repo to fix any
issues we spot (or even just for general improvements).
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org