commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Grobmeier <grobme...@gmail.com>
Subject Re: [ALL] suggestion for improvement: Unify homepage layout for all commons subprojects
Date Mon, 16 Jan 2012 16:00:18 GMT
On Mon, Jan 16, 2012 at 4:55 PM, Benedikt Ritter
<bene@systemoutprintln.de> wrote:
> Am 16.01.2012 16:40, schrieb Christian Grobmeier:
>
>> On Mon, Jan 16, 2012 at 4:26 PM, Benedikt Ritter
>> <bene@systemoutprintln.de>  wrote:
>>>
>>> Am 16.01.2012 16:16, schrieb sebb:
>>>
>>>> On 16 January 2012 15:02, Christian Grobmeier<grobmeier@gmail.com>
>>>>  wrote:
>>>>>
>>>>>
>>>>> Actually Simone has already brought up a bootstrap'ped variant of the
>>>>> Commons homepage I liked very much. Not sure what was the problem with
>>>>> that.
>>>>
>>>>
>>>>
>>>> The major problem was that it did not meet the branding requirements.
>>>
>>>
>>>
>>> I have created a jira issue:
>>> https://issues.apache.org/jira/browse/COMMONSSITE-65
>>>
>>> What do you think about my idea of providing a road map for every
>>> project?
>>
>>
>> Basically yes, but I am afraid that some components do not have a road
>> map because they are not maintained to well (like Jelly for example or
>> logging). I guess only a few components have enough steam to work
>> after a roadmap (like math maybe)
>
>
> Okay, I get that. But I think every project should at least be able to
> determine, when the next release is scheduled. As I described with
> Collections, there are major changes coming up, and it would be nice to
> know, when we can expect those to be released.
>
> Maybe every project has to consider for themselves, if they can maintain a
> road map. So as for collections, I should maybe propose that on their
> submailinglist.
> I must say, that it is a bit scary, that most project do not have at least
> an internal road map...

Well, we want your spare time.

Feel free to patch, code, suggest and finally help with a roadmap as a
committer :-)
http://www.apache.org/foundation/getinvolved.html

>
>
>>
>>
>>>
>>> Best regards
>>>
>>>
>>>>
>>>>> We should put it on our table again, as the current Commons site
>>>>> looks like we are jdk 1.3 users (ok, we support 1.3 on some places,
>>>>> but this does not mean we should be proud of that ;-))
>>>>>
>>>>>
>>>>> On Mon, Jan 16, 2012 at 3:49 PM, Benedikt Ritter
>>>>> <bene@systemoutprintln.de>    wrote:
>>>>>>
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> looking at the different commons project pages, it occurs to me,
that
>>>>>> all
>>>>>> pages use a slightly different layout. For example comparing Lang,
>>>>>> BeanUtils
>>>>>> and Collections with one another the first thing are the page titles:
>>>>>>
>>>>>> - Home
>>>>>> - BeanUtils - Commons
>>>>>> - Collections - Home
>>>>>>
>>>>>> If I were to rate this titles, I would say that "BeanUtils - Commons"
>>>>>> is
>>>>>> the
>>>>>> best one, followed by "Collections - Home". "Home" from Lang's project
>>>>>> page
>>>>>> is clearly the worst page title I can think of.
>>>>>>
>>>>>> Looking at the content area, there is not much to complain about.
All
>>>>>> three
>>>>>> content areas are structured nearly the same way (although IMHO
>>>>>> BeanUtils
>>>>>> content area is a bit overloaded with release informations).
>>>>>>
>>>>>> When it comes to the sidebar, things get completely inconsistent.
>>>>>> First of all: Why doesn't Lang's homepage has a link so ApacheCon?
>>>>>> Why does BeanUtils have a Documentation are and a Project
>>>>>> Documentation
>>>>>> area?
>>>>>> Where do I get all the informations about developing BeanUtils from
>>>>>> (as
>>>>>> Lang
>>>>>> and Collections have a distinct development area)?
>>>>>> Why does Lang's ASF area have more links than the ones of the others?
>>>>>> Why do the release history pages of all three projects look so
>>>>>> completely
>>>>>> different?
>>>>>>
>>>>>> In addition to that, I think that one thing is really missing on
all
>>>>>> of
>>>>>> the
>>>>>> three above mentioned pages: There is no road map for future releases!
>>>>>> How
>>>>>> can I know if I should wait for the next Collections release, that
>>>>>> provides
>>>>>> generics or better start my new project using the latest release?
>>>>>> Maybe
>>>>>> it
>>>>>> will be out next week, maybe I have to wait one year. I don't know...
>>>>>> There
>>>>>> really has to be a road map, so that the users know when they can
>>>>>> expect
>>>>>> the
>>>>>> next release and what they can expect from it.
>>>>>>
>>>>>> I guess, I have made my point clear, and I bet that looking at other
>>>>>> commons
>>>>>> project pages would result in finding even more layout variants.
>>>>>> I don't want to study the page layout all over again, when I browse
>>>>>> through
>>>>>> the different project pages. I want everything to be at the same
place
>>>>>> (as
>>>>>> far as possible). So I propose to unify all page layouts. This post
is
>>>>>> not
>>>>>> supposed to present the perfect layout, but rather be a discussion
>>>>>> starter
>>>>>> on how such a layout could look like (if you guys think that a unified
>>>>>> layout is needed at all...).
>>>>>>
>>>>>> Regards
>>>>>> Benedikt
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> http://www.grobmeier.de
>>>>> https://www.timeandbill.de
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>



-- 
http://www.grobmeier.de
https://www.timeandbill.de

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message