You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Tony Collen <co...@umn.edu> on 2003/11/24 21:28:28 UTC
Re: Moving docs from Wiki
BTW, when a page is moved, I think we should keep the page on the wiki, and perhaps keep a record of
when the last version was committed to CVS.
Blowing away docs (like the features list) isn't too useful, especially since I was going to point
to the version of the docs in the Wiki, and possibly make a bunch of revisions to the page. But
then I suppose I could just edit the new file in CVS and commit.
Tony
Re: Moving docs from Wiki
Posted by Upayavira <uv...@upaya.co.uk>.
Joerg Heinicke wrote:
> On 24.11.2003 21:55, Upayavira wrote:
>
>> Tony Collen wrote:
>>
>>> BTW, when a page is moved, I think we should keep the page on the
>>> wiki, and perhaps keep a record of when the last version was
>>> committed to CVS.
>>>
>>> Blowing away docs (like the features list) isn't too useful,
>>> especially since I was going to point to the version of the docs in
>>> the Wiki, and possibly make a bunch of revisions to the page. But
>>> then I suppose I could just edit the new file in CVS and commit.
>>
>>
>>
>> I agree that blowing away docs is bad. However, just leaving them is
>> pretty bad too.
>>
>> IMO, once a doc is moved to CVS, the original wiki page should be
>> replaced by a placeholder, which is where people can place comments
>> about the related page in CVS.
>
>
> From that point of view my solution must be really good in your
> opinion :-)
>
> http://wiki.cocoondev.org/Wiki.jsp?page=CocoonFeatures
Yup! Hadn't looked :-(
Regards, Upayavira
Re: Moving docs from Wiki
Posted by Tony Collen <co...@umn.edu>.
Bertrand Delacretaz wrote:
>
> Le Lundi, 24 nov 2003, à 22:00 Europe/Zurich, Joerg Heinicke a écrit :
>
>> ...From that point of view my solution must be really good in your
>> opinion :-)
>>
>> http://wiki.cocoondev.org/Wiki.jsp?page=CocoonFeatures
>
>
> hmmm..maybe we should push a little more towards patches?
>
> Instead of
> If you want to add further features or correct some issues please add it
> either here or provide a patch to the official documentation.
>
> I'd write
> You can still use this page for comments, but for content changes please
> provide patches as described in [MovedToCvs].
+1. I like the idea of having stuff gravitate more towards getting docs into CVS.. but sometimes I
just want to be able to flesh some stuff out on the Wiki. After enough revisions, I'd probably just
delete it and commit it myself, so we should just reccommend that patches be provided.
>
> WDYT?
>
Tony
Re: Moving docs from Wiki
Posted by Joerg Heinicke <jh...@virbus.de>.
On 24.11.2003 22:05, Bertrand Delacretaz wrote:
>
> Le Lundi, 24 nov 2003, à 22:00 Europe/Zurich, Joerg Heinicke a écrit :
>
>> ...From that point of view my solution must be really good in your
>> opinion :-)
>>
>> http://wiki.cocoondev.org/Wiki.jsp?page=CocoonFeatures
>
>
> hmmm..maybe we should push a little more towards patches?
>
> Instead of
> If you want to add further features or correct some issues please add it
> either here or provide a patch to the official documentation.
>
> I'd write
> You can still use this page for comments, but for content changes please
> provide patches as described in [MovedToCvs].
>
> WDYT?
No objection. Change it as you want to.
Joerg
Re: Moving docs from Wiki
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le Lundi, 24 nov 2003, à 22:00 Europe/Zurich, Joerg Heinicke a écrit :
> ...From that point of view my solution must be really good in your
> opinion :-)
>
> http://wiki.cocoondev.org/Wiki.jsp?page=CocoonFeatures
hmmm..maybe we should push a little more towards patches?
Instead of
If you want to add further features or correct some issues please add
it either here or provide a patch to the official documentation.
I'd write
You can still use this page for comments, but for content changes
please provide patches as described in [MovedToCvs].
WDYT?
Re: Moving docs from Wiki
Posted by Joerg Heinicke <jh...@virbus.de>.
On 24.11.2003 21:55, Upayavira wrote:
> Tony Collen wrote:
>
>> BTW, when a page is moved, I think we should keep the page on the
>> wiki, and perhaps keep a record of when the last version was committed
>> to CVS.
>>
>> Blowing away docs (like the features list) isn't too useful,
>> especially since I was going to point to the version of the docs in
>> the Wiki, and possibly make a bunch of revisions to the page. But
>> then I suppose I could just edit the new file in CVS and commit.
>
>
> I agree that blowing away docs is bad. However, just leaving them is
> pretty bad too.
>
> IMO, once a doc is moved to CVS, the original wiki page should be
> replaced by a placeholder, which is where people can place comments
> about the related page in CVS.
From that point of view my solution must be really good in your opinion :-)
http://wiki.cocoondev.org/Wiki.jsp?page=CocoonFeatures
Joerg
Re: Moving docs from Wiki
Posted by Joerg Heinicke <jh...@virbus.de>.
On 24.11.2003 21:58, Bertrand Delacretaz wrote:
>> ...I agree that blowing away docs is bad. However, just leaving them
>> is pretty bad too.
>>
>> IMO, once a doc is moved to CVS, the original wiki page should be
>> replaced by a placeholder, which is where people can place comments
>> about the related page in CVS.
>
>
> I have added a note about this at
> http://wiki.cocoondev.org/Wiki.jsp?page=MovedToCvs .
>
> Of course this can still be discussed here, but having the "rules" on
> the wiki should help.
>
> -Bertrand
Perfect, Bertrans :-)
Joerg
Re: Moving docs from Wiki
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le Lundi, 24 nov 2003, à 22:06 Europe/Zurich, Tony Collen a écrit :
> ...Would a centralized list of pages that were moved over (along with
> the last date they were moved) be useful to maintain?
If all moved pages point to
http://wiki.cocoondev.org/Wiki.jsp?page=MovedToCvs then the "Referenced
by" link of that page is your list ;-)
-Bertrand
Re: Moving docs from Wiki
Posted by Tony Collen <co...@umn.edu>.
Bertrand Delacretaz wrote:
> I have added a note about this at
> http://wiki.cocoondev.org/Wiki.jsp?page=MovedToCvs .
>
> Of course this can still be discussed here, but having the "rules" on
> the wiki should help.
I also put a note on the CocoonFeatures page about when it was last moved over to CVS, which is
useful. Would a centralized list of pages that were moved over (along with the last date they were
moved) be useful to maintain?
Or maybe that's too much to keep track of.
>
> -Bertrand
>
Tony
Re: Moving docs from Wiki
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le Lundi, 24 nov 2003, à 21:55 Europe/Zurich, Upayavira a écrit :
> ...I agree that blowing away docs is bad. However, just leaving them
> is pretty bad too.
>
> IMO, once a doc is moved to CVS, the original wiki page should be
> replaced by a placeholder, which is where people can place comments
> about the related page in CVS.
I have added a note about this at
http://wiki.cocoondev.org/Wiki.jsp?page=MovedToCvs .
Of course this can still be discussed here, but having the "rules" on
the wiki should help.
-Bertrand
Re: Moving docs from Wiki
Posted by Upayavira <uv...@upaya.co.uk>.
Tony Collen wrote:
> BTW, when a page is moved, I think we should keep the page on the
> wiki, and perhaps keep a record of when the last version was committed
> to CVS.
>
> Blowing away docs (like the features list) isn't too useful,
> especially since I was going to point to the version of the docs in
> the Wiki, and possibly make a bunch of revisions to the page. But
> then I suppose I could just edit the new file in CVS and commit.
I agree that blowing away docs is bad. However, just leaving them is
pretty bad too.
IMO, once a doc is moved to CVS, the original wiki page should be
replaced by a placeholder, which is where people can place comments
about the related page in CVS.
Regards, Upayavira
Re: Moving docs from Wiki
Posted by Upayavira <uv...@upaya.co.uk>.
Tony Collen wrote:
> Joerg Heinicke wrote:
>
>> The problem I saw (and because of this I removed the list) are the
>> missing diffs (or the bad usability with it) after further additions
>> to the page are made. Imagine in a half year you want to update the
>> page in the CVS, in the meantime there were 10 changes in the wiki
>> page, maybe someone reordered all the things! You can start from
>> scratch then or try to reproduce all the changes for the CVS version
>> - and this from version n to v. n+1, from v. n+1 to v. n+2 and so on.
>> After the removal of the list I think we have a cleaner approach.
>
>
> Hmm, then perhaps just a note of when the old docs were moved to CVS
> would suffice?
Exactly, and a reference to the new doc, and a space where people can
comment on the new doc. So only changes go on this wiki page.
Regards, Upayavira
Re: Moving docs from Wiki
Posted by Tony Collen <co...@umn.edu>.
Joerg Heinicke wrote:
> The problem I saw (and because of this I removed the list) are the
> missing diffs (or the bad usability with it) after further additions to
> the page are made. Imagine in a half year you want to update the page in
> the CVS, in the meantime there were 10 changes in the wiki page, maybe
> someone reordered all the things! You can start from scratch then or try
> to reproduce all the changes for the CVS version - and this from version
> n to v. n+1, from v. n+1 to v. n+2 and so on. After the removal of the
> list I think we have a cleaner approach.
Hmm, then perhaps just a note of when the old docs were moved to CVS would suffice?
>
> Joerg
>
Tony, can't think of a funny sig anymore.
Re: Moving docs from Wiki
Posted by Joerg Heinicke <jh...@virbus.de>.
On 24.11.2003 21:28, Tony Collen wrote:
> BTW, when a page is moved, I think we should keep the page on the wiki,
> and perhaps keep a record of when the last version was committed to CVS.
>
> Blowing away docs (like the features list) isn't too useful, especially
> since I was going to point to the version of the docs in the Wiki, and
> possibly make a bunch of revisions to the page. But then I suppose I
> could just edit the new file in CVS and commit.
The problem I saw (and because of this I removed the list) are the
missing diffs (or the bad usability with it) after further additions to
the page are made. Imagine in a half year you want to update the page in
the CVS, in the meantime there were 10 changes in the wiki page, maybe
someone reordered all the things! You can start from scratch then or try
to reproduce all the changes for the CVS version - and this from version
n to v. n+1, from v. n+1 to v. n+2 and so on. After the removal of the
list I think we have a cleaner approach.
Joerg