Git Product home page Git Product logo

ismir_web's People

Contributors

ehumphrey85 avatar ejhumphrey avatar fzalkow avatar meinardmueller avatar ybayle avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ismir_web's Issues

Update new board members

President: Fabien Gouyon
President-elect: Emilia Gomez
Secretary: Eric Humphrey
Treasurer: Xiao Hu
Members at large: Amélie Anglade, Meinard Mueller and Geoffroy Peeters
Student member: Andy Sarroff

Link to github

Hello,

I think it would be nice to include an explicit link to the github repository at the ismir website, in the resource page http://ismir.net/resources.php

It is specially useful to locate paper templates, contribute to the ismir web site, etc

Now it is under 'corrections' but it is not clear that we can find there paper templates for instance.

emilia

[RFC] On the use of web technologies, toward a CONTRIBUTING.md

note: for context, this is partly inspired by #24 and #27. It's probably time this conversation was rebooted.

When the idea of bringing the website into the 21st century was raised at ISMIR2013, the general consensus (at the time, at least) was to keep it as simple as possible for three key reasons:

  1. Technological maintenance and portability: By sticking to widely adopted technologies, we wouldn't have to chase upgrades or accidentally tie ourselves to abandonware. This happened to the database that had been in use, but was no longer maintained and couldn't be installed on a modern server.
  2. Easy for web novices to update and maintain: Maintenance of the ISMIR website(s) has fallen to the board, an elected group of former or present academics. This has traditionally placed a strong requirement that whatever technologies used in the website are as simple as possible.
  3. Hosting cost and performance: The ISMIR society buys time on a single (shared) VM to host the website. Our traffic is (currently) minimal, but a static website would help guarantee speedy load times.

This is what motivated the initial HTML / CSS website, and for similar reasons, the introduction of PHP concerns me somewhat (but I digress). This is to say, I am skeptical of the value added by, say, JavaScript relative to the maintenance cost it could introduce and potential uncertainty around its lifecycle. This is likely to be an important consideration as long as the website is maintained by the society's board.

That said, I do not feel as worried about web services, since they tend to be somewhat interchangeable, especially if the website's implementation is not too complex. This is especially true where cost is involved, such as:

  • Using Zenodo to host both papers and proceedings, which also provides the benefit of a DOI and clean citation metadata.
  • Using GitHub Pages to host both the website and the proceedings subdomains, which has the added feature (to me, at least) of enforcing a static website.

If either were to go away or change their business model, it would be straightforward to re-establish the website on ISMIR-managed hosting.

I'm curious if those who've contributed code or conversation to the site in the past (@ybayle, @woodshop, @stefanbalke, @meinardmueller) wanted to weigh in on these things? It seems like the only real long-term solution for a maintainable website is one in which the community contributes to the site, and that would really warrant a CONTRIBUTING.md guideline.

Missing Chiariglione02

Totally AWOL

@inproceedings{DBLP:conf/ismir/Chiariglione02,
  author    = {Leonardo Chiariglione},
  title     = {Technology and Art - Putting Things in Context},
  booktitle = {{ISMIR} 2002, 3rd International Conference on Music Information Retrieval,
               Paris, France, October 13-17, 2002, Proceedings},
  year      = {2002},
  url       = {http://ismir2002.ismir.net/Proceedings/02-FP08-1.pdf},
  timestamp = {Wed, 01 Mar 2006 15:23:23 +0100},
  biburl    = {http://dblp.uni-trier.de/rec/bib/conf/ismir/Chiariglione02},
  bibsource = {dblp computer science bibliography, http://dblp.org}
}

http://dblp.uni-trier.de/rec/bibtex/conf/ismir/Chiariglione02

membership details

it's come up that the website doesn't state membership cost ($10USD), and I'm wondering if there's other info / details that could be added in the same PR while we're at it.

BellBGB05

PDF stalls, and cannot find elsewhere.

citation:

@inproceedings{DBLP:conf/ismir/BellBGB05,
  author    = {Tim Bell and
               David Blizzard and
               Richard D. Green and
               David Bainbridge},
  title     = {Design of a Digital Music Stand},
  booktitle = {{ISMIR} 2005, 6th International Conference on Music Information Retrieval,
               London, UK, 11-15 September 2005, Proceedings},
  pages     = {430--433},
  year      = {2005},
  url       = {http://ismir2005.ismir.net/proceedings/3043.pdf},
  timestamp = {Mon, 04 Jun 2012 19:05:51 +0200},
  biburl    = {http://dblp.uni-trier.de/rec/bib/conf/ismir/BellBGB05},
  bibsource = {dblp computer science bibliography, http://dblp.org}
}

http://dblp.uni-trier.de/rec/bibtex/conf/ismir/BellBGB05

Repository footprint is too large

Bordering on redundancy with #24, but worthy of its own callout – as of #27, the repository is now too large (≈1000MB). We knew going in that the proceedings were big, but nothing warned of the total size ... whoops. Per GitHubs docs:

We recommend repositories be kept under 1GB each. This limit is easy to stay within if large files are kept out of the repository. If your repository exceeds 1GB, you might receive a polite email from GitHub Support requesting that you reduce the size of the repository to bring it back down.

In addition, we place a strict limit of files exceeding 100 MB in size. For more information, see "Working with large files."

In which case, I'd escalate this to "bug" level. If nothing else, cloning this repository is now bandwidth prohibitive, which is unfortunate.

Triage, however, is going to be a bit of work.

  • I think we can start moving at least the PDF proceedings to Zenodo manually. There are at most 18 and we currently only have a subset of them. We'll need the ISBNs for each, which is likely (?) in each PDF.
  • Once the PDFs are hosted elsewhere, we can fix the links in the website source.
  • We'll need to either go back and remove these items from the git history to get the repo size back down, or bail on this repository altogether. Keeping the git history is nice, but I'm not opposed to the latter.

Archive ISMIR2015

Kickstart httrack, contact organizers about transfer on failure / pain & suffering.

Resources page appearance

I made multiple MIR-related lists that I wanted to add on my website. However, I think it would be better instead to enhance the already existing lists on http://www.ismir.net/resources.html. Unfortunately, adding a lot of material would make the resources page looks messy and too big. I would like to suggest 2 ideas to overcome this:

  1. Add a dropdown to the menu with one page per type of resources
  2. Keep one resources page but use tabs

If you think this is not a problem to have a lot of links, I would still be happy to make a pull request with all my links.

Archive ISMIR2014

Scrape failed due to absolute URLs littered throughout the source; follow up with organizers to get static bundle.

Slack access?

Hello,

I would like to join the ISMIR Slack channel. I submitted my email through https://launchpass.com/mircommunity but I never heard back. Is this supposed to enroll me automatically or should I just be patient and wait for someone to approve my membership?

Cheers,
Chris

Footer fixes

Currently copy-pasted across pages, which is super hacky. Also the formatting is a little bit janky north to south.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.