Hi,
Kai Backman wrote:
- Change the upper tab on the frontpage from "Contributing" to
"Developers" and make it link to development.oo.org
I believe we had this discussion going on earlier. The thing with
"Developers" as menu-item is that it won't really attract people who
want e.g. to write documentation or translate OOo in other languages.
The fact that developers won't instantly recognize contributing as the
link they could be interested in... I'm not so sure whether that is a
major issue. That said, the contributing page can be improved and so can
the development pages.
- Fix development.oo.org to be the landing page for everyone
interested in working with OO.o (localization folks, UNO devs,
marketing, C++ devs).
That is actually what contributing.OOo is for. Contributing is more generic.
We should first sell the potential devs on OO.o by giving them
initial concrete successes and only then start presenting all the
different variations of contribution.
Could you explain what you have in mind when you are talking about
"initial concrete successes"?
So how does the process work here, assuming I already have commit access?
Probably we'll be discussing it first on this list a bit since it
affects a lot of different pages. It may also be somewhat troublesome
that different sub domains can be handled by different projects (not
sure who's responsible for the contributing subdomain (I'm only a
web-dev contributor)). Suggestions can be made by uploading websites to
either your own hosting space or OOo's and/or simply by adding comments
to a discussion. I'd suggest/prefer first discussing it, creating
somewhat of a plan, and then get to prototyping soon. Thus first get the
plans straight. Prototypes always generate new discussion.... so that
process will repeat a couple of times. When we agree, someone will need
to get it in place who has write access to that specific area.
I feel more like what kay is saying:
So, two things come to mind immediately...Fix up
http://contributing.openoffice.org/programming.html
(I'd would propose fixing up the whole contributing page, which is so
style-wise really outdated)
and fix up the main development page
Well, first I'd like to know what it's function is... now
development.ooo also features links to writing documentation, making
localisations and qa. Though they might be related somehow, I'd keep it
more on track (and split tracks on the contributing page already). Next
I believe (but I'm not a programmer) there should be made a better
distinction between core c++ development (and maybe a bit of Java... )
and developing applications on OOo (from macros to converters) or
connecting to the OOo-software. This is all kind of mixed up at the
moment. But maybe I'm too much uninformed and is this view simply stupid.
I'd suggest:
0. Define the functions of the pages (and maybe rediscuss whether
contributing is the best description on the home page (i believe so))
1. Redesign the whole contributing.ooo area (guess we could try to make
it fit all on only one page; introduction is often or obsolete or too
detailed)
2. Gather/propose suggestions for the development page (but guess some
other group discusses/person desides for its content)
3. Maybe propose a redesign for the development page that can be
implemented (but speaking for myself, I know too little of what can be
found there)
I've got to disappoint you at this moment, since I'm busy finnishing a
project... but I'll be happy to join the discussion.
Yours,
Maarten Brouwers
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
