You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xbean-dev@geronimo.apache.org by Guillaume Nodet <gn...@gmail.com> on 2007/02/12 18:23:17 UTC
XBean web site
The XBean web site has been moved from goopen.org to the
ASF confluence. I have set up a cron job to rsync the
autoexported site to
http://geronimo.apache.org/xbean/
as explained at http://cwiki.apache.org/CWIKI/
The new site should be up in a few hours (time for the mirrors to
be updated).
--
Cheers,
Guillaume Nodet
Re: XBean web site
Posted by Hernan Cunico <hc...@gmail.com>.
Let's do it then!
I'll start another thread for discussion
Cheers!
Hernan
Jason Dillon wrote:
> On Feb 14, 2007, at 7:00 AM, Hernan Cunico wrote:
>> As for the cwiki, we discussed earlier (well, long time ago) that the
>> cwiki and the web site should not be the same, so we went "very
>> similar" but not exactly the same. Some folks were concerned that we
>> would end up focusing on the cwiki and leave aside the main web site.
>> (pls don't make me find that thread ;-) )
>
> Um... dig it up :-P
>
> I think that http://geronimo.apache.org *should* contain content which
> is rendered into static files from cwiki and copied into place (and/or
> added to svn I don't care) on people.
>
> Just look at what Cayenne has done:
>
> http://cayenne.apache.org/
>
> And ActiveMQ:
>
> http://activemq.apache.org/home.html
>
> and OpenEJB:
>
> http://incubator.apache.org/openejb/
>
> And there are probably more that I have not see yet...
>
> These are really functional, easy to maintain, easy to grow, easy to
> refactor, dang pretty to look at websites driven by Confluence +
> autoexport.
>
> I think we should do the same.
>
> --jason
>
Re: XBean web site
Posted by Jason Dillon <ja...@planet57.com>.
On Feb 14, 2007, at 7:00 AM, Hernan Cunico wrote:
> As for the cwiki, we discussed earlier (well, long time ago) that
> the cwiki and the web site should not be the same, so we went "very
> similar" but not exactly the same. Some folks were concerned that
> we would end up focusing on the cwiki and leave aside the main web
> site. (pls don't make me find that thread ;-) )
Um... dig it up :-P
I think that http://geronimo.apache.org *should* contain content
which is rendered into static files from cwiki and copied into place
(and/or added to svn I don't care) on people.
Just look at what Cayenne has done:
http://cayenne.apache.org/
And ActiveMQ:
http://activemq.apache.org/home.html
and OpenEJB:
http://incubator.apache.org/openejb/
And there are probably more that I have not see yet...
These are really functional, easy to maintain, easy to grow, easy to
refactor, dang pretty to look at websites driven by Confluence +
autoexport.
I think we should do the same.
--jason
Re: XBean web site
Posted by Hernan Cunico <hc...@gmail.com>.
Jason Dillon wrote:
> On Feb 13, 2007, at 7:22 AM, Hernan Cunico wrote:
>>> ...
>
> I think we could be there... just needs a wee bit more love. I don't
> see any of the bugs in AE as blockers.
I just replied to you in another mail. Listed there what are the issues I think are getting in the way.
>
> The biggest issue for me was I hated the 1+ hour sync time from cwiki
> change to live content... that really pissed me off and I ended up
> dropping at the time.
Oh yeah, that's a royal PITA itself, but we can't blame the plugin for that, can we!? ;-)
Is there anything we can do to force publishing these updates faster?
>
>
>> ...
>
> Whats to discus? I'm aware of some of the problems... but I don't think
> that any of them prevent us from using the GMOxSITE space for
> geronimo.apache.org.
Check the other mail.
>
>>> ...
>> We do have a consistent look & feel all across the web site, we should
>> keep it that way
>
> Eh... yes and no... click on the user/dev list links in the top-nav, or
> the issue tracker. Or click on any link that takes you to cwiki. Aside
> from the hideous mbox junk and jira, the only thing that is consistent
> is *part* of the page header (the blue bar with the G logo).
>
> I don't consider this really consistent.
I think you are talking about different sites. What can we do about JIRA or the mail archives, do we have any control on how that info is presented?
As for the cwiki, we discussed earlier (well, long time ago) that the cwiki and the web site should not be the same, so we went "very similar" but not exactly the same. Some folks were concerned that we would end up focusing on the cwiki and leave aside the main web site. (pls don't make me find that thread ;-) )
For those things we do have control we should try to make them look as consistent as possible.
Cheers!
Hernan
>...
> --jason
>
Re: XBean web site
Posted by Jason Dillon <ja...@planet57.com>.
On Feb 13, 2007, at 7:22 AM, Hernan Cunico wrote:
>> I completely disagree.
>> I believe that Geronimo should also use Confluence to support
>> generation of the website. Aside from a few minor issues, and the
>> lag time from export to live, I don't see any reason not to use
>> Confluence in this manner. It has been on my TODO list for quite
>> some time, I did an initial POC, but got sucked up into TCK-land
>> which has been taking up most of my time.
>> I actually don't think that the current Geronimo website xdoc
>> +script thing is very good and it should go soon. Its not very
>> friendly, people tend to forget steps and corrupt the site, and
>> its not easy to add new content to.
> I know, we are all sucked up into other priorities that we need to
> attend to. The POC in the cwiki looks great (I would chop off the
> JIRAs from the home page though ;-) and once we get those plugin
> issues fixed we should move over Confluence right away. I'll help
> out in any way I can ;-)
> But, until we get there, we should not disrupt what we have working
> today, no matter how much we would like to be using a different tool.
I think we could be there... just needs a wee bit more love. I don't
see any of the bugs in AE as blockers.
The biggest issue for me was I hated the 1+ hour sync time from cwiki
change to live content... that really pissed me off and I ended up
dropping at the time.
> btw, let's discuss the plugin issues and solutions on a different
> thread, let me know when you have some time to look at it because
> I've been also trying to get some fixed already. AFAIK there is no
> other place for keeping track (discussing actually) of this issues
> and fixes other than http://could.it/bugs/browse/EXP
Whats to discus? I'm aware of some of the problems... but I don't
think that any of them prevent us from using the GMOxSITE space for
geronimo.apache.org.
>> Blah... each different part of the site has a slightly different
>> look to it... I don't think this matters all that much right now.
>> While once we get all websites into Confluence, then I think it
>> should be easy enough to get them all kinda looking the same.
> We do have a consistent look & feel all across the web site, we
> should keep it that way
Eh... yes and no... click on the user/dev list links in the top-nav,
or the issue tracker. Or click on any link that takes you to cwiki.
Aside from the hideous mbox junk and jira, the only thing that is
consistent is *part* of the page header (the blue bar with the G logo).
I don't consider this really consistent.
>>> Bottom line, I think we should be consistent in the way we
>>> present the web site and the way we maintain it.
>> Sure, and lets be consistent and use Confluence ;-)
> Be careful what you wish for, another joining subproject could come
> in using MS Front Page :-0
Highly, highly, highly... HIGHLY... unlikely :-P
--jason
Re: XBean web site
Posted by Hernan Cunico <hc...@gmail.com>.
Jason Dillon wrote:
> On Feb 12, 2007, at 11:42 AM, Hernan Cunico wrote:
>> ...
>
> I completely disagree.
>
> I believe that Geronimo should also use Confluence to support generation
> of the website. Aside from a few minor issues, and the lag time from
> export to live, I don't see any reason not to use Confluence in this
> manner. It has been on my TODO list for quite some time, I did an
> initial POC, but got sucked up into TCK-land which has been taking up
> most of my time.
>
> I actually don't think that the current Geronimo website xdoc+script
> thing is very good and it should go soon. Its not very friendly, people
> tend to forget steps and corrupt the site, and its not easy to add new
> content to.
>
I know, we are all sucked up into other priorities that we need to attend to. The POC in the cwiki looks great (I would chop off the JIRAs from the home page though ;-) and once we get those plugin issues fixed we should move over Confluence right away. I'll help out in any way I can ;-)
But, until we get there, we should not disrupt what we have working today, no matter how much we would like to be using a different tool.
btw, let's discuss the plugin issues and solutions on a different thread, let me know when you have some time to look at it because I've been also trying to get some fixed already. AFAIK there is no other place for keeping track (discussing actually) of this issues and fixes other than http://could.it/bugs/browse/EXP
>
>> So far we have three subprojects listed and they are integrated in
>> ...
>>
>> The xbean piece of the site does not match the template used for the
>> Geronimo site, it is similar but not the same. I think we are
>> projecting an inconsistent web site image.
>
> Blah... each different part of the site has a slightly different look to
> it... I don't think this matters all that much right now. While once we
> get all websites into Confluence, then I think it should be easy enough
> to get them all kinda looking the same.
>
We do have a consistent look & feel all across the web site, we should keep it that way
>
>> Bottom line, I think we should be consistent in the way we present the
>> web site and the way we maintain it.
>
> Sure, and lets be consistent and use Confluence ;-)
Be careful what you wish for, another joining subproject could come in using MS Front Page :-0
Cheers!
Hernan
>
> --jason
>
Re: XBean web site
Posted by Jason Dillon <ja...@planet57.com>.
On Feb 12, 2007, at 11:42 AM, Hernan Cunico wrote:
> Guillaume,
> continuing our conversation, now on dev@, I'll reissue some of my
> previous comments (just my observations, hopefully it still will
> make sense ;-) )
>
> The XBean folks are using Confluence to maintain their site but we
> (Geronimo) are not. We still use xdocs and ant script to build our
> site. The source for Geronimo's web site is on svn.
>
> We are not using Confluence for Geronimo's web site due to some
> issues with the autoexport plugin. Until we address those issues,
> vote and mover over Confluence, IMO, the subprojects listed under
> Geronimo's web site URL ( geronimo.apache.org/XYZ_project ) should
> use the same build method we use and be part of Geronimo's web site
> svn repo.
I completely disagree.
I believe that Geronimo should also use Confluence to support
generation of the website. Aside from a few minor issues, and the
lag time from export to live, I don't see any reason not to use
Confluence in this manner. It has been on my TODO list for quite
some time, I did an initial POC, but got sucked up into TCK-land
which has been taking up most of my time.
I actually don't think that the current Geronimo website xdoc+script
thing is very good and it should go soon. Its not very friendly,
people tend to forget steps and corrupt the site, and its not easy to
add new content to.
> So far we have three subprojects listed and they are integrated in
> three different ways:
>
> 1.- Development Tools : part of main web site src and build process
> (ideal)
> 2.- GBuild : link to cwiki (external link, no real
> integration but not disruptive either)
> 3.- XBean : bypass svn repo and copied directly into /
> www/geronimo.apache.org/xbean (IMO, *really really bad practice*)
>
> The way it is explained in the link you are pointing out (http://
> cwiki.apache.org/CWIKI/) goes well if you don't have the other half
> of your website already in production and authored with a totally
> different method.
>
> The fastest way to fix this would be to have an external link to
> XBean cwiki. Similar to what we have with GBuild. However this does
> not address the integration issue.
>
> We add subprojects to an existing structure/process and these new
> subprojects, I think, should adapt to the current procedures in place.
>
> What I do consider a *really bad practice* is a melange of methods
> for authoring the web site. I consider XBean part of the Geronimo
> site since it's URL is geronimo.apache.org/xbean
>
> The xbean piece of the site does not match the template used for
> the Geronimo site, it is similar but not the same. I think we are
> projecting an inconsistent web site image.
Blah... each different part of the site has a slightly different look
to it... I don't think this matters all that much right now. While
once we get all websites into Confluence, then I think it should be
easy enough to get them all kinda looking the same.
> Bottom line, I think we should be consistent in the way we present
> the web site and the way we maintain it.
Sure, and lets be consistent and use Confluence ;-)
--jason
Re: XBean web site
Posted by Hernan Cunico <hc...@gmail.com>.
Soon is going to be a year since we moved Confluence in as our "cwiki". At that time we were using version 0.13 of the plugin. Today we are using a 0.14 beta version that addresses some of the initial issues, but not all.
Some of the issues I think stand in our way are:
- Plugin wont update exported pages that have content dynamically created by other macros ({children} or {toc} for example)
- Plugin wont update attachments in the HTML version when these are modified on the Confluence side.
- Plugin wont rename (or allow you to delete) HTML versions when the Confluence page name changes.
- In the exported HTML, all Confluence native content (images like the check boxes) still point as absolute links to the cwiki base URL. So, the exports are not totally complete/self-contained.
- Some reference to Confluence data (dynamic links) get also translated as absolute links pointing to the cwiki base URL. Similar case as the one just described above.
- Some Confluence macros (thumbnails for example) just don't get translated right and wont work properly in the exported HTML version.
- There are some issues with JIRA integration too (like dynamic content update and missing images)
I would personally prefer to get these sorted out before we move on.
Cheers!
Hernan
Jason Dillon wrote:
> On Feb 13, 2007, at 2:44 PM, Hernan Cunico wrote:
>>> used for the main
>>> site, i think that redirecting is a bad idea as we want to keep the
>>> url in
>>> geronimo.apache.org.
>>
>> Totally agree, but we are not using Confluence for the site yet. I was
>> bringing that up as a temp solution till we fix the autoexport plugin
>> issues and move full steam forward to authoring all sites (main and
>> subprojects) with Confluence. Never mind, I wont be surfacing that
>> idea again ;-)
>
> Hernan, I think that the plugin works fine to move forward... OpenEJB,
> ActiveMQ, XBean, and several others are using it w/no significant
> problems. Yes I know there are a few issues, but we can fix them
> *after* we move, I don't see those problems as blocking.
>
> --jason
>
Re: XBean web site
Posted by Jason Dillon <ja...@planet57.com>.
On Feb 13, 2007, at 2:44 PM, Hernan Cunico wrote:
>> used for the main
>> site, i think that redirecting is a bad idea as we want to keep
>> the url in
>> geronimo.apache.org.
>
> Totally agree, but we are not using Confluence for the site yet. I
> was bringing that up as a temp solution till we fix the autoexport
> plugin issues and move full steam forward to authoring all sites
> (main and subprojects) with Confluence. Never mind, I wont be
> surfacing that idea again ;-)
Hernan, I think that the plugin works fine to move forward...
OpenEJB, ActiveMQ, XBean, and several others are using it w/no
significant problems. Yes I know there are a few issues, but we can
fix them *after* we move, I don't see those problems as blocking.
--jason
Re: XBean web site
Posted by Hernan Cunico <hc...@gmail.com>.
Guillaume Nodet wrote:
> On 2/13/07, Hernan Cunico <hc...@gmail.com> wrote:
>> ...
>
> I don't really understand the need to link directly. There is no benefit
> and
> it forces an external link, which seems bad imo, because this looks like
> an externally managed site, rather than a part of geronimo.apache.org.
>
That's fine with me, I'll along with the opinion of the majority
>>
>> Can you tell me how the XBean space is organized?
>> An index.html (autoexported) seems to be missing, do you mind if I
>> create one?
>
> Yeah, I forgot that :-(
> What I did for ServiceMix and ActiveMQ is to add a svn up after the rsync
> to download the additional resources not available from the wiki.
> Maybe an easy way is to just rename the home page to index, which
> should be sufficient.
No need to rename, you could create a new one and do an {include} of Home. That's what I did for Geronimo spaces, it "technically" gets updated automatically. (that's one of the issues with the plugin, it wont refresh all the automatically generated data. i.e. {include}, {children}, {toc}... don't get updated most of the time)
>>
>> ...
>
> As stated above, a link may not be enough. For example the css is
> maintained
> separatly in the svn tree. And last, but not least, if conluence is
That's what I think brings some noise in. Using Confluence version control for some things and svn for other.
> used for the main
> site, i think that redirecting is a bad idea as we want to keep the url in
> geronimo.apache.org.
Totally agree, but we are not using Confluence for the site yet. I was bringing that up as a temp solution till we fix the autoexport plugin issues and move full steam forward to authoring all sites (main and subprojects) with Confluence. Never mind, I wont be surfacing that idea again ;-)
>
>>
>> ...
>
> I have not seen much issues listed reported by geronimo developers.
Do you mean the plugin? if so, there were a whole bunch. There were discussions on infra@, direct communication with the plugin author and there is a dedicated JIRA install for issue tracking external to the ASF infrastructure.
> I think when the main Geronimo web site is edited in confluence, we need
> to keep it at geronimo.apache.org, and not redirect to
> cwiki.apache.org/GMOxSITE/
Nobody ever mentioned anything like that.
>
>>
>> Any volunteers to tackle some of the issues with the autoexport plugin?
>> the sooner we fix these the sooner we'll have the *one-for-all*
>> authoring tool !!!
>
> Which one exactly ? We use it for ServiceMix and ActiveMQ without any
> problems ...
Take your pick ;-)
http://could.it/bugs/secure/IssueNavigator.jspa?reset=true&pid=10020&status=1
Keep in mind not all the issues have been reported there.
Don't get me wrong, I really want to use Confluence for everything. I was one of those annoying gadflies testing and and pushing to bring Confluence over to the ASF infrastructure.
Maybe I'm just too picky ;-)
Cheers!
Hernan
Re: XBean web site
Posted by David Blevins <da...@visi.com>.
On Feb 13, 2007, at 1:15 PM, Guillaume Nodet wrote:
> What I did for ServiceMix and ActiveMQ is to add a svn up after the
> rsync
> to download the additional resources not available from the wiki.
> Maybe an easy way is to just rename the home page to index, which
> should be sufficient.
That's pretty much what everyone did.
-David
Re: XBean web site
Posted by Guillaume Nodet <gn...@gmail.com>.
On 2/13/07, Hernan Cunico <hc...@gmail.com> wrote:
> quick quick quick you are Mr. !!! ;-)
>
> As I said before, a quick fix would be to either add a link or a redirect to the cwiki (same thing we have for GBuild) and remove, for now, the xbean directory in /www/geronimo.apache.org
> (temporary solution till we sort out confluence reorg and plugin issues)
>
> If no one objects I would just add a link to the cwiki.
> Can somebody stop the crontab, if we temporarily use the external link there is no point in continue having this process running.
I don't really understand the need to link directly. There is no benefit and
it forces an external link, which seems bad imo, because this looks like
an externally managed site, rather than a part of geronimo.apache.org.
>
> Can you tell me how the XBean space is organized?
> An index.html (autoexported) seems to be missing, do you mind if I create one?
Yeah, I forgot that :-(
What I did for ServiceMix and ActiveMQ is to add a svn up after the rsync
to download the additional resources not available from the wiki.
Maybe an easy way is to just rename the home page to index, which
should be sufficient.
>
>
> As for me helping out, well I'm volunteering to move into production Geronimo's website authored with Confluence. That's where we all want to be, right? Confluence? as well as help out integrating the other subproject spaces so we deliver a consistent message all across the site.
>
> There is no point in migrating autoexported HTML to xdoc and then back to confluence. That's why I'm suggesting to have a link pointing to the cwiki autoexported space.
As stated above, a link may not be enough. For example the css is maintained
separatly in the svn tree. And last, but not least, if conluence is
used for the main
site, i think that redirecting is a bad idea as we want to keep the url in
geronimo.apache.org.
>
> As for maintaining going forward, there isn't much I can do to consciously update any of the subprojects sites, I'm simply not *that* aware of the day-to-day or *need to communicate* news. It wouldn't make much more sense if I do the updates, would it!? ;-) What did you have in mind?
>
> Once we fix the plugin issues and go live with the autoexported Geronimo web site we could then consolidate into Geronimo's space (GMOxSITE) all the other subprojects web site spaces. Copy (or maybe just reference if at all possible) GBuild and XBean confluence spaces into GMOxSITE. How does that sound?
I have not seen much issues listed reported by geronimo developers.
I think when the main Geronimo web site is edited in confluence, we need
to keep it at geronimo.apache.org, and not redirect to
cwiki.apache.org/GMOxSITE/
>
> Any volunteers to tackle some of the issues with the autoexport plugin?
> the sooner we fix these the sooner we'll have the *one-for-all* authoring tool !!!
Which one exactly ? We use it for ServiceMix and ActiveMQ without any
problems ...
>
> Cheers!
> Hernan
>
> James Strachan wrote:
> > Hernan, thanks for volunteering to migrate the XBean site to whatever
> > technology you wish and maintaining it going forward :)
> >
> >
> > On 2/12/07, Hernan Cunico <hc...@gmail.com> wrote:
> >> Guillaume,
> >> continuing our conversation, now on dev@, I'll reissue some of my
> >> previous comments (just my observations, hopefully it still will make
> >> sense ;-) )
> >>
> >> The XBean folks are using Confluence to maintain their site but we
> >> (Geronimo) are not. We still use xdocs and ant script to build our
> >> site. The source for Geronimo's web site is on svn.
> >>
> >> We are not using Confluence for Geronimo's web site due to some issues
> >> with the autoexport plugin. Until we address those issues, vote and
> >> mover over Confluence, IMO, the subprojects listed under Geronimo's
> >> web site URL ( geronimo.apache.org/XYZ_project ) should use the same
> >> build method we use and be part of Geronimo's web site svn repo.
> >>
> >> So far we have three subprojects listed and they are integrated in
> >> three different ways:
> >>
> >> 1.- Development Tools : part of main web site src and build process
> >> (ideal)
> >> 2.- GBuild : link to cwiki (external link, no real
> >> integration but not disruptive either)
> >> 3.- XBean : bypass svn repo and copied directly into
> >> /www/geronimo.apache.org/xbean (IMO, *really really bad practice*)
> >>
> >> The way it is explained in the link you are pointing out
> >> (http://cwiki.apache.org/CWIKI/) goes well if you don't have the other
> >> half of your website already in production and authored with a totally
> >> different method.
> >>
> >> The fastest way to fix this would be to have an external link to XBean
> >> cwiki. Similar to what we have with GBuild. However this does not
> >> address the integration issue.
> >>
> >> We add subprojects to an existing structure/process and these new
> >> subprojects, I think, should adapt to the current procedures in place.
> >>
> >> What I do consider a *really bad practice* is a melange of methods for
> >> authoring the web site. I consider XBean part of the Geronimo site
> >> since it's URL is geronimo.apache.org/xbean
> >>
> >> The xbean piece of the site does not match the template used for the
> >> Geronimo site, it is similar but not the same. I think we are
> >> projecting an inconsistent web site image.
> >>
> >>
> >> Bottom line, I think we should be consistent in the way we present the
> >> web site and the way we maintain it.
> >>
> >> Again, if I missed or totally forgot the discussion about this pls let
> >> me know, I would really appreciate if some one can point me to it.
> >>
> >> Comments?
> >>
> >> Cheers!
> >> Hernan
> >>
> >> Guillaume Nodet wrote:
> >> > The XBean web site has been moved from goopen.org to the
> >> > ASF confluence. I have set up a cron job to rsync the
> >> > autoexported site to
> >> > http://geronimo.apache.org/xbean/
> >> >
> >> > as explained at http://cwiki.apache.org/CWIKI/
> >> >
> >> > The new site should be up in a few hours (time for the mirrors to
> >> > be updated).
> >> >
> >>
> >
> >
>
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
Re: XBean web site
Posted by Dain Sundstrom <da...@iq80.com>.
On Feb 13, 2007, at 9:24 AM, Hernan Cunico wrote:
> quick quick quick you are Mr. !!! ;-)
>
> As I said before, a quick fix would be to either add a link or a
> redirect to the cwiki (same thing we have for GBuild) and remove,
> for now, the xbean directory in /www/geronimo.apache.org
> (temporary solution till we sort out confluence reorg and plugin
> issues)
>
> If no one objects I would just add a link to the cwiki.
> Can somebody stop the crontab, if we temporarily use the external
> link there is no point in continue having this process running.
I hate to break the news to you but James was being extremely
sarcastic. I don't think any of the xbean developers would vote to
move from confluence to xdoc. If you think I'm wrong, start a vote
thread on the xbean development mailing list.
Anyway, I officially object, and I think infrastructure will object
as you load down the cwiki site with read-only users.
-dain
Re: XBean web site
Posted by Hernan Cunico <hc...@gmail.com>.
quick quick quick you are Mr. !!! ;-)
As I said before, a quick fix would be to either add a link or a redirect to the cwiki (same thing we have for GBuild) and remove, for now, the xbean directory in /www/geronimo.apache.org
(temporary solution till we sort out confluence reorg and plugin issues)
If no one objects I would just add a link to the cwiki.
Can somebody stop the crontab, if we temporarily use the external link there is no point in continue having this process running.
Can you tell me how the XBean space is organized?
An index.html (autoexported) seems to be missing, do you mind if I create one?
As for me helping out, well I'm volunteering to move into production Geronimo's website authored with Confluence. That's where we all want to be, right? Confluence? as well as help out integrating the other subproject spaces so we deliver a consistent message all across the site.
There is no point in migrating autoexported HTML to xdoc and then back to confluence. That's why I'm suggesting to have a link pointing to the cwiki autoexported space.
As for maintaining going forward, there isn't much I can do to consciously update any of the subprojects sites, I'm simply not *that* aware of the day-to-day or *need to communicate* news. It wouldn't make much more sense if I do the updates, would it!? ;-) What did you have in mind?
Once we fix the plugin issues and go live with the autoexported Geronimo web site we could then consolidate into Geronimo's space (GMOxSITE) all the other subprojects web site spaces. Copy (or maybe just reference if at all possible) GBuild and XBean confluence spaces into GMOxSITE. How does that sound?
Any volunteers to tackle some of the issues with the autoexport plugin?
the sooner we fix these the sooner we'll have the *one-for-all* authoring tool !!!
Cheers!
Hernan
James Strachan wrote:
> Hernan, thanks for volunteering to migrate the XBean site to whatever
> technology you wish and maintaining it going forward :)
>
>
> On 2/12/07, Hernan Cunico <hc...@gmail.com> wrote:
>> Guillaume,
>> continuing our conversation, now on dev@, I'll reissue some of my
>> previous comments (just my observations, hopefully it still will make
>> sense ;-) )
>>
>> The XBean folks are using Confluence to maintain their site but we
>> (Geronimo) are not. We still use xdocs and ant script to build our
>> site. The source for Geronimo's web site is on svn.
>>
>> We are not using Confluence for Geronimo's web site due to some issues
>> with the autoexport plugin. Until we address those issues, vote and
>> mover over Confluence, IMO, the subprojects listed under Geronimo's
>> web site URL ( geronimo.apache.org/XYZ_project ) should use the same
>> build method we use and be part of Geronimo's web site svn repo.
>>
>> So far we have three subprojects listed and they are integrated in
>> three different ways:
>>
>> 1.- Development Tools : part of main web site src and build process
>> (ideal)
>> 2.- GBuild : link to cwiki (external link, no real
>> integration but not disruptive either)
>> 3.- XBean : bypass svn repo and copied directly into
>> /www/geronimo.apache.org/xbean (IMO, *really really bad practice*)
>>
>> The way it is explained in the link you are pointing out
>> (http://cwiki.apache.org/CWIKI/) goes well if you don't have the other
>> half of your website already in production and authored with a totally
>> different method.
>>
>> The fastest way to fix this would be to have an external link to XBean
>> cwiki. Similar to what we have with GBuild. However this does not
>> address the integration issue.
>>
>> We add subprojects to an existing structure/process and these new
>> subprojects, I think, should adapt to the current procedures in place.
>>
>> What I do consider a *really bad practice* is a melange of methods for
>> authoring the web site. I consider XBean part of the Geronimo site
>> since it's URL is geronimo.apache.org/xbean
>>
>> The xbean piece of the site does not match the template used for the
>> Geronimo site, it is similar but not the same. I think we are
>> projecting an inconsistent web site image.
>>
>>
>> Bottom line, I think we should be consistent in the way we present the
>> web site and the way we maintain it.
>>
>> Again, if I missed or totally forgot the discussion about this pls let
>> me know, I would really appreciate if some one can point me to it.
>>
>> Comments?
>>
>> Cheers!
>> Hernan
>>
>> Guillaume Nodet wrote:
>> > The XBean web site has been moved from goopen.org to the
>> > ASF confluence. I have set up a cron job to rsync the
>> > autoexported site to
>> > http://geronimo.apache.org/xbean/
>> >
>> > as explained at http://cwiki.apache.org/CWIKI/
>> >
>> > The new site should be up in a few hours (time for the mirrors to
>> > be updated).
>> >
>>
>
>
Re: XBean web site
Posted by James Strachan <ja...@gmail.com>.
Hernan, thanks for volunteering to migrate the XBean site to whatever
technology you wish and maintaining it going forward :)
On 2/12/07, Hernan Cunico <hc...@gmail.com> wrote:
> Guillaume,
> continuing our conversation, now on dev@, I'll reissue some of my previous comments (just my observations, hopefully it still will make sense ;-) )
>
> The XBean folks are using Confluence to maintain their site but we (Geronimo) are not. We still use xdocs and ant script to build our site. The source for Geronimo's web site is on svn.
>
> We are not using Confluence for Geronimo's web site due to some issues with the autoexport plugin. Until we address those issues, vote and mover over Confluence, IMO, the subprojects listed under Geronimo's web site URL ( geronimo.apache.org/XYZ_project ) should use the same build method we use and be part of Geronimo's web site svn repo.
>
> So far we have three subprojects listed and they are integrated in three different ways:
>
> 1.- Development Tools : part of main web site src and build process (ideal)
> 2.- GBuild : link to cwiki (external link, no real integration but not disruptive either)
> 3.- XBean : bypass svn repo and copied directly into /www/geronimo.apache.org/xbean (IMO, *really really bad practice*)
>
> The way it is explained in the link you are pointing out (http://cwiki.apache.org/CWIKI/) goes well if you don't have the other half of your website already in production and authored with a totally different method.
>
> The fastest way to fix this would be to have an external link to XBean cwiki. Similar to what we have with GBuild. However this does not address the integration issue.
>
> We add subprojects to an existing structure/process and these new subprojects, I think, should adapt to the current procedures in place.
>
> What I do consider a *really bad practice* is a melange of methods for authoring the web site. I consider XBean part of the Geronimo site since it's URL is geronimo.apache.org/xbean
>
> The xbean piece of the site does not match the template used for the Geronimo site, it is similar but not the same. I think we are projecting an inconsistent web site image.
>
>
> Bottom line, I think we should be consistent in the way we present the web site and the way we maintain it.
>
> Again, if I missed or totally forgot the discussion about this pls let me know, I would really appreciate if some one can point me to it.
>
> Comments?
>
> Cheers!
> Hernan
>
> Guillaume Nodet wrote:
> > The XBean web site has been moved from goopen.org to the
> > ASF confluence. I have set up a cron job to rsync the
> > autoexported site to
> > http://geronimo.apache.org/xbean/
> >
> > as explained at http://cwiki.apache.org/CWIKI/
> >
> > The new site should be up in a few hours (time for the mirrors to
> > be updated).
> >
>
--
James
-------
http://radio.weblogs.com/0112098/
Re: XBean web site
Posted by Hernan Cunico <hc...@gmail.com>.
Guillaume,
continuing our conversation, now on dev@, I'll reissue some of my previous comments (just my observations, hopefully it still will make sense ;-) )
The XBean folks are using Confluence to maintain their site but we (Geronimo) are not. We still use xdocs and ant script to build our site. The source for Geronimo's web site is on svn.
We are not using Confluence for Geronimo's web site due to some issues with the autoexport plugin. Until we address those issues, vote and mover over Confluence, IMO, the subprojects listed under Geronimo's web site URL ( geronimo.apache.org/XYZ_project ) should use the same build method we use and be part of Geronimo's web site svn repo.
So far we have three subprojects listed and they are integrated in three different ways:
1.- Development Tools : part of main web site src and build process (ideal)
2.- GBuild : link to cwiki (external link, no real integration but not disruptive either)
3.- XBean : bypass svn repo and copied directly into /www/geronimo.apache.org/xbean (IMO, *really really bad practice*)
The way it is explained in the link you are pointing out (http://cwiki.apache.org/CWIKI/) goes well if you don't have the other half of your website already in production and authored with a totally different method.
The fastest way to fix this would be to have an external link to XBean cwiki. Similar to what we have with GBuild. However this does not address the integration issue.
We add subprojects to an existing structure/process and these new subprojects, I think, should adapt to the current procedures in place.
What I do consider a *really bad practice* is a melange of methods for authoring the web site. I consider XBean part of the Geronimo site since it's URL is geronimo.apache.org/xbean
The xbean piece of the site does not match the template used for the Geronimo site, it is similar but not the same. I think we are projecting an inconsistent web site image.
Bottom line, I think we should be consistent in the way we present the web site and the way we maintain it.
Again, if I missed or totally forgot the discussion about this pls let me know, I would really appreciate if some one can point me to it.
Comments?
Cheers!
Hernan
Guillaume Nodet wrote:
> The XBean web site has been moved from goopen.org to the
> ASF confluence. I have set up a cron job to rsync the
> autoexported site to
> http://geronimo.apache.org/xbean/
>
> as explained at http://cwiki.apache.org/CWIKI/
>
> The new site should be up in a few hours (time for the mirrors to
> be updated).
>
Re: XBean web site
Posted by Dain Sundstrom <da...@iq80.com>.
Awesome! Thanks Guillaume
-dain
On Feb 12, 2007, at 9:23 AM, Guillaume Nodet wrote:
> The XBean web site has been moved from goopen.org to the
> ASF confluence. I have set up a cron job to rsync the
> autoexported site to
> http://geronimo.apache.org/xbean/
>
> as explained at http://cwiki.apache.org/CWIKI/
>
> The new site should be up in a few hours (time for the mirrors to
> be updated).
>
> --
> Cheers,
> Guillaume Nodet