ccMixter Needs Developers!

Please take a look at the teams below and see if your skills match.

Current Site Maintenance Team
This team is a devOps team focusing on the “ops” side, but requires dev skill as well.

Skills Required for the Team
Not everyone has to have all these skills, but they should all be represented on team.
*Linux sysadmin skills via SSH
*PHP and Apache
*Some Javascript and HTML would be useful.
*Help desk skills

Next Version Team
The “next version” team would also be devOps, but focused on development. The key vision of this team is to move to a modern REST model where posting to the server is done in a predictable, API tokened, JSON oriented way, with results rendered to the UI in a reliable JSON fashion.

Skills Required for the Team
Not everyone has to have all these skills, but they should all be represented on team.
*Full stack skills in Apache/PHP and MEAN (or comparable frameworks.)
*Visual Design skills
*Wireframing and sketchy gui
*People with a lot of patience and creativity.
*Strong opinions about what music collaboration should look like
*Willing to read “ccmixter: A Memoir.”

Still intrigued? Awesome! Please follow this link and read Admiral Bob’s development vision for ccMixter for more details. Reply to this post or contact us when you are ready and able to join one of the Dev Teams.

Not quite ready to jump on board? You can still help us CRACK the CODE! Support the development of ccMixter by becoming a Patron.

See:
http://ccmixter.org/thread/...

…indeed! I’ve been waiting for this since the upload policy announcement in November, and good to see it happening.

I have meta questions. Will there be a separate Forum thread for feedback on the document itself, and on the Vision? For example:

- What is the ambition level?
** Spawning more sites? There were more once…
** Creating and maintaining a programming community?
** Refocusing on the user (i.e., remixer) community?
** Still open for discussion?
- Will the work continue the ccMixter open source tradition?
** Still openly posted on GitHub?
** How wildly freewheeling the contributions?
** How tightly moderated/peer reviewed?
- Will the dual thread (near-term maintenance, long-term vision) continue?
** I worry “creative” gravity favors the second, visionary effort.
- How about basic HTML?
** Sure would love to have been able to insert a normal unordered list ;-)

Anyway, the simple first question is: “Is that this thread?”

The ambition level:

- not to be coy, but the amount of ambition we have will have a direct correlation with the size of our volunteer pool, and with the amount of funding we are able to raise. I don’t think we want to go too crazy, but there are some fundamental challenges that have to be solved in the future - we need a write API, and we need an API that is authorized by API key, in order to throttle usage. We need a more cohesive UI than what the beta site got off to. We probably need slightly better stem discovery than the existing sites, something like a Dig for remixers. And there are a lot of outstanding bugs and requests for the existing sites. How much of that we can do is dependent on how well resourced we end up being.

Spawning more sites:

You mean ccHost implementations out there? That would be a big plus, because it would give us a community of communities. I don’t think our focus will be on building that out though - it might have to grow organically.

A programming community:

I’m hoping the programming group is simply a subset of the existing community; united to its existing values and ethos. We’re all remixers - remixing code is simply a specialized subset of that.

Refocusing on the User

That’s what a read/write API can do for us. It will allow us to separate user interface from functionality, and allow others to build on the work with apps, etc. We’ve seen all kinds of use of our API to extend games, multimedia, and consumer oriented stuff. How terrific would it be if the next GarageBand could post directly to ccMixter?

GitHub?

Yep. It is there now. That won’t change.

Freewheeling?

The process should have the same rigour any normal FOSS application has. There are committers who have access, other people can do pulls and suggest patches. Or fork, if need be. I like the openness of the Linux community, but ccMixter has a very gentle and congenial culture. I love that our forums and comments have almost zero flaming. The code remix needs to preserve that.

Dual tracks for continuity

Yes. This is just common sense. Someone needs to be able to respond to quick needs, and that can be just as interesting challenging as long term visioneering (the payoff is rapid, right? :) ) That’s what will attract creatives to the short term project: introduction of a new cool integration with a cloud service, auth method, or an integration project that helps bring a DAW integration on board is just as awesome as a big scale restructure - which can take a long time and requires a lot of patience before a payoff comes.

Basic HTML?

If by that you mean something that works without Javascript, I think that day is done, frankly. We’re in the HTML5 world now.

Hi there.

I really waited for something like this! In real live (the live next to my real passion 7OOP3D) I’m work for a digital agency as Sr. Technical Project Manager. I’m into frontend technology as well as in backend technology.

You can count on me…

Where can the current status of things be viewed? Nothing here has been updated since January .. :
Github Search

My CV: https://moikrug.ru/saintbyte

This really working on apache???

wouldn’t mind helping here and there.

Very nice post and right to the point. also, see other posts really good content I find here. Thank you.