Re: wiki

Bruce Hoult wrote:
> On Thu, Apr 10, 2008 at 5:25 PM, Carl Gay <carlgay <at> gmail.com> wrote:

>> I think it is wrong to make changes to one library and knowingly (?)
>>  leave other libraries in the project in a broken state for extended
>>  periods of time.  I think the correct way to have done this is to keep
>>  libraries/network/wiki up-to-date with the changes made to Koala until
>>  such time as a replacement wiki is ready.
I don't see the point in upgrading the current wiki, when developing a 
replacement at the same, to throw away the upgraded wiki after finishing 
it. Sorry, I don't have the time to do that.

If you want to have a working wiki, just check out an old revision of 
koala, web-framework and wiki, that's what a version control system is 
good for.

>>  I also don't see the need for a separate repository for the wiki
>>  project, which makes working on the combined code base that much more
>>  difficult.
You don't seem to be working on it - I do. I don't want to be harsh or
anything, but subversion takes away a lot of the sparse time I have.

>>  Am I the only one bothered by this?
> 
> No.
> 
> I think it's the responsibility of someone who changes an API to make
> a reasonable effort to track down and update uses of that API.
Sure, I'm responsible for upgrading it and I'm currently doing so.
What's the problem?

--

-- 
Gd-hackers mailing list
Gd-hackers <at> gwydiondylan.org
https://www.opendylan.org/mailman/listinfo/gd-hackers