<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Sans Serif'; font-size:12pt; font-weight:400; font-style:normal;">Op woensdag 18 november 2009 10:52:54 schreef Sascha Wilde:<br>
> Richard Bos <ml@radoeka.nl> writes:<br>
> > Op dinsdag 17 november 2009 16:36:21 schreef Sascha Wilde:<br>
> >> One thing we agreed upon is, that it would be nice to have all the<br>
> >> sources in a none discriminating package format (can you say "tar"?)<br>
> >> available, distributed and build able, so that one could easily build<br>
> >> Kolab server without having the pre-requisite of OpenPKG -- Gunnar<br>
> >> recently started a thread on this topic.<br>
> ><br>
> > See above. The build service does not have an openpkg repository. That<br>
> > would have been nice. I think that it is a bit hard to set up, besides<br>
> > that it is not very known.<br>
><br>
> I'm not sure how your comment relates to the paragraph above, I was<br>
> talking on classical tar packaging, not OpenPKG -- or are you saying we<br>
> would need the tars to use the build service?<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>The output of the build service are packages. Those packages are build from tarbals. So, yes you need tarbals to use the build service.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> > If the Horde project will not come up with a polished GUI, ain't it<br>
> > possible that kolab project adds this to the Horde project? That way<br>
> > both projects benefit, isn't it?<br>
><br>
> That would be exactly the thing to do! I thought that was what I<br>
> wrote... ;-)<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Yes, that's what you wrote indeed. I see it now after reading back that part :)<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> >> The suggestion has been made to take the administrative (web admin)<br>
> >> interface as a kind of playground to test out our capabilities of<br>
> >> creating an modern, appealing and user friendly web UI.<br>
> ><br>
> > I have always thought of moving kolab-webadmin into horde as that<br>
> > interface is nicer, prettier than kolab-webadmin....<br>
><br>
> That's one possible strategy, which will be evaluated.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>For the user this seems do-able anyway: as the user can use the web-admin for updating his / her vacation message and personal information. Not too much. For the administrator it is much more work....<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> >> In any case this will be one of the more exciting areas in midterm Kolab<br>
> >> server development. We are looking forward to your comments...<br>
> ><br>
> > I'm surprised that you're thinking of ditching horde. Assuming that<br>
> > Horde-4 delivers what we expect ;)<br>
><br>
> Well, maybe you expect more than we do. To make it completely clear: we<br>
> are just thinking, and we allow our self to think even of drastic<br>
> changes, as what we are longing for is a drastic improvement. But no<br>
> decision has been made yet.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>You were clear ;)<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>-- <br>
Richard<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p></body></html>