[bt-devel] Integration into KDE (e.g. KDEEDU)

David Blue (Mailing List Addy) davidslists at gmx.net
Wed Jun 1 19:26:02 MST 2005


On Tuesday 31 May 2005 03:28 pm, heiko.evermann at gmx.de wrote:
> If you do not like kdeedu, you could also propose a different kde group.
> But I think kdeedu would be the best. kdetoys would not be a better choice.
> The main focus on kdeedu is to provide teaching applications. And in a way
> bibletime fits very nicely there.

Yes agreee here it's the "tainment" portion of edutainment. That always makes 
me think of educational games.

> > You need at least version 1.5.8 of sword library. bibletime will not be
>
> compiled
> and everything is fine. Those people who make the binary distributions will
> provide suitable RPM-files and would in our case provide a sword-1.5.8.rpm
> and make the installation of kdeedu.rpm dependent on sword-1.5.8.
> Or, if a Linux distro has religions reservations against providing a binary
> for bibletime, they could choose not to compile bibletime and then their
> kdeedu.rpm would not include bibletime.

Well my concern was more that sword 1.5.8 was a long time in the making, and 
as a result Bibletime 1.5 has been a long time in making as well. Basically 
changes were made in the svn repository for the sword project that we came to 
rely upon, and thus had to wait until sword 1.5.8 was released before 
releasing Bibletime 1.5rc1

> * Development takes place in the "HEAD", that is the main branch of the
> source repository. (I think since they switched over from cvs to
> subversion, it is called "trunk" now. ) Here you can develop any way you
> please. It should compile. You can even extract your own personal source
> snapshots and publish them on bibletime.info.

Right, I've seen projects like Kpilot doing things like this.

> * For a major release (e.g. KDE 3.4) at a certain point a branch is opened
> (e.g. KDE_3_4_BRANCH), that means within the source control system, a copy
> is made. This branch is then used for providing the maintenance releases
> KDE 3.4.1, KDE 3.4.2 etc.

I think we do similar things currently, though we don't always release a 1.5.1 
for instance. Usually things wait until 1.6, or what have you.

> * There are restrictions on development in the branches. Only bug fixes are
[snip]
> After Feb 26 2005, HEAD was open again for development, as any further
> development was made in the branch.

Ok, that I was already aware of, I was thinking there were additional 
requirements that were different than just the release time requirements

> So that would put some restrictions on bibletime. But on the other hand
> this would also mean that in the preparation for the release, lots of other
> people would build KDE from source and would find out, whethere bibletime
> compiles fine. If you want to be part of KDE, you just have to make sure,
> that everything works fine when the release snapshot is done. So all these
> rules make sense.

Of course this means more bug reports as well, and there are only a couple, 
three of us actively working really.

> We should at least try. After all, Bible time itself is just a program to
> display bible translations. It does contain the bible text. It only allows
> the user to download the text. I think that the community should be
> tolerant enough to tolerate a program that displays a book that 1 third of
> the worlds population consider to be an important pillar of their faith.)
> And as I said before, I would even tolerate Muslims to provide a similar
> tool for the Quran, as this would help me as a Christian to point out its
> errors and to prove that these errors are not just a result of
> mistranslations as such a tool would enable me to find my way through the
> Arabic text. I think we should at least try.

You would also think that the community would be tolerant enough to tolerate a 
kde wallpaper with a verse on it, but often this is just simply not the case. 
There are those who would view Bibletime's presence within kde as us trying 
to force our religion on them.

-- 
--David's Mailinglist and Spam Receiver
   Keeping me (fairly) spam free since 2002


More information about the bt-devel mailing list