I have recently been turned on to the Pushtape project. It aims to be a full-featured music CMS built on top of Drupal. It is still in development, but looks promising.
There is some very obvious overlap between our projects. They already have a discography set up for D7, and though I think it has issues, it seems to be more developed than my module is.
I'm about to send a message to the author of that project, but I'd like to get input from everyone about this first. If we do combine forces, this would entail major changes to both my module and their project, and I want to make sure it's all in the best interest of the Drupal community.
Comments
Comment #1
strawberrybrick commentedPlease do not abandon the Discogs module. It is a simple solution to take information from the Discogs.com API and integrate it into Drupal.
Comment #2
planet4sale commentedI can see the advantage of making a decision now on the shape of 7 so as to save work later.
As to which route to take, I would say that as the 6 version has the ability to import data from Discogs API it is immediately a very useful module.
Comment #3
gusaus commentedIf the vision is to evolve into more of a 'discography framework' then possibly it woud make sense to take over the discography module and create something that can be modified for specific use cases like Pushtape, Discogs and others.
I posted a similar comment in the Pushtape project.
Comment #4
alpp commentedI don't know much about Discography Module, but looking through the issues of Pushtape project i see that it will already include a discography feature within. Under these circumstances combining forces of Pushtape and Discogs projects sounds like a good idea to me. Pushtape will have album and song nodes, and if a Discogs extension imports the album/track info from Discogs API, this will accomplish the issues in the previous discussions. i do think this would be the right path to go on.
Comment #5
Karlheinz commentedI just want to make a couple things clear.
I heard back from the author of the Pushtape project. Whatever happens, it looks like I'm going to be merging this project with his. There's too much overlap to not make it happen.
Having said that, I will guarantee that the ability to import discogs.com albums into Drupal will not be abandoned. The merger is not about removing functionality from any of you (or us). It's about making sure that both our modules will provide the desired functionality to as many musicians and music lovers as possible.
It also looks like tracks will indeed be their own node, since this is something that is intentionally set up in Pushtape (they are looking to mimic the functionality of something like Soundcloud, which is a good idea, but a different emphasis than my module). I'm looking into solving all of the problems associated with that, and the guy who created Pushtape seems to know about those problems as well, so we seem to be on the same page.
At the moment everything is up in the air. My vote is to have Discogs handle the entirety of the discography functions for Pushtape, but of course I'd say that. We are still working things out, and there are several technical difficulties we must resolve.
In any case, I want to assure you all that whatever you're doing with Discogs now, you'll be able to do the same thing in the future.
As for the Discography module: that project was abandoned in 2005, long before I started the Discogs module. It's obviously abandoned, it doesn't even have any releases you can download.
Comment #6
gusaus commentedSounds like a great plan. There's also an IRC channel (#pushtape) where zirafa and others interested in Pushtape hang out. I realize discograpy is abandoned, but it might be a great namespace to take over for a general purpose discography module. There are instructions here if you're interested.
Comment #7
Karlheinz commentedJust FYI: I found out just now that there is a Spotify module as well. It looks like it's doing exactly the same thing as Discogs, except with the Spotify API.
Further evidence that Drupal really needs a centralized discography framework.
I made an issue in the Spotify queue, if anyone wants to see it:
#1463006: Integrate with Discogs/Pushtape
Comment #8
gusaus commentedYes - and as I noted in http://drupal.org/node/1226226#comment-5504590 (and above) we have the perfect namespace to take over. Wouldn't that make sense to take over http://drupal.org/node/22152?
Comment #9
ebieymjunior commentedThis also looks interesting:
http://drupal.org/project/spotify_play_button
Comment #10
alpp commentedany updates on this issue?
Comment #11
Karlheinz commentedUpdate:
I will not be making the Discogs module be a plugin for Pushtape.
However, I am making it a framework, so that integration into Pushtape should be possible with a module that implements a single hook. At least that's the plan.
I am changing the priority to "minor" until I get the D7 version into a working state.
Comment #12
Karlheinz commentedChanging the title to describe how to actually implement this feature.
I couldn't do this until the 7.x framework was fully developed.
Comment #13
Karlheinz commentedI finished this. Hooray!
It's called the Pushtape Discography Adapter, and it can be found here:
https://drupal.org/project/pushtape_discography_adpt
It is a separate project, so I am closing this ticket. Any issues with Pushtape integration should be handled in the queue for the Pushtape Discography Adapter project.