#MeeGork

First day was slightly hindered by the dead office firewall box, but still good progress:

• features list and prioritization
• basic architectural plan
• Midgard schemas for package and repository information
• OBS client library for PHP
• started on .spec file parser

.spec file parser can now read basic data, such as name, version, url etc. The complex data parsing will be implemented tomorrow (e.g. depends x.y.z package versions etc)

I will also work on the debian control and dsc parsers, by borrowing code from @xfade.

@ferenc great! I hope today we'll be able to retrieve, store and browse apps from OBS

This is where we will work on the Packages web UI with @xfade http://github.com/nemein/com_meego_packages

If you want to run a copy of the Packages software we're working on, here is how:

• You need PHP 5.3
• You need php5-midgard2
• You need Pake
• You need PHPTAL
• You need a Git checkout of git://github.com/midgardproject/midgardmvc_core.git

$ cd midgardmvc_core
$ pake init_mvc [https://github.com/nemein/com_meego_p...](https://github.com/nemein/com_meego_packages/raw/master/application.yml) /path/to/target/directory

$ php -c /path/to/target/directory/php.ini /path/to/target/directory/midgardmvc_core/httpd/midgardmvc-root-appserv.php

Package information coming from OBS can now be browsed, though lots of work needed to make it actually nice

Cool!
Nice work in a few days.

Packages component functionality is now there. Next up is commenting. Initially we need:

• Listing comments for an object
• Posting a new comment (registered users only)
• Feed of comments for an object
• Requesting email notifications for new comments
• Importing comments from an external feed

RPM spec parser done. Now we are integrating it with the rest of the system. Data has been pulled from OBS and inserted to the database. Next is to display that on a web page. Good progress guys!

I will be doing the debian control and dsc parsing in this sprint too, because we want that for Maemo ;)

Getting more data from the packages (thanks to the .spec file parser from @ferenc)

PHP's XmlWriter seems to be the way to go when we start generating OCS APIs tomorrow http://simonwillison.net/2003/Apr/29/xmlWriter/

@bergie that's the wrong link. proper one is this: http://docs.php.net/xmlwriter

Packages can now be commented by valid users. Needs to look nicer, of course

Sketching the MeeGo Extras workflow:

• Check whether user is allowed (is maintainer?)
• Check that package is valid (package name and targets checks)
• Build and copy to Testing
  
  - If build fails, then we notify and cancel
• Get reviews from packages web page (timeout if we don't get them)
• Check reviews
• Copy to Extras
• OK

@indeyets is improving the Pake application installer to be smarter about dependencies and I'm working on attachment variant serving

Now that we have a variant-capable attachment server (powered by Zeta Components, package screenshots coming from OBS work too.

Package relations are now stored in the database. We deal with the following relations:

• runtime dependencies
• build dependencies
• provided packages
• obsoleted packages
• conflicting packages

TODO:

comments:
- subscribe to comments
- reply to comment
- mail owner of package on comment

packages:
- show requires, buildrequires linked to actual package instance pages
- show maintainers
- link to package in actual repository

ocs:
- create ocswriter class for writing both XML and JSON output.
- content/list

repository:
- list repositories by release. For example MeeGo:1.1

rating:
- create rating component

Downloads:
- create template for Downloads
- show latest, hot, popular

Package relations are now shown on the package details page. Although we still don't provide nice links. Wonder how to check if a package exists in that particular repository...

Added most of the remaining minimally needed OCS api parts.

Next up will be to setup a staging VM at meego.com