python-musicbrainz3: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(Added musicbrainz-devel mailing list link)
No edit summary
Line 1: Line 1:
The python-musicbrainz3 package is the successor of python-musicbrainz2.
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.
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.
Line 13: Line 13:
* Keep the amount and quality of documentation
* Keep the amount and quality of documentation
* Write more test cases
* Write more test cases

== Project Plan ==

There are a few open tasks:

# Set up project infrastructure
## Wiki page ('''done''')
## Git repository (Rob, '''in progress''')
## Jira project?
## Reviewboard?
# Evaluate tools
## XML mapping tool (Matt, '''in progress''')
## Unit test runner (nose?)
# Set up project structure in the repository


== Links ==
== Links ==
Line 26: Line 40:
== Project Infrastructure ==
== Project Infrastructure ==


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


== Ideas ==
== Ideas and Open Questions ==


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

Revision as of 10:51, 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

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?