Overview
Request 849966 accepted
- Upgrade to version 1.0 20 years birthday edition
+ new major feature: the addition of the Activity Settings menu
with Dataset selection for more than 50 activities.
+ 4 new activities:
- Analog Electricity activity
- Learn digits and two subactivities to learn additions and subtractions.
- Baby keyboard
- Gravity (forwarded request 849562 from bruno_friedmann)
- Created by bruno_friedmann
- In state accepted
Request History
bruno_friedmann created request
- Upgrade to version 1.0 20 years birthday edition
+ new major feature: the addition of the Activity Settings menu
with Dataset selection for more than 50 activities.
+ 4 new activities:
- Analog Electricity activity
- Learn digits and two subactivities to learn additions and subtractions.
- Baby keyboard
- Gravity (forwarded request 849562 from bruno_friedmann)
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto accepted review
Check script succeeded
dimstar_suse added openSUSE:Factory:Staging:adi:17 as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:17"
dimstar_suse accepted review
Picked "openSUSE:Factory:Staging:adi:17"
dimstar accepted review
licensedigger accepted review
ok
dimstar_suse accepted review
Staging Project openSUSE:Factory:Staging:adi:17 got accepted.
dimstar_suse approved review
Staging Project openSUSE:Factory:Staging:adi:17 got accepted.
dimstar_suse accepted request
Staging Project openSUSE:Factory:Staging:adi:17 got accepted.
In case for clarifying Licence, there's one component added, but after digging I + upstream we concluse we should be ok to still use gpl Johnny also found https://www.mozilla.org/en-US/MPL/2.0/FAQ/ (especially Q14 and Q25): as long as the "Exhibit B" is not in the source code (so the js file), there is no issue and we can use it in a GPL3 software without double-licensing... And the "Exhibit B" is not in the source file, so we are good to go.
I'm more worried about gcompris-qt-1.0/src/activities/analog_electricity/AGPL-LICENSE - AGPL is quite different to GPL in its nature and should be mentioned
Outch! Thanks a lot Stefan for spotting this, that escape my review. I've just immediately inform upstream to see what is the best to do especially with this specific activity. If I can abuse your long packaging experience, would it be ok for Factory to have a GPL-AGPL bi-licensed package ?
https://en.wikipedia.org/wiki/Affero_General_Public_License#Compatibility_with_the_GPL - not a problem per se