[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Minutes of the KOffice meeting
From:       Robert Knight <robertknight () gmail ! com>
Date:       2005-09-05 14:05:13
Message-ID: 13ed09c0050905070559db5b44 () mail ! gmail ! com
[Download RAW message or body]

Hi,

>They start by saying what licence the program has, then listing its authors.

> In my opinion, that's not particularly friendly for users.  We say it's 'free'
> on the front page - I bet there aren't many who care whether KSpread is GPL
> or LGPL.

I agree, looking at the koffice.org website, the other big issue that
struck me is how inaccessible the binary packages are (you have to go
through EIGHT links to get one of the RPMs)

I think that ideally, the 'work-flow' for a user trying to get the
latest KOffice would be something like:

- User selects distro & version from combo-box dropdowns on the front
page of the site.
- This takes the user to a distro-specific page which tells the user
the easiest way to get the latest KOffice for their distro - it should
also provide a link to the binary packages contributed by KDE users or
distro pacakgers.

On the development side, the front-page should also include a call for
developers, artists etc, rather than just the little "Get Involved"
link on the left hand side.

If someone would be willing to help with providing the "get KOffice"
instructions for the various distros, I could put some time into this?

Regards,
Robert.

On 05/09/05, Martin Ellis <martin.ellis@kdemail.net> wrote:
> Hi,
> 
> Thanks for the summary, Inge.
> 
> On Monday 05 Sep 2005 10:41, Inge Wallin wrote:
> > 1. Discussion about wether to release another version for Qt3, or if we
> > should go Qt4 immediately
> ...
> > Decision: Since the port to Qt4 will take a very long time and we don't
> > want KDE4 to be released without a working KOffice, we will go Qt4 as soon
> > as possible. David Faure will contact all the maintainers, and get a
> > confirmation.  We will also help Kexi and Krita make their own releases
> > outside the standard schedule of KOffice. (A tip might be to look at the
> > release script created for the stand-alone releases of Kalzium by Carsten
> > Niehaus.)
> 
> Seems sensible.  At the moment the problem with separate releases for
> Kexi is our use of an unreleased library in koffice/lib: koproperty.
> 
> It seems quite awkward to convince svn2dist to include more than one source
> directory from the module (we need kexi and part of lib).  I'm working on
> this.
> 
> BTW, packagers still haven't quite figured out how to deal with independent
> releases.  Perhaps it'd be good to have some suggestions on the KOffice web
> site for packaging such releases (maybe duplicated in the source tree).
> 
> > 3. Discussion about how to attract new developers.
> >  - The API docs should be better.  There is now a feature that creates the
> > docs automatically by typing "make apidocs".  What is missing is often a
> > top-level description of the design and usage of each library.
> 
> I've been trying to figure out why following the instructions on how to build
> a local copy of the docs produces different results to those on the web site.
> We should get this sorted first, so we don't end up making dozens of 'does
> this work?' API doc commits.
> 
> > 4. We need to have some non-coder contributors as well.
> 
> I agree.
> 
> > 5. PR
> 
> Two things:
> 
> 1)
> The filters page on koffice.org is out of date - not good PR.
> At the very least we should provide a filter status list for KOffice 1.4.
> 
> We could start by just taking a copy from 1.3 and updating to reflect the 1.4
> changelogs.  Any objections?
> 
> 2)
> I've been thinking the individual application pages on koffice.org
> aren't very friendly.
> They start by saying what licence the program has, then listing its authors.
> 
> In my opinion, that's not particularly friendly for users.  We say it's 'free'
> on the front page - I bet there aren't many who care whether KSpread is GPL
> or LGPL.
> 
> What are people's opinions (particularly those who have made large
> contributions to KOffice) on putting this information on a 'sub'-page, and
> putting a pretty screenshot on the front page with the description instead?
> 
> (Yeah, OK.  I'm just thinking about what was in Aaron Seigo's presentation)
> 
> 
> Cheers
> Martin
> 
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel
>
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

[prev in list] [next in list] [prev in thread] [next in thread]