Incubator/Projects/GCompris: Difference between revisions
Line 87: | Line 87: | ||
|- | |- | ||
{{FeatureDone|Repository and code available (in playground)|Playground-ish: They're using the GitLab test install}} | {{FeatureDone|Repository and code available (in playground)|Playground-ish: They're using the GitLab test install}} | ||
{{ | {{FeatureDone|Mailing list available|...}} | ||
{{FeatureDone|Website available (if applicable)|Yes, on own infrastructure}} | {{FeatureDone|Website available (if applicable)|Yes, on own infrastructure}} | ||
{{FeatureInProgress|Active community|Push more use of the mailing list}} | {{FeatureInProgress|Active community|Push more use of the mailing list}} | ||
{{FeatureTodo|Manifesto compliance|...}} | {{FeatureTodo|Manifesto compliance|...}} | ||
|} | |} |
Revision as of 11:40, 16 November 2014
GCompris
Sponsor: Kevin Ottens
GCompris is a high quality educational software suite comprising of numerous activities for children aged 2 to 10.
Some of the activities are game orientated, but nonetheless still educational.
Currently GCompris offers in excess of 100 activities and more are being developed.
Team
- Bruno Coudoin (maintainer)
- Aruna Sankaranarayanan
- Emmanuel Charruau
- Holger Kaelberer
- Johnny Jazeix
- Stephane Mankowski
- Thibaut Romain
Manifesto Compliance Plan
Values
Open Governance
Already open goverance to some extent, anyone with a KDE account can contribute, mailing list and IRC available.
Focus point: mailing list under used, people tend to mail directly Bruno in private. Proposed action: push contributors toward the mailing list for discussions.
Free Software
All GPL v3+, no brainer.
Inclusivity
No barrier known toward the contributors.
Innovation
Not really applying to this area, that said, spearhead efforts on Android, Windows port and such.
Common Ownership
All clear no known barrier, anyone can contribute directly.
End-User Focus
Perfectly in target, software for children and schools.
Commitments
- Code of Conduct: supported
- Contributor License Agreement: none
- Established practices: CMake + Qt like most, code reviews except for most active core contributors
- Source materials hosted on our git infrastructure (they are part of the gitlab testing projects)
- Online services, some are not on KDE infrastructure: website, wiki, mailing list, voice assets, gcompris.net emails, source tarballs, binaries for windows, mac, android (+ payment system), use KDE's bugzilla
- KDE Licensing policy: a few copyright headers missing, otherwise following it
- KDE branding guidelines: no reference to KDE yet
- No patents
- Agrees to transferring the GCompris brand in case of bus rampage :-)
Proposed actions:
- website + wiki + gcompris.net: should propose continuity plan to sysadmin
- mailing list: should migrate to KDE infra
- voice assets: should migrate to KDE infra
- source tarballs: should migrate to KDE infra
- binaries: to be discussed on kde-community again to finally answer if yes or no we're fine with hosting on KDE infra those binaries which have a code to unlock them fully
Benefits
No brainer, already participating in Randa, posting on planet, etc.
Sponsor Checklists
Candidate ready
Status | Description | Notes |
---|---|---|
DONE | Project description | |
DONE | Project team | |
DONE | Manifesto compliance plan |
Incubating
Status | Description | Notes | |
---|---|---|---|
DONE | Repository and code available (in playground) | Playground-ish: They're using the GitLab test install | |
DONE | Mailing list available | ... | |
DONE | Website available (if applicable) | Yes, on own infrastructure | |
IN PROGRESS | Active community | Push more use of the mailing list | |
TO DO | Manifesto compliance | ... | <{{{3}}}> |