Commit 3eaeca9f authored by Sam Muirhead's avatar Sam Muirhead

fix README links

parent 1bce8da7
......@@ -29,7 +29,7 @@ Sure thing:
- an (illustrated) explanation of [how the core process of creating, committing and remixing works](How-to-commit.md).
- the [Equipment List](Equipment_list.md) has everything you will need to run a workshop.
- the instructional [Posters](Posters/) and [Commit Log](Commit-Log/) which you can print or adapt.
- the instructional [Posters](Print/Instructional-Posters/) and [Commit Log](Commit-Log/) and more [resources to print](Print) or adapt.
- a [blogpost](http://www.cameralibre.cc/cut-copy-and-paste/) about the workshop we ran at Mozilla Festival 2017
- a [blogpost](http://www.cameralibre.cc/arts-commons/) and [recipe](https://gitlab.com/cameralibre/arts-commons/blob/master/Co-creation%20Collage%20Workshop.md) for a more basic version of the workshop at Arts & Commons in 2016
- The [Roadmap](https://gitlab.com/cameralibre/cut-copy-and-paste/blob/master/ROADMAP.md) outlining the upcoming tasks and milestones for the project.
......@@ -52,7 +52,7 @@ Of course - if you would like to run a version of these workshops, go ahead - yo
As of 2018 I am based in Aotearoa New Zealand, so I'd love other people to pick up the project and run workshops in places which are harder for me to get to (so... pretty much anywhere).
But if you publish a new version, you need to attribute me and use the same license that I have used. (Everything in this repository (unless otherwise indicated) is licensed under [Creative Commons Attribution-Sharealike](https://gitlab.com/cameralibre/cut-copy-and-paste/blob/master/Posters/CC-BY-SA-WTF.pdf).)
But if you publish a new version, you need to attribute me and use the same license that I have used. (Everything in this repository (unless otherwise indicated) is licensed under [Creative Commons Attribution-Sharealike](Print/Instructional-Posters/CC-BY-SA-WTF.pdf).)
### I want take part in a workshop! <a name="take-part">
......@@ -65,15 +65,16 @@ If you have any suggestions or improvements please get in touch:
- [my website](http://www.cameralibre.cc/)
- [twitter](https://twitter.com/cameralibre)
- Secure Scuttlebutt: @UhORGzAhEE3gqy/pH5vK+EgbpZfnyYvdI46TVBJH6Mw=.ed25519
- on the [Open Source Design](https://discourse.opensourcedesign.net/t/teaching-open-source-collaboration-to-designers-without-digital-tools/289) forum
- or open an [issue](https://docs.gitlab.com/ee/user/project/issues/index.html) here on Gitlab. If you go to this project's [Issues](https://gitlab.com/cameralibre/cut-copy-and-paste/issues) page, you will see the option to simply email an issue. Follow the instructions and if you need any help with Git or Gitlab, just ask - a lot of it is over my head too, we can learn together :)
### People: Who's involved? <a name="team">
I'm [Sam](https://twitter.com/cameralibre), I'm based in Te Whanganui-a-Tara (Wellington), Aotearoa New Zealand but I spent 2009-2017 in Berlin, where this project was initially developed. I like to explore, explain and advocate for Open Source beyond the world of software. I do so by making [documentaries and animations](http://cameralibre.cc): about open everything, made with free software, and built on free culture. 5 years ago I also lived a [Year of Open Source](http://edition.cnn.com/2013/06/04/opinion/sam-muirhead-year-open-source), I've run workshops on community building, licensing and open source hardware business models and co-founded an international movement for an open source approach to create a waste-free, sustainable circular economy ([OSCEdays](https://oscedays.org/)).
I'm [Sam](https://twitter.com/cameralibre), I'm a Mozilla Fellow working with Creative Commons, based in Te Whanganui-a-Tara (Wellington), Aotearoa New Zealand. I like to explore, explain and advocate for Open Source beyond the world of software. I've often done so by making [documentaries and animations](http://cameralibre.cc): about open everything, made with free software, and built on free culture. 5 years ago I also lived a [Year of Open Source](http://edition.cnn.com/2013/06/04/opinion/sam-muirhead-year-open-source), I've run workshops on community building, licensing and open source hardware business models and co-founded an international movement for an open source approach to create a waste-free, sustainable circular economy ([OSCEdays](https://oscedays.org/)).
[Judith Carnaby](http://www.judithcarnaby.com/) is an illustrator, teacher and writer on illustration. She has made great contributions to the development of the project, and will be co-hosting workshops with me.
[Judith Carnaby](http://www.judithcarnaby.com/) is an illustrator, teacher and writer on illustration. She has made great visual and conceptual contributions to the development of the project, and will be co-hosting workshops with me.
[Jan-Christoph Borchardt](https://jancborchardt.net/) took part in the first Cut, Copy & Paste workshop prototype in 2017, has contributed many new ideas and great feedback, and is the first person to run a Cut, Copy & Paste workshop without me :)
......@@ -95,4 +96,4 @@ What differentiates the two projects is that:
- git physical uses carbon paper as its duplication device, whereas we use a photocopier
- git-physical has a much better name ;)
- the Cut, Copy & Paste workshop is _also_ heavily inspired by git, but ours is a looser interpretation than Miglena's.
This is because I don't see git (and sites like Gitlab/Github etc) as the solution to artistic version control, at least not in their current state. For me, and perhaps for other non-programmers, git is too esoteric, too text/code-focused, too technical, too imbued with programmer culture ([git blame](https://www.git-scm.com/docs/git-blame), etc). So... if somebody could quickly whip up a simplified, friendlier git equivalent for visual and artistic work, that would be just lovely. Please? Thanks.
\ No newline at end of file
This is because I don't see git (and sites like Gitlab/Github etc) as the solution to artistic version control, at least not in their current state. For me, and perhaps for other non-programmers, git is too esoteric, too text/code-focused, too technical, too imbued with programmer culture ([git blame](https://www.git-scm.com/docs/git-blame), etc). So... if somebody could quickly whip up a simplified, friendlier git equivalent for visual and artistic work, that would be just lovely. Please? Thanks.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment