6:53 p.m.
After months of sitting in limbo it looks like there may finally be
movement on getting hibernate.org content moved over to the
magnolia/clearspace setup.
We need to figure out what all still needs to be done in terms of
content. For core (+ annotations/em) I have a good idea of the work
still to do. But in terms of search, validator, shards and tools
(nhibernate?) I have no idea.
This will not happen until next week at the earliest as I have a meet up
scheduled with the JBoss design team here in Austin to go over LnF,
navigation, etc later this week.
Like one specific thing I know we have to iron out is navigation and
side bar content for the various subprojects. Will the various
subprojects "be under" hibernate? The infrastructure is really built so
that all projects are at the same level. I think it comes down to how
much content (pages) we see for each sub project and how y'all want the
nav and menus to work. If a unified set of nav and menus along with a
minimal set of content pages is acceptable then its probably doable to
just create sub content pages under the main set of hibernate pages. If
y'all want something more elaborate or separate nav/menus than we are
going to have to split these up I think (I'll verify to make sure this
is still the case).
--
steve(a)hibernate.org
http://hibernate.org
8:43 a.m.
I think content wise the current sub project approach will work. Looking
at search.hibernate.org and validator.hibernate.org one can see that there
is
not so much content for this content pages. The bulk of information is
really in
the wiki which is a different thing (Clearspace). Btw, what's going to
happen
with the domains search.hibernate.org and validator.hibernate.org? Will
they forward
to the corresponding sub project page on JBoss.org?
Will EM and Annotations still be listed as sub projects though. I guess
from a current
point of view we could combine them into Core. Not sure whether we have to
consider
long time users though who might be looking for these projects.
We also have to consider the new Static Metamodel Generator. Currently it
does not have its
own project page. Will we just add it to Core or will it be its own
standalone
sub project?
Maybe we should even consider moving the actual source code into a maven
module. If I remember
right the main issue stopping us from doing so were build problems, right?
Shards I know nothing about. I am not even sure who does. Seems the best
we can do there
is to move the current content from shards.hibernate.org.
--Hardy
On Mon, 22 Feb 2010 21:53:37 -0300, Steve Ebersole <steve(a)hibernate.org>
wrote:
After months of sitting in limbo it looks like there may finally be
movement on getting hibernate.org content moved over to the
magnolia/clearspace setup.
We need to figure out what all still needs to be done in terms of
content. For core (+ annotations/em) I have a good idea of the work
still to do. But in terms of search, validator, shards and tools
(nhibernate?) I have no idea.
This will not happen until next week at the earliest as I have a meet up
scheduled with the JBoss design team here in Austin to go over LnF,
navigation, etc later this week.
Like one specific thing I know we have to iron out is navigation and
side bar content for the various subprojects. Will the various
subprojects "be under" hibernate? The infrastructure is really built so
that all projects are at the same level. I think it comes down to how
much content (pages) we see for each sub project and how y'all want the
nav and menus to work. If a unified set of nav and menus along with a
minimal set of content pages is acceptable then its probably doable to
just create sub content pages under the main set of hibernate pages. If
y'all want something more elaborate or separate nav/menus than we are
going to have to split these up I think (I'll verify to make sure this
is still the case).
11:07 a.m.
On 02/23/2010 08:43 AM, Hardy Ferentschik wrote:
I think content wise the current sub project approach will work.
Looking
at search.hibernate.org and validator.hibernate.org one can see that
there is
not so much content for this content pages. The bulk of information is
really in
the wiki which is a different thing (Clearspace). Btw, what's going to
happen
with the domains search.hibernate.org and validator.hibernate.org? Will
they forward
to the corresponding sub project page on JBoss.org?
Well the "sub
domains" are apprently not really sub domains at all.
They are simple redirects. So for example, http://core.hibernate.org
simply directs the browser to https://www.hibernate.org/344.html ;
https://annotations.hibernate.org/ directs to
https://www.hibernate.org/397.html ; etc. The point though is that
these "sub domains" really just identify single information pages, one
per "sub domain". And yes redirects from the old urls to the new
targets will all be handled.
This was the gist of my question below. Is this what we want to keep?
For the sub-projects, is a single sub-page enough? Again this is no
different than what we have today.
Here is an example of incorporating sub-projects in this infrastructure:
http://jboss.org/gatein
http://jboss.org/gatein/portletcontainer.html
The fact that the banner goes away between the 2 is coincidental. We
can set it up either way. And we can have each sub-project define its
own nav items (overview/pages, download, community, etc). The real
question becomes when or whether we want these sub-projects accessible
from the main site navigation.
Will EM and Annotations still be listed as sub projects though. I
guess
from a current
point of view we could combine them into Core. Not sure whether we have
to consider
long time users though who might be looking for these projects.
I planned on not
having them as separate sub-projects. The main page
has an announcement about them (and envers) being combined into the main
project.
We also have to consider the new Static Metamodel Generator.
Currently
it does not have its
own project page. Will we just add it to Core or will it be its own
standalone
sub project?
Maybe we should even consider moving the actual source code into a maven
module. If I remember
right the main issue stopping us from doing so were build problems, right?
No
idea.
Shards I know nothing about. I am not even sure who does. Seems the
best
we can do there
is to move the current content from shards.hibernate.org.
Yep, which will be the
default for anything I don't hear about.
--Hardy
On Mon, 22 Feb 2010 21:53:37 -0300, Steve Ebersole <steve(a)hibernate.org>
wrote:
> After months of sitting in limbo it looks like there may finally be
> movement on getting hibernate.org content moved over to the
> magnolia/clearspace setup.
>
> We need to figure out what all still needs to be done in terms of
> content. For core (+ annotations/em) I have a good idea of the work
> still to do. But in terms of search, validator, shards and tools
> (nhibernate?) I have no idea.
>
> This will not happen until next week at the earliest as I have a meet up
> scheduled with the JBoss design team here in Austin to go over LnF,
> navigation, etc later this week.
>
> Like one specific thing I know we have to iron out is navigation and
> side bar content for the various subprojects. Will the various
> subprojects "be under" hibernate? The infrastructure is really built so
> that all projects are at the same level. I think it comes down to how
> much content (pages) we see for each sub project and how y'all want the
> nav and menus to work. If a unified set of nav and menus along with a
> minimal set of content pages is acceptable then its probably doable to
> just create sub content pages under the main set of hibernate pages. If
> y'all want something more elaborate or separate nav/menus than we are
> going to have to split these up I think (I'll verify to make sure this
> is still the case).
>
--
steve(a)hibernate.org
http://hibernate.org
6:35 p.m.
On Tue, 23 Feb 2010 14:07:55 -0300, Steve Ebersole <steve(a)hibernate.org>
wrote:
> We also have to consider the new Static Metamodel Generator.
Currently
> it does not have its
> own project page. Will we just add it to Core or will it be its own
> standalone
> sub project?
> Maybe we should even consider moving the actual source code into a maven
> module. If I remember
> right the main issue stopping us from doing so were build problems,
> right?
No idea.
I guess there is also the issue of license. Currently the annotation
processor
uses the Apache License (version 2). Partly out of historic reasons, since
in
the beginnings it was a prototype for Sun and partly out of the idea that
using
APL would make it easier for IDE/Tools to make use of it. So in order to
integrate
it into Core we would have to change that.
Somehow having a separate project seems wrong given the very specific
problem
the tool solves. Thoughts?
--Hardy
2:56 p.m.
I updated the subproject spaces for Validator, Search and Shards (for the
latter I just copied
what we had, we might add somewhere a note that there is currently no
active development on this
project)
For the links "Community->Chat" and "Community->Mailinglist" I
am
currently linking to the Hibernate
Core version of these pages, since the content is identical. However, it
might be better to make
copies since it screws up navigation.
Leaves still the question of the Metamodel Generator. I would be happy to
just have it mentioned from
within the Core pages. However, since it currently has its own issue
tracker and source control repository
it probably does not fit into our current structure. If we go for a
subproject we will need a banner for
this subproject as well, since afaik all subprojects will get their own
banners which will make it easier
for the user to see in which context they are within the Hibernate page.
--Hardy
On Mon, 22 Feb 2010 21:53:37 -0300, Steve Ebersole <steve(a)hibernate.org>
wrote:
After months of sitting in limbo it looks like there may finally be
movement on getting hibernate.org content moved over to the
magnolia/clearspace setup.
6:56 p.m.
Another thought is to handle metamodel generator as a module in core. I think we need to
make that decision based on whether it makes sense rather than what looks good on the
website or what is 'easy' in the build tool (as long as it possible of course).
Does it rely on core at all?
-- Sent from my Palm Pre
steve(a)hibernate.org
http://hibernate.orgHardy Ferentschik wrote:
I updated the subproject spaces for Validator, Search and Shards (for the
latter I just copied
what we had, we might add somewhere a note that there is currently no
active development on this
project)
For the links "Community->Chat" and "Community->Mailinglist" I
am
currently linking to the Hibernate
Core version of these pages, since the content is identical. However, it
might be better to make
copies since it screws up navigation.
Leaves still the question of the Metamodel Generator. I would be happy to
just have it mentioned from
within the Core pages. However, since it currently has its own issue
tracker and source control repository
it probably does not fit into our current structure. If we go for a
subproject we will need a banner for
this subproject as well, since afaik all subprojects will get their own
banners which will make it easier
for the user to see in which context they are within the Hibernate page.
--Hardy
On Mon, 22 Feb 2010 21:53:37 -0300, Steve Ebersole &lt;steve(a)hibernate.org>
wrote:
After months of sitting in limbo it looks like there may finally be
movement on getting hibernate.org content moved over to the
magnolia/clearspace setup.
9:01 a.m.
On Fri, 26 Feb 2010 21:56:07 -0300, Steve Ebersole <steve(a)hibernate.org>
wrote:
Another thought is to handle metamodel generator as a module in core.
I
think we need to make that decision based on whether it makes sense
rather than what looks good on the website or what is 'easy' in the
build tool (as long as it possible of course).
Does it rely on core at all?
No, it does not depend at Core at all. Maybe it deserves it's own
subproject after all.
5413
days inactive
5417
days old
6 comments
2 participants
participants (2)
-
Hardy Ferentschik -
Steve Ebersole