Bodega meeting notes

Aaron J. Seigo aseigo at kde.org
Mon Nov 4 09:22:33 UTC 2013


Hi everyone,

Here are the notes from the bodega meeting.

== Agenda

* defining desired feature set (not limited to this release cycle)
* selection of feature set goal for v0.2
* dev cycle length (e.g. how many weeks)

== Attendees

* aseigo
* zack
* notmart
* terietor 
* kokeroulis 
* unormal

== Feature Set Identification

* ability to tip/donate
* subscriptions (e.g. for magazines)
* expanded support for albums/collections. aseigo added a lot of them to 
bugzilla at kde.org. we do need to be able to add an images and do pricing for 
lists of subassets, download them all, and work with whole lists from the 
publishers side
* sorting, in particular combined with searching but it also affects all 
listings. by date of publication/last update, number of downloads,ranking and 
name,
* nice support for "featured", "editor picks" and such (and use it to make a 
pretty startup/welcome page in the client)
* web ui
* in-app purchases
* messaging (email digesting, ability to filter / turn specific kinds of 
messages off, in-system messaging so you don’t have to perpetually check your 
email and which can be used for quick communication between warehouse and 
partners)
* alternative files for assets (books in multiple formats, applications with 
different builds for different systems)
* custom post-processing for certain events, in particular publishing
   * proper download size for rpms that are from an identifier file
* migrate License out of assets table and make a tag
* add link field to tags (so licenses can be linked to explanatory text, e.g.)
*  curation: ability to add tags you own to other people's assets
* other payment methods other than CC-via-stripe

== Dev Cycle

Short with a number of crucial bug fixes and lets say 2 major features. short, 
manageable, sweet and still exciting

Dev rules:
* all bug fixes from here on out must come with a corresponding unit test
* all feature dev done in a topic branch
* features must have good code coverage with unit tests (will measure with 
istanbul)
* all changes to database (sql, plsql or default data set) must have an update 
* file in sql/updates
* bug fixes
  * small fixes go into the stable branch, then merge into master
  * large fixes not suitable for stable (like the licenses thing) -> topic 
branch

== v0.2 Topic Selection

Features
* tipping / pay what you want
* collections epic
https://bugs.kde.org/buglist.cgi?list_id=779837&short_desc=collections&query_format=advanced&bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&short_desc_type=allwordssubstr&product=bodega

Fixes
* licenses as tags (aseigo on server, marco on manager app)
* publish post-processing (proper download size for rpms that are from an 
identifier file (notmart)
* automatic mimetype

== Web Client
First beta based on emberjs, parallel dev with server v0.2

== v0.3 Short List?
* multiple files for asset
* subscriptions


-- 
Aaron J. Seigo


More information about the Active mailing list