On Friday, November 27, 2015 08:04:17 PM Federico Leva wrote:
To clarify, Wikimedia Italia doesn't financially
sponsor this site nor
contribute content to it. AFAIK our volunteers provided some MediaWiki
training to the site's users. Wikimedia Italia is always happy when
MediaWiki usage spreads, but recommends Wikibooks and Wikiversity as
primary platforms for OER activities.
A few important Wikimedia Italia members have actually contributed much
content to the site. I think that the relationship between KDE and WMI is
mutually beneficial, as we bring in a lot more contributors to MediaWiki and
similar technologies, and at the same time develop much free content.
Everybody wins. :-)
As for your question, there are a couple useful things
you can do:
1) write a document where you explain what makes your platform more
suitable for your activities and what features Wikibooks/Wikiversity
lack in your opinion;
I briefly answered in my previous mail to a question similar to this.
A strong presence within the academical world is also a non-techical, but key
element. Two universities (Milano-Bicocca and Pisa) have already decided to
join the activities with all of their professors and students. I expect
several more to come (we have ongoing contacts), in the near future.
2) publish your code in Gerrit:
(you made a
Docker extensiona and the skin, right?
We have a few modifications here and there, also on OCG and more standard
extensions (like Math). We will do more. We're temporarly hosting our source
code on github, while we're reworking with the sysadmins on the git.kde.org
infrastructure, but as a KDE project we will have to move the official repos,
per project policy.
Since git is decentralized, I hope we can still find great spaces for
3) report bugs and feature requests
4) (as you use Debian) take ownership of the Debian package, which is
currently abandoned: https://wiki.debian.org/MediaWiki
We're not using a Debian package, we're using our custom baked solution of
variously integrated docker containers, which allows for an almost identical
setup for development and production, with a pretty nice deployment procedure.
It seemed much easier than Vagrant for our usecases. All of our scripts are
also open. This allows deployment on several Linux flavors.
Thank you very much for your reply and your support! :-)