Hi everyone,
For those are interested, we're organising a call to talk exclusively
about the WebEngine/Reveal.js branch I've been working on.
Please use the Doodle below to select a date and time that works best
for you. I've selected all the times that work best for me, but if you
have a
On 2018-08-31 15:24, Raoul Snyman via openlp-dev wrote:
https://doodle.com/poll/p3qebgkbyspsgu68
So far it looks like we'll be meeting on Monday. If you're still
interested in being part of the meeting discussing the port to
WebEngine, please mark your availability on Doodle, and join us
On 2018-10-11 10:53, Bastian Germann wrote:
I noticed the issue with pyenchant as well. Therefore I made it an
optional dependency in my "setup" branch.
Yup, I saw. Tomas, Tim, I remember us looking at a possible replacement
for pyenchant. Do you remember what it was?
The pymediainfo
On 2018-10-23 17:25, Kyle Nweeia wrote:
Hi, I'm new here. Please let me know if there's anything small I could
work
on.
Here's something: https://bugs.launchpad.net/openlp/+bug/1800761
This bug has been creeping up a lot lately, and I think it's to do with
a change to SongSelect. From what
Here's another one that is an easy fix:
https://bugs.launchpad.net/openlp/+bug/1678632
There's a break inside a for loop which should also set "run_search" to
False.
openlp/plugins/songs/lib/songselect.py line 173
--
Raoul Snyman
+1 (520) 490-9743
ra...@snyman.info
Hi everyone,
For those who are interested, I'd like to organise another huddle to
touch base with where we are with the WebEngine migration.
Please can you vote for what time suits you best:
https://cloud.snyman.info/index.php/apps/polls/poll/bOqWjFXdKBbRerXJ
Also, here's a list of tasks
On 2018-09-02 01:06, Raoul Snyman via openlp-dev wrote:
So far it looks like we'll be meeting on Monday. If you're still
interested in being part of the meeting discussing the port to
WebEngine, please mark your availability on Doodle, and join us on the
day.
It looks like the majority
Hi everyone,
It looks like the best slot for everyone is going to be this Saturday
evening/Sunday morning, the 6th or 7th of April. Please see the times
below for your timezone:
UTC: 7 April at 06:00
California/Arizona: 6 April at 23:00
UK: 7 April at 07:00
Germany/Denmark: 7 April at 08:00
Hey everyone,
There were various action items that came out of our huddle on
Saturday/Sunday that are unassigned, and a number of them are well
suited for folks that want to start contributing to OpenLP.
Easy
Smoke Tests:
We need a few people to do some basic manual click testing. Try
Hi everyone,
We discussed the first alpha release in the huddle the other day, but
I'd like to continue that conversation here.
Some pertinent questions:
- What features should be in the release?
- What level of stability do we want?
- When should actually release it?
* Specific date?
*
Hi everyone,
Thanks for joining us in our 3rd huddle!
Here are the minutes that I made of the huddle, please add anything I
missed:
https://etherpad.net/p/openlp-huddle-3-minutes
Thank you!
--
Raoul Snyman
ra...@snyman.info
___
openlp-dev
Hi everyone,
I've created a page on our wiki[0] to keep track of our move to GitLab.
We've already moved the documentation[1] over to GitLab, and we've set
up CI[2] and deployment[3] for it. It's working great so far.
I've just kinda written names down next to projects on the list of
things
Hey folks,
We've been chatting a little in IRC today about the first alpha release.
We also mentioned moving to GitLab as part of the alpha release.
Before we can get to the alpha release, however, we need a few things
done:
1. About dialog updates (move to GPL3, etc)
2. Alerts
3. Theme
Hey everyone,
Just a quick note to let you know that we have migrated the main OpenLP
codebase to GitLab:
https://gitlab.com/openlp/openlp
That means that we have almost everything in GitLab. I've imported all
the bugs from Launchpad into issues in GitLab, and formally disabled the
bug
I've started a release blog post:
https://pad.lqdn.fr/p/openlp-3.0-alpha1
--
Raoul Snyman
ra...@snyman.info
___
openlp-dev mailing list
openlp-dev@openlp.io
https://lists.openlp.io/mailman/listinfo/openlp-dev
Hello everyone!
A while back we decided to switch to using pytest[0] for running our
tests. It's much faster than nose[1], and pretty actively developed. For
the most part, pytest can run tests written for the built-in unittest[2]
framework (which is what nose uses). Unfortunately there seem
On 2019-10-08 15:22, Benjamin Hoving wrote:
The basic problem is that the QApplication object is only meant to be
instantiated once for the lifetime of the application, which is what
happens during the normal execution of OpenLP, but during testing, the
QApplication is created and destroyed many
I think that almost all the issues slated for the Alpha 2 release have
been resolved. Do we want to put a date to the release? The 31st of
May?
We're still on for the 31st. Let's try to get the last fixes in today
(Friday) so that we can build and upload packages on Saturday.
--
Raoul
Hello everyone,
With the next release supposedly being a beta release, I think we need to make
a firm decision on what features need to be in OpenLP 3.0, and what we may want
to leave for the next release.
Also, a reminder that we want to move toward more releases more often, with
smaller
Hello everyone,
The server running at openlp.io (aka get.openlp.org) has been assigned a
new IP address, and has some updates that need to be performed. This
will all necessitate a reboot as well. For the most part, I expect there
to be no significant problems, all the domains will be pointed
On 2020-06-05 23:59, Raoul Snyman via openlp-dev wrote:
I'll be rebooting the server shortly, once I have the domains updated.
Server is back up and running. Let me know if you run into any problems.
--
Raoul Snyman
ra...@snyman.info
___
openlp-dev
Hello everyone,
I just wanted to thank and congratulation everybody for the work done on the
tests. Our code coverage has been hovering at 59% for the last few weeks (or
months) and yesterday we finally hit 60% code coverage!
This is a fantastic achievement, and I'm very grateful to each
Hey everyone,
Ever found yourself writing a for-loop in a test, and wondering if
there's a better way to do it? Kinda like this?
def test_media_length(media_env):
"""
Check the duration of a few different files via MediaInfo
"""
for test_data in TEST_MEDIA:
# GIVEN:
23 matches
Mail list logo
