Jennifer Baek <[email protected]> writes: >Thanks so much for your feedback! The suicide comment was made by >someone on the Piratepad, but it's hard to track who did it. > >I know someone who can and is willing do the work to code this >graphic with CSS3 and HTML5. While he's coding, we can continue to >work on the substance of the comments. However, it will take some >time, so the project will probably not meet our initial Monday >deadline. > >So here are my slew of questions: > >* Is it worth continuing to work on this if it's going to take > additional days to complete? If it continue to work on this, it > might take me an additional 3-5 days (w/ my job and all) (Perhaps, > releasing this at a later time, would help continue the discussion > beyond the typically short lifespan of content on the Internet). I'm > happy to pass off the Illustrator file to anyone who wants to build > upon whatever I worked on. > >* What can we do to improve the structure/substance of the response? > Should we select only a few parts and put more substantive > annotations? This may help add a *narrative flow* to the piece.
I think point two is good, yeah. Just because David Lowery wrote a sentence doesn't mean we *have* to respond to it, after all :-). You could still include all of Lowery's letter, but just respond to a smaller number of excerpts from it, and the responses could be clearly ordered in a way that they flow downward in order and can be the guide for the reader, who looks inward to Lowery's letter from time to time to get the context for what's being responded to. As for whether it's worth it: your call. I do think things will have died down somewhat by the end of next week, i.e., the "buzz" will be clearly declining, though not entirely gone. QCO would still be happy run the piece, though: we usually aim for articles that are of long-term interest, and that can be referred to later from other stuff, and this would count. So keeping up with the buzz is important, but it's not the only factor. Again, though, completely your call. Given Zac Shaw's response, I think the need for this is less than it was a week ago, so if you wanted to devote your free time to something different, no one could blame you. >* Do you have any recommendations on resources that I can look to to > beef up the substance of our comments? I'm still learning on > becoming more knowledgable about the nuances and the Free Culture > perspective, so this would be tremendously helpful. Well now, I would be untrue to my colleagues and myself if I didn't point to http://questioncopyright.org/ :-). A starting point there is http://questioncopyright.org/guide, though that page needs updating now as we've published some of pieces since then that would supersede other stuff listed on that page. But there are lots of good resources on the web; I get the feeling Zac Shaw's site has a lot of good stuff too. Check out some of the sites listed along the right side of http://questioncopyright.org/guide ... well, here, I'll just list them out below to make it easier. (And if you absolutely have to pick just one, try Falkvinge.net, which I find enjoyable to read as well as extremely informative -- though all the sites are good and worth a visit): http://falkvinge.net/ http://techdirt.com/blog.php?tag=copyright http://righttocreate.blogspot.com/ http://www.okfn.org/ http://www.againstmonopoly.org http://taxpayeraccess.org/ http://c4sif.org/ http://arrangersagainstcopyright.org/ http://www.chillingeffects.org/ http://stpeter.im/?cat=10 http://www.CopyrightReform.us/ http://anticopyright.org http://public.resource.org http://transformativeworks.org http://www.law.duke.edu/cspd/ >* What color? Hah! I'm the world's worst visual designer. The orange was fine with me, but if other people say it's not ideal, they're probably right -- I just can't tell because when I look, I see the words not the colors :-). -K _______________________________________________ Discuss mailing list [email protected] http://lists.freeculture.org/mailman/listinfo/discuss FAQ: http://wiki.freeculture.org/Fc-discuss
