Hi,
Why are templates part of the documentation project? Shouldn't they
rather be with art.oo.o?
No. Templates are here from the beginning. If Marketing, and hence the
subproject art, feel that theirs is a better place, the leads of the
marketing project can ask.
I am not asking why they were where they are. I am asking if
templates are a logical part of documentation.
Why not? On-line help is sort of in this category in that it has been
closed until recently and seems to me to be less open than it might be.
Firstly, this is not about how "open" or "closed", how easy or hard
to contribute a thing is. This project is called "documentation" so
it should encompass every piece of OOo that delivers documentation
to the user or the developer.
Secondly, the so-called online help has been open for years. The
mere fact that contributing is more difficult because it uses
a special format, is compiled like the source code and is integral
piece of the source code base doesn't make it any less open.
In that sense, having it in the doc project, which is open to
contributions, is a bit strange too, Don't you think or is there some
other item on the agenda?
Online Help is open for contributions. Why are you
implying that it isn't?
[...]
What is the doc project's purpose? Provide help for users
of OOo in form of documentation of any kind and attract
contributors helping to improve that documentation. Do we
have a charter? Maybe I misunderstood that.
Perhaps you first message was not clear. If seemed to me that you were
suggesting that we fragment things even more than they are. No offence.
No, I wasn't talking about fragmentation. I was talking about
structure. I was trying to think as a new user coming to the
doc.oo.o site seeking help. I would like to guide these help
seekers to documentation easily and separate them from the ones
who would like to contribute (maybe have the seekers contribute
themselves later on, too).
From a *contributor's* point of view, it makes sense to present
documentation split up by presentation channels, like Guides,
Howtos, FAQs, Setup Guides, Online Help and whatnot.
As a *user* looking for help, I don't care *where* my information is,
I just want to find it. Thus, a consolidated approach guiding the
user to the information seems to make more sense to me.
In the first step, we should ask the visitor whether he/she
a) is looking for help on using OOo
b) wants to contribute to the doc.oo.o project
In case of a), let them
1) search the complete documentation for their problem
2) browse documentation type by type
In case of b), let them
1) easily join the project and give instructions on how
to contribute, what needs to be done etc. Pretty much what
we already have on the front page
2) get to a "workspace" where they can start contributing.
This is the sort of structure I was thinking of.
Perhaps you could propose to the council that a new project be created.
This, of course, would mean many changes to Issue Tracker to accommodate
such an event.
No. What a strange idea to separate online help from the rest
of docs. Would you also make a new project for the FAQs?
Ok. Then your suggestion is equally strange. Templates are an integral
part of how we use OOo and aren't we fragmented enough. Afterall the
templates we have had, not counting those from the contest, were
accumulated from the start of the project. So back to why we need yet
another fragmentation. Also, I should like to point out that a
invoice template is hardly and art form :-)
Fair enough. I understand that templates are historically with us.
I don't want to get rid of them, and I don't want to fragment.
I was just questioning if doc.oo.o is their natural home from
the view point of a user.
Apart from that, I have seen lots of invoices that present a
sufficient degree of creativity to be called art ;-)
Aurélien, if you have any ideas about the "more modern way of
presenting", maybe we can use that for a consistent presentation
of the doc.oo.o pages?
I have not read Aurelien's intro yet but think that any ideas presented
should be considered. However, who is going to implement them? Aurelien,
do you wish to take on the task?
Why not put planning before implementation and discuss what
the scope of such a project would be and agree on changes first?
I has been discussed and IIRC, you were going to help. (See the links in
my message to Aurelien) Seems that we still have no screenshots.
Yes. That's why I raised that here again. I think we should work on
a structured revamp of the pages. I see if I can get a proposal up.
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
