Additions:
**UPDATE : mageia-app-db now has a project's website : http://madb.org **
Deletions:
Additions:
- user front-end can be translated (if requesting a backport is as simple as choosing the package name and version)
- Rémi Verschelde (Akien)
- Rémi Verschelde (Akien)
Deletions:
- Remi Verschelde (Akien)
Additions:
- user front-end can be translated (if requesting a backport is as simple as choosing the package name and version) [[http://essaysexperts.com/ buy custom writing essay]]
- Remi Verschelde (Akien)
- Remi Verschelde (Akien)
Deletions:
- Rémi Verschelde (Akien)
Additions:
**UPDATE : mageia-app-db now has a project's website : http://mageia-app-db.tuxette.fr/projects/mageia-app-db/wiki **
Deletions:
Additions:
- mageia board approval, so that this project can become mainstream (with LDAP integration, mageia.org integration...) : DONE https://mageia.org/pipermail/mageia-discuss/20101103/002873.html and http://meetbot.mageia.org/mageia-meeting/2010/mageia-meeting.2010-11-02-20.05.html
- see roadmap at http://github.com/agallou/mageia-app-db
- see roadmap at http://github.com/agallou/mageia-app-db
Deletions:
Additions:
The project's goal is to address the following listed needs, through a web application (hopefully hosted on mageia servers), which could be the main access point for users searching for information on the available packages, backports requests and new soft requests handling.
Deletions:
Additions:
- mageia board approval, so that this project can become mainstream (with LDAP integration, mageia.org integration...) : DONE
- other devs : LATER in the development process, when we have a list of tasks which can be delegated
- artwork (we have to make a pretty web application) : depends on Mageia Guidelines. When they're ready we'll welcome contributions
- other devs : LATER in the development process, when we have a list of tasks which can be delegated
- artwork (we have to make a pretty web application) : depends on Mageia Guidelines. When they're ready we'll welcome contributions
Deletions:
- other devs : LATER in the development process
- artwork (we have to make a pretty web application)
Additions:
- mageia board approval, without which this project couldn't become mainstream (and so no LDAP integration, no mageia.org integration...) : DONE
- other devs : LATER in the development process
- artwork (we have to make a pretty web application)
Here is a first draft for the roadmap : http://github.com/agallou/mageia-app-db/wiki/ROADMAP
- other devs : LATER in the development process
- artwork (we have to make a pretty web application)
Here is a first draft for the roadmap : http://github.com/agallou/mageia-app-db/wiki/ROADMAP
Deletions:
- other devs
- design (we have to make a pretty web application)
- a mageia sysadm team member for coordination with the Mageia project
http://github.com/agallou/mageia-app-db/wiki/ROADMAP
Additions:
===ROADMAP ===
http://github.com/agallou/mageia-app-db/wiki/ROADMAP
http://github.com/agallou/mageia-app-db/wiki/ROADMAP
Additions:
- mageia board approval, without which this project couldn't become mainstream (and so no LDAP integration, no mageia.org integration...)
Deletions:
Additions:
===Existing discussions of interest or existing tools/processes===
~~- [[http://maemo.org/packages/package_instance/view/fremantle_extras-testing_free_armel/lugdulov/0.3.0-2/ example of package submitted]] people can vote, add comments, report bugs, see changes, even [[http://maemo.org/packages/view/lugdulov/ see all versions and activity]]
~~- [[http://maemo.org/packages/package_instance/view/fremantle_extras-testing_free_armel/lugdulov/0.3.0-2/ example of package submitted]] people can vote, add comments, report bugs, see changes, even [[http://maemo.org/packages/view/lugdulov/ see all versions and activity]]
Deletions:
Additions:
~- LibreOffice is thinking of using Pootle, which seems to be appropriate from their discussions. See : http://translate.sourceforge.net/wiki/pootle/index and : http://en.wikipedia.org/wiki/Pootle
Deletions:
Additions:
~- Maemo QA process for applications : http://bergie.iki.fi/blog/application_quality_assurance_in_linux_distributions/
~~- http://wiki.maemo.org/Extras-testing#How_it_works_in_practice
~~- http://wiki.maemo.org/Extras-testing#How_it_works_in_practice
Deletions:
Additions:
~- http://wiki.maemo.org/Extras-testing#How_it_works_in_practice
Additions:
LibreOffice is thinking of using Pootle, which seems to be appropriate from their discussions. See : http://translate.sourceforge.net/wiki/pootle/index and : http://en.wikipedia.org/wiki/Pootle
Additions:
~~- http://maintainers.mandriva.com/listpkgs.php?owner=1 existing list of unmaintained packages
~~- http://sophie.zarb.org/stat/Mandriva,cooker stats of packages / packagers
~~- http://sophie.zarb.org/stat/Mandriva,cooker stats of packages / packagers
Additions:
~- https://mageia.org/pipermail/mageia-discuss/20101024/002601.html Some people could review current packages, some other could write proper description, a third set will review it, and the last part of the group will organize this with packagers and push the description to cauldron.
~~- http://www.debian.org/doc/developers-reference/best-pkging-practices.html#bpp-pkg-synopsis good practices for descriptions
~~- http://www.debian.org/doc/developers-reference/best-pkging-practices.html#bpp-pkg-synopsis good practices for descriptions
Additions:
~~- http://mdk.jack.kiev.ua/stats/doc/trunk/po/ Mandriva Tools Localization Stats for rpm-summary-contrib.po, rpm-summary-main.po...
Additions:
~- https://mageia.org/pipermail/mageia-discuss/20101024/002586.html One problem in choosing packages is that for many a description of what the app does is sparse or nonexistent
Additions:
CategoryMageiaDev
Deletions:
Revision [239]
Edited on 2010-10-27 20:54:21 by BenoitAudouard [some precisions + existing discussions]Additions:
- //have official package pages which can be linked from upstream projects websites or used by other distributions to find easily information about our packages (can be particularly useful for localized short summary and description.//
- cross-distribution comparisons of packages will sometimes require to identify different naming of packages among distributions (particularly for libs)
===Existing discussions of interest===
Some discussions can contribute to some parts of this project.
~- https://mageia.org/pipermail/mageia-dev/20101025/001356.html maintainer groups, for some packages we have more than one people willing to work on that package
CategoryMageiaDevc
- cross-distribution comparisons of packages will sometimes require to identify different naming of packages among distributions (particularly for libs)
===Existing discussions of interest===
Some discussions can contribute to some parts of this project.
~- https://mageia.org/pipermail/mageia-dev/20101025/001356.html maintainer groups, for some packages we have more than one people willing to work on that package
CategoryMageiaDevc
Deletions:
CategoryMageiaDev
Additions:
In what follows, I will suppose that the release cycle is a stable release every x months, with security/bugfix updates and backports for version updates. However, most of what follows still applies for a rolling release.
Deletions:
Additions:
In what follows, I will suppose that the release cycle is a stable release every x months, with security/bugfix updates and backports for version updates.
Additions:
- interaction with Sophie / common features merge if needed / help using the RPM databases : Olivier Thauvin (Nanar)
Deletions:
Additions:
- Adrien Gallou (ttp)
- alpha/beta testing, translations
- Marianne Lombard (Jehane)
- alpha/beta testing, translations
- Marianne Lombard (Jehane)
Deletions:
- alpha/beta testing
Additions:
- interaction with Sophie / common features merge if needed / help using the RPM databases : Olivier Thauvin
- mageia board approval, without which this project can become mainstream (and so no LDAP integration, no mageia.org integration...)
- mageia board approval, without which this project can become mainstream (and so no LDAP integration, no mageia.org integration...)
Deletions:
- interaction with Sophie / common features merge if needed / help using the RPM databases : Olivier Thauvin ?
Additions:
- **download package**
- //download source package//
- __others__
- //have official package pages which can be linked from upstream projects websites or used by other distributions to find easily information about our packages.//
- //download source package//
- __others__
- //have official package pages which can be linked from upstream projects websites or used by other distributions to find easily information about our packages.//
Revision [211]
Edited on 2010-10-24 14:27:24 by BenoitAudouard [some precisions + existing discussions]Additions:
- **easy opt-in as tester for specific packages ou package groups**
- **collect and see users' needs (backports, new softs)**
- **request for testing (especially for update candidates and package version upgrade (aka backports) candidates)**
- **empower users into testers ("you asked for this backport, please test it and report back. Do you accept to test future backports for this package too?")**// or even into packagers (see which new apps users requested, and try to build the src.rpm for it)//
- **collect and see users' needs (backports, new softs)**
- **request for testing (especially for update candidates and package version upgrade (aka backports) candidates)**
- **empower users into testers ("you asked for this backport, please test it and report back. Do you accept to test future backports for this package too?")**// or even into packagers (see which new apps users requested, and try to build the src.rpm for it)//
Deletions:
- ***collect and see users' needs (backports, new softs)***
- ***request for testing (especially for update candidates and package version upgrade (aka backports) candidates)***
- ***empower users into testers ("you asked for this backport, please test it and report back. Do you accept to test future backports for this package too?")***// or even into packagers (see which new apps users requested, and try to build the src.rpm for it)//
Revision [210]
Edited on 2010-10-24 14:26:04 by BenoitAudouard [some precisions + existing discussions]Additions:
===Project: mageia-app-db===
Deletions:
Revision [209]
Edited on 2010-10-24 14:25:39 by BenoitAudouard [some precisions + existing discussions]Additions:
===Project** : mageia-app-db===
===Which needs do we want to address?===
===Some constraints:===
===Why a dedicated application and not just using bugzilla?===
===What about Sophie?===
===What's the name of this project?===
===Already available resources for this project===
===Resources needed for the project development===
----
CategoryMageiaDev
===Which needs do we want to address?===
===Some constraints:===
===Why a dedicated application and not just using bugzilla?===
===What about Sophie?===
===What's the name of this project?===
===Already available resources for this project===
===Resources needed for the project development===
----
CategoryMageiaDev
Deletions:
**Which needs do we want to address?**
**Some constraints**:
**Why a dedicated application and not just using bugzilla?**
**What about Sophie?**
**What's the name of this project?**
**Already available resources for this project **
**Resources needed for the project development**
Additions:
- stats on package usage, if possible
Additions:
- ability to contribute better descriptions for existing packages (as they say many package descriptions are useless)
Additions:
- integration into Mageia website (using the LDAP user database). If possible, nice to have : SSO (single sign on).
Deletions:
Additions:
**Already available resources for this project **
- project lead
- Samuel Verschelde (Stormi)
- specifications, development
- Adrien Gallou (technical lead)
- Samuel Verschelde (Stormi)
- alpha/beta testing
- Rémi Verschelde (Akien)
- Daniel Tartavel
**Resources needed for the project development**
- mageia board approval, without which there would be no such project
- other devs
- design (we have to make a pretty web application)
- a mageia sysadm team member for coordination with the Mageia project
- interaction with Sophie / common features merge if needed / help using the RPM databases : Olivier Thauvin ?
- translators (first version can be english only, but localization is planned from a technical point of view from the start)
- project lead
- Samuel Verschelde (Stormi)
- specifications, development
- Adrien Gallou (technical lead)
- Samuel Verschelde (Stormi)
- alpha/beta testing
- Rémi Verschelde (Akien)
- Daniel Tartavel
**Resources needed for the project development**
- mageia board approval, without which there would be no such project
- other devs
- design (we have to make a pretty web application)
- a mageia sysadm team member for coordination with the Mageia project
- interaction with Sophie / common features merge if needed / help using the RPM databases : Olivier Thauvin ?
- translators (first version can be english only, but localization is planned from a technical point of view from the start)