python-musicbrainz3: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
No edit summary
Line 27: Line 27:
## Unit test runner (nose?)
## Unit test runner (nose?)
# Set up project structure in the repository
# Set up project structure in the repository
# Gather data for the parser
## Update MMD Relax NG schema if necessary
## Prepare comprehensive set of example documents for the test suite


== Links ==
== Links ==

Revision as of 15:13, 14 March 2010

The python-musicbrainz3 package is the successor of python-musicbrainz2.

NGS is coming, so a rewrite is in order to keep up with MB development. This wiki page collects information, plans, and ideas for this project.

Feel free to edit!

Goals

  • Fully support the NGS data model and web service
  • Require Python 2.6 and aim to be as close to Python 3 as possible
  • Make it more pythonic where possible (naming conventions?)
  • Remove rarely used cruft (what would that be?)
  • Keep the amount and quality of documentation
  • Write more test cases

Project Plan

There are a few open tasks:

  1. Set up project infrastructure
    1. Wiki page (done)
    2. Git repository (Rob, in progress)
    3. Jira project?
    4. Reviewboard?
  2. Evaluate tools
    1. XML mapping tool (Matt, in progress)
    2. Unit test runner (nose?)
  3. Set up project structure in the repository
  4. Gather data for the parser
    1. Update MMD Relax NG schema if necessary
    2. Prepare comprehensive set of example documents for the test suite

Links

Links with documentation and other relevant information.


Project Infrastructure

  • This wiki page is the central source of information
  • Discussion can take place on the development mailing list
  • Soon: git repository
  • TODO: Review board?
  • TODO: Jira?

Ideas and Open Questions

  • Use an XML mapping package (xml.etree?)
  • Import version history into git?