Hello,
I'm going to be trying your software and noticed that you need some
documentation help. I've attached the link to my web-site as an introduction;
I'd be glad to offer some pro-bono assistance if needed:
http://www.prodocumentation.com/index.php?p=1_4_Documentation
I look forward to pla
Dear Open Representative,
I am a veteran of the computer industry. I started as a programmer and worked
my way to Vice President of a small consulting company. I have written user
handbooks for technical people as well as the end user. I am currently teaching
English as a Second Language to inte
Hi,
I am a Technical writer with 13 years' experience. I would like to
contribute to this community by writing user guides and "how to"
documents. How do I start?
--
Thanks.
Regards,
Kavitha.
Mobile: 9791060689
--
-
To unsubscribe
For those of you who may wish (as I do) to work on docs for LibreOffice
as well as for OpenOffice.org, there is now a list called
documentat...@libreoffice.org
subscription with: documentation+subscr...@libreoffice.org
digest subscription with: documentation+subscribe-dig...@libreoffice.org
archiv
Hi
I am a proofreader and copy editor, but not a programmer. I would be
interested in helping when the User Guide is at either the editing or
proofreading stage.
Ann Haslam
-
To unsubscribe, e-mail: dev-unsubscr...@documen
Hi Jean, Andy,
Am Fri, 02 Apr 2010 07:02:39 +1000
schrieb Jean Hollis Weber :
> Andy Brown wrote:
> > Jean Hollis Weber wrote:
> >> I'll be writing some other notes to this list about this work, and
> >> the organisation, and the help I would like to get from others,
> >> and whether we should c
Jean Hollis Weber wrote:
Andy Brown wrote:
Jean Hollis Weber wrote:
I'll be writing some other notes to this list about this work, and
the organisation, and the help I would like to get from others, and
whether we should change what we're doing, etc. Meanwhile, for anyone
interested, the webs
Andy Brown wrote:
Jean Hollis Weber wrote:
I'll be writing some other notes to this list about this work, and the
organisation, and the help I would like to get from others, and
whether we should change what we're doing, etc. Meanwhile, for anyone
interested, the website is: http://friendsofop
Jean Hollis Weber wrote:
I'll be writing some other notes to this list about this work, and the
organisation, and the help I would like to get from others, and whether
we should change what we're doing, etc. Meanwhile, for anyone
interested, the website is: http://friendsofopendocument.com/
The
In a recent note I referred to the evaluation going on at OOo
Marketing regarding the marketing plan, and the discussion thread on
that topic. One of Lars's posts includes a reference to OOoAuthors:
http://marketing.openoffice.org/servlets/ReadMsg?list=dev&msgNo=29827
He says in that post:
"Doc
Hi Claire,
Claire Wood schrieb:
Hi
Can anyone help me either tonight or tomorrow (Tuesday). I have a job
interview on Wednesday and part of hte criteria is knowledge of
documentation translation processes. Can anyone give me an indication of
what it is at OOo so I can use that as an example?
Hi
Can anyone help me either tonight or tomorrow (Tuesday). I have a job
interview on Wednesday and part of hte criteria is knowledge of
documentation translation processes. Can anyone give me an indication of
what it is at OOo so I can use that as an example? Is there a place on the
wiki that
many or most faqs are very out of date & need to be updated. Sometimes
best solution is to write a sentence or two & point to another wiki
page where it's discussed in detail. Or marked applies to version 2 or
whatever is relevant. Or even deleted -- some go back to v1. -- Jean
On Friday, February
Dear All
I have added an item for discussion to the following link because I could
not follow the instructions on the page. I think they refer to a previous
version of OOo.
http://wiki.services.openoffice.org/wiki/Documentation/FAQ/Writer/FormattingText/How_do_I_remove_the_dictionaries_I_don%27t
On 02/11/2010 01:35 PM, Claire Wood wrote:
> Hi All
>
> Not sure if you want us to report whether something is old or not, so here
> goes.
>
> I read through this question and followed the procedures. I think it is old
> because 3.2 doesn't have those glitches, you can clearly see the menu
> opt
On 02/11/2010 01:42 PM, Claire Wood wrote:
> Hi All
>
> I've checked this document and it is OK.
>
Hi Claire.
Thanks for looking over the FAQs :-)
If you find one that is tagged to be checked for accuracy and style, and
after you review it, you find it's OK, then you can remove the Wki code
th
Hi All
I've checked this document and it is OK.
--
Best wishes
Claire Wood
Hi All
Not sure if you want us to report whether something is old or not, so here
goes.
I read through this question and followed the procedures. I think it is old
because 3.2 doesn't have those glitches, you can clearly see the menu
options in the Edit Menu and Compare options.
I'm not sure wh
On Wed, 25 Nov 2009 20:02:16 +0100
Clayton wrote:
> > From other wikis I'm used to expect Category Entries at the top of
> > the page, not at the bottom. It makes life much easier ;-)
>
> Do you mean the [[Category]] entry?
>
> I don't think there is any rule one way or the other on the OOoWiki
Somewhere along the line, people added Category coding to the bottom
of the page.. ...
It (bottom) is recommended practice on Wp, and Category shows up at the
bottom of both preview and regular-view pages.
--
/tj/
-
To unsubs
On Wednesday 25 November 2009 20:02, Clayton wrote:
> > From other wikis I'm used to expect Category Entries at the top of
> > the page, not at the bottom. It makes life much easier ;-)
>
> Do you mean the [[Category]] entry?
Yep
> I don't think there is any rule one way or the other on the OOoWi
> From other wikis I'm used to expect Category Entries at the top of the
> page, not at the bottom. It makes life much easier ;-)
Do you mean the [[Category]] entry?
I don't think there is any rule one way or the other on the OOoWiki.
Somewhere along the line, people added Category coding to the
On Wednesday 25 November 2009 18:54, T. J. Frazier wrote:
> Nino Novak wrote:
> >> # Documentation/DE/How Tos/Filme in Impress unter Linux ohne Java
> >
> > done.
>
> Maybe not quite. Still shows in Cat:Doc.
:-/
From other wikis I'm used to expect Category Entries at the top of the
page, not at
Nino Novak wrote:
# Documentation/DE/How Tos/Filme in Impress unter Linux ohne Java
done.
Maybe not quite. Still shows in Cat:Doc.
--
/tj/
-
To unsubscribe, e-mail: dev-unsubscr...@documentation.openoffice.org
For addition
On Wednesday 25 November 2009 15:38, Clayton wrote:
> Nino: Would you be able to take care of correcting the categories on
> the orphaned DE pages?
> # DE/Documentation/OOo3 User Guides
> # DE/Documentation/OOoAuthors User Manual
done
> # Documentation/DE/Dashboard/TestPage
It's a l10n test Pa
I've been working my way through the Documentation Category,a nd am down
to just a few more pages that need a proper home.
http://wiki.services.openoffice.org/wiki/Category:Documentation
Nino: Would you be able to take care of correcting the categories on
the orphaned DE pages?
# DE/Document
amaloney wrote:
Did I use the incorrect forum for these?
http://www.nabble.com/OOo3-Documentation-Margins-td20047732.html
http://www.nabble.com/Documentation---US-Letter-Size-td20047589.html
Al,
I just looked at your questions. The PDFs of the OOo3 user guides
produced by OOoAuthors are des
amaloney wrote:
Did I use the incorrect forum for these?
http://www.nabble.com/OOo3-Documentation-Margins-td20047732.html
http://www.nabble.com/Documentation---US-Letter-Size-td20047589.html
There are numerous forums for OOo on the web but I would
suggest that you use the "official" one:
http
Did I use the incorrect forum for these?
http://www.nabble.com/OOo3-Documentation-Margins-td20047732.html
http://www.nabble.com/Documentation---US-Letter-Size-td20047589.html
Al Maloney
--
View this message in context:
http://www.nabble.com/Documentation-Format-tp20073200p20073200.html
Sent
On 09/28/08 00:43, Jean Hollis Weber wrote:
Uwe Fischer wrote:
do you think we have enough documentation about using OOo in different
languages, writing systems, locales?
...
Jonathon Blake wrote a document titled OOo in a Multi-Lingual
Environment, but I don't know where the latest iterat
Uwe Fischer wrote:
do you think we have enough documentation about using OOo in different
languages, writing systems, locales?
No, I don't think we have enough of that type of documentation.
The application help just covers the very basics. Look for the index
word "CTL" in the installed help
Hi,
do you think we have enough documentation about using OOo in different
languages, writing systems, locales?
The application help just covers the very basics. Look for the index
word "CTL" in the installed help, for example, or search for "Asian"
keyword.
This certainly is not sufficient i
Arthur Buijs wrote:
Jim Harris schreef:
[...]
But is the wiki the right way to go? How often will different versions
of the different manuals be published for download. How will formatting
work be done? The wiki involvs excellent tools for discussion and a
really simplistic way of editing, but
Jim Harris schreef:
[...]
But is the wiki the right way to go? How often will different versions
of the different manuals be published for download. How will formatting
work be done? The wiki involvs excellent tools for discussion and a
really simplistic way of editing, but the content is actua
Hi,
Scott Carr schreef:
Frank Peters wrote:
Per Eriksson wrote:
[...]
I don't know how to handle document repository and versioning as
such, collab.net does not appear to offer anything useful out of the
box and
mediawikis capabilities are very limited here, too.
Maybe limited, but I th
On 6/23/07, Jean-Francois Nifenecker <[EMAIL PROTECTED]>
wrote:
Frank Peters a écrit :
> Per Eriksson wrote:
>> But is the wiki the right way to go? How often will different versions
>
> I'm not sure but I would like to evaluate that. For some info types it
> will definitely be the right way to
Frank Peters a écrit :
Per Eriksson wrote:
But is the wiki the right way to go? How often will different versions
I'm not sure but I would like to evaluate that. For some info types it
will definitely be the right way to go (FAQs, Howtos, Application
Help, all that modular stuff).
I think a
On 6/20/07, Frank Peters <[EMAIL PROTECTED]> wrote:
Oh, if there is a way to view/download/print the entire "manual",
there wouldn't be a need for PDF per se. All I'm saying
is that we need an offline delivery channel that will enable users to
download and print a manual (collection of pages). I
Frank Peters wrote:
Per Eriksson wrote:
I personally agree this is better than uploading files to issues.
To be honest, I don't like the fact that we use issues to track docs
anyway. Issuetracker is bulky and obscure. I would strongly vote for
having
a readily visible dashboard with links to p
Frank Peters wrote:
...
Joe, thank you, thank you for bringing that up and pointing to the
elephant. There is much truth to what you write and actually I
think we need to revisit the documentation "strategy" for OOo,
meaning how will we produce, maintain, and publish documentation.
...
Readin
Jim,
Frank, when you have time, please elaborate a bit for everyone about the
conditions / situation ("case"), and reasons, you "still think that in this
case, PDF is the way to go", specifically, the source (online) system and the
benefits gained from the extra work of maintaining PDFs (perhaps
Jean Hollis Weber wrote:
I agree that topic size may actually be an issue. If you split books by
chapter, the individual chapters may get too big to handle via wiki.
Maybe you need to get more granular.
I've started splitting some of the larger chapters of the OOoAuthors
guides into sub-chapt
Frank, when you have time, please elaborate a bit for everyone about the
conditions / situation ("case"), and reasons, you "still think that in this
case, PDF is the way to go", specifically, the source (online) system and the
benefits gained from the extra work of maintaining PDFs (perhaps on
I think you missed the part where I said "(or printed)".
Jim
>>> [EMAIL PROTECTED] 6:36:17 PM 6/19/2007 >>>
Frank Peters wrote:
> Jim Harris wrote:
>
> > In "... many users still value a [book-type] manual that they can download,
> > print out and read offline. So there is still the need for
Frank Peters wrote:
I agree that topic size may actually be an issue. If you split books by
chapter, the individual chapters may get too big to handle via wiki.
Maybe you need to get more granular.
I've started splitting some of the larger chapters of the
OOoAuthors guides into sub-chapters,
Per wrote:
But is the wiki the right way to go?
How often will different versions of the different manuals be
published for download.
a) If WikiMedia is used, one can archive key pages for a specific
version of OOo.
For example:
* Stylist:
* Stylist_1.0
* Stylist_1.1
* Stylist_1.2
* Stylist_1
Per Eriksson wrote:
But is the wiki the right way to go? How often will different versions
I'm not sure but I would like to evaluate that. For some info types it
will definitely be the right way to go (FAQs, Howtos, Application
Help, all that modular stuff).
of the different manuals be publis
Frank Peters wrote:
> Jim Harris wrote:
>
> > In "... many users still value a [book-type] manual that they can download,
> > print out and read offline. So there is still the need for creating PDF
> > files", I agree with the goals and premise, but not the conclusion.
> >
> > This is one of my "
Per Eriksson wrote:
I personally agree this is better than uploading files to issues.
To be honest, I don't like the fact that we use issues to track docs
anyway. Issuetracker is bulky and obscure. I would strongly vote for having
a readily visible dashboard with links to project pages on the wi
Jim Harris wrote:
In "... many users still value a [book-type] manual that they can download,
print out and read offline. So there is still the need for creating PDF
files", I agree with the goals and premise, but not the conclusion.
This is one of my "pet peeves" about most help-style document
In "... many users still value a [book-type] manual that they can download,
print out and read offline. So there is still the need for creating PDF files",
I agree with the goals and premise, but not the conclusion.
This is one of my "pet peeves" about most help-style documentation: When the
Frank Peters wrote:
> Per Eriksson wrote:
>
> >> Sorry to bring up such a rude question...
> >
> > Thank you Joe,
> >
> > There is nothing I value higher than feedback!
> >
> > Scott Carr and Frank Peters, are there any possibilities to start
> > looking for a Pootle-like web-based document man
Per Eriksson wrote:
Sorry to bring up such a rude question...
Thank you Joe,
There is nothing I value higher than feedback!
Scott Carr and Frank Peters, are there any possibilities to start
looking for a Pootle-like web-based document management solution?
I personally agree this is better t
I'm mostly a lurker here; I wish I had more time to contribute.
As something of an observer, it seems to me that there's an elephant in
the room.
OOo--Writer is what we're talking about of course--is a fine tool for
writing a book, or a PDF version of a book. But books, printed or PDF,
are n
Joe Smith wrote:
> Per Eriksson wrote:
> > ...
> > First off, typographical conventions are great. They make the content
> > easy to read, prevent that meanings are interpreted wrong and increase
> > the readability. It also makes the documentation look better and more
> > professional. Our documen
Per Eriksson wrote:
...
First off, typographical conventions are great. They make the content
easy to read, prevent that meanings are interpreted wrong and increase
the readability. It also makes the documentation look better and more
professional. Our documentation today use some conventions in
Hello!
I have been thinking of the documentation that has been published by the
community the last year, and have some thoughts to share with you all.
Some thoughts have arisen when reading books on other areas aswell as
Suns documentation for the StarOffice 8 product.
First off, typographical co
Louis Suarez-Potts wrote:
Jean Hollis Weber wrote:
OOoAuthors work is currently licensed under CC-BY 2.5 or later (we'll
be progressively updating this to say 3.0 or later).
I was thinking of that license, too.
To allow for the possibility of this material being placed on the wiki
with minim
Hi,
On 2007-04-04, at 17:02 , Jean Hollis Weber wrote:
Frank Peters wrote:
Louis Suarez-Potts wrote:
Frank Peters wrote:
I would second Andre in allowing wiki pages to specify a license
and have a default license for pages that do not specify the their
license.
That seems good to me, too...
G. Roderick Singleton wrote:
Search just plain sucks. See
http://qa.openoffice.org/issues/show_bug.cgi?id=52046
In spite of the open issue, nothing has improved.
Search on the main OOo website definitely sucks. Even if it
worked well (which it doesn't) for the HTML pages on the site, I
don'
Frank Peters wrote:
Louis Suarez-Potts wrote:
Frank Peters wrote:
I would second Andre in allowing wiki pages to specify a license
and have a default license for pages that do not specify the their
license.
That seems good to me, too... But I'd rather not allow for even the
possibility of p
Andre wrote:
> Initially, it will result in a significant decrease in the number of
> FAQs. However, it will clear up the licensing issue. It should also
> ensure that the information is applicable for current (2.0) versions
> of OOo.
If this is the only way, I'd rather live with the non-perf
Hi,
On 2007-04-04, at 14:10 , Andre Schnabel wrote:
Hi Jonathon,
Jonathon Blake schrieb:
For Drew, Louis,etc:
My suggestion would be:
* Close down the wiki for a couple of weeks;
* Add a script that requires a specific licence (or one of a set of
licences) to be used for all material submit
Hi André,
On 2007-04-04, at 13:23 , Andre Schnabel wrote:
Thus,
"Content posted after [date] is Public Domain except where
otherwise noted, in which case copyright holders may use the
Public Document License (PDL), as noted in the License page of
OpenOffice.org, http://www.openof
Hi Jonathon,
Jonathon Blake schrieb:
For Drew, Louis,etc:
My suggestion would be:
* Close down the wiki for a couple of weeks;
* Add a script that requires a specific licence (or one of a set of
licences) to be used for all material submitted;
* Delete all existing content from the wiki;
* Ope
Doug wrote:
* My opinion: the OOo wiki is a public domain forum. I couldn't care
The major problems with claiming public domain are:
* Several major countries do not recognize the concept;
* For countries that do recognize "Public Domain", putting material in
the public domain from the date o
Hi Louis,
Louis Suarez-Potts schrieb:
That seems good to me, too... But I'd rather not allow for even the
possibility of proprietary licenses on the wiki, which the wording
suggested seems to permit, as does our current wording. Ie, I want
open licenses.
whatever is meant by proprietary lic
On Wed, 2007-04-04 at 08:52 +1000, Jean Hollis Weber wrote:
> marbux wrote:
> > +1. Copyrighted material can be parked on another site and linked from
> > the wiki.
>
> Quite true, and that's more or less the situation we have now
> with the Docs website: it links to material that for various
>
Louis Suarez-Potts wrote:
Hi,
On 2007-04-04, at 06:10 , Frank Peters wrote:
Andre Schnabel wrote:
So, I'd be happy with posting something like, "Content posted after
[date] is licensed in accordance with OpenOffice.org's license
policy, which can be found at
http://www.openoffice.org/licens
Hi,
On 2007-04-04, at 06:10 , Frank Peters wrote:
Andre Schnabel wrote:
So, I'd be happy with posting something like, "Content posted
after [date] is licensed in accordance with OpenOffice.org's
license policy, which can be found at http://www.openoffice.org/
license.html. Content posted
Andre Schnabel wrote:
So, I'd be happy with posting something like, "Content posted after
[date] is licensed in accordance with OpenOffice.org's license policy,
which can be found at http://www.openoffice.org/license.html. Content
posted prior to this date is copyrighted Sun Microsystems and
Hi Louis,
Louis Suarez-Potts schrieb:
André S. corrected it (some scorching involved--we both cite the same
issue, too) [0] and we returned to status quo ante. Except that I
think that there needs to be copyright info that is better than what
we have now but that we cannot retroactively dete
Le mardi 3 avril 2007 22:MM, marbux a écrit :
Hi Marbux,
> Like I said earlier, I have no work-around for the problem of
> recycling wiki content, at least none that isn't pretty intricate. I
> suspect that is why all wikis that can be edited by the public simply
> ignore the problem. The downsi
Hi,
Sorry for entering this late; I don't always scan this list.
We actually have (naturally) visited this issue. Early this year, it
was brought to my attention that there was no really informative
copyright information and guidance for the wikis, and the idea I and
others had was that it
marbux wrote:
+1. Copyrighted material can be parked on another site and linked from
the wiki.
Quite true, and that's more or less the situation we have now
with the Docs website: it links to material that for various
reasons can't go on the OOo website itself.
Unfortunately, that's not the
On 4/3/07, DougT <[EMAIL PROTECTED]> wrote:
Drew,
You get all of my votes plus any extras I can find lying around.
Frank,
I understand your position, but not your resignation to the status quo.
* My opinion: the OOo wiki is a public domain forum. I couldn't care
less about what Wikipedia does
Drew,
You get all of my votes plus any extras I can find lying around.
Frank,
I understand your position, but not your resignation to the status quo.
* My opinion: the OOo wiki is a public domain forum. I couldn't care
less about what Wikipedia does with their material. If people want to
publi
On 4/3/07, Andrew Jensen <[EMAIL PROTECTED]> wrote:
> >
I've been reading along silently and now I would like to make a comment.
What the heck is all the fuss about?
Look, why is this an issue at all - if you post to a public wiki it is
in the Public Domain - maybe I am being naive but here is
Hi Andrew,
It's a nasty situation and it's particularly irksome that this
uncertainty hinders free development and doesn't help the user
a thing.
Frank
Hi,
I've been reading along silently and now I would like to make a comment.
What the heck is all the fuss about?
Look, why is this an is
Hi Andrew,
Andrew Jensen schrieb:
What the heck is all the fuss about?
About legal issues :-(
Look, why is this an issue at all - if you post to a public wiki it is
in the Public Domain - maybe I am being naive but here is how I feel:
maybe someone will come along and use something that I p
>
It's a nasty situation and it's particularly irksome that this
uncertainty hinders free development and doesn't help the user
a thing.
Frank
Hi,
I've been reading along silently and now I would like to make a comment.
What the heck is all the fuss about?
Look, why is this an issue at all
marbux wrote:
Modify the editing screen on the wiki with licensing options. Specify
the license you would prefer to have people use as the default. Give
options to select other popular licenses or to specify a license that
isn't in the small set of licenses listed with check boxes. Write a
routi
Jean Hollis Weber wrote:
On 26 March 2007, Frank Peters wrote:
Jean Hollis Weber wrote:
I am thinking about moving doc content from elsewhere (eg OOoAuthors
or my or others' own personal websites), where the existing material
is under Creative Commons license. If such material could stay under
Perhaps a way forward:
Modify the editing screen on the wiki with licensing options. Specify
the license you would prefer to have people use as the default. Give
options to select other popular licenses or to specify a license that
isn't in the small set of licenses listed with check boxes. Write
On 26 March 2007, Frank Peters wrote:
Jean Hollis Weber wrote:
I am thinking about moving doc content from elsewhere (eg OOoAuthors
or my or others' own personal websites), where the existing material
is under Creative Commons license. If such material could stay under
CC on the wiki, then tha
Frank Peters wrote:
Andre Schnabel wrote:
Hi,
Frank Peters schrieb:
Correct. But again - this situation is caused by the way, the wiki
started. As it started without licensing resctrictions, only the
Copyright is relevant.
The wiki copyright page states
"Copyright 1999-2007 by the contrib
Andre Schnabel wrote:
Hi,
Frank Peters schrieb:
Correct. But again - this situation is caused by the way, the wiki
started. As it started without licensing resctrictions, only the
Copyright is relevant.
The wiki copyright page states
"Copyright 1999-2007 by the contributing authors and Sun
Hi,
Frank Peters schrieb:
Correct. But again - this situation is caused by the way, the wiki
started. As it started without licensing resctrictions, only the
Copyright is relevant.
The wiki copyright page states
"Copyright 1999-2007 by the contributing authors and Sun Microsystems,
Inc."
Jean Hollis Weber wrote:
Frank Peters wrote:
Creating new documentation content
If we create new documentation content on the wiki, it must be
created using the PDL to be compatible with doc.oo.o
If the documentation *stays on* the wiki and is not moved to doc.oo.o,
then it should not need to
Frank Peters wrote:
Creating new documentation content
If we create new documentation content on the wiki, it must be
created using the PDL to be compatible with doc.oo.o
If the documentation *stays on* the wiki and is not moved to
doc.oo.o, then it should not need to be created using the PDL.
Hi André,
[...]
So that means that all pages on the wiki that currently
don't have an explicit license note carry no license at all
and that anyone who wants to reuse the content in any form
needs to contact the copyright holder for approval?
Correct. But again - this situation is caused by t
Hi Frank,
Frank Peters schrieb:
Andre Schnabel wrote:
Interesting discussion, and necessary, too. We need to look
at how we can make the wiki usable for documentation purposes
either by changing the licensing of the wiki or the docs.
I see no reason to change the licensing at the wiki, as t
Jean Hollis Weber wrote:
Andre Schnabel wrote,
No -this does not answer any question. The wiki has been
established without any licensing restrictions.
Frank Peters wrote:
We need to look at how we can make the wiki usable for
documentation purposes
Is there any reason why the wiki cann
Andre Schnabel wrote:
Interesting discussion, and necessary, too. We need to look
at how we can make the wiki usable for documentation purposes
either by changing the licensing of the wiki or the docs.
I see no reason to change the licensing at the wiki, as there is no
explicit license.
So
Andre Schnabel wrote,
No -this does not answer any question. The wiki has been
established without any licensing restrictions.
Frank Peters wrote:
We need to look at how we can make the wiki usable for
documentation purposes
Is there any reason why the wiki cannot contain a "user
docume
Hi Frank, *
Frank Peters schrieb:
Interesting discussion, and necessary, too. We need to look
at how we can make the wiki usable for documentation purposes
either by changing the licensing of the wiki or the docs.
I see no reason to change the licensing at the wiki, as there is no
explicit
You seemed to have missed the point.
Ok, but I beg your pardon. As I'm not a native english speaker could you
make clear, what the point is? (Ok, I guess I know)
What goes on the wiki is fine by
me. However, as I pointed out, the only editable stuff permitted on the
documentation project mu
Hi,
G. Roderick Singleton schrieb:
You seemed to have missed the point.
Ok, but I beg your pardon. As I'm not a native english speaker could you
make clear, what the point is? (Ok, I guess I know)
What goes on the wiki is fine by
me. However, as I pointed out, the only editable stuff per
On Sun, 2007-03-25 at 17:12 +0200, Andre Schnabel wrote:
> Hi,
>
>
> G. Roderick Singleton schrieb:
> > Further, as a member of the CC I recommend that you implement the
> > changes necessary so that the documentation project can use material
> > generated on the wiki.
>
> I cannot heal things
Hi,
G. Roderick Singleton schrieb:
Further, as a member of the CC I recommend that you implement the
changes necessary so that the documentation project can use material
generated on the wiki.
I cannot heal things that have been missed whe the wiki started. So I
cannot apply any licensing t
1 - 100 of 113 matches
Mail list logo
