Re: netbeans.org design changes

Hello Manfred,

Manfred Riem wrote:
> Well, here it goes then :-)

:-)  Thanks for writing.  These are good ideas -

> 1. Move the Edge newsletter to a project so it can be browsable as
> edge.netbeans.org.
>    By doing this you can also have Edge editors without them needing access
> to the 
>    whole webspace. 

Very true, and that is a problem right now.  However ... :-)  I
have another plan ... I'm not sure if this will be possible,
but I was wondering if we could set up a web-admin based tool
on our netbeans.info host (where we are able to do PHP/MySQL
stuff), to replace the whole CVS/XML setup completely.  That
way any (authenticated) person with a browser could work on
translations, no XML knowledge required, no CVS account required.
It would also, I hope, make it easier for translation teams to
split up the work - the tool would easily allow you to translate
just one story from an issue.

What do you think ?  I stress that this is just an idea now, I
am sure there are some issues I haven't thought about; even if
we decide to do that it is months away at least.

> 2. Use the <modulename>.netbeans.org more to get information out. A module
> owner will
>    be more involved once people start 'complaining' about the documentation.

I am 100% in support of this idea, I really think this would help
things.  The problem has always been getting development teams to
spend time/effort on their websites.  Some teams do of course, some
of the module sites are great.  But certainly not most.

> 3. Make the planning documents for 4.0 and later more prominent.
> 
> 4. Move everything that is older than 2 years to an archive, I know, touchy,
> but people
>    don't like to have to go through documents that are obsoleted.

Agreed on both.  Let's try to address these going forward ...

Thanks for the ideas!

-- 
Jack Catchpoole
NetBeans/Sun Microsystems
http://www.netbeans.org/