Server updated

A few minutes ago we completed the update to the latest version of the MusicBrainz server. New features: Implemented the changes to alleviate some of the problems related to Style Guideline #5 Added new show artists link in the album edit links. This shows all of the tracks and change track artist links for a … Continue reading “Server updated”

A few minutes ago we completed the update to the latest version of the MusicBrainz server.

New features:

  • Implemented the changes to alleviate some of the problems related to Style Guideline #5
  • Added new show artists link in the album edit links. This shows all of the tracks and change track artist links for a given album, which is a nice short-cut for changing one track artist and not a whole album at the same time.
  • Wiki formatting in annotations

Closed bugs:

  • Users cannot remove their email address if they have moderations open. (bug #1222947)
  • cannot create duplicate artist during change track/move album (bug #1332702)
  • changed the ‘Mailing List’ links to be consistent (bug #1333094)
  • CSS: minor margin problem in 20051023 release (bug #1344427)
  • Indicate on subject line if mod note is for your mod (bug #1348545)
  • Add rel=”nofollow” to outgoing AR web links (bug #1260342)
  • deselect AR link leads to unknown artist/album (bug #1358789)
  • AR display: still showing ‘…’ when View All Relationships (bug #1232367)
  • FreeDB’s imports of AC/DC and such bad (bug #1014240)
  • group link types for URLs selectable (bug #1363133)
  • ModBot should not delete artist if it is target for any mods (bug #1349243)
  • [patch] Homepage HTML no longer validates (bug #1337604)
  • Multiple Duplicate artists created during import of VA album (bug #1339958)
  • New “Release” page when adding album ignores preferences (bug #1335764)
  • Empty artists script causes DB server to crash (bug #1375624)

Please file a bug report if you find something amiss.

Technorati Tags: ,

MusicBrainz web service: Time to adopt a Tos?

I recently got word that at least one for-profit company (who shall remain nameless right now) is/was using the MusicBrainz web service in their paid commercial offering. Personally, I don’t think its OK for a for-profit company to be consuming the resources of a non-profit — we make all of our data and software available … Continue reading “MusicBrainz web service: Time to adopt a Tos?”

I recently got word that at least one for-profit company (who shall remain nameless right now) is/was using the MusicBrainz web service in their paid commercial offering. Personally, I don’t think its OK for a for-profit company to be consuming the resources of a non-profit — we make all of our data and software available for companies to download and use for free (as in speech and beer). If someone wants to use our data for their product, they should do it with their own resources.

For the first set version of the Terms of Service, I would like to keep things simple and not add too many rules. Given that I would like to solicit feedback about adopting the following Terms of Service for the web service:

I’d like to get some feedback on this, so please leave a comment:

  • Does this make sense philosophically?
  • Do you spot any problems with this setup?
  • What else should we consider?

Technorati Tags: ,

The impending quasi-death of Style Guideline #5

On January 8th, 2006 we will update the server with the Style Guideline 5 Disaster Relief fix that was discussed at the MusicBrainz Summit 7. From the wiki page: The plans are as follows: Allow albums with various artists on the tracks but which are attributed to one artist to be moved to this artist. … Continue reading “The impending quasi-death of Style Guideline #5”

On January 8th, 2006 we will update the server with the Style Guideline 5 Disaster Relief fix that was discussed at the MusicBrainz Summit 7.

From the wiki page:

The plans are as follows:

Allow albums with various artists on the tracks but which are attributed to one artist to be moved to this artist.

Change the StyleGuideline like this: “If two or more primary artists perform on a track, create a collaboration artist for them and attach the track to it.”

Note, that the use of “feat.” will still be valid for guest performing artists.

For more information on this change, please read the wiki page. These changes are now live on the staging server if you want to give them a try.

Technorati Tags: , ,

Server mini update

We just updated the server with a set of minor bug fixes. Mostly formatting and appearance bugs have been fixed and new preferences to control how the top menu works have been added. That’s it — happy brainzing!

We just updated the server with a set of minor bug fixes. Mostly formatting and appearance bugs have been fixed and new preferences to control how the top menu works have been added. That’s it — happy brainzing!

Server updated finally!

The server has been updated – this release includes a redesigned navigation system, changes to the Autofix (a.k.a. Guess Case) tool and Album Editor. Track durations can now be edited and a number of smaller bugs have been fixed. A big thanks goes out to g0llum, lukz, matt and djce for making this release a … Continue reading “Server updated finally!”

The server has been updated – this release includes a redesigned navigation system, changes to the Autofix (a.k.a. Guess Case) tool and Album Editor. Track durations can now be edited and a number of smaller bugs have been fixed.

A big thanks goes out to g0llum, lukz, matt and djce for making this release a reality. Now that we have this pesky re-org release out of the way, we hope to bring you several more releases before the end of the year.

Continue reading “Server updated finally!”

Server Updates

The server has been updated once again, bringing you Album Languages, completely rewritten Guess Case functionality, fancy-looking input forms and a few bug fixes. Read on for the full change log…

The server has been updated once again, bringing you Album Languages,
completely rewritten Guess Case functionality, fancy-looking input forms
and a few bug fixes.

Read on for the full change log…

Continue reading “Server Updates”

Wikidocs server release

We just updated the main server with improved and updated documentation and improved news item handling. This release allows us to delegate the documentation tasks of MusicBrainz to a greater number of people, which should keep our documentation more up to date. Wikidocs A number of static web pages for documentation and other content that … Continue reading “Wikidocs server release”

We just updated the main server with improved and updated documentation and improved news item handling. This release allows us to delegate the documentation tasks of MusicBrainz to a greater number of people, which should keep our documentation more up to date.

Wikidocs

A number of static web pages for documentation and other content that goes stale over time, has been replaced with a set of wiki pages. To accomplish this, we’ve created a separate new wiki that is accessible to a handful of brainerz who have volunteered as documentation experts. All of the pages in this wiki are camouflaged so that the end user doesn’t really see that it is a wiki. Visitors with an untrained eye should not notice that our documentation is now served via a wiki — the end user will just see that the wikidoc pages have a prefix of /wd.

Blog news and release notes

The Movable Type blog software is now used to publish release notes (such as this one) and general news entries. This centralizes the news into one convenient place where we can give measured access to various people in the community. It also removes some of the clutter that has built up in the main web page.

MetaBrainz and financial pages

The MetaBrainz web page has been launched and all financial pages have been moved there. More on this tomorrow during the official launch!

Changes of interest to developers

Dave Evans says:

Replication: changed DB_IS_REPLICATED to REPLICATION_TYPE – finer degree
of control. When importing data into a slave, refuse to import
non-replicated tables. Rewrote the replication slave code to be more
robust, and slightly faster.

Other minor fixes for when running as a slave.

committed a patch by Lukas Lalinsky to avoid a server trip when changing
artist type

Fixed very minor date-related error in RelationshipBox

Advanced relationships released!

Some will say that hell froze over today… We just updated the main server with Advanced Relationships (AR)! After nearly two years of brainstorming and several months of tinkering, the new feature is finally live! (see the release notes for details) This new feature takes MusicBrainz into a new direction towards becoming a music encyclopedia … Continue reading “Advanced relationships released!”

Some will say that hell froze over today…

We just updated the main server with Advanced Relationships (AR)!

After nearly two years of brainstorming and several months of tinkering, the new feature is finally live! (see the release notes for details)

This new feature takes MusicBrainz into a new direction towards becoming a music encyclopedia — as opposed to a simple music metadatabase. While the server team does not believe in version numbers for the server (we prefer to use dates), this could be considered MusicBrainz Version 1.75 — its not quite MusicBrainz 2.0, but we’re getting really close. Now that we have Advanced Relationships in place we will be able to easily add on Concerts and Record Label support in future releases — that would bring us to MusicBrainz 2.0. ๐Ÿ™‚

A few more notes about this release:

  1. IMPORTANT if you have a replicating server (!!): Due to a small bork-up in the release process, you must do a full import on your database to kickstart the replication process again. Sorry for the hassle! ๐Ÿ™
  2. If the site hassles you about an unverified mail address, simply log out and back in.
  3. If you’re adding AR links and think up new link types or new instruments/vocals, please add them to this wiki page
  4. How does AR change the styleguidelines? Should you still do silly things like ‘feat.’? Yes, please continue to follow the style guidelines. I’ll work with Tarragon to update them with respect to AR.

Big thanks for helping with this goes to: Dave Evans and Don Redman. Thanks to everyone else who helped brainstorm and test the new feature!