[Kolab-devel] Kolab 16 for Debian

Aaron J. Seigo aseigo at mykolab.com
Sun Nov 6 23:54:37 CET 2016


On Saturday, November 5, 2016 07.55:24 Timotheus Pokorra wrote:
> Hello Aaron,
> 
> > Until we had a few ... "events" ... that took up the team's time last
> > month, we were actually planning on charting out and leading a packaging
> > effort for 16.1 during October. I hope we will see this go forward this
> > month. As soon as we have a firm "yes" on our availability, we'll let
> > everyone know here.
> That is a very helpful information. I think if there would be more
> communication like this, it could motivate people to help with
> packaging.

I didn't want to start waving flags around until we new 100% that we had the 
time to put to it. Turns out that caution was warranted, as we ended up not 
having any time for it in October, and that would have left you and the others 
on your own without much assistance and participation from us .. and that 
would be pretty crappy for us to say "hey, we're plotting a new release build 
here.." and then disappear ;)

I do agree with you, however, and as soon as this is rescheduled (and I really 
expect it to Happen this month), I will be sure to let everyone know here (and 
elsewhere)

> > I have no personal opinion on which is better or worse. I know that
> > packagers tend to hate the vendorized-builds that are more and more The
> > Standard Practice for frameworks as varied as node.js, PHP and
> > Erlang/Elixir. But it does make it easy to make shippable binaries you
> > KNOW will work with ZERO conflict with any other applications.
> 
> Yes that is a big discussion in the distributions.

I've noticed :)

> I think that with a vendorized build, the community is fully dependant
> on the vendor. Although the community could help with packaging there
> as well...
> The vendor takes all the responsibility to deliver fully patched packages.

Indeed, on all points.

> Jeroen sometimes hinted he wished that distributions would take on the
> job of packaging Kolab.
> Did I get that right?

Yes.

> With Mono, another open source project I am involved in, we did make

Indeed; those are the sorts of results we'd like to see as well ..

well, let's see what Novemeber brings us, firstly .. and then let's think to 
the future in 2017. BTW: are you going to be @ FOSDEM?

-- 
Aaron Seigo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20161106/2bbad831/attachment.sig>


More information about the devel mailing list