The Summer of Code application process has just begun and we’re soliciting feedback on what projects we should suggest to students this year. Please take a look at our Summer of Code Ideas page and add your ideas if its not already there.
Thanks!
MetaBrainz Foundation Community Blog
The Summer of Code application process has just begun and we’re soliciting feedback on what projects we should suggest to students this year. Please take a look at our Summer of Code Ideas page and add your ideas if its not already there.
Thanks!
Sorry for being a whole week behind the scheduled update time! However, we’ve got a huge release here, which will hopefully make up for the delay!
Many thanks to Calvin Walton, Johannes Weißl, Ian McEwen, Michael Wiencek and the MusicBrainz developers for all their work on this release.
A Git tag should be live later, but the commit is b5f45992a24bf.
Nicolás Tamargo (reosarevok) is replacing Kuno Woudt (warp) as style leader. This will allow Kuno to fully concentrate on development, and also allow our other style leader Nikki to dedicate more of her time to testing changes and make it less likely for us to have botched releases.
We are also updating the proposal process, and tying it to the Jira tracker, to avoid the manual updating of the proposal table and problems with two people using the same proposal number by mistake. The updated system is at Proposals – the huge table there has been moved to Proposals/History
We just finished pushing out an update last night, and sadly it didn’t go particularly smoothly. As part of ongoing efforts to try and fix the release editor, we temporarily made everything worse and ended up losing quite a lot of session data. I’m profusely sorry that this didn’t go better! We think things are stable again now though, so if you do see any bugs that you haven’t encountered before, please do make sure to let us know over at the bug tracker. Other than that, there were quite a few internal changes to our production setup in this release – we moved to a more modern Plack based setup and used our recent Carton packaging work. Here are the other bugs that got fixed. Thanks to Ian McEwan and Michael Wiencek for helping make this release happen!
Our friends at Last.fm just donated a 48 port gig switch to MusicBrainz! This new (to us) switch will allow us to shorten the update cycle for our indexed searches. Currently it takes about 3 hours to generate the indexes and to push them out to the search servers. With this new switch, we should be able to push the indexes quite a bit faster, which should shave off 60-90 minutes off our update cycle.
Thanks so much for the donation! Thanks to Adrian for making this happen in next to no time!
Yesterday we held our mini-summit in London to great success. The MusicBrainz team huddled up in a hotel last night and finished writing up notes of everything we covered, and you can now have a look at them on the wiki at MusicBrainz Summit/2012-Mini_Summit/Notes. In general, we provided an update of what’s been happening at MusicBrainz, what’s coming up in the future, and heard how each company are using MusicBrainz. Discussions have started with respect to classical support, but don’t expect anything concrete any time soon!
Many thanks to everyone who came along to this summit and helped make it work – it was great seeing you all!
On Monday we’re having the MusicBrainz mini-summit in London. Following the summit, starting at 6pm, we’re going to move to the Tower Tavern to have a pint of beer (or a few).
While the summit is open to people who have registered ahead of time, the pub gathering will be open to anyone who would like to join in. We’re not going to have any formal topics scheduled for the gathering — just a friendly gathering of like minded souls and of course, beer!
I hope to see you on Monday evening!
We’ve just pushed out the last MusicBrainz web server update out for this month. Here are the bugs we’ve squashed, and the new features and improvements that have been added. As always, keep helping out with scheduling at the scheduling game, and we’ll do our best to get the important things fixed as soon as we can! Thanks to Ian McEwan, Lukáš Lalinský, Calvin Walton, Johannes Weißl and the MusicBrainz developers for their work on this update.
The tag for this release is v-2012-01-26-ngs-bug-fixes.
Andy Hawkins says:
In conjunction with Lukas I’ve been working on a complete rewrite of libmusicbrainz to support the new Web Service v2 released alongside NGS. I’m happy to announce the official release of this new library (libmusicbrainz4).
The library is written as a relatively simple parser for the results from the Web Service, with as little logic as possible. This should mean it is easy to maintain to keep in step with any changes in the schema for the XML Web Service.
The main interface is a C++ class ‘CQuery’, that returns a Metadata object containing a parsed version of the response. There is also a C interface that loosely wraps the C++ classes.
Using the library requires a good understanding of the queries and responses to and from the Web Service. Download the library, or browse the online documentation or generate the documentation from the source with make docs.
If you find any issues, please report them using JIRA (under the project ‘libmusicbrainz’).
I will follow the musicbrainz-devel mailing list and the #musicbrainz-devel IRC channel on freenode in order to answer questions if at all possible.
Thanks.
Andy
Sadly, our testing for replication failed to catch a problem with the instructions we posted yesterday. If, when running the replication scripts you encountered the below error, please read on!
Attribute (conn) does not pass the type constraint because: Validation failed for 'DBIx::Connector' with value DBI::db=HASH(0x9e957d0) (not isa DBIx::Connector)
We made some changes to our database connection routines recently, and the replication scripts were not correctly migrated. We’ve got these changes in now though, so to fix this problem, repeat the instructions in our previous post, but use the v-2012-01-12-schema-change-2 tag. This should correspond to commit eb89c2b51f79..., which you can verify by running git rev-parse HEAD.
Sorry about these problems!