| 1 |
On Sun, 2007-10-14 at 00:05 +0200, Wulf C. Krueger wrote: |
| 2 |
> On Saturday, 13. October 2007 19:27:05 Chris Gianelloni wrote: |
| 3 |
> > On Thu, 2007-10-11 at 13:11 +0200, Gunnar Wrobel wrote: |
| 4 |
> > > The project has advanced far enough though that I feel it is a good |
| 5 |
> > > time point to declare this a real Gentoo project. |
| 6 |
> > > http://www.gentoo.org/proj/en/kolab/index.xml |
| 7 |
> > Umm... why? Why does a package need a project? Is this not just a |
| 8 |
> > mail server? |
| 9 |
> |
| 10 |
> It's a full-blown collaboration/groupware server and it will likely need a |
| 11 |
> fair bit of coordination between different herds and maintainers as it |
| 12 |
> uses several major F/OSS components which (at least until recently) need |
| 13 |
> patches and integration changes to be usable with Kolab. |
| 14 |
> |
| 15 |
> http://kolab.org/about-kolab-server.html |
| 16 |
> |
| 17 |
> > I don't mean any offense. I just want to know. Why do we need to |
| 18 |
> > create a project, which should normally be reserved for wide-sweeping |
| 19 |
> > changes or things that require massive amounts of coordination? |
| 20 |
> |
| 21 |
> Indeed. Having tried to use Kolab on Gentoo before, I assume it will be |
| 22 |
> the latter that makes a Kolab project reasonable. |
| 23 |
|
| 24 |
Cool. In the future (this is to everyone), can we say this kind of |
| 25 |
information in the announcement message so we don't end up having to ask |
| 26 |
such questions? |
| 27 |
|
| 28 |
Thanks, |
| 29 |
|
| 30 |
-- |
| 31 |
Chris Gianelloni |
| 32 |
Release Engineering Strategic Lead |
| 33 |
Alpha/AMD64/x86 Architecture Teams |
| 34 |
Games Developer/Foundation Trustee |
| 35 |
Gentoo Foundation |
Archives