https://wiki.musicbrainz.org/api.php?action=feedcontributions&user=RobertKaye&feedformat=atomMusicBrainz Wiki - User contributions [en]2024-03-28T21:52:20ZUser contributionsMediaWiki 1.39.4https://wiki.musicbrainz.org/index.php?title=Development/Summer_of_Code/2024/ListenBrainz&diff=77447Development/Summer of Code/2024/ListenBrainz2024-03-04T16:10:04Z<p>RobertKaye: </p>
<hr />
<div>ListenBrainz allows users to store a list of songs that they have listened to, get personalised recommendations, and more. [[:lb:|Try it out.]]<br />
<br />
== Getting started ==<br />
(see also: [[Development/Summer of Code/Getting started|Getting started with GSoC]])<br />
<br />
If you want to work on ListenBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some things that we might ask you about<br />
<br />
* Show that you understand the goals that ListenBrainz wants to achieve, which are written on its homepage<br />
* Create an oauth application on the MusicBrainz website and add the configuration information to your ListenBrainz server. Use this to log in to your server with your MusicBrainz details<br />
* Use the import script that is part of the ListenBrainz server to load scrobbles from last.fm to your ListenBrainz server, or the main ListenBrainz server<br />
* Use your preferred programming language to write a submission tool that can send Listen data to your local ListenBrainz server. You could make up some fake data for song names and artists. This data doesn't have to be real.<br />
* Try and delete the ListenBrainz database on your local server to remove the fake data that you added.<br />
* Look at the list of tickets that we have open for ListenBrainz and see if you understand what tasks the tickets involve<br />
* We strongly urge you to look through our ticket tracker and find some easy tickets, pick one and implement it and then send us a PR -- that way we can see how you work. Ask in IRC for clarification if you don't understand what the ticket means. Check out our [https://tickets.metabrainz.org/issues/?filter=12410 easy first bugs tickets]<br />
<br />
== Ideas ==<br />
We're adding a number of new social features to ListenBrainz that we hope will enable people discover more music they like and users who have similar music tastes to their own. We're working on some of these features now, but we will need to get help for other features:<br />
=== Add machine learning to BPM detection code ===<br />
<br />
Proposed mentors: ''mayhem''<br><br />
Languages/skills: Python/Flask, Machine Learning<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A deployable ML model that does accurate BPM detection<br><br />
Short Description: Create a machine learning model to help select the BPM of an audio track.<br><br />
Full Description:<br />
<br />
ListenBrainz could really use reliable BPM values for music that is represented in MusicBrainz. However, the algorithms for this have problems that are very tricky to solve. We believe that we can use neural networks to improve the "peak selection" portion of this project [https://github.com/scaperot/the-BPM-detector-python the-BPM-detector-python]. The ListenBrainz team will collect a suitable training dataset of a few thousand different audio files with known BPM values that can be used for training this model. We expect the participant who gets selected for this project to design, train and test the neural network and as a final deliverable create a model and it associated code necessary to integrate this into existing MetaBrainz projects for deployement.<br />
<br />
=== Integrate music streaming from Subsonic ===<br />
<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A new music service integration for users to play recordings on ListenBrainz.<br><br />
Short Description: Add support for playing music in BrainzPlayer from a Subsonic API<br><br />
Full Description:<br />
<br />
LB has a number of music discovery features that use BrainzPlayer to facilitate track playback. BrainzPlayer (BP) is a custom React component in LB that uses multiple data sources to search and play a track. As of now, it supports Spotify, Youtube and Soundcloud as a music service. LB would like to be able to stream music from a private music collection using web apps like [https://www.navidrome.org/ Navidrome], [https://www.funkwhale.audio/ Funkwhale] and other apps that implement the [http://www.subsonic.org/pages/index.jsp Subsonic API]. The following major tasks need to be completed: 1) Add subsonic API player as a service to our music services backend; this will require some schema changes/extensions in order to have user specify the URL of their service as part of the music service configuration. 2) Add the react based front-end UI to that allows users to setup their own Subsonic API instance as a service. 3) Add support to BrainzPlayer for logging into the subsonic API service and playing music from it.<br />
<br />
=== Integrate Deezer music streaming service for recording listens and playing music ===<br />
<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask, Typescript/React<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A new music service integration for users to play and record listens on ListenBrainz.<br><br />
Short Description: Add support for playing music in BrainzPlayer from the Deezer streaming service.<br><br />
Full Description:<br />
<br />
ListenBrainz has a number of music discovery features that use BrainzPlayer to facilitate track playback. BrainzPlayer (BP) is a custom React component in LB that uses multiple data sources to search and play a track. As of now, it supports Spotify, Youtube and Soundcloud as a music service. LB also supports linking a Spotify account to record listening history. We have looked into some other services and found that Deezer provides the music playback and recording listening history capability. Integrating these services into LB would make for a good SoC project.<br />
<br />
=== Integrate Internet Archive in BrainzPlayer ===<br />
<br />
Proposed mentors: ''lucifer'', ''monkey''<br><br />
Languages/skills: Python/Flask, Typescript/React, Postgres<br><br />
Estimated Project Length: 350 hours<br><br />
Difficulty: medium<br><br />
Excepted Outcomes: A deployable component to play internet archive music<br><br />
Short Description: Add support for playing music in BrainzPlayer from the Internet Archive<br><br />
Full Description:<br />
<br />
ListenBrainz has a number of music discovery features that use BrainzPlayer to facilitate track playback. BrainzPlayer (BP) is a custom React component in LB that uses multiple data sources to search and play a track. The [https://archive.org/details/78rpm 78 RPMs and Cylinder Recordings] is a collection of digitized recordings from physical releases of the early 20th century. Each recording comes with audio streaming, and metadata web service. It can be used to retrieve metadata automatically and to embed a player in ListenBrainz using BrainzPlayer. A lot of similar music collections are hosted by the Internet Archive which can be made available for playing on ListenBrainz.<br />
<br />
=== Revamped Last.fm listens importer ===<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask<br><br />
Estimated Project Length: 90 or 175 hours<br><br />
Difficulty: Medium<br><br />
Expected Outcomes: An improved importer for Last.FM users to import their listens into ListenBrainz.<br><br />
Short Description: Write a new Last.fm imported on the back-end.<br><br />
Full Description:<br />
<br />
ListenBrainz has a Last.fm importer written in Typescript that runs in the user's browser and lets them import scrobbles as listens in ListenBrainz. This is a one time import and if you submit scrobbles to Last.fm again, you need to re-run the importer manually. Also, the user needs to keep their tab open while the import runs which is inconvenient. Further, a lot of issues have been reported with it in the past like API calls to last.fm getting blocked by uBlock. Because the importer runs on the frontend/client side we have limited visibility into its functioning and errors. It would be better to create an importer like the one we have for spotify which runs on the backend and continuously updates ListenBrainz with spotify streams of the user.<br />
<br />
=== Exporting playlists to SoundCloud and Apple Music ===<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask<br><br />
Estimated Project Length: 90 or 175 hours, depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: SoundCloud/Apple Music users can export LB playlists to respective services<br><br />
Short Description: Add support for importing and exporting playlists to and from SoundCloud and Apple Music.<br><br />
Full Description:<br />
<br />
ListenBrainz generates music recommendation playlists. These playlists can be listened to on ListenBrainz using BrainzPlayer if the user has connected a music service to LB. Users can also configure such playlists to be automatically exported to the music service of their choice. Currently, we only support Spotify for playlist export. We should also add support for exporting playlists to SoundCloud and Apple Music.<br />
<br />
=== Music Recommendation: Implement a new Troi patch for generating music recommendations ===<br />
<br />
Proposed mentors: ''mayhem''<br><br />
Languages/skills: Python, possibly Postgres<br><br />
Estimated Project Length: 175 or 350 hours, depending on the scope that is suggested.<br><br />
Difficulty: Easy/Medium, depends on what is proposed.<br><br />
Expected outcomes: One or more finished, debugged and tested plugins for Troi.<br><br />
Short Description: Implement a new music recommendation patch for the Troi recommendation engine.<br><br />
Full Description:<br />
<br />
Our [https://github.com/metabrainz/troi-recommendation-playground troi recommendation toolkit] is our playground for developing recommendation algorithms. The toolkit already knows how to fetch data from ListenBrainz for stats, collaborative filtered recommended tracks, similar artists and similar recordings. From MusicBrainz it can fetch needed metadata such as genres and tags. The exact goal for this project really depends on you and what ideas you bring to the table, but the idea is to create a new Patch (plugin) for Troi that creates a new type of playlist that we can periodically offer to our users.<br />
<br />
If this sounds interesting to you, we strongly recommend that you turn up in our IRC channel and chat with at ''mayhem'' or ''lucifer'' about your idea before you go into a full proposal. Music recommendations can seem exciting and fun, but the details of how to make them happen and all the things that need to be considered is a significant challenge.<br />
<br />
=== '''Add RSS feeds''' ===<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python, possibly Postgres<br><br />
Estimated Project Length: 175 or 350 hours, depending on the scope that is suggested.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: Three or more functional RSS feeds.<br><br />
<br />
ListenBrainz provides a number of interesting opportunities for generating RSS feeds (a short list of user-requested feeds is in [[jira:MBS-941|MBS-941]] and linked tickets - but do not limit yourself to these). For example: New releases by an artist, new releases in genre, all new releases, user-specific new releases from [[:lb:explore/fresh-releases/|Fresh Releases]] 'for you' function. The complexity of our data allows for complex feed options - as well as new releases by date we may want to offer feeds of new additions (regardless of release date). You may need to communicate with the community, as well as potential third-party developers, to find what the most useful and requested types of feeds are. Some potential feeds rely on primarily MusicBrainz data, so there may be project cross-over that you will be expected to plan and manage.<br />
<br />
The RSS feeds will have to dynamically generated and served using a Flask endpoint so that in appropriate cases, each user get a customized feed based on their preferences and listening history. Also, RSS feeds/readers do not provide a method of authentication which will need to be figured in case some feed serves such data.<br />
<br />
<br />
'''Artist, Album, User Pages in ListenBrainz Android/iOS App for all users'''<br />
<br />
Proposed mentors: ''akshaaatt''<br><br />
Languages/skills: Kotlin, Android development, JetPack Compose, Retrofit / Swift, SwiftUI, Alamofire, iOS Development<br><br />
Estimated Project Length: 350 hours<br><br />
Difficulty: Medium<br><br />
Expected outcomes: A finished app feature that allows users to view detailed album, artist, and user pages within the app.<br><br />
Short Description: Enhance the mobile app with detailed album, artist, and user pages.<br><br />
Full Description:<br />
<br />
This project aims to significantly enhance the user experience of the ListenBrainz mobile application by introducing comprehensive album, artist, and user pages. This initiative will bridge the gap between the app and the ListenBrainz website's extensive database, offering a richer, more detailed exploration of music data directly within the app.<br />
<br />
The primary goal is to enable users to delve into detailed pages for albums, artists, and other users within the app. These pages will provide in-depth information, such as album track lists, artist discographies, similar artists, and detailed user profiles including their music preferences, listening habits, and social connections.<br />
<br />
Key features of this project include:<br />
<br />
* Album Pages: Display detailed album information including track lists, release dates, genres, and artist links. Integration with music streaming services to listen to tracks directly from the app may also be explored.<br />
* Artist Pages: Offer comprehensive artist profiles featuring a biography, discography, related artists, and upcoming events. This will enable users to discover new music and learn more about their favorite artists.<br />
* User Pages: Enhance user profiles to include detailed listening statistics, favorite tracks, albums, and artists. Implement a feature for users to follow others and explore music communities within the app.<br />
<br />
To ensure a seamless and intuitive user experience, the project will require close adherence to the UI/UX design guidelines provided by the ListenBrainz design team. This includes creating responsive layouts that adapt to various screen sizes and implementing a modern, user-friendly interface design using JetPack Compose for Android and SwiftUI for iOS.<br />
<br />
By completing this project, the ListenBrainz app will become a more comprehensive platform for music discovery and community engagement, offering detailed insights into albums, artists, and user profiles, all within a beautifully designed mobile application interface.<br />
<br />
=== Dashboard Page in ListenBrainz Android/iOS App for all users ===<br />
Proposed mentors: ''akshaaatt''<br><br />
Languages/skills: Kotlin, Android development, JetPack Compose, Retrofit / Swift, SwiftUI, Alamofire, iOS Development<br><br />
Estimated Project Length: 175 or 350 hours<br><br />
Difficulty: Medium<br><br />
Expected outcomes: A finished app feature that gives the user the ability to view your dashboard as well as that of other users<br><br />
Short Description: Add a dashboard page to our mobile apps.<br><br />
Full Description:<br />
<br />
This project aims to seamlessly integrate all functionalities of the ListenBrainz website's Dashboard into the ListenBrainz application. This integration will be achieved through a combination of web view components for certain features and native development for others, depending on the specific requirements of each functionality.<br />
<br />
The primary objective is to enable users not only to view their own dashboard within the app but also to explore the dashboards of other users. This exploration can be initiated in various ways, including through a search function or by selecting a user from their feed, leading to a more connected and interactive user experience.<br />
<br />
A crucial aspect of this project is to maintain design consistency with the ListenBrainz website. The mobile app's UI/UX should align with the design elements and user experience guidelines provided in the Figma files shared by the design team.<br />
<br />
By completing this project, the ListenBrainz app will offer a comprehensive profile/dashboard feature for users, mirroring the website's functionality. This includes displaying detailed music listening statistics, recent listens, top artists, and more, all within a user-friendly and engaging mobile interface.<br />
<br />
=== ListenBrainz iOS App - Road to Production ===<br />
Proposed mentors: ''akshaaatt''<br />
<br />
Languages/skills: Swift, SwiftUI, Alamofire, iOS Development<br><br />
Estimated Project Length: 175 hours<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: Match user interface and functionality as per figmas and the Android app, address bugs and ensure app stability.<br><br />
Short Description: To launch the iOS mobile app on the app store, we need to get relevant approvals. The design should be consistent, the app should be stable and all the app offerings should work as desired.<br><br />
Full Description:<br />
<br />
The developer should make sure that the Feed, Profile/Dashboard, Explore and Settings are all consistent with the Android app/relevant Figma design.<br />
<br />
The aim should be:<br />
<br />
* A fully functional ListenBrainz app for iOS that matches the user interface and functionality outlined in the project's design documents. [https://www.figma.com/file/tFLTQiq7QlA1oGRTJVtXml/ListenBrainz-App?type=design&node-id=351%3A956&mode=design&t=Cauk64QOJAR9Ui2e-1 Figma]<br />
* A stable and reliable app experience, with all features working as intended and any identified bugs resolved.<br />
<br />
By completing this project, the ListenBrainz app will offer a comprehensive user experience, mirroring the website's and Android app's functionality.<br />
<br />
=== BrainzPlayer Revamp in the ListenBrainz Android App ===<br />
Proposed mentors: ''akshaaatt''<br />
<br />
Languages/skills: Kotlin, Android development, JetPack Compose, ExoPlayer<br><br />
Estimated Project Length: 175 hours<br><br />
Difficulty: Medium<br><br />
Expected Outcomes: Improve user interface and functionality, address bugs and ensure app stability.<br><br />
Short Description: Refactor the BrainzPlayer in or android mobile app.<br><br />
Full Description:<br />
<br />
The ListenBrainz local player (BrainzPlayer) will undergo a UI/UX overhaul as per the [https://www.figma.com/file/tFLTQiq7QlA1oGRTJVtXml/ListenBrainz-App?type=design&node-id=351%3A956&mode=design&t=Cauk64QOJAR9Ui2e-1 Figma].<br />
<br />
This redesign will modernize the player's appearance and interaction, aligning it with the latest design trends and user expectations. The overhaul is not just cosmetic; it will extend to the app's functionality, with particular attention to the integration of Spotify and YouTube players. This feature will allow users to seamlessly play music from Spotify and YouTube directly within the ListenBrainz app, enriching the user's music experience by aggregating their music playback through a single interface.<br />
<br />
Additionally, the project will focus on refining the app's existing features and display mechanisms, ensuring that the music playback is not only smooth but also visually appealing and user-friendly.</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Development/Summer_of_Code/ApplicationTemplate&diff=77416Development/Summer of Code/ApplicationTemplate2024-02-22T11:27:30Z<p>RobertKaye: Created page with "When submitting an application to the MetaBrainz Foundation, please make sure to use the template below as the basis of your application. Please read the questions very carefu..."</p>
<hr />
<div>When submitting an application to the MetaBrainz Foundation, please make sure to use the template below as the basis of your application. Please read the questions very carefully and then answer them completely.<br />
<br />
Nickname:</br><br />
IRC nick/Matrix handle:</br><br />
Email:</br><br />
<br />
Do you have Twitter/X, Mostondon, GitHub, or any other public profiles you think we might find interesting?<br />
<br />
Tell us more about your proposed project? Where can we find any diagrams or other things that will help us understand<br />
your proposal better? (If these things are already covered in the main application, its safe to skip this question)<br />
<br />
As part of applying for SoC we require that you take your idea and write a post for our <br />
[https://community.metabrainz.org MusicBrainz MetaBrainz community site] with the tag [https://community.metabrainz.org/c/metabrainz/gsoc-applications gsoc-applications]<br />
so that we can help you review your idea before you dive deep into writing your application.<br />
<br />
Please propose the idea and then respond to any<br />
questions that may arise. Improve your proposal based on the feedback you receive from the community. If you cannot<br />
get the community to support your idea your chances for getting your proposal accepted are very slim. If you fail to get<br />
community feedback for your project idea, we will not accepted your project!<br />
<br />
Tell us about the computer(s) you have available for working on your SoC project?<br />
<br />
When did you first start programming?<br />
<br />
What type of music do you listen to? (please list a series of MBIDs as examples)<br />
<br />
What aspects of MusicBrainz/ListenBrainz/BookBrainz/Picard interest you the most?<br />
<br />
Have you ever used MusicBrainz to tag your files or use any of our projects in the past?<br />
<br />
Have you contributed to other Open Source projects? If so, which projects and can we see some of your code?<br />
<br />
If you have not contributed to open source projects, do you have other code we can look at?<br />
<br />
What sorts of programming projects have you done on your own time?<br />
<br />
How much time do you have available, and how would you plan to use it? Please note that you're not allowed to have a second job or be attending university while working on Summer of Code. It always ends badly for everyone and if we find out that you have another job or university courses, we're likely to fail you.</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Development/Summer_of_Code/2024&diff=77415Development/Summer of Code/20242024-02-22T11:17:22Z<p>RobertKaye: </p>
<hr />
<div>Are you interested in working with MetaBrainz in Google Summer of Code 2024? You're in the right place!<br />
<br />
== Important Schedule Note ==<br />
<br />
'''If you're arriving here after 18 March, 2024, you've missed your chance to apply with us. We will not consider applications from applicants who have not discussed their idea during the application discussion phase which ends March 18. We will make no exceptions.'''<br />
<br />
== Where to start ==<br />
<br />
; New to MetaBrainz?<br />
: The MetaBrainz Foundation has been set up to build community maintained databases and make them available in the public domain or under Creative Commons licenses.<br />
; New to MetaBrainz development and/or GSoC?<br />
: [[Development/Summer of Code/Getting started|Getting started with GSoC]]<br />
<br />
== Application template ==<br />
<br />
When you're ready to write your application, please use this <br />
[[Development/Summer_of_Code/ApplicationTemplate|Application Template]] as the basis of your application.<br />
<br />
== Projects ==<br />
<br />
=== [[Development/Summer of Code/2024/BookBrainz|BookBrainz]] ===<br />
{| class="wikitable"<br />
| rowspan="3" |[[File:BookBrainz logo small notext.png|link=https://wiki.musicbrainz.org/File:BookBrainz_logo_small_notext.png]]<br />
|BookBrainz is a database of book metadata.<br />
We're interested in projects that help us reach our roadmap, and that add major functionalities to the website.<br />
<br />
Please see our [[Development/Summer of Code/2024/BookBrainz|ideas page]] for more details and information on getting started.<br />
|-<br />
|'''Top 3 Desired Skills''': Node.js, React, SQL<br />
|-<br />
|[[Development/Summer of Code/2024/BookBrainz|Ideas page]]<nowiki> | </nowiki>[[bb:|Main page]]<nowiki> | </nowiki>[[discourse:c/bookbrainz|Forums]]<br />
|}<br />
----<br />
<br />
=== [[Development/Summer of Code/2024/ListenBrainz|ListenBrainz]] ===<br />
{| class="wikitable"<br />
| rowspan="3" |[[File:ListenBrainz logo small notext.png|link=https://wiki.musicbrainz.org/File:ListenBrainz_logo_small_notext.png]]<br />
|An open source music website that allows users to import their listen history. One of the goals is for this data to be used for building open music recommendation systems.<br />
|-<br />
|'''Languages/skills''': Python, Flask, Postgres, Spark, React, Android<br />
|-<br />
|[[Development/Summer of Code/2024/ListenBrainz|Ideas page]]<nowiki> | </nowiki>[[:lb:|Main page]]<nowiki> | </nowiki>[[discourse:c/listenbrainz/|Forums]]<br />
|}<br />
----<br />
<br />
=== [[Development/Summer of Code/2024/MetaBrainz|MetaBrainz]] ===<br />
{| class="wikitable"<br />
| rowspan="3" |[[File:MetaBrainz logo small notext.png|link=https://wiki.musicbrainz.org/File:MetaBrainz_logo_small_notext.png]]<br />
|A non-profit that believes in free, open access to data. It is the parent organization responsible for maintaining all other projects listed on this page. <br />
|-<br />
|'''Languages/skills''': Python, Flask, Postgres, HTML<br />
|-<br />
|[[Development/Summer of Code/2024/MetaBrainz|Ideas page]]<nowiki> | </nowiki>[[:lb:|Main page]]<nowiki> | </nowiki>[[discourse:c/metabrainz/|Forums]]<br />
|}<br />
----<br />
<br />
=== [[Development/Summer of Code/2024/MusicBrainz|MusicBrainz]] ===<br />
{| class="wikitable"<br />
| rowspan="3" |[[File:MusicBrainz logo small notext.png|link=https://wiki.musicbrainz.org/File:MusicBrainz_logo_small_notext.png]]<br />
|A community-maintained open source music encyclopedia that collects music metadata and makes it available to the public.<br />
|-<br />
|'''Languages/skills''': JavaScript (React), PostgreSQL, Rust<br />
|-<br />
|[[Development/Summer of Code/2024/MusicBrainz|Ideas page]]<nowiki> | </nowiki>[[mb:|Main page]]<nowiki> | </nowiki>[[discourse:c/musicbrainz|Forums]]<br />
|}<br />
----<br />
<br />
=== [[Development/Summer of Code/2024/Picard|MusicBrainz Picard]] ===<br />
{| class="wikitable"<br />
| rowspan="3" |[[File:Picard_logo_small_notext.png|link=https://wiki.musicbrainz.org/File:Picard_logo_small_notext.png]]<br />
|'''MusicBrainz Picard''' is a cross-platform (Linux/Mac OS X/Windows) application written in Python and is the official MusicBrainz [[MusicBrainz Enabled Applications|tagger]]. It supports the majority of audio file formats, is capable of using audio fingerprints ([[AcoustID|AcoustIDs]]), performing CD lookups and [[Disc ID|disc ID]] submissions, and it has excellent Unicode support.<br />
|-<br />
|'''Languages/skills''': Python, PyQt<br />
|-<br />
|[[Development/Summer of Code/2024/Picard|Ideas page]]<nowiki> | </nowiki>[[picard:|Main page]]<nowiki> | </nowiki>[[discourse:c/picard|Forums]]<br />
|}</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Development/Summer_of_Code/2024/Picard&diff=77398Development/Summer of Code/2024/Picard2024-02-12T12:23:18Z<p>RobertKaye: </p>
<hr />
<div>MusicBrainz Picard is a cross-platform (Linux/Mac OS X/Windows) application written in Python and is the official MusicBrainz [[MusicBrainz Enabled Applications|tagger]]. It supports the majority of audio file formats, is capable of using audio fingerprints ([[AcoustID|AcoustIDs]]), performing CD lookups and [[Disc ID|disc ID]] submissions, and it has excellent Unicode support. [[picard:|Try it out.]]<br />
<br />
==Getting Started==<br />
(see also: [[Development/Summer of Code/Getting started|Getting started with GSoC]])<br />
<br />
==Ideas==<br />
<br />
=== Configuration wizard on first run ===<br />
<br />
Proposed Mentors: ''outsidecontext'' / ''zas'' <br><br />
Languages/skills: Python / Qt<br><br />
Estimated Project Length: 175 hours<br />
Difficulty: Medium<br />
Expected Outcome: A fully debugged, deployable wizard for Picard.<br />
<br />
Implement a setup wizard that runs on first start. The wizard will replace the current "new user dialog" and will allow the user to setup the basic configuration. The setup wizard is focused on helping new users, so it should focus on the most relevant options while keeping things easy. See the ticket [[jira:PICARD-292|PICARD-292]].<br />
<br />
This project would entail the following components:<br />
<br />
# Define the relevant configuration options that the wizard should offer<br />
# Define the individual steps of the wizard dialog<br />
# Design the user interface with Qt designer<br />
# Implement the dialog logic in Python<br />
<br />
=== Add options for cover art processing ===<br />
<br />
Proposed Mentors: ''outsidecontext'' / ''zas'' <br><br />
Languages/skills: Python / Image processing<br><br />
Estimated Project Length: 350 hours<br />
Difficulty: Medium<br />
Expected Outcomes: A deployable new features PR for Picard.<br />
<br />
Picard should allow to post process cover art images provided by the providers. For this there could be provider independent options to restrict image sizes, resize images if it exceeds a maximum allowed size or automatic format conversion.<br />
<br />
This project would entail the following components:<br />
# Evaluate the suggested components for image processing and choose the best fit<br />
# Add the necessary options UI to allow the user to configure the image processing<br />
# Implement the image processing for resizing and format selection<br />
# Implement a image post processing plugin hook to allow plugins to do additional image manipulations<br />
<br />
Related ticket [https://tickets.metabrainz.org/browse/PICARD-2121 Add cover art image processing]</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Development/Summer_of_Code/2024/MetaBrainz&diff=77397Development/Summer of Code/2024/MetaBrainz2024-02-12T12:21:26Z<p>RobertKaye: </p>
<hr />
<div>The MetaBrainz Foundation is a non-profit that believes in free, open access to data. It has been set up to build community maintained databases and make them available in the public domain or under Creative Commons licenses. <br />
<br />
The projects listed here do not relate to any one *Brainz.<br />
<br />
== Getting started ==<br />
(see also: [[Development/Summer of Code/Getting started|Getting started with GSoC]])<br />
<br />
== Ideas ==<br />
<br />
=== MetaBrainz-wide notifications system ===<br />
<br />
Proposed mentors: ''lucifer/mayhem''<br><br />
Languages/skills: Python/Flask/Postgres<br><br />
Estimated Project Length: 350 hours.<br><br />
Difficulty: Hard<br><br />
Expected Outcomes: A system to show notifications to users on-site and in emails<br><br />
<br />
Right now we have no means of letting users know when something happened in their MeB community (read: all projects). For example, just in ListenBrainz we have the following use cases. In order to keep people interested in the project, we should be sending notifications to users when things happen:<br />
<br />
* They have a new follower<br />
* A track was recommended to them personally.<br />
* When a playlist was created for them.<br />
* A YIM, monthly YIM or monthly stats are ready for a user.<br />
<br />
There are probably more things for which we need to sending notifications, but you get the idea. Ideally such a system would set reasonable defaults for new users and then allow them to customize the settings to their own needs. Ideally the user could choose if they wish a certain notification to be sent at all and if so, if it should be sent immediately or in a digest. The user should also choose the digest frequency: None, daily, weekly.<br />
<br />
We have sketched more detailed requirements and implementation plans in the past. You should join our IRC channel to start discussion on this project.<br />
<br />
''Note:'' This is a very hard project and we're only going to select candidates who are very proficient with Python/Flask and Postgres.<br />
<br />
=== Matrix Room chatlogger ===<br />
<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask/Postgres or Node/Typescript/Postgres<br><br />
Estimated Project Length: 350 hours.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A chatlogger for our matrix rooms<br><br />
<br />
We have recently decided to migrate from IRC to matrix for communication. We have BrainzBot (a fork of BotBotMe), an IRC based bot that reads all the messages and logs them to a Postgres database. These logs are displayed on chatlogs.metabrainz.org. We have a functioning IRC-matrix bridge so BrainzBot chatlogging continues to work fine, but it would be preferred to have a matrix-based version of the bot eventually. Since we self host our matrix homeserver where a lot of the room related data is stored, it would also be interesting to explore if we can directly serve chatlogs using its existing database. In addition to chatlogging, BrainzBot has a few other commands that would need to be accommodated in this new bot.</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Development/Summer_of_Code/2024/ListenBrainz&diff=77395Development/Summer of Code/2024/ListenBrainz2024-02-12T11:56:27Z<p>RobertKaye: </p>
<hr />
<div>ListenBrainz allows users to store a list of songs that they have listened to, get personalised recommendations, and more. [[:lb:|Try it out.]]<br />
<br />
== Getting started ==<br />
(see also: [[Development/Summer of Code/Getting started|Getting started with GSoC]])<br />
<br />
If you want to work on ListenBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some things that we might ask you about<br />
<br />
* Show that you understand the goals that ListenBrainz wants to achieve, which are written on its homepage<br />
* Create an oauth application on the MusicBrainz website and add the configuration information to your ListenBrainz server. Use this to log in to your server with your MusicBrainz details<br />
* Use the import script that is part of the ListenBrainz server to load scrobbles from last.fm to your ListenBrainz server, or the main ListenBrainz server<br />
* Use your preferred programming language to write a submission tool that can send Listen data to your local ListenBrainz server. You could make up some fake data for song names and artists. This data doesn't have to be real.<br />
* Try and delete the ListenBrainz database on your local server to remove the fake data that you added.<br />
* Look at the list of tickets that we have open for ListenBrainz and see if you understand what tasks the tickets involve<br />
* If you want to, see if you can contribute to fixing a ticket. Either add a comment to the ticket or ask in IRC for clarification if you don't understand what the ticket means<br />
<br />
== Ideas ==<br />
We're adding a number of new social features to ListenBrainz that we hope will enable people discover more music they like and users who have similar music tastes to their own. We're working on some of these features now, but we will need to get help for other features:<br />
=== Add machine learning to BPM detection code ===<br />
<br />
Proposed mentors: ''mayhem''<br><br />
Languages/skills: Python/Flask, Machine Learning<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A deployable ML model that does accurate BPM detection<br><br />
Short Description: Create a machine learning model to help select the BPM of an audio track.<br><br />
Full Description:<br />
<br />
ListenBrainz could really use reliable BPM values for music that is represented in MusicBrainz. However, the algorithms for this have problems that are very tricky to solve. We believe that we can use neural networks to improve the "peak selection" portion of this project [https://github.com/scaperot/the-BPM-detector-python the-BPM-detector-python]. The ListenBrainz team will collect a suitable training dataset of a few thousand different audio files with known BPM values that can be used for training this model. We expect the participant who gets selected for this project to design, train and test the neural network and as a final deliverable create a model and it associated code necessary to integrate this into existing MetaBrainz projects for deployement.<br />
<br />
=== Integrate music streaming from Subsonic ===<br />
<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A new music service integration for users to play recordings on ListenBrainz.<br><br />
Short Description: Add support for playing music in BrainzPlayer from a Subsonic API<br><br />
Full Description:<br />
<br />
LB has a number of music discovery features that use BrainzPlayer to facilitate track playback. BrainzPlayer (BP) is a custom React component in LB that uses multiple data sources to search and play a track. As of now, it supports Spotify, Youtube and Soundcloud as a music service. LB would like to be able to stream music from a private music collection using web apps like [https://www.navidrome.org/ Navidrome], [https://www.funkwhale.audio/ Funkwhale] and other apps that implement the [http://www.subsonic.org/pages/index.jsp Subsonic API]. The following major tasks need to be completed: 1) Add subsonic API player as a service to our music services backend; this will require some schema changes/extensions in order to have user specify the URL of their service as part of the music service configuration. 2) Add the react based front-end UI to that allows users to setup their own Subsonic API instance as a service. 3) Add support to BrainzPlayer for logging into the subsonic API service and playing music from it.<br />
<br />
=== Integrate Deezer music streaming service for recording listens and playing music ===<br />
<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask, Typescript/React<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A new music service integration for users to play and record listens on ListenBrainz.<br><br />
Short Description: Add support for playing music in BrainzPlayer from the Deezer streaming service.<br><br />
Full Description:<br />
<br />
ListenBrainz has a number of music discovery features that use BrainzPlayer to facilitate track playback. BrainzPlayer (BP) is a custom React component in LB that uses multiple data sources to search and play a track. As of now, it supports Spotify, Youtube and Soundcloud as a music service. LB also supports linking a Spotify account to record listening history. We have looked into some other services and found that Deezer provides the music playback and recording listening history capability. Integrating these services into LB would make for a good SoC project.<br />
<br />
=== Integrate Internet Archive in BrainzPlayer ===<br />
<br />
Proposed mentors: ''lucifer'', ''monkey''<br><br />
Languages/skills: Python/Flask, Typescript/React, Postgres<br><br />
Estimated Project Length: 350 hours<br><br />
Difficulty: medium<br><br />
Excepted Outcomes: A deployable component to play internet archive music<br><br />
Short Description: Add support for playing music in BrainzPlayer from the Internet Archive<br><br />
Full Description:<br />
<br />
ListenBrainz has a number of music discovery features that use BrainzPlayer to facilitate track playback. BrainzPlayer (BP) is a custom React component in LB that uses multiple data sources to search and play a track. The [https://archive.org/details/78rpm 78 RPMs and Cylinder Recordings] is a collection of digitized recordings from physical releases of the early 20th century. Each recording comes with audio streaming, and metadata web service. It can be used to retrieve metadata automatically and to embed a player in ListenBrainz using BrainzPlayer. A lot of similar music collections are hosted by the Internet Archive which can be made available for playing on ListenBrainz.<br />
<br />
=== Revamped Last.fm listens importer ===<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask<br><br />
Estimated Project Length: 90 or 175 hours<br><br />
Difficulty: Medium<br><br />
Expected Outcomes: An improved importer for Last.FM users to import their listens into ListenBrainz.<br><br />
Short Description: Write a new Last.fm imported on the back-end.<br><br />
Full Description:<br />
<br />
ListenBrainz has a Last.fm importer written in Typescript that runs in the user's browser and lets them import scrobbles as listens in ListenBrainz. This is a one time import and if you submit scrobbles to Last.fm again, you need to re-run the importer manually. Also, the user needs to keep their tab open while the import runs which is inconvenient. Further, a lot of issues have been reported with it in the past like API calls to last.fm getting blocked by uBlock. Because the importer runs on the frontend/client side we have limited visibility into its functioning and errors. It would be better to create an importer like the one we have for spotify which runs on the backend and continuously updates ListenBrainz with spotify streams of the user.<br />
<br />
=== Exporting playlists to SoundCloud and Apple Music ===<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask<br><br />
Estimated Project Length: 90 or 175 hours, depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: SoundCloud/Apple Music users can export LB playlists to respective services<br><br />
Short Description: Add support for importing and exporting playlists to and from SoundCloud and Apple Music.<br><br />
Full Description:<br />
<br />
ListenBrainz generates music recommendation playlists. These playlists can be listened to on ListenBrainz using BrainzPlayer if the user has connected a music service to LB. Users can also configure such playlists to be automatically exported to the music service of their choice. Currently, we only support Spotify for playlist export. We should also add support for exporting playlists to SoundCloud and Apple Music.<br />
<br />
=== Music Recommendation: Implement a new Troi patch for generating music recommendations ===<br />
<br />
Proposed mentors: ''mayhem''<br><br />
Languages/skills: Python, possibly Postgres<br><br />
Estimated Project Length: 175 or 350 hours, depending on the scope that is suggested.<br><br />
Difficulty: Easy/Medium, depends on what is proposed.<br><br />
Expected outcomes: One or more finished, debugged and tested plugins for Troi.<br><br />
Short Description: Implement a new music recommendation patch for the Troi recommendation engine.<br><br />
Full Description:<br />
<br />
Our [https://github.com/metabrainz/troi-recommendation-playground troi recommendation toolkit] is our playground for developing recommendation algorithms. The toolkit already knows how to fetch data from ListenBrainz for stats, collaborative filtered recommended tracks, similar artists and similar recordings. From MusicBrainz it can fetch needed metadata such as genres and tags. The exact goal for this project really depends on you and what ideas you bring to the table, but the idea is to create a new Patch (plugin) for Troi that creates a new type of playlist that we can periodically offer to our users.<br />
<br />
If this sounds interesting to you, we strongly recommend that you turn up in our IRC channel and chat with at ''mayhem'' or ''lucifer'' about your idea before you go into a full proposal. Music recommendations can seem exciting and fun, but the details of how to make them happen and all the things that need to be considered is a significant challenge.<br />
<br />
=== '''Add RSS feeds''' ===<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python, possibly Postgres<br><br />
Estimated Project Length: 175 or 350 hours, depending on the scope that is suggested.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: Three or more functional RSS feeds.<br><br />
<br />
ListenBrainz provides a number of interesting opportunities for generating RSS feeds (a short list of user-requested feeds is in [[jira:MBS-941|MBS-941]] and linked tickets - but do not limit yourself to these). For example: New releases by an artist, new releases in genre, all new releases, user-specific new releases from [[:lb:explore/fresh-releases/|Fresh Releases]] 'for you' function. The complexity of our data allows for complex feed options - as well as new releases by date we may want to offer feeds of new additions (regardless of release date). You may need to communicate with the community, as well as potential third-party developers, to find what the most useful and requested types of feeds are. Some potential feeds rely on primarily MusicBrainz data, so there may be project cross-over that you will be expected to plan and manage.<br />
<br />
The RSS feeds will have to dynamically generated and served using a Flask endpoint so that in appropriate cases, each user get a customized feed based on their preferences and listening history. Also, RSS feeds/readers do not provide a method of authentication which will need to be figured in case some feed serves such data.<br />
<br />
=== Dashboard Page in ListenBrainz Android/iOS App for all users ===<br />
Proposed mentors: ''akshaaatt''<br />
Languages/skills: Kotlin, Android development, JetPack Compose, Retrofit / Swift, SwiftUI, Alamofire, iOS Development<br />
Estimated Project Length: 350 hours<br />
Difficulty: Medium<br />
Expected outcomes: A finished app feature that gives the user the ability to view your dashboard as well as that of other users<br><br />
Short Description: Add a dashboard page to our mobile apps.<br><br />
Full Description:<br />
<br />
This project aims to seamlessly integrate all functionalities of the ListenBrainz website's Dashboard into the ListenBrainz application. This integration will be achieved through a combination of web view components for certain features and native development for others, depending on the specific requirements of each functionality.<br />
<br />
The primary objective is to enable users not only to view their own dashboard within the app but also to explore the dashboards of other users. This exploration can be initiated in various ways, including through a search function or by selecting a user from their feed, leading to a more connected and interactive user experience.<br />
<br />
A crucial aspect of this project is to maintain design consistency with the ListenBrainz website. The mobile app's UI/UX should align with the design elements and user experience guidelines provided in the Figma files shared by the design team.<br />
<br />
By completing this project, the ListenBrainz app will offer a comprehensive profile/dashboard feature for users, mirroring the website's functionality. This includes displaying detailed music listening statistics, recent listens, top artists, and more, all within a user-friendly and engaging mobile interface.<br />
<br />
=== BrainzPlayer Revamp in the ListenBrainz Android App ===<br />
Proposed mentors: ''akshaaatt''<br />
Languages/skills: Kotlin, Android development, JetPack Compose, ExoPlayer<br><br />
Estimated Project Length: 350 hours<br><br />
Difficulty: Medium<br><br />
Expected Outcomes: Improve user interface and functionality, address bugs and ensure app stability.<br><br />
Short Description: Refactor the BrainzPlayer in or android mobile app.<br><br />
Full Description:<br />
<br />
The ListenBrainz local player (BrainzPlayer) will undergo a UI/UX overhaul as per the [https://www.figma.com/file/tFLTQiq7QlA1oGRTJVtXml/ListenBrainz-App?type=design&node-id=351%3A956&mode=design&t=Cauk64QOJAR9Ui2e-1 Figma].<br />
<br />
This redesign will modernize the player's appearance and interaction, aligning it with the latest design trends and user expectations. The overhaul is not just cosmetic; it will extend to the app's functionality, with particular attention to the integration of Spotify and YouTube players. This feature will allow users to seamlessly play music from Spotify and YouTube directly within the ListenBrainz app, enriching the user's music experience by aggregating their music playback through a single interface.<br />
<br />
Additionally, the project will focus on refining the app's existing features and display mechanisms, ensuring that the music playback is not only smooth but also visually appealing and user-friendly.</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Development/Summer_of_Code/2024/ListenBrainz&diff=77391Development/Summer of Code/2024/ListenBrainz2024-02-12T11:33:38Z<p>RobertKaye: </p>
<hr />
<div>ListenBrainz allows users to store a list of songs that they have listened to, get personalised recommendations, and more. [[:lb:|Try it out.]]<br />
<br />
== Getting started ==<br />
(see also: [[Development/Summer of Code/Getting started|Getting started with GSoC]])<br />
<br />
If you want to work on ListenBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some things that we might ask you about<br />
<br />
* Show that you understand the goals that ListenBrainz wants to achieve, which are written on its homepage<br />
* Create an oauth application on the MusicBrainz website and add the configuration information to your ListenBrainz server. Use this to log in to your server with your MusicBrainz details<br />
* Use the import script that is part of the ListenBrainz server to load scrobbles from last.fm to your ListenBrainz server, or the main ListenBrainz server<br />
* Use your preferred programming language to write a submission tool that can send Listen data to your local ListenBrainz server. You could make up some fake data for song names and artists. This data doesn't have to be real.<br />
* Try and delete the ListenBrainz database on your local server to remove the fake data that you added.<br />
* Look at the list of tickets that we have open for ListenBrainz and see if you understand what tasks the tickets involve<br />
* If you want to, see if you can contribute to fixing a ticket. Either add a comment to the ticket or ask in IRC for clarification if you don't understand what the ticket means<br />
<br />
== Ideas ==<br />
We're adding a number of new social features to ListenBrainz that we hope will enable people discover more music they like and users who have similar music tastes to their own. We're working on some of these features now, but we will need to get help for other features:<br />
=== Add machine learning to BPM detection code ===<br />
<br />
Proposed mentors: ''mayhem''<br><br />
Languages/skills: Python/Flask, Machine Learning<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A deployable ML model that does accurate BPM detection<br />
<br />
ListenBrainz could really use reliable BPM values for music that is represented in MusicBrainz. However, the algorithms for this have problems that are very tricky to solve. We believe that we can use neural networks to improve the "peak selection" portion of this project [https://github.com/scaperot/the-BPM-detector-python the-BPM-detector-python]. The ListenBrainz team will collect a suitable training dataset of a few thousand different audio files with known BPM values that can be used for training this model. We expect the participant who gets selected for this project to design, train and test the neural network and as a final deliverable create a model and it associated code necessary to integrate this into existing MetaBrainz projects for deployement.<br />
<br />
=== Integrate music streaming from Subsonic ===<br />
<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A new music service integration for users to play recordings on ListenBrainz.<br />
<br />
LB has a number of music discovery features that use BrainzPlayer to facilitate track playback. BrainzPlayer (BP) is a custom React component in LB that uses multiple data sources to search and play a track. As of now, it supports Spotify, Youtube and Soundcloud as a music service. LB would like to be able to stream music from a private music collection using web apps like [https://www.navidrome.org/ Navidrome], [https://www.funkwhale.audio/ Funkwhale] and other apps that implement the [http://www.subsonic.org/pages/index.jsp Subsonic API]. The following major tasks need to be completed: 1) Add subsonic API player as a service to our music services backend; this will require some schema changes/extensions in order to have user specify the URL of their service as part of the music service configuration. 2) Add the react based front-end UI to that allows users to setup their own Subsonic API instance as a service. 3) Add support to BrainzPlayer for logging into the subsonic API service and playing music from it.<br />
<br />
=== Integrate Deezer music streaming service for recording listens and playing music ===<br />
<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask, Typescript/React<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A new music service integration for users to play and record listens on ListenBrainz.<br />
<br />
LB has a number of music discovery features that use BrainzPlayer to facilitate track playback. BrainzPlayer (BP) is a custom React component in LB that uses multiple data sources to search and play a track. As of now, it supports Spotify, Youtube and Soundcloud as a music service. LB also supports linking a Spotify account to record listening history. We have looked into some other services and found that Deezer provides the music playback and recording listening history capability. Integrating these services into LB would make for a good SoC project.<br />
<br />
=== Integrate Internet Archive in BrainzPlayer ===<br />
<br />
Proposed mentors: ''lucifer'', ''monkey''<br><br />
Languages/skills: Python/Flask, Typescript/React, Postgres<br><br />
Estimated Project Length: 350 hours<br><br />
Difficulty: medium<br />
<br />
LB has a number of music discovery features that use BrainzPlayer to facilitate track playback. BrainzPlayer (BP) is a custom React component in LB that uses multiple data sources to search and play a track. The [https://archive.org/details/78rpm 78 RPMs and Cylinder Recordings] is a collection of digitized recordings from physical releases of the early 20th century. Each recording comes with audio streaming, and metadata web service. It can be used to retrieve metadata automatically and to embed a player in ListenBrainz using BrainzPlayer. A lot of similar music collections are hosted by the Internet Archive which can be made available for playing on ListenBrainz.<br />
<br />
=== Revamped Last.fm listens importer ===<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask<br><br />
Estimated Project Length: 90 or 175 hours<br><br />
Difficulty: Medium<br><br />
Expected Outcomes: An improved importer for Last.FM users to import their listens into ListenBrainz.<br />
<br />
LB has a Last.fm importer written in Typescript that runs in the user's browser and lets them import scrobbles as listens in ListenBrainz. This is a one time import and if you submit scrobbles to Last.fm again, you need to re-run the importer manually. Also, the user needs to keep their tab open while the import runs which is inconvenient. Further, a lot of issues have been reported with it in the past like API calls to last.fm getting blocked by uBlock. Because the importer runs on the frontend/client side we have limited visibility into its functioning and errors. It would be better to create an importer like the one we have for spotify which runs on the backend and continuously updates ListenBrainz with spotify streams of the user.<br />
<br />
=== Exporting playlists to SoundCloud and Apple Music ===<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask<br><br />
Estimated Project Length: 90 or 175 hours, depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: SoundCloud/Apple Music users can export LB playlists to respective services<br />
<br />
LB generates music recommendation playlists. These playlists can be listened to on LB using BrainzPlayer if the user has connected a music service to LB. Users can also configure such playlists to be automatically exported to the music service of their choice. Currently, we only support Spotify for playlist export. We should also add support for exporting playlists to SoundCloud and Apple Music.<br />
<br />
=== Music Recommendation: Implement a new Troi patch for generating music recommendations ===<br />
<br />
Proposed mentors: ''mayhem''<br><br />
Languages/skills: Python, possibly Postgres<br><br />
Estimated Project Length: 175 or 350 hours, depending on the scope that is suggested.<br><br />
Difficulty: Easy/Medium, depends on what is proposed.<br><br />
Expected outcomes: One or more finished, debugged and tested plugins for Troi.<br />
<br />
Our [https://github.com/metabrainz/troi-recommendation-playground troi recommendation toolkit] is our playground for developing recommendation algorithms. The toolkit already knows how to fetch data from ListenBrainz for stats, collaborative filtered recommended tracks, similar artists and similar recordings. From MusicBrainz it can fetch needed metadata such as genres and tags. The exact goal for this project really depends on you and what ideas you bring to the table, but the idea is to create a new Patch (plugin) for Troi that creates a new type of playlist that we can periodically offer to our users.<br />
<br />
If this sounds interesting to you, we strongly recommend that you turn up in our IRC channel and chat with at ''mayhem'' or ''lucifer'' about your idea before you go into a full proposal. Music recommendations can seem exciting and fun, but the details of how to make them happen and all the things that need to be considered is a significant challenge.<br />
<br />
=== '''Add RSS feeds''' ===<br />
''For lucifer to review and expand''<br />
<br />
Proposed mentors: ''lucifer?''<br><br />
Languages/skills: <br><br />
Estimated Project Length: <br><br />
Expected Outcomes: Three(?) or more functional RSS feeds.<br />
<br />
ListenBrainz provides a number of interesting opportunities for generating RSS feeds (a short list of user-requested feeds is in [[jira:MBS-941|MBS-941]] and linked tickets - but do not limit yourself to these). For example: New releases by an artist, new releases in genre, all new releases, user-specific new releases from [[:lb:explore/fresh-releases/|Fresh Releases]] 'for you' function. The complexity of our data allows for complex feed options - as well as new releases by date we may want to offer feeds of new additions (regardless of release date). You may need to communicate with the community, as well as potential third-party developers, to find what the most useful and requested types of feeds are. Some potential feeds rely on primarily MusicBrainz data, so there may be project cross-over that you will be expected to plan and manage.<br />
<br />
=== Dashboard Page in ListenBrainz Android/iOS App for all users ===<br />
Proposed mentors: ''akshaaatt''<br />
Languages/skills: Kotlin, Android development, JetPack Compose, Retrofit / Swift, SwiftUI, Alamofire, iOS Development<br />
Estimated Project Length: 350 hours<br />
Difficulty: Medium<br />
Expected outcomes: A finished app feature that gives the user the ability to view your dashboard as well as that of other users<br />
<br />
This project aims to seamlessly integrate all functionalities of the ListenBrainz website's Dashboard into the ListenBrainz application. This integration will be achieved through a combination of web view components for certain features and native development for others, depending on the specific requirements of each functionality.<br />
<br />
The primary objective is to enable users not only to view their own dashboard within the app but also to explore the dashboards of other users. This exploration can be initiated in various ways, including through a search function or by selecting a user from their feed, leading to a more connected and interactive user experience.<br />
<br />
A crucial aspect of this project is to maintain design consistency with the ListenBrainz website. The mobile app's UI/UX should align with the design elements and user experience guidelines provided in the Figma files shared by the design team.<br />
<br />
By completing this project, the ListenBrainz app will offer a comprehensive profile/dashboard feature for users, mirroring the website's functionality. This includes displaying detailed music listening statistics, recent listens, top artists, and more, all within a user-friendly and engaging mobile interface.<br />
<br />
=== BrainzPlayer Revamp in the ListenBrainz Android App ===<br />
Proposed mentors: ''akshaaatt''<br />
Languages/skills: Kotlin, Android development, JetPack Compose, ExoPlayer<br />
Estimated Project Length: 350 hours<br />
Difficulty: Medium<br />
Expected Outcomes: Improve user interface and functionality, address bugs and ensure app stability.<br />
<br />
The ListenBrainz local player (BrainzPlayer) will undergo a UI/UX overhaul as per the [https://www.figma.com/file/tFLTQiq7QlA1oGRTJVtXml/ListenBrainz-App?type=design&node-id=351%3A956&mode=design&t=Cauk64QOJAR9Ui2e-1 Figma].<br />
<br />
This redesign will modernize the player's appearance and interaction, aligning it with the latest design trends and user expectations. The overhaul is not just cosmetic; it will extend to the app's functionality, with particular attention to the integration of Spotify and YouTube players. This feature will allow users to seamlessly play music from Spotify and YouTube directly within the ListenBrainz app, enriching the user's music experience by aggregating their music playback through a single interface.<br />
<br />
Additionally, the project will focus on refining the app's existing features and display mechanisms, ensuring that the music playback is not only smooth but also visually appealing and user-friendly.</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=jspf&diff=77341jspf2024-01-26T11:02:58Z<p>RobertKaye: </p>
<hr />
<div>== Introduction ==<br />
<br />
The ListenBrainz team is currently working to create Playlist support and we've chosen [https://xspf.org/jspf/ JSPF] as our playlist transport format. This format will be used for importing/exporting playlists, in our API and internally between our web servers and the client browser sessions.<br />
<br />
There are a number of fields that we require that are not part of JSPF/XSPF, so we've defined two extensions to JSPF. Our proposed format example is here:<br />
<br />
<br />
{<br />
"playlist" : {<br />
"extension" : {<br />
"<nowiki>https://musicbrainz.org/doc/jspf#playlist</nowiki>" : {<br />
"created_for" : "Mr_Monkey",<br />
"creator" : "troi-bot",<br />
"collaborators" : [<br />
"rob",<br />
"alastairp",<br />
"zas"<br />
],<br />
"copied_from" : "<nowiki>https://listenbrainz.org/playlist/9dae92c5-c98e-4e7e-9c15-8b6d32607aed</nowiki>",<br />
"copied_from_deleted": true,<br />
"public" : true,<br />
"last_modified_at": "2020-11-27T10:45:49+00:00",<br />
"additional_metadata": { . . . } <br />
}<br />
},<br />
"creator" : "ListenBrainz Troi",<br />
"date" : "2005-01-08T17:10:47-05:00",<br />
"title" : "1980s flashback jams",<br />
"track" : [<br />
{<br />
"title" : "Gold",<br />
"identifier" : "<nowiki>https://musicbrainz.org/recording/e8f9b188-f819-4e43-ab0f-4bd26ce9ff56</nowiki>",<br />
"creator" : "Spandau Ballet",<br />
"extension" : {<br />
"<nowiki>https://musicbrainz.org/doc/jspf#track</nowiki>" : {<br />
"added_by" : "zas",<br />
"artist_identifiers" : [<br />
"<nowiki>https://musicbrainz.org/artist/4c0d9acf-a8a1-4765-9c56-05f92f68c048</nowiki>"<br />
],<br />
"added_at" : "2020-11-27T10:45:49+00:00",<br />
"release_identifier" : "<nowiki>https://musicbrainz.org/release/8d3acbb4-c541-4324-a124-a670615f0f77</nowiki>",<br />
"additional_metadata": { <br />
"subsonic_id": "e66f7f91-2884-4cdf-97b3-24faee6be03e"<br />
} <br />
}<br />
},<br />
"album" : "True"<br />
}<br />
],<br />
"identifier" : "<nowiki>https://listenbrainz.org/playlist/7f4cf4d3-f5ca-453a-b5c8-00e8a30a9bac</nowiki>"<br />
}<br />
}<br />
<br />
==playlist==<br />
<br />
The https://musicbrainz.org/doc/jspf#playlist namespace defines the following fields that augment the data about a playlist:<br />
<br />
* creator: The ListenBrainz user who created this playlist.<br />
* created_for: Which ListenBrainz user was the playlist generated for? This is for music recommendation bots generating playlists for users.<br />
* collaborators: Who are the ListenBrainz users who have access to edit this playlist?<br />
* copied_from: This field identifies a playlist, using the identifier syntax, from which this playlist was copied from.<br />
* copied_from_deleted: If the source playlist that this playlist has been copied from has been deleted, this field will be set to true and the copied_from field will not be returned.<br />
* public: Indicates if this playlist is public or private. Must be a boolean value <code>true</code> or <code>false</code>.<br />
* last_modified_at: The timestamp for when this playlist was last modified.<br />
* additional_metadata: This dict allows a playlist creator to submit additional playlist metadata that may be used by playlist generation tools. The content of this field is defined by the playlist generation tools and is beyond the scope of this document.<br />
<br />
==track==<br />
<br />
The https://musicbrainz.org/doc/jspf#track namespace defines the following fields that augment the data about a particular track:<br />
<br />
* added_by: The ListenBrainz user who added this track.<br />
* artist_identifiers: A list of MusicBrainz Artist URIs that identify the artist that are part of the MusicBrainz artist credit id for this track.<br />
* added_at: The timestamp for when this track was added to the playlist.<br />
* release_identifier: The MusicBrainz ID URI for the release that contained this track.<br />
* additional_metadata: This dict allows a playlist creator to submit additional track metadata that may be used by playlist generation tools. The content of this field is defined by the playlist generation tools and is beyond the scope of this document.<br />
** subsonic_id: The subsonic_id local id for this given track.<br />
<br />
[[Category:Documentation]] [[Category:WikiDocs Page]]</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Development/Summer_of_Code/2024/ListenBrainz&diff=77336Development/Summer of Code/2024/ListenBrainz2024-01-23T16:46:43Z<p>RobertKaye: </p>
<hr />
<div>ListenBrainz allows users to store a list of songs that they have listened to, get personalised recommendations, and more. [[:lb:|Try it out.]]<br />
<br />
== Getting started ==<br />
(see also: [[Development/Summer of Code/Getting started|Getting started with GSoC]])<br />
<br />
If you want to work on ListenBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some things that we might ask you about<br />
<br />
* Show that you understand the goals that ListenBrainz wants to achieve, which are written on its homepage<br />
* Create an oauth application on the MusicBrainz website and add the configuration information to your ListenBrainz server. Use this to log in to your server with your MusicBrainz details<br />
* Use the import script that is part of the ListenBrainz server to load scrobbles from last.fm to your ListenBrainz server, or the main ListenBrainz server<br />
* Use your preferred programming language to write a submission tool that can send Listen data to your local ListenBrainz server. You could make up some fake data for song names and artists. This data doesn't have to be real.<br />
* Try and delete the ListenBrainz database on your local server to remove the fake data that you added.<br />
* Look at the list of tickets that we have open for ListenBrainz and see if you understand what tasks the tickets involve<br />
* If you want to, see if you can contribute to fixing a ticket. Either add a comment to the ticket or ask in IRC for clarification if you don't understand what the ticket means<br />
<br />
== Ideas ==<br />
We're adding a number of new social features to ListenBrainz that we hope will enable people discover more music they like and users who have similar music tastes to their own. We're working on some of these features now, but we will need to get help for other features:<br />
<br />
<br />
=== Add machine learnning to BMP detection code ===<br />
<br />
Proposed mentors: ''mayhem''<br><br />
Languages/skills: Python/Flask, Machine Learning<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A deployable ML model that does accurate BPM detection<br />
<br />
ListenBrainz could really use reliable BPM values for music that is represented in MusicBrainz. However, the algorithms for this have problems that are very tricky to solve. We believe that we can use neural networks to improve the "peak selection" portion of this project [https://github.com/scaperot/the-BPM-detector-python the-BPM-detector-python]. The ListenBrainz team will collect a suitable training dataset of a few thousand different audio files with known BPM values that can be used for training this model. We expect the participant who gets selected for this project to design, train and test the neural network and as a final deliverable create a model and it associated code necessary to integrate this into existing MetaBrainz projects for deployement.<br />
<br />
=== Integrate music streaming from Subsonic ===<br />
<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A new music service integration for users to play recordings on ListenBrainz.<br />
<br />
LB has a number of music discovery features that use BrainzPlayer to facilitate track playback. BrainzPlayer (BP) is a custom React component in LB that uses multiple data sources to search and play a track. As of now, it supports Spotify, Youtube and Soundcloud as a music service. LB would like to be able to stream music from a private music collection using web apps like [https://www.navidrome.org/ Navidrome], [https://www.funkwhale.audio/ Funkwhale] and other apps that implement the [http://www.subsonic.org/pages/index.jsp Subsonic API]. The following major tasks need to be completed: 1) Add subsonic API player as a service to our music services backend; this will require some schema changes/extensions in order to have user specify the URL of their service as part of the music service configuration. 2) Add the react based front-end UI to that allows users to setup their own Subsonic API instance as a service. 3) Add support to BrainzPlayer for logging into the subsonic API service and playing music from it.<br />
<br />
<br />
=== Integrate Deezer music streaming service for recording listens and playing music ===<br />
<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask, Typescript/React<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A new music service integration for users to play and record listens on ListenBrainz.<br />
<br />
LB has a number of music discovery features that use BrainzPlayer to facilitate track playback. BrainzPlayer (BP) is a custom React component in LB that uses multiple data sources to search and play a track. As of now, it supports Spotify, Youtube and Soundcloud as a music service. LB also supports linking a Spotify account to record listening history. We have looked into some other services and found that Deezer provides the music playback and recording listening history capability. Integrating these services into LB would make for a good SoC project.<br />
<br />
=== Music Recommendation: Implement a new Troi patch for generating music recommendations ===<br />
<br />
Proposed mentors: ''mayhem''<br><br />
Languages/skills: Python, possibly Postgres<br><br />
Estimated Project Length: 175 or 250 hours, depending on the scope that is suggested.<br><br />
Expected outcomes: One or more finished, debugged and tested plugins for Troi.<br />
<br />
Our [https://github.com/metabrainz/troi-recommendation-playground troi recommendation toolkit] is our playground for developing recommendation algorithms. The toolkit already knows how to fetch data from ListenBrainz for stats, collaborative filtered recommended tracks, similar artists and similar recordings. From MusicBrainz it can fetch needed metadata such as genres and tags. The exact goal for this project really depends on you and what ideas you bring to the table, but the idea is to create a new Patch (plugin) for Troi that creates a new type of playlist that we can periodically offer to our users.<br />
<br />
If this sounds interesting to you, we strongly recommend that you turn up in our IRC channel and chat with at ''mayhem'' or ''lucifer'' about your idea before you go into a full proposal. Music recommendations can seem exciting and fun, but the details of how to make them happen and all the things that need to be considered is a significant challenge.<br />
<br />
<br />
<br />
'''Manual album and multi-track submission'''<br />
<br />
Another idea for the mentors to review for inclusion -<br />
<br />
Jivte added the 'manually submit listens' function to LB a while back, but it is missing some features from the initial mockups/ticket: https://tickets.metabrainz.org/browse/LB-1157<br />
<br />
With YIM getting bigger every year we are getting more and more requests for better submission features. A good GSoC project could be to flesh out the manual submitter to match the original mockups. There are the tickets for the core functions that are missing:<br />
<br />
[[jira:LB-1401|LB-1401 Manually add album listens]]<br />
<br />
[[jira:LB-1448|LB-1448: Manually add a queue of song/album listens]]<br />
<br />
- ''aerozol''<br />
=== [Name] ===<br />
Proposed Mentors:<br />
<br />
Languages/skills:<br />
<br />
Estimated Project Length:<br />
<br />
Difficulty: [easy/medium]hard<br />
<br />
Expected outcomes:<br />
<br />
[description]</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Development/Summer_of_Code/2024&diff=77330Development/Summer of Code/20242024-01-23T13:28:17Z<p>RobertKaye: </p>
<hr />
<div>Are you interested in working with MetaBrainz in Google Summer of Code 2024? You're in the right place!<br />
<br />
'''IMPORTANT NOTE: If you're arriving here after 18 March, 2024, you've missed your chance to apply with us. We will not consider applications from applicants who have not discussed their idea during the application discussion phase which ends March 18. We will make no exceptions.'''<br />
<br />
== Where to start[edit | edit source] ==<br />
<br />
; New to MetaBrainz?<br />
: The MetaBrainz Foundation has been set up to build community maintained databases and make them available in the public domain or under Creative Commons licenses.<br />
; New to MetaBrainz development and/or GSoC?<br />
: [[Development/Summer of Code/Getting started|Getting started with GSoC]]<br />
<br />
== Projects ==<br />
<br />
=== [[Development/Summer of Code/2024/BookBrainz|BookBrainz]] ===<br />
{| class="wikitable"<br />
| rowspan="3" |[[File:BookBrainz logo small notext.png|link=https://wiki.musicbrainz.org/File:BookBrainz_logo_small_notext.png]]<br />
|BookBrainz is a database of book metadata.<br />
We're interested in projects that help us reach our roadmap, and that add major functionalities to the website.<br />
<br />
Please see our [[Development/Summer of Code/2024/BookBrainz|ideas page]] for more details and information on getting started.<br />
|-<br />
|'''Top 3 Desired Skills''': Node.js, React, SQL<br />
|-<br />
|[[Development/Summer of Code/2024/BookBrainz|Ideas page]]<nowiki> | </nowiki>[[bb:|Main page]]<nowiki> | </nowiki>[[discourse:c/bookbrainz|Forums]]<br />
|}<br />
----<br />
<br />
=== [[Development/Summer of Code/2024/ListenBrainz|ListenBrainz]] ===<br />
{| class="wikitable"<br />
| rowspan="3" |[[File:ListenBrainz logo small notext.png|link=https://wiki.musicbrainz.org/File:ListenBrainz_logo_small_notext.png]]<br />
|An open source music website that allows users to import their listen history. One of the goals is for this data to be used for building open music recommendation systems.<br />
|-<br />
|'''Languages/skills''': Python, Flask, Postgres, Spark, React, Android<br />
|-<br />
|[[Development/Summer of Code/2024/ListenBrainz|Ideas page]]<nowiki> | </nowiki>[[:lb:|Main page]]<nowiki> | </nowiki>[[discourse:c/listenbrainz/|Forums]]<br />
|}<br />
----<br />
<br />
=== [[Development/Summer of Code/2024/MusicBrainz|MusicBrainz]] ===<br />
{| class="wikitable"<br />
| rowspan="3" |[[File:MusicBrainz logo small notext.png|link=https://wiki.musicbrainz.org/File:MusicBrainz_logo_small_notext.png]]<br />
|A community-maintained open source music encyclopedia that collects music metadata and makes it available to the public.<br />
|-<br />
|'''Languages/skills''': JavaScript (React), PostgreSQL, Rust<br />
|-<br />
|[[Development/Summer of Code/2024/MusicBrainz|Ideas page]]<nowiki> | </nowiki>[[mb:|Main page]]<nowiki> | </nowiki>[[discourse:c/musicbrainz|Forums]]<br />
|}<br />
----<br />
<br />
=== [[Development/Summer of Code/2024/Picard|MusicBrainz Picard]] ===<br />
{| class="wikitable"<br />
| rowspan="3" |[[File:Picard_logo_small_notext.png|link=https://wiki.musicbrainz.org/File:Picard_logo_small_notext.png]]<br />
|'''MusicBrainz Picard''' is a cross-platform (Linux/Mac OS X/Windows) application written in Python and is the official MusicBrainz [[MusicBrainz Enabled Applications|tagger]]. It supports the majority of audio file formats, is capable of using audio fingerprints ([[AcoustID|AcoustIDs]]), performing CD lookups and [[Disc ID|disc ID]] submissions, and it has excellent Unicode support.<br />
|-<br />
|'''Languages/skills''': Python, PyQt<br />
|-<br />
|[[Development/Summer of Code/2024/Picard|Ideas page]]<nowiki> | </nowiki>[[picard:|Main page]]<nowiki> | </nowiki>[[discourse:c/picard|Forums]]<br />
|}</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Development/Summer_of_Code/2024/ListenBrainz&diff=77328Development/Summer of Code/2024/ListenBrainz2024-01-23T13:12:00Z<p>RobertKaye: </p>
<hr />
<div>ListenBrainz allows users to store a list of songs that they have listened to, get personalised recommendations, and more. [[:lb:|Try it out.]]<br />
<br />
== Getting started ==<br />
(see also: [[Development/Summer of Code/Getting started|Getting started with GSoC]])<br />
<br />
If you want to work on ListenBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some things that we might ask you about<br />
<br />
* Show that you understand the goals that ListenBrainz wants to achieve, which are written on its homepage<br />
* Create an oauth application on the MusicBrainz website and add the configuration information to your ListenBrainz server. Use this to log in to your server with your MusicBrainz details<br />
* Use the import script that is part of the ListenBrainz server to load scrobbles from last.fm to your ListenBrainz server, or the main ListenBrainz server<br />
* Use your preferred programming language to write a submission tool that can send Listen data to your local ListenBrainz server. You could make up some fake data for song names and artists. This data doesn't have to be real.<br />
* Try and delete the ListenBrainz database on your local server to remove the fake data that you added.<br />
* Look at the list of tickets that we have open for ListenBrainz and see if you understand what tasks the tickets involve<br />
* If you want to, see if you can contribute to fixing a ticket. Either add a comment to the ticket or ask in IRC for clarification if you don't understand what the ticket means<br />
<br />
== Ideas ==<br />
We're adding a number of new social features to ListenBrainz that we hope will enable people discover more music they like and users who have similar music tastes to their own. We're working on some of these features now, but we will need to get help for other features:<br />
<br />
<br />
=== Music Recommendation: Implement a new Troi patch for generating music recommendations ===<br />
<br />
Proposed mentors: ''mayhem''<br><br />
Languages/skills: Python, possibly Postgres<br><br />
Estimated Project Length: 175 or 250 hours, depending on the scope that is suggested.<br><br />
Expected outcomes: One or more finished, debugged and tested plugins for Troi.<br />
<br />
Our [https://github.com/metabrainz/troi-recommendation-playground troi recommendation toolkit] is our playground for developing recommendation algorithms. The toolkit already knows how to fetch data from ListenBrainz for stats, collaborative filtered recommended tracks, similar artists and similar recordings. From MusicBrainz it can fetch needed metadata such as genres and tags. The exact goal for this project really depends on you and what ideas you bring to the table, but the idea is to create a new Patch (plugin) for Troi that creates a new type of playlist that we can periodically offer to our users.<br />
<br />
If this sounds interesting to you, we strongly recommend that you turn up in our IRC channel and chat with at ''mayhem'' or ''lucifer'' about your idea before you go into a full proposal. Music recommendations can seem exciting and fun, but the details of how to make them happen and all the things that need to be considered is a significant challenge.<br />
<br />
<br />
=== Integrate music streaming from Subsonic ===<br />
<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A new music service integration for users to play recordings on ListenBrainz.<br />
<br />
LB has a number of music discovery features that use BrainzPlayer to facilitate track playback. BrainzPlayer (BP) is a custom React component in LB that uses multiple data sources to search and play a track. As of now, it supports Spotify, Youtube and Soundcloud as a music service. LB would like to be able to stream music from a private music collection using web apps like [https://www.navidrome.org/ Navidrome], [https://www.funkwhale.audio/ Funkwhale] and other apps that implement the [http://www.subsonic.org/pages/index.jsp Subsonic API]. The following major tasks need to be completed: 1) Add subsonic API player as a service to our music services backend; this will require some schema changes/extensions in order to have user specify the URL of their service as part of the music service configuration. 2) Add the react based front-end UI to that allows users to setup their own Subsonic API instance as a service. 3) Add support to BrainzPlayer for logging into the subsonic API service and playing music from it.<br />
<br />
<br />
=== Integrate Deezer music streaming service for recording listens and playing music ===<br />
<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask, Typescript/React<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A new music service integration for users to play and record listens on ListenBrainz.<br />
<br />
LB has a number of music discovery features that use BrainzPlayer to facilitate track playback. BrainzPlayer (BP) is a custom React component in LB that uses multiple data sources to search and play a track. As of now, it supports Spotify, Youtube and Soundcloud as a music service. LB also supports linking a Spotify account to record listening history. We have looked into some other services and found that Deezer provides the music playback and recording listening history capability. Integrating these services into LB would make for a good SoC project.<br />
<br />
<br />
'''Manual album and multi-track submission'''<br />
<br />
Another idea for the mentors to review for inclusion -<br />
<br />
Jivte added the 'manually submit listens' function to LB a while back, but it is missing some features from the initial mockups/ticket: https://tickets.metabrainz.org/browse/LB-1157<br />
<br />
With YIM getting bigger every year we are getting more and more requests for better submission features. A good GSoC project could be to flesh out the manual submitter to match the original mockups. There are the tickets for the core functions that are missing:<br />
<br />
[[jira:LB-1401|LB-1401 Manually add album listens]]<br />
<br />
[[jira:LB-1448|LB-1448: Manually add a queue of song/album listens]]<br />
<br />
- ''aerozol''<br />
=== [Name] ===<br />
Proposed Mentors:<br />
<br />
Languages/skills:<br />
<br />
Estimated Project Length:<br />
<br />
Difficulty: [easy/medium]hard<br />
<br />
Expected outcomes:<br />
<br />
[description]</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Development/Summer_of_Code/2024/ListenBrainz&diff=77327Development/Summer of Code/2024/ListenBrainz2024-01-23T13:11:00Z<p>RobertKaye: </p>
<hr />
<div>ListenBrainz allows users to store a list of songs that they have listened to, get personalised recommendations, and more. [[:lb:|Try it out.]]<br />
<br />
== Getting started ==<br />
(see also: [[Development/Summer of Code/Getting started|Getting started with GSoC]])<br />
<br />
If you want to work on ListenBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some things that we might ask you about<br />
<br />
* Show that you understand the goals that ListenBrainz wants to achieve, which are written on its homepage<br />
* Create an oauth application on the MusicBrainz website and add the configuration information to your ListenBrainz server. Use this to log in to your server with your MusicBrainz details<br />
* Use the import script that is part of the ListenBrainz server to load scrobbles from last.fm to your ListenBrainz server, or the main ListenBrainz server<br />
* Use your preferred programming language to write a submission tool that can send Listen data to your local ListenBrainz server. You could make up some fake data for song names and artists. This data doesn't have to be real.<br />
* Try and delete the ListenBrainz database on your local server to remove the fake data that you added.<br />
* Look at the list of tickets that we have open for ListenBrainz and see if you understand what tasks the tickets involve<br />
* If you want to, see if you can contribute to fixing a ticket. Either add a comment to the ticket or ask in IRC for clarification if you don't understand what the ticket means<br />
<br />
== Ideas ==<br />
We're adding a number of new social features to ListenBrainz that we hope will enable people discover more music they like and users who have similar music tastes to their own. We're working on some of these features now, but we will need to get help for other features:<br />
<br />
<br />
=== Music Recommendation: Implement a new Troi patch for generating music recommendations ===<br />
<br />
Proposed mentors: ''mayhem''<br><br />
Languages/skills: Python, possibly Postgres<br><br />
Estimated Project Length: 175 or 250 hours, depending on the scope that is suggested.<br><br />
Expected outcomes: One or more finished, debugged and tested plugins for Troi.<br />
<br />
Our [https://github.com/metabrainz/troi-recommendation-playground troi recommendation toolkit] is our playground for developing recommendation algorithms. The toolkit already knows how to fetch data from ListenBrainz for stats, collaborative filtered recommended tracks, similar artists and similar recordings. From MusicBrainz it can fetch needed metadata such as genres and tags. The exact goal for this project really depends on you and what ideas you bring to the table, but the idea is to create a new Patch (plugin) for Troi that creates a new type of playlist that we can periodically offer to our users.<br />
<br />
If this sounds interesting to you, we strongly recommend that you turn up in our IRC channel and chat with at ''mayhem'' or ''lucifer'' about your idea before you go into a full proposal. Music recommendations can seem exciting and fun, but the details of how to make them happen and all the things that need to be considered is a significant challenge.<br />
<br />
<br />
=== Integrate music streaming from Subsonic ===<br />
<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A new music service integration for users to play recordings on ListenBrainz.<br />
<br />
LB has a number of music discovery features that use BrainzPlayer to facilitate track playback. BrainzPlayer (BP) is a custom React component in LB that uses multiple data sources to search and play a track. As of now, it supports Spotify, Youtube and Soundcloud as a music service. LB would like to be able to stream music from a private music collection using web apps like [https://www.navidrome.org/ Navidrome], [https://www.funkwhale.audio/ Funkwhale] and other apps that implement the [http://www.subsonic.org/pages/index.jsp Subsonic API]. The following major tasks need to be completed: 1) Add subsonic API player as a service to our music services backend; this will require some schema changes/extensions in order to have user specify the URL of their service as part of the music service configuration. 2) Add the react based front-end UI to that allows users to setup their own Subsonic API instance as a service. 3) Add support to BrainzPlayer for logging into the subsonic API service and playing music from it.<br />
<br />
<br />
'''Manual album and multi-track submission'''<br />
<br />
Another idea for the mentors to review for inclusion -<br />
<br />
Jivte added the 'manually submit listens' function to LB a while back, but it is missing some features from the initial mockups/ticket: https://tickets.metabrainz.org/browse/LB-1157<br />
<br />
With YIM getting bigger every year we are getting more and more requests for better submission features. A good GSoC project could be to flesh out the manual submitter to match the original mockups. There are the tickets for the core functions that are missing:<br />
<br />
[[jira:LB-1401|LB-1401 Manually add album listens]]<br />
<br />
[[jira:LB-1448|LB-1448: Manually add a queue of song/album listens]]<br />
<br />
- ''aerozol''<br />
=== [Name] ===<br />
Proposed Mentors:<br />
<br />
Languages/skills:<br />
<br />
Estimated Project Length:<br />
<br />
Difficulty: [easy/medium]hard<br />
<br />
Expected outcomes:<br />
<br />
[description]</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23-delhi&diff=77085MusicBrainz Summit/23-delhi2023-10-24T14:35:45Z<p>RobertKaye: /* Agenda */</p>
<hr />
<div>Summit 23, Delhi edition, is happening on November 17 & 18, in Delhi, India.<br />
<br />
Option: Group dinner also on the 16th.<br />
<br />
Mayhem will bring sticker and will hopefully have t-shirts for everyone who doesn't already have one.<br />
==Agenda==<br />
<br />
We are likely going to follow a similar model as we did for this year's summit in Barcelona:<br />
<br />
* Open the meeting space in the morning<br />
* Have lunch brought in<br />
* Formally meet in the afternoon.<br />
* Leave for drinks/dinner<br />
<br />
Costs for food and the space will be covered by MetaBrainz.<br />
<br />
==Meeting Space & Lodgings==<br />
<br />
We're working on renting a meeting room at a co-working space somewhere near Janpath/Connaught Place.<br />
<br />
==Attendees==<br />
Summit attendees:<br />
{| class="wikitable sortable"<br />
!<br />
!Need lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|akshaaatt<br />
|N<br />
|Anything good<br />
|not needed<br />
|-<br />
|mayhem<br />
|N<br />
|E eats everything<br />
|not needed<br />
|-<br />
|riksucks<br />
|?<br />
|<br />
|<br />
|-<br />
|lucifer<br />
|N<br />
|<br />
|not needed<br />
|-<br />
|param<br />
|?<br />
|<br />
|<br />
|-<br />
|jasje<br />
|N<br />
|Anything<br />
|44 or XXL<br />
|-<br />
|ansh<br />
|?<br />
|<br />
|<br />
|-<br />
|theflash<br />
|?<br />
|<br />
|<br />
|}</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23-delhi&diff=77083MusicBrainz Summit/23-delhi2023-10-24T14:26:51Z<p>RobertKaye: </p>
<hr />
<div>Summit 23, Delhi edition, is happening on November 17 & 18, in Delhi, India.<br />
==Schedule of Events==<br />
<br />
TBD<br />
<br />
==Agenda==<br />
<br />
TBD<br />
<br />
==Meeting Space & Lodgings==<br />
<br />
TBD<br />
<br />
==Attendees==<br />
Summit attendees:<br />
{| class="wikitable sortable"<br />
!<br />
!Need lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|akshaaatt<br />
|N<br />
|Anything good<br />
|not needed<br />
|-<br />
|mayhem<br />
|N<br />
|E eats everything<br />
|not needed<br />
|-<br />
|riksucks<br />
|?<br />
|<br />
|<br />
|-<br />
|lucifer<br />
|N<br />
|<br />
|not needed<br />
|-<br />
|param<br />
|?<br />
|<br />
|<br />
|-<br />
|jasje<br />
|?<br />
|<br />
|<br />
|-<br />
|ansh<br />
|?<br />
|<br />
|<br />
|-<br />
|theflash<br />
|?<br />
|<br />
|<br />
|}</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23-delhi&diff=77082MusicBrainz Summit/23-delhi2023-10-24T14:21:59Z<p>RobertKaye: Created page with "Summit 23, Delhi edition, is happening on November 17 & 18, in Delhi, India. ==Schedule of Events== TBD ==Agenda== TBD ==Meeting Space & Lodgings== TBD ==Attendees== S..."</p>
<hr />
<div>Summit 23, Delhi edition, is happening on November 17 & 18, in Delhi, India.<br />
<br />
<br />
==Schedule of Events==<br />
<br />
TBD<br />
<br />
==Agenda==<br />
<br />
TBD<br />
<br />
==Meeting Space & Lodgings==<br />
<br />
TBD<br />
<br />
==Attendees==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29<br />
|EY 49 - 8:15<br />
|8<br />
| Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|LH 1812 - 12:50<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|<del>30</del><br />
|<del>EZY 2325 - 15:55</del><br />
|<del>7</del><br />
|<del>Airplane</del><br />
|<del>Y</del><br />
|<del>Everything</del><br />
|M<br />
|-<br />
|bitmap<br />
|29<br />
|AA 40 - 09:30<br />
|8<br />
|Airplane<br />
| Y<br />
|Vegetarian<br />
|M<br />
|-<br />
| cc<br />
|26<br />
|Airplane 14:25h<br />
|30<br />
|Airplane 12:15h<br />
|Y<br />
|mostly anything<br />
|M for manly<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|Metro<br />
|N<br />
|Everything nomnomnom<br />
|M for Monkey<br />
|-<br />
|reosarevok<br />
|27<br />
|LH 1132 - 18:05<br />
|7<br />
|LH 1125 (10:30)<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28<br />
|Train / Sants @ 19:32<br />
|7 @ 08:22<br />
|Train / Sants<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28<br />
|Train / Sants @ 19:32<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
| 30<br />
|LH 1128 - 15:15<br />
|7 @ 12:50<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27<br />
|EW 2520 - 19:45<br />
|7 @ 13:40<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|M<br />
|}</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=77016MusicBrainz Summit/232023-09-28T11:34:31Z<p>RobertKaye: </p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Virtual attendees can join via Zoom:<br />
<br />
* ''Links to come''<br />
<br />
Chat during the summit will be in the [[Communication/IRC|#metabrainz IRC channel]] (please refrain from using Zoom chat and YouTube chat will be disabled).<br />
<br />
The summit will also be streamed (and archived) on YouTube:<br />
* [https://youtube.com/live/sVQe6-WJ8i0?feature=share Day 1 (Monday)]<br />
* [https://youtube.com/live/mGq_xFbqj90?feature=share Day 2 (Tuesday)]<br />
* [https://youtube.com/live/wi-n9429Qqs?feature=share Day 3 (Wednesday)]<br />
* [https://youtube.com/live/7xOYQwASORY?feature=share Day 4 (Thursday)]<br />
* [https://youtube.com/live/rnowydzq_w0?feature=share Day 5 (Friday)]<br />
There will also be written notes.<br />
<br />
== Schedule of Events ==<br />
<br />
Every morning we'll gather in the office and have breakfast. Come when you are ready to come. Lunch is in the office at 13:00. <br />
<br />
'''Livestreamed meetings are each day 14:00 - 19:30 local time (12:00 - 17:30 GMT)''' <br />
<br />
We will tackle big topics, after which smaller ad-hoc topics can be suggested by anyone.<br />
<br />
* Morning - 13:00: Be in the office, catch up with people, whatever<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places<br />
* Big topics: 14:00 - 17:00 (see agenda)<br />
* Ad-hoc topics: 17:00 - 19:30<br />
* Dinner, at various restaurants or at the office, TBD. We'll have at least two nice group dinners with everyone present<br />
<br />
==Agenda==<br />
<br />
As usual, each project should be prepared to give an update on the state of the project.<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* MB search upgrades (bitmap, lucifer, reosarevok, yvanzo, zas)<br />
* Proactively dealing with spam accounts + empty account deletions (reosarevok, yvanzo, bitmap, mayhem, ...)<br />
* Workflow for security alerts (all code maintainers)<br />
* Workflow for service alerts (all service maintainers)<br />
* Event Art Archive and BB Cover Art Archive (bitmap, kellnerd, monkey, reosarevok, yvanzo)<br />
* State of the music industry (mayhem, akshaaatt)<br />
* OAuth migration update and future planning (lucifer, mayhem)<br />
* Next years' summit, limiting the scope a bit. (mayhem)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put IRC on a screen<br />
* Does it make sense to store dancers in MusicBrainz? (reo)<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* Running/writing Selenium tests for MusicBrainz Server/Docker ([[User:Bitmap|bitmap]], reosarevok, yvanzo)<br />
* Picard 3 plugin system (outsidecontext & zas)<br />
* Instagram/social media ([[User:Aerozol|aerozol]] & akshaaatt)<br />
* Mobile app design ([[User:Aerozol|aerozol]] & akshaaatt)<br />
* Centralized logging system ([[User:Atj|atj]], [[User:Bitmap|bitmap]], [[User:YvanZo|yvanzo]], rob, [[User:Zas|zas]])<br />
* MB UI Revamp PRs fixing (akshaaatt, bitmap, yvanzo, reosarevok)<br />
* Reducing open MB PRs to a sensible number (bitmap, yvanzo, reosarevok, sometimes aerozol)<br />
* AutoTag Hacking (outsidecontext, mayhem)<br />
* ...<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th (15:00) until the 7th] (AirBnB 1). If you're name is not listed in the lodgings breakdown below, then you're in this AirBnB.<br />
<br />
We've also got two hotel rooms reserved for reo/kellnerd and zas/yvanzo. Contact mayhem for details on check-in.<br />
<br />
== Notes ==<br />
<br />
* Chocolates: send your wishes to kellnerd, who will definitely bring some of the good high-proof stuff... 70% cocoa, not what you were thinking :)<br />
* Aerozol will field requests for treats from NZ<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29<br />
|EY 49 - 8:15<br />
|8<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|LH 1812 - 12:50<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|30<br />
|EZY 2325 - 15:55<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|M<br />
|-<br />
|bitmap<br />
|29<br />
|AA 40 - 09:30<br />
|8<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|cc<br />
|26<br />
|Airplane 14:25h<br />
|30<br />
|Airplane 12:15h<br />
|Y<br />
|mostly anything<br />
|M for manly<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|Metro<br />
|N<br />
|Everything nomnomnom<br />
|M for Monkey<br />
|-<br />
|reosarevok<br />
|27<br />
|LH 1132 - 18:05<br />
|7<br />
|LH 1125 (10:30)<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 <br />
|Train / Sants @ 19:32<br />
|7 @ 08:22<br />
|Train / Sants<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28<br />
|Train / Sants @ 19:32<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30 <br />
|LH 1128 - 15:15<br />
|7 @ 12:50<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27 <br />
|EW 2520 - 19:45<br />
|7 @ 13:40<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
|-<br />
|needed<br />
|3<br />
|5<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|1<br />
|1<br />
|-<br />
|AirBnB 1<br />
|<br />
|<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|<br />
|<br />
|<br />
|-<br />
|Sailboat (reo)<br />
|<br />
|<br />
|<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel 1<br />
|2 (reo, kellnerd)<br />
|2 (reo, kellnerd)<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel 2<br />
|<br />
|zas, yvanzo<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Rob's<br />
|<br />
|<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|<br />
|<br />
|-<br />
|Monkey's<br />
|cc<br />
|cc<br />
|cc<br />
|cc (leave early)<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|}<br />
<br />
=== Virtual attendees ===<br />
Lucifer :(<br />
<br />
rdswift<br />
<br />
ansh<br />
<br />
== Volunteers ==<br />
<br />
* Aerozol: Livestream<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=77015MusicBrainz Summit/232023-09-28T11:21:00Z<p>RobertKaye: </p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Virtual attendees can join via Zoom:<br />
<br />
* ''Links to come''<br />
<br />
Chat during the summit will be in the [[Communication/IRC|#metabrainz IRC channel]] (please refrain from using Zoom chat and YouTube chat will be disabled).<br />
<br />
The summit will also be streamed (and archived) on YouTube:<br />
* [https://youtube.com/live/sVQe6-WJ8i0?feature=share Day 1 (Monday)]<br />
* [https://youtube.com/live/mGq_xFbqj90?feature=share Day 2 (Tuesday)]<br />
* [https://youtube.com/live/wi-n9429Qqs?feature=share Day 3 (Wednesday)]<br />
* [https://youtube.com/live/7xOYQwASORY?feature=share Day 4 (Thursday)]<br />
* [https://youtube.com/live/rnowydzq_w0?feature=share Day 5 (Friday)]<br />
There will also be written notes.<br />
<br />
== Schedule of Events ==<br />
<br />
Every morning we'll gather in the office and have breakfast. Come when you are ready to come. Lunch is in the office at 13:00. <br />
<br />
'''Livestreamed meetings are each day 14:00 - 19:30 local time (12:00 - 17:30 GMT)''' <br />
<br />
We will tackle big topics, after which smaller ad-hoc topics can be suggested by anyone.<br />
<br />
* Morning - 13:00: Be in the office, catch up with people, whatever<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places<br />
* Big topics: 14:00 - 17:00 (see agenda)<br />
* Ad-hoc topics: 17:00 - 19:30<br />
* Dinner, at various restaurants or at the office, TBD. We'll have at least two nice group dinners with everyone present<br />
<br />
==Agenda==<br />
<br />
As usual, each project should be prepared to give an update on the state of the project.<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* MB search upgrades (bitmap, lucifer, reosarevok, yvanzo, zas)<br />
* Proactively dealing with spam accounts + empty account deletions (reosarevok, yvanzo, bitmap, mayhem, ...)<br />
* Workflow for security alerts (all code maintainers)<br />
* Workflow for service alerts (all service maintainers)<br />
* Event Art Archive and BB Cover Art Archive (bitmap, kellnerd, monkey, reosarevok, yvanzo)<br />
* State of the music industry (mayhem, akshaaatt)<br />
* OAuth migration update and future planning (lucifer, mayhem)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put IRC on a screen<br />
* Does it make sense to store dancers in MusicBrainz? (reo)<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* Running/writing Selenium tests for MusicBrainz Server/Docker ([[User:Bitmap|bitmap]], reosarevok, yvanzo)<br />
* Picard 3 plugin system (outsidecontext & zas)<br />
* Instagram/social media ([[User:Aerozol|aerozol]] & akshaaatt)<br />
* Mobile app design ([[User:Aerozol|aerozol]] & akshaaatt)<br />
* Centralized logging system ([[User:Atj|atj]], [[User:Bitmap|bitmap]], [[User:YvanZo|yvanzo]], rob, [[User:Zas|zas]])<br />
* MB UI Revamp PRs fixing (akshaaatt, bitmap, yvanzo, reosarevok)<br />
* Reducing open MB PRs to a sensible number (bitmap, yvanzo, reosarevok, sometimes aerozol)<br />
* AutoTag Hacking (outsidecontext, mayhem)<br />
* ...<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th (15:00) until the 7th] (AirBnB 1). If you're name is not listed in the lodgings breakdown below, then you're in this AirBnB.<br />
<br />
We've also got two hotel rooms reserved for reo/kellnerd and zas/yvanzo. Contact mayhem for details on check-in.<br />
<br />
== Notes ==<br />
<br />
* Chocolates: send your wishes to kellnerd, who will definitely bring some of the good high-proof stuff... 70% cocoa, not what you were thinking :)<br />
* Aerozol will field requests for treats from NZ<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29<br />
|EY 49 - 8:15<br />
|8<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|LH 1812 - 12:50<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|30<br />
|EZY 2325 - 15:55<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|M<br />
|-<br />
|bitmap<br />
|29<br />
|AA 40 - 09:30<br />
|8<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|cc<br />
|26<br />
|Airplane 14:25h<br />
|30<br />
|Airplane 12:15h<br />
|Y<br />
|mostly anything<br />
|M for manly<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|Metro<br />
|N<br />
|Everything nomnomnom<br />
|M for Monkey<br />
|-<br />
|reosarevok<br />
|27<br />
|LH 1132 - 18:05<br />
|7<br />
|LH 1125 (10:30)<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 <br />
|Train / Sants @ 19:32<br />
|7 @ 08:22<br />
|Train / Sants<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28<br />
|Train / Sants @ 19:32<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30 <br />
|LH 1128 - 15:15<br />
|7 @ 12:50<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27 <br />
|EW 2520 - 19:45<br />
|7 @ 13:40<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
|-<br />
|needed<br />
|3<br />
|5<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|1<br />
|1<br />
|-<br />
|AirBnB 1<br />
|<br />
|<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|<br />
|<br />
|<br />
|-<br />
|Sailboat (reo)<br />
|<br />
|<br />
|<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel 1<br />
|2 (reo, kellnerd)<br />
|2 (reo, kellnerd)<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel 2<br />
|<br />
|zas, yvanzo<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Rob's<br />
|<br />
|<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|<br />
|<br />
|-<br />
|Monkey's<br />
|cc<br />
|cc<br />
|cc<br />
|cc (leave early)<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|}<br />
<br />
=== Virtual attendees ===<br />
Lucifer :(<br />
<br />
rdswift<br />
<br />
ansh<br />
<br />
== Volunteers ==<br />
<br />
* Aerozol: Livestream<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76991MusicBrainz Summit/232023-09-21T09:48:09Z<p>RobertKaye: </p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* chocolates: send your wishes to kellnerd, who will definitely bring some of the good high-proof stuff... 70% cocoa, not what you were thinking :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at various restaurants or at the office, TBD. We'll have at least two nice group dinners with everyone present.<br />
<br />
<br />
The big topics and ad hoc topics will be streamed each day: 14:00 - 19:30 (at most) each day<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Don't use orange pens on the whiteboard. (new pens have been ordered, Rob will "safeguard" the orange one)<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* Running/writing Selenium tests for MusicBrainz Server/Docker ([[User:Bitmap|bitmap]], reosarevok, yvanzo)<br />
* Picard 3 plugin system (outsidecontext & zas)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th (15:00) until the 7th] (AirBnB 1). If you're name is not listed in the lodgings breakdown below, then you're in this AirBnB.<br />
<br />
We've also got two hotel rooms reserved for reo/kellnerd and zas/yvanzo. Contact mayhem for details on check-in.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29<br />
|EY 49 - 8:15<br />
|8<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|LH 1812 - 12:50<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|30<br />
|EZY 2325 - 15:55<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|M<br />
|-<br />
|bitmap<br />
|29<br />
|AA 40 - 09:30<br />
|8<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|cc<br />
|27<br />
|Airplane<br />
|30<br />
|Airplane<br />
|Y<br />
|mostly anything<br />
|M for manly<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|Metro<br />
|N<br />
|Everything nomnomnom<br />
|M for Monkey<br />
|-<br />
|reosarevok<br />
|27<br />
|LH 1132 - 18:05<br />
|7<br />
|LH 1125 (10:30)<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 <br />
|Train / Sants @ 19:32<br />
|7 @ 08:22<br />
|Train / Sants<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28<br />
|Train / Sants @ 19:32<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30 <br />
|LH 1128 - 15:15<br />
|7 @ 12:50<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27 <br />
|EW 2520 - 19:45<br />
|7 @ 13:40<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
|-<br />
|needed<br />
|3<br />
|5<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|1<br />
|1<br />
|-<br />
|AirBnB 1<br />
|<br />
|<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|<br />
|<br />
|<br />
|-<br />
|Sailboat (reo)<br />
|<br />
|<br />
|<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel 1<br />
|2 (reo, kellnerd)<br />
|2 (reo, kellnerd)<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel 2<br />
|<br />
|zas, yvanzo<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Rob's<br />
|<br />
|<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|<br />
|<br />
|-<br />
|Monkey's<br />
|cc<br />
|cc<br />
|cc<br />
|cc (leave early)<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|}<br />
<br />
=== Virtual attendees ===<br />
Lucifer. :(<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76989MusicBrainz Summit/232023-09-20T10:50:57Z<p>RobertKaye: </p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* chocolates: send your wishes to kellnerd, who will definitely bring some of the good high-proof stuff... 70% cocoa, not what you were thinking :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at various restaurants or at the office, TBD. We'll have at least two nice group dinners with everyone present.<br />
<br />
<br />
The big topics and ad hoc topics will be streamed each day: 14:00 - 19:30 (at most) each day<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Don't use orange pens on the whiteboard. (new pens have been ordered, Rob will "safeguard" the orange one)<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* Running/writing Selenium tests for MusicBrainz Server/Docker ([[User:Bitmap|bitmap]], reosarevok, yvanzo)<br />
* Picard 3 plugin system (outsidecontext & zas)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th (15:00) until the 7th] (AirBnB 1). If you're name is not listed in the lodgings breakdown below, then you're in this AirBnB.<br />
<br />
We've also got two hotel rooms reserved for reo/kellnerd and zas/yvanzo. Contact mayhem for details on check-in.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29<br />
|EY 49 - 8:15<br />
|8<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|LH 1812 - 12:50<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|30<br />
|EZY 2325 - 15:55<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|M<br />
|-<br />
|bitmap<br />
|29<br />
|AA 40 - 09:30<br />
|8<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|cc<br />
|27<br />
|Airplane<br />
|30<br />
|Airplane<br />
|Y<br />
|mostly anything<br />
|M for manly<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|Metro<br />
|N<br />
|Everything nomnomnom<br />
|M for Monkey<br />
|-<br />
|reosarevok<br />
|27<br />
|LH 1132 - 18:05<br />
|7<br />
|LH 1125 (10:30)<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 <br />
|Train / Sants @ 19:32<br />
|7 @ 08:22<br />
|Train / Sants<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28<br />
|Train / Sants @ 19:32<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30 <br />
|LH 1128 - 15:15<br />
|7 @ 12:50<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27 <br />
|EW 2520 - 19:45<br />
|7 @ 13:40<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
|-<br />
|needed<br />
|3<br />
|5<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|1<br />
|1<br />
|-<br />
|AirBnB 1<br />
|<br />
|<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|<br />
|<br />
|<br />
|-<br />
|AirBnB 2 (reo)<br />
|<br />
|<br />
|<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel 1<br />
|2 (reo, kellnerd)<br />
|2 (reo, kellnerd)<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel 2<br />
|<br />
|zas, yvanzo<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Rob's<br />
|<br />
|<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|<br />
|<br />
|-<br />
|Monkey's<br />
|cc<br />
|cc<br />
|cc<br />
|cc (leave early)<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|}<br />
<br />
=== Virtual attendees ===<br />
Lucifer. :(<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76985MusicBrainz Summit/232023-09-19T15:05:58Z<p>RobertKaye: </p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* chocolates: send your wishes to kellnerd, who will definitely bring some of the good high-proof stuff... 70% cocoa, not what you were thinking :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at various restaurants or at the office, TBD. We'll have at least two nice group dinners with everyone present.<br />
<br />
<br />
The big topics and ad hoc topics will be streamed each day: 14:00 - 19:30 (at most) each day<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Don't use orange pens on the whiteboard. (new pens have been ordered, Rob will "safeguard" the orange one)<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* Running/writing Selenium tests for MusicBrainz Server/Docker ([[User:Bitmap|bitmap]], reosarevok, yvanzo)<br />
* Picard 3 plugin system (outsidecontext & zas)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th (15:00) until the 7th] (AirBnB 1). We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29<br />
|EY 49 - 8:15<br />
|8<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|LH 1812 - 12:50<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|30<br />
|EZY 2325 - 15:55<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|M<br />
|-<br />
|bitmap<br />
|29<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|cc<br />
|27<br />
|Airplane<br />
|30<br />
|Airplane<br />
|Y<br />
|mostly anything<br />
|M for manly<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|Metro<br />
|N<br />
|Everything nomnomnom<br />
|M for Monkey<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane - LH 1132 (18:05)<br />
|7<br />
|Airplane - LH 1125 (10:30)<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 <br />
|Train / Sants @ 19:32<br />
|7 @ 08:22<br />
|Train / Sants<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28<br />
|Train / Sants @ 19:32<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30 <br />
|@ 15:15<br />
|7 @ 12:50<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27 <br />
|@ 19:45<br />
|7 @ 13:40<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
|-<br />
|needed<br />
|3<br />
|5<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|1<br />
|1<br />
|-<br />
|AirBnB 1<br />
|<br />
|<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|<br />
|<br />
|<br />
|-<br />
|AirBnB 2 (reo)<br />
|<br />
|<br />
|<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel<br />
|2 (reo, kellnerd)<br />
|2 (reo, kellnerd)<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Rob's<br />
|<br />
|<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|<br />
|<br />
|-<br />
|Monkey's<br />
|cc<br />
|cc<br />
|cc<br />
|cc (leave early)<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|}<br />
<br />
=== Virtual attendees ===<br />
Lucifer. :(<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76984MusicBrainz Summit/232023-09-19T15:00:05Z<p>RobertKaye: </p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* chocolates: send your wishes to kellnerd, who will definitely bring some of the good high-proof stuff... 70% cocoa, not what you were thinking :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at various restaurants or at the office, TBD. We'll have at least two nice group dinners with everyone present.<br />
<br />
<br />
The big topics and ad hoc topics will be streamed each day: 14:00 - 19:30 (at most) each day<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Don't use orange pens on the whiteboard. (new pens have been ordered, Rob will "safeguard" the orange one)<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* Running/writing Selenium tests for MusicBrainz Server/Docker ([[User:Bitmap|bitmap]], reosarevok, yvanzo)<br />
* Picard 3 plugin system (outsidecontext & zas)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th (15:00) until the 7th] (AirBnB 1). We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29<br />
|EY 49 - 8:15<br />
|8<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|LH 1812 - 12:50<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|30<br />
|EZY 2325 - 15:55<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|M<br />
|-<br />
|bitmap<br />
|29<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|cc<br />
|27<br />
|Airplane<br />
|30<br />
|Airplane<br />
|Y<br />
|mostly anything<br />
|M for manly<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|Metro<br />
|N<br />
|Everything nomnomnom<br />
|M for Monkey<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane - LH 1132 (18:05)<br />
|7<br />
|Airplane - LH 1125 (10:30)<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 <br />
|Train / Sants @ 19:32<br />
|7 @ 08:22<br />
|Train / Sants<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28<br />
|Train / Sants @ 19:32<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30 <br />
|@ 15:15<br />
|7 @ 12:50<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27 <br />
|@ 19:45<br />
|7 @ 13:40<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
|-<br />
|needed<br />
|2<br />
|5<br />
|8<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|1<br />
|1<br />
|-<br />
|AirBnB 1<br />
|<br />
|<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel<br />
|2<br />
|2<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Rob's<br />
|reo<br />
|reo & Kellnerd<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|<br />
|<br />
|-<br />
|Monkey's<br />
|cc<br />
|cc<br />
|cc<br />
|cc (leave early)<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|-<br />
|TBD<br />
|<br />
|<br />
|<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|}<br />
<br />
=== Virtual attendees ===<br />
Lucifer. :(<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76982MusicBrainz Summit/232023-09-19T14:45:08Z<p>RobertKaye: </p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* chocolates: send your wishes to kellnerd, who will definitely bring some of the good high-proof stuff... 70% cocoa, not what you were thinking :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at various restaurants or at the office, TBD. We'll have at least two nice group dinners with everyone present.<br />
<br />
<br />
The big topics and ad hoc topics will be streamed each day: 14:00 - 19:30 (at most) each day<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Don't use orange pens on the whiteboard. (new pens have been ordered, Rob will "safeguard" the orange one)<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* Running/writing Selenium tests for MusicBrainz Server/Docker ([[User:Bitmap|bitmap]], reosarevok, yvanzo)<br />
* Picard 3 plugin system (outsidecontext & zas)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th (15:00) until the 7th] (AirBnB 1). We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29<br />
|EY 49 - 8:15<br />
|8<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|LH 1812 - 12:50<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|30<br />
|EZY 2325 - 15:55<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|M<br />
|-<br />
|bitmap<br />
|29<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|cc<br />
|27<br />
|Airplane<br />
|30<br />
|Airplane<br />
|Y<br />
|mostly anything<br />
|M for manly<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|Metro<br />
|N<br />
|Everything nomnomnom<br />
|M for Monkey<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 @ 19:32<br />
|Train / Sants<br />
|7 @ 08:22<br />
|Train / Sants<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28 @ 19:32 <br />
|Train / Sants<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30 @ 15:15<br />
|Airplane<br />
|7 @ 12:50<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27 @ 19:45<br />
|Airplane<br />
|7 @ 13:40<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
|-<br />
|needed<br />
|2<br />
|5<br />
|8<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|1<br />
|1<br />
|-<br />
|AirBnB 1<br />
|<br />
|<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel<br />
|2<br />
|2<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Rob's<br />
|reo<br />
|reo & Kellnerd<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|<br />
|<br />
|-<br />
|Monkey's<br />
|cc<br />
|cc<br />
|cc<br />
|cc (leave early)<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|-<br />
|TBD<br />
|<br />
|<br />
|<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|}<br />
<br />
=== Virtual attendees ===<br />
Lucifer. :(<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76981MusicBrainz Summit/232023-09-19T14:40:44Z<p>RobertKaye: </p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* chocolates: send your wishes to kellnerd, who will definitely bring some of the good high-proof stuff... 70% cocoa, not what you were thinking :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at various restaurants or at the office, TBD. We'll have at least two nice group dinners with everyone present.<br />
<br />
<br />
The big topics and ad hoc topics will be streamed each day: 14:00 - 19:30 (at most) each day<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Don't use orange pens on the whiteboard. (new pens have been ordered, Rob will "safeguard" the orange one)<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* Running/writing Selenium tests for MusicBrainz Server/Docker ([[User:Bitmap|bitmap]], reosarevok, yvanzo)<br />
* Picard 3 plugin system (outsidecontext & zas)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th (15:00) until the 7th] (AirBnB 1). We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29<br />
|EY 49 - 8:15<br />
|8<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|LH 1812 - 12:50<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|30<br />
|EZY 2325 - 15:55<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|M<br />
|-<br />
|bitmap<br />
|29<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|cc<br />
|27<br />
|Airplane<br />
|30<br />
|Airplane<br />
|Y<br />
|mostly anything<br />
|M for manly<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|Metro<br />
|N<br />
|Everything nomnomnom<br />
|M for Monkey<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 @ 19:32<br />
|Train / Sants<br />
|7 @ 08:22<br />
|Train / Sants<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28 @ 19:32 <br />
|Train / Sants<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30 @ 15:15<br />
|Airplane<br />
|7 @ 12:50<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27 @ 19:45<br />
|Airplane<br />
|7 @ 13:40<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
|-<br />
|needed<br />
|3<br />
|5<br />
|8<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|1<br />
|1<br />
|-<br />
|AirBnB 1<br />
|<br />
|<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel<br />
|2<br />
|2<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Rob's<br />
|reo<br />
|reo & Kellnerd<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|<br />
|<br />
|-<br />
|Monkey's<br />
|cc<br />
|cc<br />
|cc<br />
|cc (leave early)<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|-<br />
|TBD<br />
|<br />
|<br />
|<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|}<br />
<br />
=== Virtual attendees ===<br />
Lucifer. :(<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76971MusicBrainz Summit/232023-09-12T10:29:01Z<p>RobertKaye: /* Attendees */</p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* mayhem suggests we leave Monday open for a hacking/whatever day<br />
* atj assumes people will arrive on the weekend to acclimate before the summit<br />
* chocolates: send your wishes to kellnerd, who will definitely bring some of the good high-proof stuff... 70% cocoa, not what you were thinking :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at various restaurants or at the office, TBD. We'll have at least two nice group dinners with everyone present.<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Big red light for remote participants to put their hand up<br />
* Don't use orange pens on the whiteboard<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* Running/writing Selenium tests for MusicBrainz Server/Docker ([[User:Bitmap|bitmap]], reosarevok, yvanzo)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th until the 7th] (AirBnB 1). We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29<br />
|EY 49 -- 8:15<br />
|8<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|30<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|M<br />
|-<br />
|bitmap<br />
|29<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|cc<br />
|27<br />
|Airplane<br />
|30<br />
|Airplane<br />
|Y<br />
|mostly anything<br />
|M for manly<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|Metro<br />
|N<br />
|Everything nomnomnom<br />
|M for Monkey<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 @ 19:32<br />
|Train / Sants<br />
|7 @ 08:22<br />
|Train / Sants<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28 @ 19:32 <br />
|Train / Sants<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27 @ 19:45<br />
|Airplane<br />
|7 @ 13:40<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
|-<br />
|needed<br />
|3<br />
|5<br />
|8<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|1<br />
|1<br />
|-<br />
|AirBnB 1<br />
|<br />
|<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel<br />
|2<br />
|2<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Rob's<br />
|reo<br />
|reo & Kellnerd<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|<br />
|<br />
|-<br />
|Monkey's<br />
|cc<br />
|cc<br />
|cc<br />
|cc (leave early)<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|-<br />
|TBD<br />
|<br />
|<br />
|<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|}<br />
<br />
=== Virtual attendees ===<br />
Lucifer. :(<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76935MusicBrainz Summit/232023-09-05T14:36:51Z<p>RobertKaye: /* Schedule of Events */</p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* mayhem suggests we leave Monday open for a hacking/whatever day<br />
* atj assumes people will arrive on the weekend to acclimate before the summit<br />
* chocolates :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at various restaurants or at the office, TBD. We'll have at least two nice group dinners with everyone present.<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Big red light for remote participants to put their hand up<br />
* Don't use orange pens on the whiteboard<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th until the 7th] (AirBnB 1). We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29?<br />
|Airplane<br />
|9?<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|30<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|<br />
|-<br />
|bitmap<br />
|29<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|cc<br />
|27<br />
|Airplane<br />
|29<br />
|Airplane<br />
|Y<br />
|<br />
|<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Quasi-vegetarian<br />
|<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 @ 19:32<br />
|Train / Sants<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28 @ 19:32 <br />
|Train / Sants<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Eats everything<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
|-<br />
|needed<br />
|3<br />
|5<br />
|8<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|2<br />
|1<br />
|-<br />
|AirBnB 1<br />
|<br />
|<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel<br />
|2<br />
|2<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Rob's<br />
|reo<br />
|reo & Kellnerd<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|<br />
|-<br />
|Monkey's<br />
|cc<br />
|cc<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|-<br />
|TBD<br />
|<br />
|<br />
|<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|}<br />
<br />
=== Virtual attendees ===<br />
Lucifer. :(<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76934MusicBrainz Summit/232023-09-05T12:24:51Z<p>RobertKaye: /* Attendees */</p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* mayhem suggests we leave Monday open for a hacking/whatever day<br />
* atj assumes people will arrive on the weekend to acclimate before the summit<br />
* chocolates :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at a restaurant, at 20:30.<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Big red light for remote participants to put their hand up<br />
* Don't use orange pens on the whiteboard<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th until the 7th] (AirBnB 1). We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29?<br />
|Airplane<br />
|9?<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|30<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|<br />
|-<br />
|bitmap<br />
|29<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|cc<br />
|27<br />
|Airplane<br />
|29<br />
|Airplane<br />
|Y<br />
|<br />
|<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Quasi-vegetarian<br />
|<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 @ 19:32<br />
|Train / Sants<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28 @ 19:32 <br />
|Train / Sants<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Eats everything<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
|-<br />
|needed<br />
|3<br />
|5<br />
|8<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|2<br />
|1<br />
|-<br />
|AirBnB 1<br />
|<br />
|<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel<br />
|2<br />
|2<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Rob's<br />
|reo<br />
|reo & Kellnerd<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|<br />
|-<br />
|Monkey's<br />
|cc<br />
|cc<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|-<br />
|TBD<br />
|<br />
|<br />
|<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|}<br />
<br />
=== Virtual attendees ===<br />
Lucifer. :(<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76933MusicBrainz Summit/232023-09-05T12:04:19Z<p>RobertKaye: /* Attendees */</p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* mayhem suggests we leave Monday open for a hacking/whatever day<br />
* atj assumes people will arrive on the weekend to acclimate before the summit<br />
* chocolates :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at a restaurant, at 20:30.<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Big red light for remote participants to put their hand up<br />
* Don't use orange pens on the whiteboard<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th until the 7th] (AirBnB 1). We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29?<br />
|Airplane<br />
|9?<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|29??<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|<br />
|-<br />
|bitmap<br />
|29<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|cc<br />
|27<br />
|Airplane<br />
|29<br />
|Airplane<br />
|Y<br />
|<br />
|<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Quasi-vegetarian<br />
|<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 @ 19:32<br />
|Train / Sants<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28 @ 19:32 <br />
|Train / Sants<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Eats everything<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
|-<br />
|needed<br />
|3<br />
|5<br />
|8<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|2<br />
|1<br />
|-<br />
|AirBnB 1<br />
|<br />
|<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel<br />
|2<br />
|2<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Rob's<br />
|reo<br />
|reo & Kellnerd<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|<br />
|-<br />
|Monkey's<br />
|cc<br />
|cc<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|-<br />
|TBD<br />
|<br />
|<br />
|<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|}<br />
<br />
=== Virtual attendees ===<br />
Lucifer. :(<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76932MusicBrainz Summit/232023-09-05T12:03:45Z<p>RobertKaye: /* Attendees */</p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* mayhem suggests we leave Monday open for a hacking/whatever day<br />
* atj assumes people will arrive on the weekend to acclimate before the summit<br />
* chocolates :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at a restaurant, at 20:30.<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Big red light for remote participants to put their hand up<br />
* Don't use orange pens on the whiteboard<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th until the 7th] (AirBnB 1). We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29?<br />
|Airplane<br />
|9?<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|29??<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|<br />
|-<br />
|bitmap<br />
|29<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|cc<br />
|27<br />
|Airplane<br />
|29<br />
|Airplane<br />
|Y<br />
|<br />
|<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Quasi-vegetarian<br />
|<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 @ 19:32<br />
|Train / Sants<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28 @ 19:32 <br />
|Train / Sants<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Eats everything<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
|-<br />
|needed<br />
|3<br />
|5<br />
|8<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|2<br />
|1<br />
|-<br />
|AirBnB 1<br />
|<br />
|<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel<br />
|2<br />
|2<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Rob's<br />
|reo<br />
|reo & Kellnerd<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|<br />
|-<br />
|Monkey's<br />
|cc<br />
|cc<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|-<br />
|TBD<br />
|<br />
|<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|}<br />
<br />
=== Virtual attendees ===<br />
Lucifer. :(<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76931MusicBrainz Summit/232023-09-05T11:52:06Z<p>RobertKaye: /* Attendees */</p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* mayhem suggests we leave Monday open for a hacking/whatever day<br />
* atj assumes people will arrive on the weekend to acclimate before the summit<br />
* chocolates :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at a restaurant, at 20:30.<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Big red light for remote participants to put their hand up<br />
* Don't use orange pens on the whiteboard<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th until the 7th] (AirBnB 1). We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29?<br />
|Airplane<br />
|9?<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|29??<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|<br />
|-<br />
|bitmap<br />
|29<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|cc<br />
|27<br />
|Airplane<br />
|29<br />
|Airplane<br />
|Y<br />
|<br />
|<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Quasi-vegetarian<br />
|<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 @ 19:32<br />
|Train / Sants<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28 @ 19:32 <br />
|Train / Sants<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Eats everything<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
|-<br />
|needed<br />
|3<br />
|5<br />
|8<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|2<br />
|1<br />
|-<br />
|AirBnB 1<br />
|<br />
|<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel<br />
|2<br />
|2<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Rob's<br />
|reo<br />
|reo & Kellnerd<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|<br />
|-<br />
|Monkey's<br />
|cc<br />
|cc<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|}<br />
<br />
=== Virtual attendees ===<br />
Lucifer. :(<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76930MusicBrainz Summit/232023-09-05T11:26:23Z<p>RobertKaye: /* Attendees */</p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* mayhem suggests we leave Monday open for a hacking/whatever day<br />
* atj assumes people will arrive on the weekend to acclimate before the summit<br />
* chocolates :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at a restaurant, at 20:30.<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Big red light for remote participants to put their hand up<br />
* Don't use orange pens on the whiteboard<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th until the 7th] (AirBnB 1). We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29?<br />
|Airplane<br />
|9?<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|29??<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|<br />
|-<br />
|bitmap<br />
|29<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|cc<br />
|27<br />
|Airplane<br />
|29<br />
|Airplane<br />
|Y<br />
|<br />
|<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Quasi-vegetarian<br />
|<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 @ 19:32<br />
|Train / Sants<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28 @ 19:32 <br />
|Train / Sants<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Eats everything<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
|-<br />
|needed<br />
|3<br />
|5<br />
|8<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|2<br />
|1<br />
|-<br />
|AirBnB 1<br />
|<br />
|<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|<br />
|<br />
|<br />
|-<br />
|Hotel<br />
|2<br />
|2<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Rob's<br />
|reo<br />
|reo & Kellnerd<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|<br />
|-<br />
|Monkey's<br />
|cc<br />
|cc<br />
|zas<br />
|zas<br />
|zas<br />
|zas<br />
|zas<br />
|zas<br />
|zas<br />
|zas<br />
|zas<br />
|zas<br />
|zas<br />
|}<br />
<br />
=== Virtual attendees ===<br />
Lucifer. :(<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76929MusicBrainz Summit/232023-09-05T11:06:37Z<p>RobertKaye: /* Attendees */</p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* mayhem suggests we leave Monday open for a hacking/whatever day<br />
* atj assumes people will arrive on the weekend to acclimate before the summit<br />
* chocolates :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at a restaurant, at 20:30.<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Big red light for remote participants to put their hand up<br />
* Don't use orange pens on the whiteboard<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th until the 7th] (AirBnB 1). We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29?<br />
|Airplane<br />
|9?<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|29??<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|<br />
|-<br />
|bitmap<br />
|29<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|lucifer<br />
|<br />
|<br />
|<br />
|<br />
|N<br />
|Vegetarian<br />
|<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Quasi-vegetarian<br />
|<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 @ 19:32<br />
|Train / Sants<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28 @ 19:32 <br />
|Train / Sants<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Eats everything<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
|-<br />
|needed<br />
|2<br />
|4<br />
|8<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|2<br />
|1<br />
|-<br />
|AirBnB 1<br />
|<br />
|<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|7<br />
|<br />
|<br />
|<br />
|-<br />
|Rob's<br />
|<br />
|<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|aerozol<br />
|<br />
|-<br />
|Monkey's<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|zas<br />
|zas<br />
|zas<br />
|}<br />
<br />
=== Virtual attendees ===<br />
<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76928MusicBrainz Summit/232023-09-05T10:30:15Z<p>RobertKaye: /* Attendees */</p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* mayhem suggests we leave Monday open for a hacking/whatever day<br />
* atj assumes people will arrive on the weekend to acclimate before the summit<br />
* chocolates :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at a restaurant, at 20:30.<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Big red light for remote participants to put their hand up<br />
* Don't use orange pens on the whiteboard<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th until the 7th]. We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29?<br />
|Airplane<br />
|9?<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|29??<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|<br />
|-<br />
|bitmap<br />
|29<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|lucifer<br />
|<br />
|<br />
|<br />
|<br />
|N<br />
|Vegetarian<br />
|<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Quasi-vegetarian<br />
|<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 @ 19:32<br />
|Train / Sants<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28 @ 19:32 <br />
|Train / Sants<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Eats everything<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
!10<br />
|-<br />
|2<br />
|4<br />
|8<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|2<br />
|2<br />
|1<br />
|}<br />
<br />
=== Virtual attendees ===<br />
<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76927MusicBrainz Summit/232023-09-05T10:29:49Z<p>RobertKaye: /* Attendees */</p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* mayhem suggests we leave Monday open for a hacking/whatever day<br />
* atj assumes people will arrive on the weekend to acclimate before the summit<br />
* chocolates :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at a restaurant, at 20:30.<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Big red light for remote participants to put their hand up<br />
* Don't use orange pens on the whiteboard<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th until the 7th]. We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29?<br />
|Airplane<br />
|9?<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|29??<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|<br />
|-<br />
|bitmap<br />
|29<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|lucifer<br />
|<br />
|<br />
|<br />
|<br />
|N<br />
|Vegetarian<br />
|<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Quasi-vegetarian<br />
|<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 @ 19:32<br />
|Train / Sants<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28 @ 19:32 <br />
|Train / Sants<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Eats everything<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
!10<br />
|-<br />
|2<br />
|4<br />
|8<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|2<br />
|3<br />
|2<br />
|1<br />
|}<br />
<br />
=== Virtual attendees ===<br />
<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76926MusicBrainz Summit/232023-09-05T10:24:14Z<p>RobertKaye: /* Attendees */</p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* mayhem suggests we leave Monday open for a hacking/whatever day<br />
* atj assumes people will arrive on the weekend to acclimate before the summit<br />
* chocolates :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at a restaurant, at 20:30.<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Big red light for remote participants to put their hand up<br />
* Don't use orange pens on the whiteboard<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th until the 7th]. We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29?<br />
|Airplane<br />
|9?<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|29??<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Everything<br />
|<br />
|-<br />
|bitmap<br />
|29<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|lucifer<br />
|<br />
|<br />
|<br />
|<br />
|N<br />
|Vegetarian<br />
|<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Quasi-vegetarian<br />
|<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 @ 19:32<br />
|Train / Sants<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28 @ 19:32 <br />
|Train / Sants<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Eats everything<br />
|M<br />
|}<br />
{| class="wikitable"<br />
|+Number of beds per day<br />
!27<br />
!28<br />
!29<br />
!30<br />
!1<br />
!2<br />
!3<br />
!4<br />
!5<br />
!6<br />
!7<br />
!8<br />
!9<br />
!10<br />
|-<br />
|2<br />
|4<br />
|8<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|9<br />
|3<br />
|3<br />
|2<br />
|1<br />
|}<br />
<br />
=== Virtual attendees ===<br />
<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76925MusicBrainz Summit/232023-09-05T10:08:44Z<p>RobertKaye: </p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* mayhem suggests we leave Monday open for a hacking/whatever day<br />
* atj assumes people will arrive on the weekend to acclimate before the summit<br />
* chocolates :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at a restaurant, at 20:30.<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* MB form submission flow (bitmap, outsidecontext, reosarevok, yvanzo)<br />
* MB edit search load (bitmap, reosarevok, yvanzo)<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Big red light for remote participants to put their hand up<br />
* Don't use orange pens on the whiteboard<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* Key signing party throughout the week<br />
* Picard packaging design ([[User:OutsideContext|outsidecontext]] & [[User:Aerozol|aerozol]])<br />
* Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]])<br />
* Code signing of MetaBrainz apps: experience in Picard, applicable to other distributed MB software? (outsidecontext, zas, lucifer, rob, ???)<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th until the 7th]. We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29?<br />
|Airplane<br />
|9?<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|<br />
|Airplane<br />
|<br />
|Airplane<br />
|Y<br />
|Everything<br />
|<br />
|-<br />
|bitmap<br />
|29 or 30?<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|lucifer<br />
|<br />
|<br />
|<br />
|<br />
|N<br />
|Vegetarian<br />
|<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Quasi-vegetarian<br />
|<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 @ 19:32<br />
|Train / Sants<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28 @ 19:32 <br />
|Train / Sants<br />
|10<br />
|Train<br />
|Y<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|30<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Omnivore<br />
|L<br />
|-<br />
|kellnerd<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Eats everything<br />
|M<br />
|}<br />
<br />
=== Virtual attendees ===<br />
<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76677MusicBrainz Summit/232023-07-11T15:55:26Z<p>RobertKaye: </p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* mayhem suggests we leave Monday open for a hacking/whatever day<br />
* atj assumes people will arrive on the weekend to acclimate before the summit<br />
* chocolates :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at a restaurant, at 20:30.<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Big red light for remote participants to put their hand up<br />
* Don't use orange pens on the whiteboard<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th until the 7th]. We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29?<br />
|Airplane<br />
|9?<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|<br />
|Airplane<br />
|<br />
|Airplane<br />
|Y<br />
|Everything<br />
|<br />
|-<br />
|bitmap<br />
|29 or 30?<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|lucifer<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Quasi-vegetarian<br />
|<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 or 29?<br />
|Train<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28<br />
|Airplane/Train<br />
|9 or 10<br />
|Airplane/Train<br />
|N<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|29 or 30?<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Eats everything<br />
|L<br />
|-<br />
|kellnerd<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Eats everything<br />
|M<br />
|}<br />
<br />
=== Virtual attendees ===<br />
<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76676MusicBrainz Summit/232023-07-11T15:52:32Z<p>RobertKaye: </p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* mayhem suggests we leave Monday open for a hacking/whatever day<br />
* atj assumes people will arrive on the weekend to acclimate before the summit<br />
* chocolates :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at a restaurant, at 20:30.<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Big red light for remote participants to put their hand up<br />
* Don't use orange pens on the whiteboard<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th until the 7th]. We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29?<br />
|Airplane<br />
|9?<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|<br />
|Airplane<br />
|<br />
|Airplane<br />
|Y<br />
|Everything<br />
|<br />
|-<br />
|bitmap<br />
|29 or 30?<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|lucifer<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Quasi-vegetarian<br />
|<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|Om nom nom!<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 or 29?<br />
|Train<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28<br />
|Airplane/Train<br />
|9 or 10<br />
|Airplane/Train<br />
|N<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|29 or 30?<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Eats everything<br />
|L<br />
|-<br />
|kellnerd<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|<br />
|M<br />
|}<br />
<br />
=== Virtual attendees ===<br />
<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76675MusicBrainz Summit/232023-07-11T15:46:57Z<p>RobertKaye: </p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* mayhem suggests we leave Monday open for a hacking/whatever day<br />
* atj assumes people will arrive on the weekend to acclimate before the summit<br />
* chocolates :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at a restaurant, at 20:30.<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Big red light for remote participants to put their hand up<br />
* Don't use orange pens on the whiteboard<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th until the 7th]. We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29?<br />
|Airplane<br />
|9?<br />
|Airplane<br />
|Y<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|<br />
|Airplane<br />
|<br />
|Airplane<br />
|Y<br />
|<br />
|<br />
|-<br />
|bitmap<br />
|29 or 30?<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|M<br />
|-<br />
|lucifer<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|Vegetarian<br />
|<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|<br />
|<br />
|-<br />
|reosarevok<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|N<br />
|<br />
|XL<br />
|-<br />
|yvanzo<br />
|28 or 29?<br />
|Train<br />
|7<br />
|Airplane<br />
|Y<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28<br />
|Airplane/Train<br />
|9 or 10<br />
|Airplane/Train<br />
|N<br />
|Anything good<br />
|M<br />
|-<br />
|outsidecontext<br />
|29 or 30?<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|Y<br />
|Eats everything<br />
|L<br />
|-<br />
|kellnerd<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|Y<br />
|<br />
|M<br />
|}<br />
<br />
=== Virtual attendees ===<br />
<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76467MusicBrainz Summit/232023-05-30T11:01:37Z<p>RobertKaye: </p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* mayhem suggests we leave Monday open for a hacking/whatever day<br />
* atj assumes people will arrive on the weekend to acclimate before the summit<br />
* chocolates :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at a restaurant, at 20:30.<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Big red light for remote participants to put their hand up<br />
* Don't use orange pens on the whiteboard<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.com/rooms/39353324 AirBnb from the 29th until the 7th]. We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29?<br />
|Airplane<br />
|9?<br />
|Airplane<br />
|?<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29?<br />
|Airplane<br />
|<br />
|Airplane<br />
|?<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|<br />
|Airplane<br />
|<br />
|Airplane<br />
|<br />
|<br />
|<br />
|-<br />
|bitmap<br />
|29 or 30?<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|<br />
|Vegetarian<br />
|M<br />
|-<br />
|lucifer<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|<br />
|Vegetarian<br />
|<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|reosarevok<br />
|29?<br />
|Airplane<br />
|8?<br />
|Airplane<br />
|<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|yvanzo<br />
|28 or 29?<br />
|Train<br />
|7<br />
|Airplane<br />
|?<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28<br />
|Airplane/Train<br />
|9 or 10<br />
|Airplane/Train<br />
|?<br />
|Anything good<br />
|M<br />
|}<br />
<br />
=== Virtual attendees ===<br />
<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/23&diff=76464MusicBrainz Summit/232023-05-29T11:37:22Z<p>RobertKaye: Add lodgings and note about cocktail party</p>
<hr />
<div>Summit 23 is happening between October 2 and 6 2023, at [https://officebrainz.org/ MetaBrainz HQ] in Barcelona, Spain.<br />
<br />
Notes:<br />
<br />
* mayhem suggests we leave Monday open for a hacking/whatever day<br />
* atj assumes people will arrive on the weekend to acclimate before the summit<br />
* chocolates :)<br />
* There will be a robotic cocktail party at Mayhem's house on the evening of the 29th. <br />
<br />
== Schedule of Events ==<br />
<br />
Each day we'll gather in the morning in the office, where we'll have breakfast. Come when you are ready to come. Lunch will be in the office at 13:00 and we'll start our afternoon meetings each day at 14:00. <br />
<br />
Each day we're going to tackle big topics and then once the big topics are taken care of, we'll ask for smaller topics that others wish to talk about:<br />
<br />
* Mornings, until 13:00: Be in the office, talk to people, catch up, whatever.<br />
* Lunch, 13:00 - 14:00: Lunch in the office, brought in from local places.<br />
* Big topics: 14:00 - 17:00 -- see agenda.<br />
* Ad hoc topics: 17:00 - 19:30<br />
* Dinner, at a restaurant, at 20:30.<br />
<br />
==Agenda==<br />
<br />
Big topics to discuss and who needs to be present:<br />
* …<br />
<br />
Other topics:<br />
<br />
* Why do we not bring napkins to the summits?<br />
* Use projector to see remote participants, put irc on a screen<br />
* Big red light for remote participants to put their hand up<br />
* Don't use orange pens on the whiteboard<br />
<br />
==Hack sessions==<br />
Because we'll have most of the team in the same place it might make sense to have a few in-person informal hack sessions to get some projects off the ground. Ideas:<br />
<br />
* …<br />
<br />
== Headquarters & Lodgings ==<br />
We'll be at [https://officebrainz.org/ OfficeBrainz].<br />
<br />
We'll be at this [https://www.airbnb.co.uk/rooms/39515371 AirBnb from the 29th until the 7th]. We may book additional lodgings closer to the summit.<br />
<br />
== Attendees ==<br />
Summit attendees this year, (eventually) sorted by arrival time:<br />
{| class="wikitable sortable"<br />
!<br />
!Arrival date<br />
!Arrival transport<br />
!Departure date<br />
!Departure transport<br />
!Lodging<br />
!Food Preference<br />
!T-Shirt Size<br />
|-<br />
|Aerozol<br />
|29?<br />
|Airplane<br />
|9?<br />
|Airplane<br />
|?<br />
|Vegan<br />
|M<br />
|-<br />
|akshaaatt<br />
|29?<br />
|Airplane<br />
|<br />
|Airplane<br />
|?<br />
|Anything good<br />
|L<br />
|-<br />
|atj<br />
|<br />
|Airplane<br />
|<br />
|Airplane<br />
|<br />
|<br />
|<br />
|-<br />
|bitmap<br />
|29 or 30?<br />
|Airplane<br />
|7?<br />
|Airplane<br />
|<br />
|Vegetarian<br />
|M<br />
|-<br />
|lucifer<br />
|27<br />
|Airplane<br />
|7<br />
|Airplane<br />
|<br />
|Vegetarian<br />
|<br />
|-<br />
|monkey<br />
|N/A<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|reosarevok<br />
|29?<br />
|Airplane<br />
|8?<br />
|Airplane<br />
|<br />
|E eats everything<br />
|L / XL<br />
|-<br />
|mayhem<br />
|N/A<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|yvanzo<br />
|28 or 29?<br />
|Train<br />
|7<br />
|Airplane<br />
|?<br />
|Anything good<br />
|L<br />
|-<br />
|zas<br />
|28<br />
|Airplane/Train<br />
|9 or 10<br />
|Airplane/Train<br />
|?<br />
|Anything good<br />
|M<br />
|}<br />
<br />
=== Virtual attendees ===<br />
<br />
*<br />
<br />
== Volunteers ==<br />
<br />
* Person: Task<br />
<br />
== Emergency phone numbers ==<br />
<br />
# 112 All emergencies</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Canonical_MusicBrainz_data&diff=76260Canonical MusicBrainz data2023-03-10T14:51:08Z<p>RobertKaye: </p>
<hr />
<div>We have created several datasets that use the term “canonical”. Since MusicBrainz aims to catalog all released music, the database contains a lot of different versions of releases or different versions of recordings. We find it important to collect all of these different versions, but in the end it is too much data for most of our users. Fortunately, it is easy to combine multiple pieces of well structured data into something that fits a user’s desired end-use.<br />
<br />
However, sometimes it can be challenging to work out which of the many releases/recordings is the one that “most people will think of the most representative version”. Even defining what this means is incredibly difficult, but we’ve attempted to do just that and we’re using the results of this work in our production systems on ListenBrainz to map incoming listens to MusicBrainz entries. When looking at the descriptions our datasets, please consider that “canonical” implies the most representative version. Each of our canonical datasets has a more detailed description of what “canonical” means in that given dataset.<br />
<br />
Please note the that canonical nature of our canonical MBIDs is that we do not guarantee that they will be stable over time. What is considered to be Canonical in one data dump, may not be canonical in the next data dump. We don't expect this to happen very frequently, but the possibility for this to happen does exist.<br />
<br />
As with our database dumps, in order to keep the MetaBrainz Foundation operating so that these datasets can be maintained and updated further, we require financial support from our commercial users. Without this support, the future of the datasets cannot be guaranteed. As such, even when a specific dataset is available under the Creative Commons Zero (CC0) license (public domain), we still need [https://metabrainz.org/supporters/account-type commercial users of the data to support us], on a moral basis rather than a legal one! <br />
<br />
== Canonical Release Mapping ( canonical_release_redirect.csv ) ==<br />
<br />
For each Release Group in MusicBrainz (e.g. Miles Davis - Kind of Blue), this data-set identifies one Release which is Canonical for this Release Group. Given a Release Group, this data-set can easily give you the Release that is considered Canonical for this Release Group.<br />
<br />
'''Where to download''': [http://data.metabrainz.org/pub/musicbrainz/canonical_data/ Canonical Downloads<br/><br />
'''Updated''': 1st and 15 of each month<br/><br />
'''License''': [https://creativecommons.org/share-your-work/public-domain/cc0/ Creative Commons Zero (CC0)]<br/><br />
'''Columns''':<br />
release_mbid<br />
canonical_release_mbid<br />
release_group_mbid<br />
<br />
== Canonical Recording Mapping ( canonical_recording_redirect.csv ) ==<br />
<br />
For each recording in MusicBrainz, identify the most canonical version of that recording. This has the effect of redirecting all variations of a recording (single, EP, Live recordings, remasters) to a single recording, often the version that appears on the first Album where it was released.<br />
<br />
'''Where to download''': [http://data.metabrainz.org/pub/musicbrainz/canonical_data/ Canonical Downloads<br/><br />
'''Updated''': 1st and 15 of each month<br/><br />
'''License''': [https://creativecommons.org/share-your-work/public-domain/cc0/ Creative Commons Zero (CC0)]<br/><br />
'''Columns''':<br />
recording_mbid<br />
canonical_recording_mbid<br />
canonical_release_mbid<br />
<br />
== Canonical Metadata ( canonical_musicbrainz_data.csv ) ==<br />
<br />
A list of metadata that the canonical release and canonical recording mapping refer to. While this data-set does not provide any new features, we provide the data-set as a helper in order to quickly access the MusicBrainz data, without having to download the entire MusicBrainz database.<br />
<br />
This table serves as the basis for our ListenBrainz MBID mapper that takes incoming listen data that is comprised only of an Artist Name and a Track Name and attempts to work out which the canonical track in MusicBrainz is. The combined_lookup fields is particularly useful for creating such a mapping -- see the detailed column descriptions below.<br />
<br />
If you have a body of music metadata that needs to get matched to MusicBrainz, this table can be quite helpful! Using the combined_lookup field you can quickly implement a fuzzy metadata lookup for all of the data elements that you need to find MusicBrainz IDs for.<br />
<br />
'''Where to download''': [http://data.metabrainz.org/pub/musicbrainz/canonical_data/ Canonical Downloads<br/><br />
'''Updated''': 1st and 15 of each month<br/><br />
'''License''': [https://creativecommons.org/share-your-work/public-domain/cc0/ Creative Commons Zero (CC0)]<br/><br />
'''Columns''': <br />
id<br />
artist_credit_id<br />
artist_mbids<br />
artist_credit_name<br />
release_mbid<br />
release_name<br />
recording_mbid<br />
recording_name<br />
combined_lookup<br />
score<br />
year<br />
<br />
All fields except for the ones defined below, are common MusicBrainz fields, whose definition you can find in our [https://musicbrainz.org/doc/MusicBrainz_Database/Schema schema docs]. The remaining fields are:<br />
<br />
'''combined_lookup''': This is comprised of the artist_credit_name and recording_name, with punctuation, superfluous whitespace removed and any non-ASCII characters converted into ASCII (see https://pypi.org/project/Unidecode/ for more details on this). This field therefore contains all of the useful components of artist_credit and recording_name in a way that makes it easy to lookup tracks, especially if you have fuzzy search capabilities.</br><br />
'''score''': The score column indicates a priority order of all of the items. Some searching systems, such as Typesense, require its data to be ordered<br />
<br />
Using the combined_lookuo and score functions you can take this data and index it using [https://typesense.org/ Typesense] and then start making fuzzy lookup queries against this data to match your own data to MusicBrainz.</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Canonical_MusicBrainz_data&diff=76259Canonical MusicBrainz data2023-03-10T14:47:46Z<p>RobertKaye: </p>
<hr />
<div>We have created several datasets that use the term “canonical”. Since MusicBrainz aims to catalog all released music, the database contains a lot of different versions of releases or different versions of recordings. We find it important to collect all of these different versions, but in the end it is too much data for most of our users. Fortunately, it is easy to combine multiple pieces of well structured data into something that fits a user’s desired end-use.<br />
<br />
However, sometimes it can be challenging to work out which of the many releases/recordings is the one that “most people will think of the most representative version”. Even defining what this means is incredibly difficult, but we’ve attempted to do just that and we’re using the results of this work in our production systems on ListenBrainz to map incoming listens to MusicBrainz entries. When looking at the descriptions our datasets, please consider that “canonical” implies the most representative version. Each of our canonical datasets has a more detailed description of what “canonical” means in that given dataset. <br />
<br />
As with our database dumps, in order to keep the MetaBrainz Foundation operating so that these datasets can be maintained and updated further, we require financial support from our commercial users. Without this support, the future of the datasets cannot be guaranteed. As such, even when a specific dataset is available under the Creative Commons Zero (CC0) license (public domain), we still need [https://metabrainz.org/supporters/account-type commercial users of the data to support us], on a moral basis rather than a legal one! <br />
<br />
== Canonical Release Mapping ( canonical_release_redirect.csv ) ==<br />
<br />
For each Release Group in MusicBrainz (e.g. Miles Davis - Kind of Blue), this data-set identifies one Release which is Canonical for this Release Group. Given a Release Group, this data-set can easily give you the Release that is considered Canonical for this Release Group.<br />
<br />
'''Where to download''': [http://data.metabrainz.org/pub/musicbrainz/canonical_data/ Canonical Downloads<br/><br />
'''Updated''': 1st and 15 of each month<br/><br />
'''License''': [https://creativecommons.org/share-your-work/public-domain/cc0/ Creative Commons Zero (CC0)]<br/><br />
'''Columns''':<br />
release_mbid<br />
canonical_release_mbid<br />
release_group_mbid<br />
<br />
== Canonical Recording Mapping ( canonical_recording_redirect.csv ) ==<br />
<br />
For each recording in MusicBrainz, identify the most canonical version of that recording. This has the effect of redirecting all variations of a recording (single, EP, Live recordings, remasters) to a single recording, often the version that appears on the first Album where it was released.<br />
<br />
'''Where to download''': [http://data.metabrainz.org/pub/musicbrainz/canonical_data/ Canonical Downloads<br/><br />
'''Updated''': 1st and 15 of each month<br/><br />
'''License''': [https://creativecommons.org/share-your-work/public-domain/cc0/ Creative Commons Zero (CC0)]<br/><br />
'''Columns''':<br />
recording_mbid<br />
canonical_recording_mbid<br />
canonical_release_mbid<br />
<br />
== Canonical Metadata ( canonical_musicbrainz_data.csv ) ==<br />
<br />
A list of metadata that the canonical release and canonical recording mapping refer to. While this data-set does not provide any new features, we provide the data-set as a helper in order to quickly access the MusicBrainz data, without having to download the entire MusicBrainz database.<br />
<br />
This table serves as the basis for our ListenBrainz MBID mapper that takes incoming listen data that is comprised only of an Artist Name and a Track Name and attempts to work out which the canonical track in MusicBrainz is. The combined_lookup fields is particularly useful for creating such a mapping -- see the detailed column descriptions below.<br />
<br />
If you have a body of music metadata that needs to get matched to MusicBrainz, this table can be quite helpful! Using the combined_lookup field you can quickly implement a fuzzy metadata lookup for all of the data elements that you need to find MusicBrainz IDs for.<br />
<br />
'''Where to download''': [http://data.metabrainz.org/pub/musicbrainz/canonical_data/ Canonical Downloads<br/><br />
'''Updated''': 1st and 15 of each month<br/><br />
'''License''': [https://creativecommons.org/share-your-work/public-domain/cc0/ Creative Commons Zero (CC0)]<br/><br />
'''Columns''': <br />
id<br />
artist_credit_id<br />
artist_mbids<br />
artist_credit_name<br />
release_mbid<br />
release_name<br />
recording_mbid<br />
recording_name<br />
combined_lookup<br />
score<br />
year<br />
<br />
All fields except for the ones defined below, are common MusicBrainz fields, whose definition you can find in our [https://musicbrainz.org/doc/MusicBrainz_Database/Schema schema docs]. The remaining fields are:<br />
<br />
'''combined_lookup''': This is comprised of the artist_credit_name and recording_name, with punctuation, superfluous whitespace removed and any non-ASCII characters converted into ASCII (see https://pypi.org/project/Unidecode/ for more details on this). This field therefore contains all of the useful components of artist_credit and recording_name in a way that makes it easy to lookup tracks, especially if you have fuzzy search capabilities.</br><br />
'''score''': The score column indicates a priority order of all of the items. Some searching systems, such as Typesense, require its data to be ordered<br />
<br />
Using the combined_lookuo and score functions you can take this data and index it using [https://typesense.org/ Typesense] and then start making fuzzy lookup queries against this data to match your own data to MusicBrainz.</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Canonical_MusicBrainz_data&diff=76258Canonical MusicBrainz data2023-03-10T14:47:35Z<p>RobertKaye: </p>
<hr />
<div>We have created several datasets that use the term “canonical”. Since MusicBrainz aims to catalog all released music, the database contains a lot of different versions of releases or different versions of recordings. We find it important to collect all of these different versions, but in the end it is too much data for most of our users. Fortunately, it is easy to combine multiple pieces of well structured data into something that fits a user’s desired end-use.<br />
<br />
However, sometimes it can be challenging to work out which of the many releases/recordings is the one that “most people will think of the most representative version”. Even defining what this means is incredibly difficult, but we’ve attempted to do just that and we’re using the results of this work in our production systems on ListenBrainz to map incoming listens to MusicBrainz entries. When looking at the descriptions our datasets, please consider that “canonical” implies the most representative version. Each of our canonical datasets has a more detailed description of what “canonical” means in that given dataset. <br />
<br />
As with our database dumps, in order to keep the MetaBrainz Foundation operating so that these datasets can be maintained and updated further, we require financial support from our commercial users. Without this support, the future of the datasets cannot be guaranteed. As such, even when a specific dataset is available under the Creative Commons Zero (CC0) license (public domain), we still need [https://metabrainz.org/supporters/account-type commercial users of the data to support us], on a moral basis rather than a legal one! <br />
<br />
<br />
== Canonical Release Mapping ( canonical_release_redirect.csv ) ==<br />
<br />
For each Release Group in MusicBrainz (e.g. Miles Davis - Kind of Blue), this data-set identifies one Release which is Canonical for this Release Group. Given a Release Group, this data-set can easily give you the Release that is considered Canonical for this Release Group.<br />
<br />
'''Where to download''': [http://data.metabrainz.org/pub/musicbrainz/canonical_data/ Canonical Downloads<br/><br />
'''Updated''': 1st and 15 of each month<br/><br />
'''License''': [https://creativecommons.org/share-your-work/public-domain/cc0/ Creative Commons Zero (CC0)]<br/><br />
'''Columns''':<br />
release_mbid<br />
canonical_release_mbid<br />
release_group_mbid<br />
<br />
== Canonical Recording Mapping ( canonical_recording_redirect.csv ) ==<br />
<br />
For each recording in MusicBrainz, identify the most canonical version of that recording. This has the effect of redirecting all variations of a recording (single, EP, Live recordings, remasters) to a single recording, often the version that appears on the first Album where it was released.<br />
<br />
'''Where to download''': [http://data.metabrainz.org/pub/musicbrainz/canonical_data/ Canonical Downloads<br/><br />
'''Updated''': 1st and 15 of each month<br/><br />
'''License''': [https://creativecommons.org/share-your-work/public-domain/cc0/ Creative Commons Zero (CC0)]<br/><br />
'''Columns''':<br />
recording_mbid<br />
canonical_recording_mbid<br />
canonical_release_mbid<br />
<br />
== Canonical Metadata ( canonical_musicbrainz_data.csv ) ==<br />
<br />
A list of metadata that the canonical release and canonical recording mapping refer to. While this data-set does not provide any new features, we provide the data-set as a helper in order to quickly access the MusicBrainz data, without having to download the entire MusicBrainz database.<br />
<br />
This table serves as the basis for our ListenBrainz MBID mapper that takes incoming listen data that is comprised only of an Artist Name and a Track Name and attempts to work out which the canonical track in MusicBrainz is. The combined_lookup fields is particularly useful for creating such a mapping -- see the detailed column descriptions below.<br />
<br />
If you have a body of music metadata that needs to get matched to MusicBrainz, this table can be quite helpful! Using the combined_lookup field you can quickly implement a fuzzy metadata lookup for all of the data elements that you need to find MusicBrainz IDs for.<br />
<br />
'''Where to download''': [http://data.metabrainz.org/pub/musicbrainz/canonical_data/ Canonical Downloads<br/><br />
'''Updated''': 1st and 15 of each month<br/><br />
'''License''': [https://creativecommons.org/share-your-work/public-domain/cc0/ Creative Commons Zero (CC0)]<br/><br />
'''Columns''': <br />
id<br />
artist_credit_id<br />
artist_mbids<br />
artist_credit_name<br />
release_mbid<br />
release_name<br />
recording_mbid<br />
recording_name<br />
combined_lookup<br />
score<br />
year<br />
<br />
All fields except for the ones defined below, are common MusicBrainz fields, whose definition you can find in our [https://musicbrainz.org/doc/MusicBrainz_Database/Schema schema docs]. The remaining fields are:<br />
<br />
'''combined_lookup''': This is comprised of the artist_credit_name and recording_name, with punctuation, superfluous whitespace removed and any non-ASCII characters converted into ASCII (see https://pypi.org/project/Unidecode/ for more details on this). This field therefore contains all of the useful components of artist_credit and recording_name in a way that makes it easy to lookup tracks, especially if you have fuzzy search capabilities.</br><br />
'''score''': The score column indicates a priority order of all of the items. Some searching systems, such as Typesense, require its data to be ordered<br />
<br />
Using the combined_lookuo and score functions you can take this data and index it using [https://typesense.org/ Typesense] and then start making fuzzy lookup queries against this data to match your own data to MusicBrainz.</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Canonical_MusicBrainz_data&diff=76257Canonical MusicBrainz data2023-03-10T14:46:37Z<p>RobertKaye: </p>
<hr />
<div>We have created several datasets that use the term “canonical”. Since MusicBrainz aims to catalog all released music, the database contains a lot of different versions of releases or different versions of recordings. We find it important to collect all of these different versions, but in the end it is too much data for most of our users. Fortunately, it is easy to combine multiple pieces of well structured data into something that fits a user’s desired end-use.<br />
<br />
However, sometimes it can be challenging to work out which of the many releases/recordings is the one that “most people will think of the most representative version”. Even defining what this means is incredibly difficult, but we’ve attempted to do just that and we’re using the results of this work in our production systems on ListenBrainz to map incoming listens to MusicBrainz entries. When looking at the descriptions our datasets, please consider that “canonical” implies the most representative version. Each of our canonical datasets has a more detailed description of what “canonical” means in that given dataset. <br />
<br />
As with our database dumps, in order to keep the MetaBrainz Foundation operating so that these datasets can be maintained and updated further, we require financial support from our commercial users. Without this support, the future of the datasets cannot be guaranteed. As such, even when a specific dataset is available under the Creative Commons Zero (CC0) license (public domain), we still need [https://metabrainz.org/supporters/account-type commercial users of the data to support us], on a moral basis rather than a legal one! <br />
<br />
Our canonical data-sets include:<br />
<br />
=== Canonical Release Mapping ( canonical_release_redirect.csv )===<br />
<br />
For each Release Group in MusicBrainz (e.g. Miles Davis - Kind of Blue), this data-set identifies one Release which is Canonical for this Release Group. Given a Release Group, this data-set can easily give you the Release that is considered Canonical for this Release Group.<br />
<br />
'''Where to download''': [http://data.metabrainz.org/pub/musicbrainz/canonical_data/ Canonical Downloads<br/><br />
'''Updated''': 1st and 15 of each month<br/><br />
'''License''': [https://creativecommons.org/share-your-work/public-domain/cc0/ Creative Commons Zero (CC0)]<br/><br />
'''Columns''':<br />
release_mbid<br />
canonical_release_mbid<br />
release_group_mbid<br />
<br />
=== Canonical Recording Mapping ( canonical_recording_redirect.csv ) ===<br />
<br />
For each recording in MusicBrainz, identify the most canonical version of that recording. This has the effect of redirecting all variations of a recording (single, EP, Live recordings, remasters) to a single recording, often the version that appears on the first Album where it was released.<br />
<br />
'''Where to download''': [http://data.metabrainz.org/pub/musicbrainz/canonical_data/ Canonical Downloads<br/><br />
'''Updated''': 1st and 15 of each month<br/><br />
'''License''': [https://creativecommons.org/share-your-work/public-domain/cc0/ Creative Commons Zero (CC0)]<br/><br />
'''Columns''':<br />
recording_mbid<br />
canonical_recording_mbid<br />
canonical_release_mbid<br />
<br />
=== Canonical Metadata ( canonical_musicbrainz_data.csv ) ===<br />
<br />
A list of metadata that the canonical release and canonical recording mapping refer to. While this data-set does not provide any new features, we provide the data-set as a helper in order to quickly access the MusicBrainz data, without having to download the entire MusicBrainz database.<br />
<br />
This table serves as the basis for our ListenBrainz MBID mapper that takes incoming listen data that is comprised only of an Artist Name and a Track Name and attempts to work out which the canonical track in MusicBrainz is. The combined_lookup fields is particularly useful for creating such a mapping -- see the detailed column descriptions below.<br />
<br />
If you have a body of music metadata that needs to get matched to MusicBrainz, this table can be quite helpful! Using the combined_lookup field you can quickly implement a fuzzy metadata lookup for all of the data elements that you need to find MusicBrainz IDs for.<br />
<br />
'''Where to download''': [http://data.metabrainz.org/pub/musicbrainz/canonical_data/ Canonical Downloads<br/><br />
'''Updated''': 1st and 15 of each month<br/><br />
'''License''': [https://creativecommons.org/share-your-work/public-domain/cc0/ Creative Commons Zero (CC0)]<br/><br />
'''Columns''': <br />
id<br />
artist_credit_id<br />
artist_mbids<br />
artist_credit_name<br />
release_mbid<br />
release_name<br />
recording_mbid<br />
recording_name<br />
combined_lookup<br />
score<br />
year<br />
<br />
All fields except for the ones defined below, are common MusicBrainz fields, whose definition you can find in our [https://musicbrainz.org/doc/MusicBrainz_Database/Schema schema docs]. The remaining fields are:<br />
<br />
'''combined_lookup''': This is comprised of the artist_credit_name and recording_name, with punctuation, superfluous whitespace removed and any non-ASCII characters converted into ASCII (see https://pypi.org/project/Unidecode/ for more details on this). This field therefore contains all of the useful components of artist_credit and recording_name in a way that makes it easy to lookup tracks, especially if you have fuzzy search capabilities.</br><br />
'''score''': The score column indicates a priority order of all of the items. Some searching systems, such as Typesense, require its data to be ordered<br />
<br />
Using the combined_lookuo and score functions you can take this data and index it using [https://typesense.org/ Typesense] and then start making fuzzy lookup queries against this data to match your own data to MusicBrainz.</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Canonical_MusicBrainz_data&diff=76256Canonical MusicBrainz data2023-03-10T14:39:30Z<p>RobertKaye: </p>
<hr />
<div>We have created several datasets that use the term “canonical”. Since MusicBrainz aims to catalog all released music, the database contains a lot of different versions of releases or different versions of recordings. We find it important to collect all of these different versions, but in the end it is too much data for most of our users. Fortunately, it is easy to combine multiple pieces of well structured data into something that fits a user’s desired end-use.<br />
<br />
However, sometimes it can be challenging to work out which of the many releases/recordings is the one that “most people will think of the most representative version”. Even defining what this means is incredibly difficult, but we’ve attempted to do just that and we’re using the results of this work in our production systems on ListenBrainz to map incoming listens to MusicBrainz entries. When looking at the descriptions our datasets, please consider that “canonical” implies the most representative version. Each of our canonical datasets has a more detailed description of what “canonical” means in that given dataset. <br />
<br />
As with our database dumps, in order to keep the MetaBrainz Foundation operating so that these datasets can be maintained and updated further, we require financial support from our commercial users. Without this support, the future of the datasets cannot be guaranteed. As such, even when a specific dataset is available under the Creative Commons Zero (CC0) license (public domain), we still need [https://metabrainz.org/supporters/account-type commercial users of the data to support us], on a moral basis rather than a legal one! <br />
<br />
Our canonical data-sets include:<br />
<br />
=== Canonical Release Mapping ( canonical_release_redirect.csv )===<br />
<br />
For each Release Group in MusicBrainz (e.g. Miles Davis - Kind of Blue), this data-set identifies one Release which is Canonical for this Release Group. Given a Release Group, this data-set can easily give you the Release that is considered Canonical for this Release Group.<br />
<br />
Columns:<br />
release_mbid<br />
canonical_release_mbid<br />
release_group_mbid<br />
<br />
=== Canonical Recording Mapping ( canonical_recording_redirect.csv ) ===<br />
<br />
For each recording in MusicBrainz, identify the most canonical version of that recording. This has the effect of redirecting all variations of a recording (single, EP, Live recordings, remasters) to a single recording, often the version that appears on the first Album where it was released.<br />
<br />
Columns:<br />
recording_mbid<br />
canonical_recording_mbid<br />
canonical_release_mbid<br />
<br />
=== Canonical Metadata ( canonical_musicbrainz_data.csv ) ===<br />
<br />
A list of metadata that the canonical release and canonical recording mapping refer to. While this data-set does not provide any new features, we provide the data-set as a helper in order to quickly access the MusicBrainz data, without having to download the entire MusicBrainz database.<br />
<br />
This table serves as the basis for our ListenBrainz MBID mapper that takes incoming listen data that is comprised only of an Artist Name and a Track Name and attempts to work out which the canonical track in MusicBrainz is. The combined_lookup fields is particularly useful for creating such a mapping -- see the detailed column descriptions below.<br />
<br />
If you have a body of music metadata that needs to get matched to MusicBrainz, this table can be quite helpful! Using the combined_lookup field you can quickly implement a fuzzy metadata lookup for all of the data elements that you need to find MusicBrainz IDs for.<br />
<br />
Columns: <br />
id<br />
artist_credit_id<br />
artist_mbids<br />
artist_credit_name<br />
release_mbid<br />
release_name<br />
recording_mbid<br />
recording_name<br />
combined_lookup<br />
score<br />
year<br />
<br />
All fields except for the ones defined below, are common MusicBrainz fields, whose definition you can find in our [https://musicbrainz.org/doc/MusicBrainz_Database/Schema schema docs]. The remaining fields are:<br />
<br />
'''combined_lookup''': This is comprised of the artist_credit_name and recording_name, with punctuation, superfluous whitespace removed and any non-ASCII characters converted into ASCII (see https://pypi.org/project/Unidecode/ for more details on this). This field therefore contains all of the useful components of artist_credit and recording_name in a way that makes it easy to lookup tracks, especially if you have fuzzy search capabilities.</br><br />
'''score''': The score column indicates a priority order of all of the items. Some searching systems, such as Typesense, require its data to be ordered<br />
<br />
Using the combined_lookuo and score functions you can take this data and index it using [https://typesense.org/ Typesense] and then start making fuzzy lookup queries against this data to match your own data to MusicBrainz.</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Canonical_MusicBrainz_data&diff=76244Canonical MusicBrainz data2023-03-08T16:42:23Z<p>RobertKaye: </p>
<hr />
<div>We have created several datasets that use the term “canonical”. Since MusicBrainz aims to catalog all released music, the database contains a lot of different versions of releases or different versions of recordings. We find it important to collect all of these different versions, but in the end it is too much data for most of our users. Fortunately, it is easy to combine multiple pieces of well structured data into something that fits a user’s desired end-use.<br />
<br />
However, sometimes it can be challenging to work out which of the many releases/recordings is the one that “most people will think of the most representative version”. Even defining what this means is incredibly difficult, but we’ve attempted to do just that and we’re using the results of this work in our production systems on ListenBrainz to map incoming listens to MusicBrainz entries. When looking at the descriptions our datasets, please consider that “canonical” implies the most representative version. Each of our canonical datasets has a more detailed description of what “canonical” means in that given dataset. <br />
<br />
As with our database dumps, in order to keep the MetaBrainz Foundation operating so that these datasets can be maintained and updated further, we require financial support from our commercial users. Without this support, the future of the datasets cannot be guaranteed. As such, even when a specific dataset is available under the Creative Commons Zero (CC0) license (public domain), we still need commercial users of the data to support us, on a moral basis rather than a legal one! <br />
<br />
Our canonical data-sets include:<br />
<br />
=== Canonical Release Mapping ( canonical_release_redirect.csv )===<br />
<br />
For each Release Group in MusicBrainz (e.g. Miles Davis - Kind of Blue), this data-set identifies one Release which is Canonical for this Release Group. Given a Release Group, this data-set can easily give you the Release that is considered Canonical for this Release Group.<br />
<br />
Columns:<br />
release_mbid<br />
canonical_release_mbid<br />
release_group_mbid<br />
<br />
<br />
=== Canonical Recording Mapping ( canonical_recording_redirect.csv ) ===<br />
<br />
For each recording in MusicBrainz, identify the most canonical version of that recording. This has the effect of redirecting all variations of a recording (single, EP, Live recordings, remasters) to a single recording, often the version that appears on the first Album where it was released.<br />
<br />
Columns:<br />
recording_mbid<br />
canonical_recording_mbid<br />
canonical_release_mbid<br />
<br />
<br />
=== Canonical Metadata ( canonical_musicbrainz_data.csv ) ===<br />
<br />
A list of metadata that the canonical release and canonical recording mapping refer to. While this data-set does not provide any new features, we provide the data-set as a helper in order to quickly access the MusicBrainz data, without having to download the entire MusicBrainz database.<br />
<br />
This table serves as the basis for our ListenBrainz MBID mapper that takes incoming listen data that is comprised only of an Artist Name and a Track Name and attempts to work out which the canonical track in MusicBrainz is. The combined_lookup fields is particularly useful for creating such a mapping -- see the detailed column descriptions below.<br />
<br />
If you have a body of music metadata that needs to get matched to MusicBrainz, this table can be quite helpful! Using the combined_lookup field you can quickly implement a fuzzy metadata lookup for all of the data elements that you need to find MusicBrainz IDs for.<br />
<br />
Columns: <br />
id<br />
artist_credit_id<br />
artist_mbids<br />
artist_credit_name<br />
release_mbid<br />
release_name<br />
recording_mbid<br />
recording_name<br />
combined_lookup<br />
score<br />
year<br />
<br />
All fields except for the ones defined below, are common MusicBrainz fields, whose definition you can find in our [https://musicbrainz.org/doc/MusicBrainz_Database/Schema schema docs]. The remaining fields are:<br />
<br />
'''combined_lookup''': This is comprised of the artist_credit_name and recording_name, with punctuation, superfluous whitespace removed and any non-ASCII characters converted into ASCII (see https://pypi.org/project/Unidecode/ for more details on this). This field therefore contains all of the useful components of artist_credit and recording_name in a way that makes it easy to lookup tracks, especially if you have fuzzy search capabilities.</br><br />
'''score''': The score column indicates a priority order of all of the items. Some searching systems, such as Typesense, require its data to be ordered<br />
<br />
Using the combined_lookuo and score functions you can take this data and index it using Typesense and then start making fuzzy lookup queries against this data to match your own data to MusicBrainz.</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Canonical_MusicBrainz_data&diff=76243Canonical MusicBrainz data2023-03-08T16:41:22Z<p>RobertKaye: </p>
<hr />
<div>We have created several datasets that use the term “canonical”. Since MusicBrainz aims to catalog all released music, the database contains a lot of different versions of releases or different versions of recordings. We find it important to collect all of these different versions, but in the end it is too much data for most of our users. Fortunately, it is easy to combine multiple pieces of well structured data into something that fits a user’s desired end-use.<br />
<br />
However, sometimes it can be challenging to work out which of the many releases/recordings is the one that “most people will think of the most representative version”. Even defining what this means is incredibly difficult, but we’ve attempted to do just that and we’re using the results of this work in our production systems on ListenBrainz to map incoming listens to MusicBrainz entries. When looking at the descriptions our datasets, please consider that “canonical” implies the most representative version. Each of our canonical datasets has a more detailed description of what “canonical” means in that given dataset. <br />
<br />
As with our database dumps, in order to keep the MetaBrainz Foundation operating so that these datasets can be maintained and updated further, we require financial support from our commercial users. Without this support, the future of the datasets cannot be guaranteed. As such, even when a specific dataset is available under the Creative Commons Zero (CC0) license (public domain), we still need commercial users of the data to support us, on a moral basis rather than a legal one! <br />
<br />
Our canonical data-sets include:<br />
<br />
=== Canonical Release Mapping ( canonical_release_redirect.csv )===<br />
<br />
For each Release Group in MusicBrainz (e.g. Miles Davis - Kind of Blue), this data-set identifies one Release which is Canonical for this Release Group. Given a Release Group, this data-set can easily give you the Release that is considered Canonical for this Release Group.<br />
<br />
Columns:<br />
release_mbid<br />
canonical_release_mbid<br />
release_group_mbid<br />
<br />
<br />
=== Canonical Recording Mapping ( canonical_recording_redirect.csv ) ===<br />
<br />
For each recording in MusicBrainz, identify the most canonical version of that recording. This has the effect of redirecting all variations of a recording (single, EP, Live recordings, remasters) to a single recording, often the version that appears on the first Album where it was released.<br />
<br />
Columns:<br />
recording_mbid<br />
canonical_recording_mbid<br />
canonical_release_mbid<br />
<br />
<br />
=== Canonical Metadata ( canonical_musicbrainz_data.csv ) ===<br />
<br />
A list of metadata that the canonical release and canonical recording mapping refer to. While this data-set does not provide any new features, we provide the data-set as a helper in order to quickly access the MusicBrainz data, without having to download the entire MusicBrainz database.<br />
<br />
This table serves as the basis for our ListenBrainz MBID mapper that takes incoming listen data that is comprised only of an Artist Name and a Track Name and attempts to work out which the canonical track in MusicBrainz is. The combined_lookup fields is particularly useful for creating such a mapping -- see the detailed column descriptions below.<br />
<br />
If you have a body of music metadata that needs to get matched to MusicBrainz, this table can be quite helpful! Using the combined_lookup field you can quickly implement a fuzzy metadata lookup for all of the data elements that you need to find MusicBrainz IDs for.<br />
<br />
Columns: <br />
id<br />
artist_credit_id<br />
artist_mbids<br />
artist_credit_name<br />
release_mbid<br />
release_name<br />
recording_mbid<br />
recording_name<br />
combined_lookup<br />
score<br />
year<br />
<br />
All fields except for the ones defined below, are common MusicBrainz fields, whose definition you can find in our [https://musicbrainz.org/doc/MusicBrainz_Database/Schema schema docs]. The remaining fields are:<br />
<br />
combined_lookup: This is comprised of the artist_credit_name and recording_name, with punctuation, superfluous whitespace removed and any non-ASCII characters converted into ASCII (see https://pypi.org/project/Unidecode/ for more details on this). This field therefore contains all of the useful components of artist_credit and recording_name in a way that makes it easy to lookup tracks, especially if you have fuzzy search capabilities.<br />
score: The score column indicates a priority order of all of the items. Some searching systems, such as Typesense, require its data to be ordered<br />
<br />
Using the combined_lookuo and score functions you can take this data and index it using Typesense and then start making fuzzy lookup queries against this data to match your own data to MusicBrainz.</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Canonical_MusicBrainz_data&diff=76242Canonical MusicBrainz data2023-03-08T16:31:55Z<p>RobertKaye: </p>
<hr />
<div>We have created several datasets that use the term “canonical”. Since MusicBrainz aims to catalog all released music, the database contains a lot of different versions of releases or different versions of recordings. We find it important to collect all of these different versions, but in the end it is too much data for most of our users. Fortunately, it is easy to combine multiple pieces of well structured data into something that fits a user’s desired end-use.<br />
<br />
However, sometimes it can be challenging to work out which of the many releases/recordings is the one that “most people will think of the most representative version”. Even defining what this means is incredibly difficult, but we’ve attempted to do just that and we’re using the results of this work in our production systems on ListenBrainz to map incoming listens to MusicBrainz entries. When looking at the descriptions our datasets, please consider that “canonical” implies the most representative version. Each of our canonical datasets has a more detailed description of what “canonical” means in that given dataset. <br />
<br />
As with our database dumps, in order to keep the MetaBrainz Foundation operating so that these datasets can be maintained and updated further, we require financial support from our commercial users. Without this support, the future of the datasets cannot be guaranteed. As such, even when a specific dataset is available under the Creative Commons Zero (CC0) license (public domain), we still need commercial users of the data to support us, on a moral basis rather than a legal one! <br />
<br />
Our canonical data-sets include:<br />
<br />
=== Canonical Release Mapping ( canonical_release_redirect.csv )===<br />
<br />
For each Release Group in MusicBrainz (e.g. Miles Davis - Kind of Blue), this data-set identifies one Release which is Canonical for this Release Group. Given a Release Group, this data-set can easily give you the Release that is considered Canonical for this Release Group.<br />
<br />
Columns:<br />
release_mbid<br />
canonical_release_mbid<br />
release_group_mbid<br />
<br />
=== Canonical Recording Mapping ( canonical_recording_redirect.csv ) ===<br />
<br />
For each recording in MusicBrainz, identify the most canonical version of that recording.<br />
This has the effect of redirecting all variations of a recording (single, EP, Live recordings, remasters) to a single recording, often the version that appears on the first Album where it was released.<br />
<br />
Columns:<br />
recording_mbid<br />
canonical_recording_mbid<br />
canonical_release_mbid<br />
<br />
=== Canonical Metadata ( canonical_musicbrainz_data.csv ) ===<br />
<br />
A list of metadata used to create the two canonical mappings.<br />
<br />
Columns: <br />
id<br />
artist_credit_id<br />
artist_mbids<br />
artist_credit_name<br />
release_mbid<br />
release_name<br />
recording_mbid<br />
recording_name<br />
combined_lookup<br />
score<br />
year<br />
<br />
All fields except for the ones defined below, are common MusicBrainz fields, whose definition you can find in our schema docs. The remaining fields are:<br />
<br />
* combined_lookup: This is comprised of the artist_credit_name and recording_name, with punctuation, superfluous whitespace removed and any non-ASCII characters converted into ASCII (see https://pypi.org/project/Unidecode/ for more details on this). This field therefore contains all of the useful components of artist_credit and recording_name in a way that makes it easy to lookup tracks, especially if you have fuzzy search capabilities.<br />
* score: The score column indicates a priority order of all of the items. Some searching systems, such as typesense, require its data to be ordered</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Canonical_MusicBrainz_data&diff=76241Canonical MusicBrainz data2023-03-08T16:17:02Z<p>RobertKaye: Created page with "We have created several datasets that use the term “canonical”. Since MusicBrainz aims to catalog all released music, the database contains a lot of different versions of..."</p>
<hr />
<div>We have created several datasets that use the term “canonical”. Since MusicBrainz aims to catalog all released music, the database contains a lot of different versions of releases or different versions of recordings. We find it important to collect all of these different versions, but in the end it is too much data for most of our users. Fortunately, it is easy to combine multiple pieces of well structured data into something that fits a user’s desired end-use.<br />
<br />
However, sometimes it can be challenging to work out which of the many releases/recordings is the one that “most people will think of the most representative version”. Even defining what this means is incredibly difficult, but we’ve attempted to do just that and we’re using the results of this work in our production systems on ListenBrainz to map incoming listens to MusicBrainz entries. When looking at the descriptions our datasets, please consider that “canonical” implies the most representative version. Each of our canonical datasets has a more detailed description of what “canonical” means in that given dataset. <br />
<br />
As with our database dumps, in order to keep the MetaBrainz Foundation operating so that these datasets can be maintained and updated further, we require financial support from our commercial users. Without this support, the future of the datasets cannot be guaranteed. As such, even when a specific dataset is available under the Creative Commons Zero (CC0) license (public domain), we still need commercial users of the data to support us, on a moral basis rather than a legal one! <br />
<br />
Our canonical data-sets include:<br />
<br />
=== Canonical Release Mapping ===<br />
<br />
For each Release Group in MusicBrainz (e.g. Miles Davis - Kind of Blue), this data-set identifies one Release which is Canonical for this Release Group. Given a Release Group, this data-set can easily give you the Release that is considered Canonical for this Release Group.<br />
<br />
==== Dump format ====<br />
<br />
File: canonical_release_redirect.csv<br />
Format: CSV<br />
Columns: release_mbid, canonical_release_mbid, release_group_mbid<br />
<br />
=== Canonical Recording Mapping ===<br />
<br />
For each recording in MusicBrainz, identify the most canonical version of that recording.<br />
This has the effect of redirecting all variations of a recording (single, EP, Live recordings, remasters) to a single recording, often the version that appears on the first Album where it was released.<br />
<br />
==== Dump format ====<br />
<br />
File: canonical_recording_redirect.csv)<br />
Format: CSV<br />
Columns: recording_mbid,canonical_recording_mbid,canonical_release_mbid<br />
<br />
<br />
=== Canonical Metadata ===<br />
<br />
A list of metadata used to create the two canonical mappings.<br />
<br />
==== Dump format ====<br />
<br />
File: canonical_musicbrainz_data.csv<br />
Format: CSV<br />
Columns: id,artist_credit_id,artist_mbids,artist_credit_name,release_mbid,release_name,recording_mbid,recording_name,combined_lookup,score,year<br />
<br />
All fields except for the ones defined below, are common MusicBrainz fields, whose definition you can find in our schema docs. The remaining fields are:<br />
<br />
* combined_lookup: This is comprised of the artist_credit_name and recording_name, with punctuation, superfluous whitespace removed and any non-ASCII characters converted into ASCII (see https://pypi.org/project/Unidecode/ for more details on this). This field therefore contains all of the useful components of artist_credit and recording_name in a way that makes it easy to lookup tracks, especially if you have fuzzy search capabilities.<br />
* score: The score column indicates a priority order of all of the items. Some searching systems, such as typesense, require its data to be ordered</div>RobertKayehttps://wiki.musicbrainz.org/index.php?title=Development/Summer_of_Code/2023/ListenBrainz&diff=76240Development/Summer of Code/2023/ListenBrainz2023-03-08T11:22:33Z<p>RobertKaye: </p>
<hr />
<div>ListenBrainz allows users to store a list of songs that they listen to and get personalised recommendations. Read more information on [https://listenbrainz.org its homepage].<br />
<br />
== Getting started ==<br />
(see also: [[Development/Summer_of_Code/Getting_started|Getting started with GSoC]])<br />
<br />
If you want to work on ListenBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some things that we might ask you about<br />
* Show that you understand the goals that ListenBrainz wants to achieve, [[:lb:about/|which are written on its homepage]]<br />
* [https://listenbrainz.readthedocs.io/en/latest/developers/devel-env.html#register-a-musicbrainz-application Create an oauth application on the MusicBrainz website] and add the configuration information to your ListenBrainz server. Use this to log in to your server with your MusicBrainz details<br />
* Use the [https://listenbrainz.readthedocs.io/en/latest/users/api-usage.html#submitting-listens import script] that is part of the ListenBrainz server to load scrobbles from last.fm to your ListenBrainz server, or the main ListenBrainz server<br />
* Use your preferred programming language to write a submission tool that can send Listen data to your local ListenBrainz server. You could make up some fake data for song names and artists. This data doesn't have to be real.<br />
* Try and delete the ListenBrainz database on your local server to remove the fake data that you added.<br />
* Look at the [https://tickets.metabrainz.org/browse/LB-1211?jql=project%20%3D%20LB%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20%3D%20good-first-bug%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC list of tickets] that we have open for ListenBrainz and see if you understand what tasks the tickets involve<br />
* If you want to, see if you can contribute to fixing a ticket. Either add a comment to the ticket or ask in IRC for clarification if you don't understand what the ticket means<br />
<br />
We're adding a number of new social features to ListenBrainz that we hope will enable people discover more music they like and users who have similar music tastes to their own. We're working on some of these features now, but we will need to get help for other features:<br />
<br />
<br />
=== UI/UX improvements to our Fresh Releases page ===<br />
<br />
Proposed mentors: ''mayhem''<br><br />
Languages/skills: React<br><br />
Estimated Project Length: 175 hours, possible 350<br><br />
Expected outcomes: A set of PRs that improve the UI/UX of our Fresh Releases page, ready to be released into production.<br />
<br />
Last summer we had a student implement our [https://listenbrainz.org/explore/fresh-releases Fresh Releases] page that shows what releases have been recently added to MusicBrainz. Intended as a music discovery tool, this page allows all users to browse new releases and people who have submitted listens to ListenBrainz can have a customized page that shows Fresh Releases relevant to their past listening history. We find that the page is rather quite interesting, but our student wasn't able to really get the UI/UX into a state where we are happy with it. Our UI/UX designer has worked out what the improved Fresh Releases UI should look like and now we are looking for a student to implement these UI improvements. We anticipate that this is a 100% javascript/react project with a focus on creating a slick and smooth UI for this rather interesting page.<br />
<br />
=== Dataset Hoster Improvements ===<br />
<br />
Proposed mentors: ''mayhem''<br><br />
Languages/skills: Python, Flask, Postgres. Potentially React.<br><br />
Estimated Project Length: 175 hours<br><br />
Expected outcomes: A set of PRs that improve the dataset hoster, ready to be released into production.<br />
<br />
Our [https://github.com/metabrainz/data-set-hoster Data Set Hoster] is a super fast way to get the results of an SQL query or other data sets online for people to explore. Our [https://labs.api.listenbrainz.org/ ListenBrainz Labs API] page uses this software to make a few data sets available to the public. There are two layers to this project: Both the web interface as well as a JSON based API. The dataset hoster is literally the fasted way to make a new data endpoint!<br />
<br />
Originally the dataset hoster returned rows of (usually) database rows with no extra information; but over time the results returned from a query have become more complex to also include returning markup in order to display more information to the user. The data structure that is currently being returned by the data set hoster could be simplified a bit to make the data easier to consume for callers. The project also has a set of bugs that we've not gotten around to addressing, which need fixing.<br />
<br />
Finally, we wish to have some new features added to the hoster:<br />
<br />
* When an MBID is recognized in a cell of the output, we wish to show a drop-down button next to that MBID. The items of this drop-down should be a link to all of the data-sets that could be initiated with that MBID. For instance, if the user has made a search for a similar artist and the output shows a list of artists, next to each artist MBID, the downdown should offer to run a new similar artist search and other searches that can be initiated with an artist MBID. These drop-downs would allow users to explore our connected datasets, which would be a great asset.<br />
* Add queries for all MusicBrainz entities, so that MBIDs can be quickly looked up from textual input.<br />
<br />
If you are interested in this project, come to the #metabrainz IRC channel and chat with ''mayhem'' or ''lucifer'' and we'll help you get started.<br />
<br />
=== Interactive Artist Similarity Graph ===<br />
<br />
Proposed mentors: ''mayhem''<br><br />
Languages/skills: Python, React, D3<br><br />
Estimated Project Length: 350 hours<br><br />
Expected outcomes: A set of PRs that improve implement an artist similarity graph, ready to be released into production.<br />
<br />
The ListenBrainz project has a number of music exploration tools (see the explore menu on listenbrainz.org) and we would like to add another exploration page: Interactive Artist Similarity Graph. In this exploration page, the user should first be presented with a search box that allows them to search for and select an artist. Once the artist is selected, the page should query the artist-similarity API endpoint for similar artists to this artist. This data contains all of the data necessary to populate the graph: MBIDs, name and the strength of the relationship between the two artists. The page should then render a graph of similar artists -- [https://medium.com/ninjaconcept/interactive-dynamic-force-directed-graphs-with-d3-da720c6d7811 this D3 tutorial] cover the basic steps that needed to implement this feature. Once the graph is rendered, the user can click on different artist nodes in the graph, to focus on the artist neighbors for the selected artist. The user should be able to "walk" through graph space to explore similar artists. For each node in the graph, there needs to be a way to show a drop-down menu where the user can selected one of the following options:<br />
<br />
* Show this artist in MusicBrainz.<br />
* Play this artist's most popular album.<br />
* Play this artist's most popular recordings.<br />
<br />
If you are interested in this project, please make contact with ''mayhem'' on IRC in the #metabrainz channel. At first we would like you to produce a mock-up of what this feature could look like -- once this mock-up is done, we can have you work with our resident UI/UX expert to improve the mock-up to function well and integrate well into our sites.<br />
<br />
You'll need to implement the explore page and instantiate the BrainzPlayer on the page, which allows the page to actually play the music for the selected artists. You will not be required to implement any of the drop-down features -- those all exist already and only need to be connected to this new explore page.<br />
<br />
=== Music Recommendation: Implement a new Troi patch for generating music recommendations ===<br />
<br />
Proposed mentors: ''mayhem''<br><br />
Languages/skills: Python, possibly Postgres, possibly Javascript/React<br><br />
Estimated Project Length: 175 or 250 hours, depending on the scope that is suggested.<br><br />
Expected outcomes: One or more finished, debugged and tested plugins for Troi.<br />
<br />
Our [https://github.com/metabrainz/troi-recommendation-playground troi recommendation toolkit] is our playground for developing recommendation algorithms. The toolkit already knows how to fetch data from ListenBrainz for stats, collaborative filtered recommended tracks, similar artists and similar recordings. From MusicBrainz it can fetch needed metadata such as genres and tags. The exact goal for this project really depends on you and what ideas you bring to the table, but the idea is to create a new Patch (plugin) for Troi that creates a new type of playlist that we can periodically offer to our users.<br />
<br />
If this sounds interesting to you, we strongly recommend that you turn up in our IRC channel and chat with at ''mayhem'' or ''lucifer'' about your idea before you go into a full proposal. Music recommendations can seem exciting and fun, but the details of how to make them happen and all the things that need to be considered is a significant challenge.<br />
<br />
=== '''Feed Section in Android App''' ===<br />
Proposed mentors: ''akshaaatt''<br />
<br />
Languages/skills: Android, Kotlin, Jetpack Libraries, Retrofit, Dagger-Hilt<br />
<br />
[[discourse:c/metabrainz|Forum for discussion]]<br />
<br />
[https://docs.google.com/document/d/1hY5oloIiANeXg1R9oSBIr2ZUHSlm7LU8qy6tW1VJMQg/edit?usp=sharing Document for a broader overview of the app]<br />
<br />
Estimated Project Length: 350 hours<br />
<br />
Difficulty: medium<br />
<br />
The users should be able to follow users and be able to access the feed in the Home page of the app. Whenever someone they follow listens to a track, recommends a track in general or to them personally, follows another user or a user follows them, pins a track, reviews an album, reviews a track, or ListenBrainz has new announcements, the feed should showcase it. Track related feed should allow the user to play the song via remote players on the app, or be able to search for that track locally and play it. Lazy loading should be used to populate the feed so that we can have infinite scrolling instead of pagination but the feed should be loaded in batches of 20. Given that we need to follow users first to populate the feed, the follow-following should be supported with this project in the app.<br />
<br />
Available APIs can be found [https://listenbrainz.readthedocs.io/en/latest/users/api/social.html here]. The [[:lb:feed/|website]] should be looked for inspiration for this feature.<br />
<br />
A prospective student thinking about this should definitely approach us on [[Communication/IRC|IRC]] and talk with us about what they have in mind and if there's anything we can discuss regarding the implementation.<br />
===CritiqueBrainz Reviews in Android App===<br />
Proposed mentors: ''akshaaatt''<br />
<br />
Languages/skills: Android, Kotlin, Jetpack Libraries, Retrofit, Dagger-Hilt<br />
<br />
[[discourse:c/metabrainz|Forum for discussion]]<br />
<br />
Estimated Project Length: 175 hours<br />
<br />
Difficulty: medium<br />
<br />
The Listens' card should have an option to allow the user to submit a review of the track/album that have listened to. This requires the developer to first move the Listens section along with the BrainzPlayer section in a separate tab, where the Listens' section is the default when the user opens the Player. The [[:lb:user/akshaaatt/|website]] should be looked for inspiration for this feature. Tracks should allow the user to play the song via remote players on the app, or be able to search for that track locally and play it. Lazy loading should be used to populate the list so that we can have infinite scrolling instead of pagination but the list should be loaded in batches of 20.<br />
<br />
A prospective student thinking about this should definitely approach us on [[Communication/IRC|IRC]] and talk with us about what they have in mind and if there's anything ng we can discuss regarding the implementation.<br />
===Listens Submitter in Android App===<br />
Proposed mentors: ''akshaaatt''<br />
<br />
Languages/skills: Android, Kotlin, Jetpack Libraries, Retrofit, Dagger-Hilt<br />
<br />
[[discourse:c/metabrainz|Forum for discussion]]<br />
<br />
Estimated Project Length: 175 hours<br />
<br />
Difficulty: medium<br />
<br />
The Listens submitted to ListenBrainz from the app need to be refined first before sending them in order to avoid spamming the user's listens with unrelated videos from YouTube for example. A page showcasing the listens from the app need to be presented in the UI for the first 30 minutes, such that the user can cancel those which they think shouldn't be submitted.<br />
<br />
A prospective student thinking about this should approach us on [[Communication/IRC|IRC]] and talk with us about what they have in mind and if there's anything we can discuss regarding the implementation.<br />
<br />
=== Integrate music streaming from Funkwhale Pods ===<br />
<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask, Typescript/React<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A new music service integration for users to play and record listens on ListenBrainz.<br />
<br />
LB has a number of music discovery features that use BrainzPlayer to facilitate track playback. BrainzPlayer (BP) is a custom React component in LB that uses multiple data sources to search and play a track. As of now, it supports Spotify, Youtube and Soundcloud as a music service. LB would like to be able to stream music from a private [Funkwhale pod https://funkwhale.audio/pod] and to do that the following major tasks need to be completed. 1) Add Funkwhale as a service to our music services backend; this will require some schema changes/extensions in order to have user specify the URL of their pod as part of the music service configuration. 2) Add the react based front-end UI to that allows users to setup their own Funkwhale pods as a service. 3) Add support to BrainzPlayer for logging into the Funkwhale OAuth API and streaming music from it.<br />
<br />
=== Integrate music streaming from Navidrome ===<br />
<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask, Typescript/React<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A new music service integration for users to play and record listens on ListenBrainz.<br />
<br />
LB has a number of music discovery features that use BrainzPlayer to facilitate track playback. BrainzPlayer (BP) is a custom React component in LB that uses multiple data sources to search and play a track. As of now, it supports Spotify, Youtube and Soundcloud as a music service. LB would like to be able to stream music from a private [https://www.navidrome.org/ Navidrome instance] and to do that the following major tasks need to be completed. 1) Add Navidrome as a service to our music services backend; this will require some schema changes/extensions in order to have user specify the URL of their pod as part of the music service configuration. 2) Add the react based front-end UI to that allows users to setup their own Navidrome instance as a service. 3) Add support to BrainzPlayer for logging into the Navidrom streaming API and playing music from it.<br />
<br />
=== Integrate Deezer music streaming service for recording listens and playing music ===<br />
<br />
Proposed mentors: ''lucifer''<br><br />
Languages/skills: Python/Flask, Typescript/React<br><br />
Estimated Project Length: Can be 175 or 350 hours depending on the integration/service chosen.<br><br />
Difficulty: Easy<br><br />
Expected Outcomes: A new music service integration for users to play and record listens on ListenBrainz.<br />
<br />
LB has a number of music discovery features that use BrainzPlayer to facilitate track playback. BrainzPlayer (BP) is a custom React component in LB that uses multiple data sources to search and play a track. As of now, it supports Spotify, Youtube and Soundcloud as a music service. LB also supports linking a Spotify account to record listening history. We have looked into some other services and found that Deezer provides the music playback and recording listening history capability. Integrating these services into LB would make for a good SoC project.</div>RobertKaye