libmediawiki
Problem statement
The fact that
|
there doesn't exist a Qt API for MediaWiki
|
affects
|
Qt and KDE developers, and their users,
|
because
|
the absence of readily available API discourages developers from building desktop tools for reading or editing MediaWiki-hosted content.
|
A successful solution would
|
provide Qt developers with such a tool, therefore enabling and encouraging them to create new software based on it.
|
Success criteria
- The library is usable and reused outside this project.
Product position
For
|
Qt and KDE developers
|
who
|
want to build software that interacts with a MediaWiki website
|
libmediawiki
|
is a Qt API
|
that
|
allows to quickly and abstractly interface with a MediaWiki interface
|
in a better way than
|
building a (different) interface from scratch each time.
|
Roles
Features
See http://www.mediawiki.org/wiki/API for details.
Name |
Priority |
Short description
|
Authentication API
|
|
Login & logout
|
Query API
|
|
Meta info, properties & lists
|
Parsing API
|
|
Template expansion & rendering
|
Editing API
|
|
Page creation, edition, move, watch
|
Maintenance API
|
|
Deletion, protection, rollback, patrol
|
User API
|
|
Block, e-mails, user rights
|
Uploading API
|
|
File upload
|
Widgets / plasmoids
Problem statement
The fact that
|
there doesn't exist Wikipedia widgets
|
affects
|
KDE users,
|
because
|
the users who need Wikipedia's services don't have widgets for the desktop.
|
A successful solution would
|
provide widgets to reach Wikipedia's services.
|
Success criteria
Product position
For
|
User of the KDE desktop
|
who
|
wish to integrates bits of Wikipedia and other Wikimedia websites in their desktop,
|
Wikipedia widgets
|
are a suite of widgets/plasmoids
|
that
|
brings pieces of information from Wikipedia/Wikimedia to their desktop
|
in a better way than
|
the browser.
|
Roles
Features
Name |
Priority |
Short description
|
Commons picture of the day
|
|
|
Wikipedia article of the day
|
|
in multiple languages?
|
Wiktionary look-up
|
|
|
Watchlist RSS
|
|
|
Mass file uploader
(name TBD)
Problem statement
The fact that
|
Wikimedia Commons doesn't provide an intuitive, fully-fledged and cross-platform mass file uploader
|
affects
|
the current and potential participants to Wikimedia Commons
|
because
|
contributing large amounts of media files
|
A successful solution would
|
provide an easy way to mass upload media files from the desktop to Wikimedia Commons.
|
Success criteria
- The tool is well-received by the community of users.
- The tool is downloaded by a large number of people.
- A large number of media files are uploaded using the tool.
Product position
Roles
- Wikimedia Commons participant
Features
Name |
Priority |
Short description
|
Multilingual descriptions
|
|
|
Copyright terms
|
|
Author, source, license
|
Specifics of Wikimedia Commons
|
|
Mandatory fields, licenses and other templates
|
Prepopulation of fields
|
|
Metadata extraction from EXIF, IPTC, XMP
|
Batch operations
|
|
Ability to apply specific changes to a selection of files
|
User preferences
|
|
Ability to customize and remember settings
|
Integration with KIPI plugins
|
|
|
Lossless rotation
|
|
|
Progress bar
|
|
|
Geolocation
|
|
Ability to extract from EXIF and add template or hide for privacy
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Offline editor
Problem statement
The fact that
|
there doesn't exist offline editor
|
affects
|
Wikipedia users
|
because
|
they have to use a browser to edit.
|
A successful solution would
|
provide an offline editor based on an akonadi resource.
|
Success criteria
- Wikipedia users choose the offline editor instead of the browser.
Product position
For
|
the Wikipedia users
|
who
|
edit the Wikipedia article.
|
Offline editor
|
is a rich editor
|
that
|
allows to edit the Wikipedia article
|
in a better way than
|
the browser.
|
Roles
Features
Name |
Priority |
Short description
|
|
|
|
|
|
|