Pushtape in its current form is lightweight and extendable for developers but does not not yet provide the ideal User Experience for musicians, managers, or others who do not know and/or care about Drupal. To get there, we really need to include the functionality listed below (in additional to making existing features easier to use):

As developing, upgrading, maintaining, patching is no simple task (especially for basically one maintainer on volunteer time), we would have a lot to gain if we could build on top of Panopoly, a base distribution that provides the UX experience we're lacking out of the box. And because Panopoly already includes most of the modules/libraries included in Pushtape, we could share the heavy lifting (including security updates, feature improvments, regular releases) with their many contributors, and focus more on building/improving tools musicians need.

If we did want to provide this functionality, either by refactoring the existing Pushtape distro/features or creating another branch (2.x.), we could start by integrating the experimental code currently on GitHub (see demo) that includes all of the above in addition to the following add-on features:

By focusing these scattered projects in one place we could refocus our contributions and seek out additional support.

Comments

gusaus’s picture

Issue summary: View changes
gusaus’s picture

Issue summary: View changes
gusaus’s picture

Issue summary: View changes
Related issues: +#2511614: Custom theme builder
gusaus’s picture

FYI there's a new thread regarding strategies for building on top of Panopoly -
https://groups.drupal.org/node/473033

We'll incorporate some of those best practices once we figure out if the code will reside as part of this project or not.

zirafa’s picture

Been laying low and watching this issue (plus related tickets), but for now I wanted to comment on a couple of assumptions being made:

# Ideal User Experience (i.e. "needs of musicians", "ease-of-use", etc)
I think you are making some assumptions about what the "ideal" user experience is based on website builder platforms (Squarespace, Bandzoogle). Pushtape's user experience is designed to be closer to that of Bandcamp & Soundcloud, where the experience and workflow is more tightly focused around the goal of quickly organizing music. While one provides a lot of open ended configuration options, the other tries to focus the user on accomplishing a few tasks quickly.

# Motivation behind the minimalism of Pushtape
Reducing overhead maintenance was definitely a reason for keeping the Pushtape feature set minimal, however it was only a part of the reasoning. One of the original design goals was to provide a *focused* user experience and workflow as described above, by favoring convention over configuration. Because of this, Pushtape behaves more like a music organizing web app and hides a lot of Drupal-isms. Making decisions for a user through convention saves them time but does limit customization options. However it is still Drupal, so it is possible to extend the feature set as you've shown, which is pretty cool to me.

# Rebuilding vs Extending
Why not just build a Pushtape Panels/Panopoly add-on feature? A complete rebuild of the distro is not likely to happen because it could potentially alienate current users and break the current stable code base. I also can't get behind the idea of a new franken-distro or a fork of Pushtape for this purpose, either, as it would be too confusing to manage and is a pretty big architecture change. If you are already committed to building a new music distro on Panopoly then I think it's an entirely separate project with a unique/different name, and probably one I wouldn't have time to help out with.

gusaus’s picture

Just a quick followup after doing some free jazz, Kamasi Washington style in #pushtape IRC.

Agreed we're talking about slightly different goals and assumptions. The code that I primarily maintain is a continuation of previous band site builder platforms such as Bryght's hosted solution (~2005?), and Music Distribution for Drupal (~2009). The current Panopoly based distro has resided on the Pushtape github repo for over 3 years, and there are probably many who think it is Pushtape.

If you take into consideration the distro incorporates all of the existing features (in addition to more), we're really talking about a different variation/flavor of the Pushtape Music distribution, rather than a totally unique project. I'm fearful that creating a separate project would not only cause confusion for users, but also developers and supporters.

So I do agree that these are (and should be) unique distributions - if it actually makes sense to keep them as variations as Pushtape, the next question is how to do that. One thought would be to have the distro I maintain be a 2.x. branch. That way we could use the same issue queue and possibly offer #1475130: providing different flavours of pushtape on install.

All in all, I strongly suggest we keep these flavors under the same Pushtape umbrella. If there isn't a clear, best practice on how to do that... then we might help pave the way.

And lastly, I would indeed like to officially maintain the Panopoly branch and also help with the overall project. Its going to take more than one person to create something that's going to be useful to the next Kamasi Washington!

zirafa’s picture

Gusaus, our projects may seem similar at the moment but due to scope/vision differences will diverge, and the gap will only widen over time. If you want to continue down this path, please name your project something different, without pushtape in the name to avoid confusion. This will allow the distributions to be managed and maintained separately.

gusaus’s picture

I know you're trying to do the right thing, but what you've described as "a culmination of many years of discussion about building a music distribution for Drupal" is not that if you're closing out long time contributors to some of those very projects you mention. For my reasons above, I don't think having what 'to many' would seem like identical/competing projects would be productive, and I don't have the time/energy to do a lot of explaining and politicking.

I got sucked into the community after the hosted band solution I was just looking to resell (built on Drupal) went away. 10 years later I'm a proud maintainer of a pretty solid distribution, but bringing it back to drupal.org doesn't seem worth it at the moment.

Zirafa, I wish you the best of luck! I'll let everybody know when the project has a new name and where they can find it.

zirafa’s picture

Status: Active » Closed (won't fix)