Hi Martin, > :murb: [maarten brouwers] wrote: >> Hi Martin, >> >> Interesting subject... >>> We are dealing with two different interpretations of a project: >>> >>> a static project like API, Wordprocessor, Impress, Base, etc. >>> >>> The IMHO more interesting interpretation of a project is the project >>> management point of view: a project is a clearly described effort to >>> achieve something in a certain timeframe. >> Is that what you refer to as 'Teams'? > No, that's what listed in the category Projects, such as the > Implementation of new Extension like the MediaWiki, PDF-Import one or > the MacOSX port.
Was kind of confusing "Project" and "Projects" ... maybe "Projects" should be renamed... the word "Teams" actually seems, to me, like a better term here... A Team to me is not that official, loosely connected people that 'teamed up' together to fix a certain issue. But I might be wrong, since I'm not a native speaker of English. Maybe what you are currently referring to as teams are more like "supporting bodies" or "Interproject efforts"... (maybe someone speaking native english can jump in here?) The thing is that if wording is confusing in some structure... the whole structure is not much of use to a newcomer. > >>> Have a list of active project would point to the area where the >>> current development effort are. That's why I introduced also the >>> Category Projects to allow listing also of such Projects. >>> >>> I'm unsure if we really need project in the sense of a static project: >> That is, we don't need projects on the wiki, or in general? I like >> projects because they are giving some context to what is happening >> there. A place to start. And having defined projects doesn't stop people >> from collaborating... look at e.g. art/marketing and the website >> project. > Yes, but we actually have the problem that in most static project > described on the website only the big dynamic projects are listed. In > the best case there is a link into the wiki, where more projects may be > listed. This is a bit confusing, the distinction between 'Project' as an accepted project, and 'Projects' as more dynamic, but temporary., cooperation between people to solve a certain issue. What you want to improve is the visibility of these dynamic cooperative efforts, right? And as for the wiki, you do not care that much about the big accepted projects (with their project leads etc). This type of information belongs on the regular website. If I have interpreted it correctly I think our thoughts are well aligned :) About the new Main Page you proposed, it seemed a bit too much trying to repeat the efforts of the static homepage (which we are currently working on). But then it is mainly about the headers used, not about the actual content. Maybe you could try to make it look a bit more developer centric? > No, the preparation for the publication should be done in the wiki, > static content I'd like to move to the website where better performance > can be expected. That is exactly how I like to see the wiki. (...) > Without providing a structure and then also using that > structure these page will stay as is: A private worksheet. Even worse: > If potential new developers will get to wiki and search for information, > he might have the chance to find some via the wiki search function but > he don't know what he will get: Is that what he is reading a brain dump > from whatever person some time ago, is that information still valid, is > it complete, is it correct ? He will not have any chance to find this > out without a structure. I have nothing against structure... but I was just expressing my concerns that it might become as structured as the normal website... that it might even replace the normal website in functionality. I see them as two different things that complement each other... but so do you :) > please see also in > http://wiki.services.openoffice.org/wiki/Information_Sharing > the problem statement: > http://ux.openoffice.org/reports/2007/website/InfoSharing.odp Actually I will stop here... I will spend my available time now on the main page... g., Maarten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
