New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publication of jams2 #45
Comments
this might come as a surprise, but... 👍 Do I hear a "pump up the jams" comeback?! |
+1 for doing this as an ismir late breaking paper. I think as @bmcfee said that the point of the paper is for publicity, and all it needs is a summary pointing back to a much longer more detailed document on the web somewhere. ALSO YES TO PUMP UP THE JAMS |
(btw, I think this goes without saying, but this is clearly a @bmcfee first author yaaa?) |
YES TO ALL :))) On Fri, Jun 26, 2015 at 11:17 AM, Rachel Bittner notifications@github.com
|
+∞ On Fri, Jun 26, 2015 at 11:18 AM, Oriol Nieto notifications@github.com
|
@bmcfee looks like it's all good to go chief. Latex / git / yada yada when you have time yada yada |
Created https://github.com/marl/jams-paper for these guys. Will probably not get around to populating it until august. Closing out this issue now. |
@justinsalamon has repeatedly kicked around the idea of writing a paper to document the changes in jams over the last year. I think this is probably a good idea, if only for publicity.
As for venues, the next obvious one is ismir2015 late breaking session (deadline: 2015-10-26). This would be an extended abstract (2 pages), which clearly doesn't suffice to document all the restructuring.
It would be nice to have a longer document as well, either a tech report or an arxiv preprint, which the late breaking session abstract can refer back to for more details. This means we'd have to crank out the paper by october, which should be plenty doable.
Who's in?
The text was updated successfully, but these errors were encountered: