IUP ISI/MediaWiki-Silk/Project vision: Difference between revisions
< IUP ISI | MediaWiki-Silk
Line 92: | Line 92: | ||
|- | |- | ||
! scope="row" | The fact that | ! scope="row" | The fact that | ||
| | | there doesn't exist Wikipedia widgets | ||
|- | |- | ||
! scope="row" | affects | ! scope="row" | affects | ||
| | | KDE users, | ||
|- | |- | ||
! scope="row" | because | ! scope="row" | because | ||
| | | the users who need Wikipedia's services don't have widgets for the desktop. | ||
|- | |- | ||
! scope="row" | A successful solution would | ! scope="row" | A successful solution would | ||
| | | provide widgets to reach Wikipedia's services. | ||
|} | |} | ||
Revision as of 12:19, 6 October 2010
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
- Qt & KDE developer
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 | is a suite of widgets/plasmoids |
that | brings pieces of information from Wikipedia/Wikimedia to their desktop |
in a better way than | the browser. |
Roles
- Wikimedia reader
- Wikimedia participant
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
For | Current and potential participants to Wikimedia Commons |
---|---|
who | want to contribute media files, |
the mass file uploader | is a cross-platform Qt application |
that | facilitates the upload of multiple files |
in a better way than | the web interface, Commonist, Nichalp's Upload Script and Pywikipediabot. |
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 | |
---|---|
affects | |
because | |
A successful solution would |
Success criteria
Product position
For | |
---|---|
who | |
that | |
in a better way than |
Roles
Features
Name | Priority | Short description |
---|---|---|
Original page
Problem statement
Le problème de | l'accès à Wikipedia, dépendant d'une connexion internet et d'un navigateur, |
---|---|
affecte | les développeurs et les utilisateurs. |
L'impact du problème est | que les utilisateurs ne peuvent pas avoir le contenu de Wikipedia sur le bureau et que s'il n'ont pas de connexion, le contenu de Wikipedia est indisponible. |
Une solution réussie permettrait de | pouvoir accéder au contenu de Wikipedia à partir de l'environnement KDE en étant connecté à internet ou hors-ligne. |
Critères de succès
- Bibliothèque utilisable et utilisée.
- Taux de satisfaction et d'utilisation élevés de la part des utilisateurs. (ex : nombre d'étoiles proche de 5)
Position du produit
Pour | les utilisateurs et les développeurs |
---|---|
Qui | cherchent à utiliser de manière simplifié Wikipedia. |
MediaWiki/Silk | est une API ainsi qu'une ressource akonadi |
Qui | permet d'interfacer l'API MediaWiki en Qt, de synchroniser des pages Wikipedia afin de les utiliser en étant hors-ligne. |
Mieux que | le navigateur internet. |