Evening All,

With all due respect to the suspended projects and their
owners/leaders/contributors, I agree. 

To the new visitor to the site, I would have thought the latest news is
PXE being updated a year ago, not ver. 3 of Bering uClibc being released
last month.  If you look in the Announcements section on the right side,
pxeinstall update, release of pxeinstall, Bering flying high....?  A
four year old story is in the top three of the announcements? 
pxeinstall updated is the only one that's relevant in that it was
updated in August of 2006 but doesn't show on the front page
announcement.  Shouldn't the actual announcement of Bering uClibc 3.0
being released be the top one?

I would think new and potential new users would find this easier to get
relevant information if Bering uClibc was moved to the forefront since
that's where the energy is being expended.

I think a redesign of the site is in order to highlight the active
project(s).  I would propose the links along the top be ordered
something like this:
Home (instead of LEAF...or at least LEAF-Home), Bering uClibc,
Historical / Archived (or something similar), Developers

Then, move the various suspended/archived projects under the Historical
link with a tree under that page leading to the various projects. 

I would then update the announcements section to highlight what's
actually been happening the past six months, not what happened in 2003
and 2002.


These are just my observations as a user and promoter, not intending to
wee wee in anyone's cornflakes.   :-)

Thanks,

Tony






KP Kirchdoerfer wrote:
> Hi;
>
> while doing some maintenance on the LEAF Bering-uClibc website, I've looked 
> into the other pages announcing other works under the LEAF umbrella:
> Bering, Oxygen, Lince and Wisp Disk.
>
> I know Bering has been more or less officially stopped  - at least J. Nilo 
> announced that he quits developement and none took th etourch since he left 
> Bering.
> Oxygen is put on very deep hold - David Douthitt from time to time explains 
> interest that something will happen, but then it stops. 
> I was always a bit mis-informed about Lince and WISP-Disk, but looking at the 
> actual pages I see, nothing happended in the last three years. The pages are 
> done Mike Noyes during transition to the actual CMS environement.
>
> I consider all the above derivatives as abandoned - if you want numbers look 
> at the FRS - the latest Bering release was in 2003,  the same probably for 
> Lince and Wisp Disk, Oxygen even more back.
>
> Correct me if I'm wrong.
>
> >From a website visitors view the LEAF pages looks like a graveyard of ideas 
> and projects  - 4 out 5 projects does not show a life sign since 2004 - which 
> is twelve "internet years" ago.
>
> Only one is active, but that isn't reflected on the main page...
>
> I get a bad feeling, to find an active project I'm part of in a row of and 
> buried under corpses.  
>
> Does anyone else feel uncomfortable with this situation and representation of 
> the LEAF project?
>
> kp 
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
> _______________________________________________
> leaf-devel mailing list
> leaf-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/leaf-devel
>
>   


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to