headers
Carl Gay | 9 Apr 12:44
Favicon

wiki

Does anyone know what the status of the wiki sources is?
The code in libraries/network/wiki has been in a seriously
broken state for quite some time now due to changes made
in koala without updating all the callers.

-Carl
--

-- 
Gd-hackers mailing list
Gd-hackers <at> gwydiondylan.org
https://www.opendylan.org/mailman/listinfo/gd-hackers
Permalink | Reply |
headers
Bastian M?üller | 10 Apr 01:41
Picon

Re: wiki

Carl Gay wrote:
Hej,

> Does anyone know what the status of the wiki sources is?
> The code in libraries/network/wiki has been in a seriously
> broken state for quite some time now due to changes made
> in koala without updating all the callers.

The new wiki is located at http://turbolent.com/~turbo24prg/projects/wiki/.
(darcs repository)

What's missing:
  - a parser
  - file upload
  - privilege handling for users/groups
There's also a TODO.

hannes recommended groups with different privileges and I asked
several times for recommendations about the details - nobody
answered until now. Please say what you think about authorization
levels and things like that.

I'm going to finish the things mentioned above ASAP, but
someone else will have to do the parser, because I don't know
how to implement/finish one.

Thanks.

kind regards,
   Bastian
(Continue reading)

Permalink | Reply |
headers
Carl Gay | 10 Apr 07:25
Picon

Re: wiki

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 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.

Am I the only one bothered by this?

-Carl

On Wed, Apr 9, 2008 at 7:41 PM, Bastian M?üller <turbo24prg <at> web.de> wrote:
> Carl Gay wrote:
>  Hej,
>
>
>  > Does anyone know what the status of the wiki sources is?
>  > The code in libraries/network/wiki has been in a seriously
>  > broken state for quite some time now due to changes made
>  > in koala without updating all the callers.
>
>  The new wiki is located at http://turbolent.com/~turbo24prg/projects/wiki/.
>  (darcs repository)
>
>  What's missing:
>   - a parser
>   - file upload
(Continue reading)

Permalink | Reply |
headers
Bruce Hoult | 10 Apr 08:26

Re: wiki

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 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.
>
>  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.
--

-- 
Gd-hackers mailing list
Gd-hackers <at> gwydiondylan.org
https://www.opendylan.org/mailman/listinfo/gd-hackers
Permalink | Reply |
headers
Bastian M?üller | 10 Apr 20:51
Picon

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?
(Continue reading)

Permalink | Reply |
headers
Peter Robisch | 11 Apr 05:06
Picon

Re: wiki

Carl Gay wrote: 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.

 So my understandig of the situation is that if currently someone checks out
the head of koala and network/wiki he cannot run the system. Is this 
the current situation?

Bastian Müller wrote:
> 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.

In case:

 Via which document or information board he knows which koala lib / wiki lib
revisions are compatible? IMHO I would appreciate a note on
  http://wiki.opendylan.org/wiki/view.dsp?title=Wiki
which clarifies the situation. That would be the place I would look for
to inform about change logs (not revision logs).

Pet-ro

--

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

Gmane