matthewepler/recode_project

home of the ReCode Project (http://recodeproject.com)

This repo is no longer being used as the central repository for the ReCode Project. All additions to the project should be submitted on our site.

I will continue to receive notifications regarding issues, but it's probably better just to use the email address below.

These files will remain here indefinitely. Please contact me if you have questions.

ReCode Project

http://www.recodeproject.com/
[email protected]
@ReCodeProject

recode_project's Issues

Source ≠ Structure = Mess?

I'd like to order the translations (sketches) a bit more meaningful.
If some people agree I'd start the ordening.

Any Ideas for the structure?

Maybe:
src/(artistsFamilyName artistsFirstName)/(name of publication)/(Issue)/(name of work)/

Better Ideas? The initial author of the sketch would be in the source. I'd do the ordening of the source. But the Webpage-Generator should also be adjusted.

Licence model not Opensource

Wow! I got across this really cool project you kicked off! Thanks a lot for your effort an all that work! Already some awesome translations in there! Unfortunately in the processing sketch files there is always the Creative Commons license CC BY-SA 3.0 disclaimer.

Of course I really like the CC licence and personally I try to publish as many intelectual property as possible under a fee licence. But unfortunately the CC-Licence is not a Software License and doesn't cover the needs for code.

Even cc agrees on that as you can see in their FAQ

If you still want to stick to a CC then the only Licence could be CC0
But because the Open Source Initiative didn't accept that licence as open it is still not a good decision.

The current code is processing code (Java) and maybe someone would like to use it in processing.js (JavaScript). Therefore is also the debate with GPL or LGPL because in JS it's not compiled and you never know what kind of Licence applies to the rest of the code. That's the reason most JS libraries do BSD, MIT or dual-licensing with BSD/MIT&GPL. Some examples:

• jquery as MIT
• processing.js as MIT
• paper.js as MIT

I would really like to see new sketches under a proper licence so the authors an users are save.

Thank you for all that cool stuff out there! 🍰
Stefan Huber

Next Steps

Hi all,

I want to make sure the next steps in the ReCode Project address the issues you find most important. I'll outline my thoughts here and please feel free to respond.

The purpose of the project is two-fold:

1. Bring these original pieces back into public view
2. Make them accessible

Current Issues:

• No way for a translator to directly edit the code that appears on the site. it is currently stored as a string, and is not connected to the github file. This could be fixed by adding user sessions but I'm unsure if having that is necessary. The alternative to user sessions would be to put a hard link to the gitHub file once it's been merged. That link would pull the contents of the file every time the page is requested.
• Translations are not sorted by date.
• Links to filtered searches are not visible and therefore not copy/pasteable
• No biographical info on the original artists. No info on translators.

Moving Forward:

• There should be an easier way to submit translations and maintain how a translation looks without having to go through me.
• Would like to hear opinions on the advantages and issues with adding a way to see the code run in the browser (applets, .js, etc).
• I would like to continue to do translations in batches. Each collection will have its own issues and it will be easier to address them as a single project instead. People can suggest original content but ultimately it will need to be reviewed before it goes up on the site. I hope to have a new batch by the end of January.
• In 2013 I'd like to have a show of these works in New York. In preparation for that, I'd like to select exemplary works from the past and get in touch with the original artists. I would interview them about the work, get as much material as I could, and then pair them up with a contemporary coder who would work on the translation of that work. The two pieces and their code would be displayed side-by-side and both parties invited to the show. Ideally, we'd have two generations of coders in the same room talking to each other next to work that retains its original form as a product. This could be accompanied by a small publication, a series of talks, or any number of offshoots.

Thanks to everyone for their work and I look forward to making this as good as it deserves to be!

-Matt Epler