Am 26.11.12 22:41, schrieb Martin Cooper:
> On Mon, Nov 26, 2012 at 12:41 PM, Lukasz Lenart 
> <lukaszlen...@apache.org>wrote:
> 
>> 2012/11/25 Johannes Geppert <jo...@apache.org>:
>>> What others think about shrinking a little bit the menu and some Content?
>>
>> +1 :-)
>>
> 
> Depends on what you mean by "shrink". We have people (e.g. Link, very
> recently) who don't seem to be able to find stuff on our menu, so making it
> smaller will not help at all. On the other hand, reducing the number of
> items would undoubtedly help.
> 
> 

I have to admit that the sheer amount of information both in the main
menu and certain pages is what it makes hard for me to find something -
even given that I'm involved with the site for some years now. While
e.g. it is educative to hear about mailing list policies first, the
actual information how to subscribe is buried under piles of letters ...
and most of nowadays users seem to have an attention span not lasting
longer than three paragraphs before they give up reading. At least the
mailing list moderation experience seems to indicate that.

Basically I think that careful reduction and hierarchical organization
of information helps to succeed getting our messages between our site
reader's ears.

That said, reducing the main menu would be good first step in my opinion.


>>
>>> 1.) The "Roadmap FAQ" is really outdated!
>>> We can update it, delete it or reference it to the current Struts3 Wiki
>> Page
>>
>> I think we can remove that page, even if we plan S3 there is not too
>> much to write - Struts 2 done better :-)
>>
> 
> A roadmap can be very useful, but it needs people committed to maintaining
> it. I think Ted was probably the only one who did this for an extended
> period. We should just remove it if we don't have something useful to say.
> 
> 

+1 - unless there is valid maintained content, we should remove the
roadmap FAQ. If at a later point we want to add up to date roadmap
information again, we might consider to call it simply "Roadmap" rather
than "Roadmap FAQ".

>>
>>> 2.) What is the mining of the "Project Minutes" ? Last update is from
>> 2008!
>>
>> I think it would be nice to put here Reports to the ASF Board which
>> Rene prepares, it's important to see what's going on with the project,
>> thus will overtake Roadmap FAQ
>>
> 
> The board minutes are a matter of public record, and are always published.
> See:
> 
> http://www.apache.org/foundation/board/calendar.html
> 
> It's not easy to find the Struts reports in that (e.g. you need to know our
> schedule), so I'd be okay with re-publishing, if we think we'll keep it up
> to date. But we should copy from the board minutes, rather than our list,
> to be sure we capture accurately what the board accepted.
> 
> 

I'm not sure if the board level reports - in this particular form - are
of widespread interest, neither do they replace well maintained news
content. Given that we had to implement a solution to automatically
extract the content from the approved reports, as Martin stated, I
wonder if this is worth the effort. A news section with targeted
information bits might be a more relevant way to go, as long at it is
well maintained.

E.g., I could imagine snippets like
- Struts Users Facebook Site hits 1.000.000 likes
- Struts Downloads peeked with the release of 4.0.1
- Externally maintained Struts 2 BootQueryNateStrap-Plugin version 9.8.7
released
- Appfuse 20.12 now with Struts2 LiquidDiamondAngular Theme support baked in
- ApacheCon NA 2015 to feature five Struts 4 talks
- John Doe has written an interesting blog post on Configuration over
Convention in Struts 4

As for the noteworthy stuff assembled into the quarterly board report, I
could volunteer to add a rehash-and-update-site workflow at around the
time the report is submitted. But I think more voluntary help would be
needed to keep such a news stream relevant.

If we go for adding approved board reports, the Development->Minutes
section would have to be filled with life again. If not, we should
consider removing it.

>>
>>> 3.) Maybe we can create on Page for the Related and Similar Projects?
>>> This would make the Menu much more cleaner.
>>
>> +1
>>
> 
> Frankly, I think we should drop related and similar projects. There is no
> meaningful determination of what does, or does not, make it into either
> list.
>

+1 as well - besides, the linked Apache projects seems to have nothing
alike any more (at least Wicket / Tapestry last time I checked).

I'd vote to drop
- Related Projects
- Similar Projects
- Java 5 for Struts 1 (Strecks)

> 
>>
>>> 4.) The Link to "Our Blogs" looks also really outdated! Last Entry is
>> from
>>> 2008.
>>> http://people.apache.org/~rubys/planet/struts/
>>
>> We can add few new, like your :-)
>>
> 
> That planet link is long-obsolete. See instead:
> 
> http://blogs.apache.org/
> 
>

Since there isn't too much going on regarding Struts even at blogs.a.o,
I'm in favor for dropping the "Our Blogs" link.

>>
>>> 5.) Is the Struts Sourceforge active? Never heard about it.
>>> http://struts.sourceforge.net/
>>
>> I've been using it some times ago, but not any more but I think it
>> should stay :-)
>>
> 
> Yeah, it should stay. It's where we can point non-committers to check in
> Struts-related code, if they so wish.
> 

Hmm - diving a bit into http://struts.sourceforge.net/, frankly it looks
like a zombie to me. All Getting Involved -> Repository links (CVS) I
tried were broken. Is there any recent activity? Wouldn't it be better
to link https://github.com/apache/struts2 instead? It should at least be
linked in addition.

Additional thoughts:
- we should not only incorporate the twitter button but also G+ and
Facebook buttons pointing to the respective Struts pages.
- Development->Source Code and Development->Source Repository should be
merged
- dropping pages does not necessarily mean removing them - as for
historic reference (and bookmarks), those pages might still be deployed
but no longer referenced from the menu

> --
> Martin Cooper
> 
> 
>>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
>> For additional commands, e-mail: dev-h...@struts.apache.org
>>
>>
> 

-- 
René Gielen
http://twitter.com/rgielen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Reply via email to