Skip to content


Collaborative futures part II

Limits of participation
How important is participation? Positive and negative participation. Think of facebook with only the ability to like something but never dislike.  It is mentioned how participation idealizes harmony and unison. Is this what everyone wants for a successful collaborative effort? Is conflict and dissent important for project development?
First things first
‘Sharing of content does not directly lead to collaboration’ work that was done alone, stands alone and is not collaborative.
Aggregated content, like hashtagged tweets, blog posts begin to lend to collaboration in a massive way because they lose their relevance and significance outside of their individual systems context. But how important is context?
Coordinating mechanisms create context.
Creating the context for threads of collaborative content, requires technical and social coordination and mediation. Wikipedia is cited as an example of technically mediated coordination, simply think of the editing process and the logging of edit history and the ability to revert from a diff.
If you think about the five pillars then you find the tenets of wikipedias social contract. As editors we are striving for a more factual and accurate online resource.

Does aggregation constitute collaboration?
Even after having a defined context does aggregated content become collaborative? Here’s where the example raised by Christina comes up of Kutiman’s sampling of multiple youtube videos coalescing into a music video unbeknownst to the original creators of youtube media.
This brings the idea of intention into the concept of collaboration. How important is intention for collaboration?
When you include hashtags in your tweets in most cases there is the intention of contributing the agglomeration of whatever it is you are tagging. Think about the creation of the concept of the hashtag. It was the goal of the programmer to allow the linking of tweets and thereby foster a network and community beyond sporadic individual expression. This raises the question of how of important is the setting of goals to collaboration. Personal goals define intention, but when they overlap amongst different members of a team and become shared goals, is it only then that collaboration is truly conceived?

Collaborationism
After having discussed the importance of intention, the converse would be looking at the repercussions of collaboration. When one considers the possibility of collaborating on multiple projects, these endeavors confer both the different group and individual indentities. In the context of online collaboration and the coordination facilitated by software services, hashing out one’s identity in a group or the group’s identity from another, becomes an interesting challenge. Think of facebook groups, friendships and the binary nature of interaction, ‘liking’ someone’s post etc. Are these adequate reflections of real social interactions?

Posted in Motivations.

Tagged with , , .


Midterm assignment: Short proposals

As we have discussed, your midterm assignment is to create at least two different project proposals that each have at least two scope variations: one full and a reduced version.

Each of the (at least) two proposals should follow this structure:

  1. an introductory descriptive paragraph, which should include a problem statement, and say *what* your tool/thing will do. This is your abstract, or elevator pitch. This should not have the full theoretical framing of the project. That will come in the final.
  2. a set of personas
  3. a use case scenario (where would someone find your tool/thing and how would they use it). Keep it short.
  4. How you will make the full fledged version. This is your “ideal world” version that fulfills all of your visions and fantasies (what tools you will use, how you will get them, how confident you are that all the moving parts will work together, etc)
  5. Your assessment of how much time this will take, and how much of the skills you currently know and what you would have to learn.
  6. How you will make the stripped down version. The stripped down version is the minimally viable product. It is the most *bare bones* version to prove that what you are trying to get at is viable. (what tools you will use, how you will get them, how confident you are that all the moving parts will work together, etc)
  7. Your assessment of how much time this will take, and how much of the skills you currently know and what you would have to learn.

You are welcome (but not required) to repeat the last two steps with scope variations in-between the full fledged and bare bones version.

I would expect two proposals with two scope variations would be effectively in 4 to 7 page range (though you will be turning in online). I am less concerned with page count, and more concerned with your process (as with all assignments in this class).

You will hopefully notice that you have done a lot of this work already. I have structured it this way. Your job here is to combine and revise the work you have already done, fill the holes, and assess each projects feasibility.

The proposals will be submitted as blog posts prior to class on March 15th.

Class that week will be dedicated to workshopping the proposals. The format we will follow will be that each participant will choose one of their two proposals to present orally. You will have 5 minutes to present, and we will have 5 minutes for feedback. Think of this as a pitch. You will want to lay out the project abstract, present very short versions of your personas, give one use case scenario, and then talk about how you would build it, and how long you think it would take.

Posted in Assignment.

Tagged with , , .


Collaborative futures part I

I’m always at a loss where to start with these blog posts since reading the collaborative futures segments I think I’ll begin with a summary of the major background concepts and include my thoughts as I go along without reproducing what Christina has already posted.

In itself, the composition of the book was a collaborative exercise, employing the crux of it’s own content in it’s production. It begins by situating itself in a context we are all familiar with after our readings in ITP core1 where we delved into Copyleft and free culture and the ideas of new media production exceeding the conserved and traditional social, academic and legal scaffolding that solidly served printed media before the internet.

I found that the somewhat initial abstract way of taking apart the concept of collaboration, by addressing who is collaborating and what makes collaboration, collaboration, interesting and a perfect segue into the background concepts of “what is collaboration?”

Assumptions:

Collaboration is not new and not rare. It is innate in our socialization amongst ourselves that we network and create things with the inclusion of others. There is the beginnings of a definition here where the emphasis lies on expanding beyond geographic limits, this networked effort to produce something open and progressive while ending on the distinction that while it may be printed, the book is unfinished as preposed by its content. (it requires expanded collaborative effort from future additions and edits)

On the invitation:

(this was by far the most garrulous introduction to any chapter) The invitation to produce something  “in connectedness with society” p15. How should someone be invited to collaborate and exactly who and why? The inviters duty becomes an important one when you consider evaluating the project at hand and the invitees, given their willingness and availability, equally so. However, why would someone collaborate?

I particularly enjoyed the Moglen metaphor to Faraday’s discovery of the dynamo,

[on incentives]: ” if you wrap the Internet around every person on the planet and spin the planet, software flows in the network. It’s an emergent property of connected human minds  that they create things for one another’s pleasure and to conquer their uneasy sense of being too alone”

Again, the inherent nature of humans to work together is implied while making the distinction between extrinsic and intrinsic rewards (incentives) for human creativity.

“Amongst, the internal motivation identified as important are: the cultivation of self determination (control over action); enhancement of self esteem.. What unites these elements is their importance in the formation of identity” This builds to the point that creating software requires some self selection on the part of the creators, where you build what you want, not because you can sell it, but because you need it and you can do it and you release it because someone else may need it and use it and build on it too.

Inevitably, it boils down to the fact that there is no singularity in humanity, we share the world with one another, with each of us having different needs and means to fulfill them. Our innate interconnectedness answers the question of “why collaborate?”, with “because we inherently do”

Social creativity:

Every creative act is in someway shape or form, a product of many preceding acts. In the digital world, attribution and ownership become questions that reach beyond the pragmatics of historically instituted copyrights. In the context of massively collaborative projects, how do we address these questions? We don’t, because we can’t if we follow what isn’t applicable today. Instead, creative commons and GPL provide us with some solution for this (as it is in the book) resurgent collectivity.

Open Relationships:

There is a need for some structure to what holds a collaborative effort together. There is now the question of whether it is possible to have this kind of structure in an open manner that is coordinated, transparent, generous and respectful of freedom without it being litigious and endemically bureaucratic?..  honestly.. i have no idea.. the suggestion is that the answer lies in friendship and otherness, though I don’t know if that is applicable in every effort.  Thoughts?

Participation and Process:

The more you invest in the project you are working on, the more worth you ascribe to it and managing this investment by a team becomes vital to any project’s completion. Invitations to collaborate become a means of critically reassessing the trajectory of a project and its creators’ workflow from the outside. Dissent becomes the anti-passivity mechanism that pushes a collaboration beyond cyclical re-validations of contributions, to something that challenges its members to do something beyond their individual capacities. Founders may retain significant power over a project, but the meritocratic nature of online collaboration allows for more horizontal than vertical authority within a project.

The idea of process fetishism struck a cord with me. That the act of open collaboration becomes the goal more so than the project itself. Kinda like a jam band, where the musicians have a great time but listeners do not. The question of whether greater online collaboration is a product of itself in earlier forms, and does that transpose to creating a goal of being relevant and up to date requires more collaboration? Does the process beget its future? More or less, collaborators must outline the goal of their effort.

 

more to come…

Posted in Motivations.

Tagged with , , .


More for the Experience and Education Group

Hi Tope, Kiran, and Amy, again.

After RHaworth moved our article, I have found it a bit confusing to figure out where to continue our work, so I wanted to add a note here (in addition to the notes left on your talk pages) that:

  • our discussions about the article should continue to happen here (http://en.wikipedia.org/wiki/User_talk:SoniaG2/sandbox).
  • actual editing of the article should happen here (http://en.wikipedia.org/wiki/User:SoniaG2/sandbox).

If you are still confused (because I found it very), don’t hesitate to reach out to me: [email protected] / 917.859.6289.

Really looking forward to seeing what our collaborative effort brings, even though RHaworth’s comments are starting to pop up a bit too frequently – but they are no DavidMcEddy, yet.

 

Cheers,

S

Posted in After Class Discussion, Assignment.

Tagged with .


Collaborative Futures

There are a lot of places that I could start writing from after reading Collaborative Futures.  Non-human Collaboration is definitely something that I am interested in.  I was also interested in thinking more about how online collaboration challenges, subverts, or reinforces “obstacles of class, gender, cultural capital, place and acquaintance” (p.29) that can come into play when collaborating generally.  This is also something that came up in this earlier reading we did on the CUNY online BA.  But I will mainly focus on art in this post.

“What does it mean for a cultural work to “execute”? Where code executes, art expresses. Indeed, many forms of art depend on ambiguity, layered meanings, and contradiction. Code is a binary language, whereas the words used to write this book, even though they are in English, will be interpreted in various unpredictable ways. Looking at all of creativity through the lens of code is reductive” (p18).

This excerpt is talking about the limits of thinking of software as an art form and the threshold between execution and expression. Three pieces of art come to mind that play with this difference of software and art, but they are really more a discussion of the digital and art than software and but can also serve to talk about the execution/expression threshold.

 Kutiman’s ThruYou discussed in Collaborative Futures (p.49) brings forth the discussion of whether intention is necessary for collaboration. Works like this and Cory Arcangel’s Paganini’s 5th Caprice beg the question.  But going back to the earlier idea of non-human collaboration we would have to ditch the idea of intention because that belongs to human consciousness and to have non-human collaboration would likely have to be without any kind of pure intentionality.

The comparison between these two videos also raises interesting questions.  Kutiman brings in collaboration of music being played at the same time and Arcangel has the song played each note or so by another person — a kind of collaboration that could never happen in real life and relies on the digital speed that I’m guessing even the most attuned musicians might not be able to achieve.  Is Arcangel any less collaborative, and Kutiman any more?

 

But what about other works of art like (my girlfriend) Megan Bigelow’s RGB: You and Me that eliminate any appearance of collaboration in the overt display.  Maybe or maybe not collaborative, this work relies on the human digital input to the web of pictures tagged with searchable human emotions. What is on the site  now are just three emotions: joyousness, loneliness and happiness.  But the RGB averages of these three emotions reflect a kind of human-google-digital assemblage of affect associated with color, or maybe color generating affect that is unique to each feeling.

In lieu of trying to make and summarizing remarks, I’ll just hope that this will generate some discussion…

Posted in Motivations.

Tagged with , , , , , , .


Redmine and Email Notifications

Hi All,

Just wanted to share my recent Redmine bug tracking experience. I wanted to find out why I was no longer receiving email notifications when a new blog post was posted (which I used to get, for Core I). So I created an account on Redmine in order to report a bug. Here is what I told them:

Hi – I’m having trouble with email notifications. I used to receive email notifications when a new blog post was posted to a blog I’m a member of, but no longer do, even though my email subscription (within the Group settings) is set to “All Email.” I do receive notifications for the following: 1) updates to a document in the blog’s group; 2) comment posted to my own blog post. Is it possible to still get notified when a new post has been added? Thanks!

Almost immediately, I was notified that the status changed from “New” to “Assigned,” and who it was assigned to. Within a day, I got a personal email from a Community Facilitator from the Commons explaining the issue behind notifications (“group blog posts are not included in the group email notification settings,”) and several solutions for activating email notifications (2 plug ins which Michael has installed and are described below).

Several more Redmine emails then appeared – the first explaining that I was sent an email with an explanation and solutions; then another saying the case was resolved, then a follow up email from Commons with yet another solution (Google’s Feedburner), and then a query to close the case.
  • To subscribe to blog post notifications: Click on “Subscribe2” which is under “Tools” in the Dashboard — and you can configure how often notifications are sent to you. Here’s the link to the plug in if you’re interested.
  • To subscribe to comment notifications: When you’re posting a comment, at the bottom of the comment box there’s a checkbox that says: Notify me of followup comments via e-mail. And here’s the link to this plug in.
To be honest, I was at first reluctant to report a bug…I think for fear it was user error, that I could be wasting people’s time, and because I had to create an account, it meant it wasn’t anonymous. But I looked through their issues archives and saw a few similar issues and figured why not, it would be nice to be notified of new posts and comments. I was certainly impressed by the very fast turnaround, the efficiency of the communication, and this feeling that the Commons community is really all about collaboration, as they welcome all to submit bugs (which is a very simple and user-friendly process) in order to contribute to improving the Commons. Also, I appreciated the transparency of the Redmine system and how anyone can go in (without logging in) and see which bugs are being worked on, which have been closed, how the process happens, and who all is involved in the process. All in all, pretty neat.

Posted in After Class Discussion.

Tagged with , , , .


A Note for the Experience and Education Group

Hi Amy, Tope, and Kirin,

Because someone redirected our talk page and sandbox that I created today to Michael’s Sandbox, Malika recommends we create the Sandbox in one of our personal pages and then cut/past a more final version of our article into the Education and Experience article page.

For now, all of the code we previously created lives on my personal sandbox: http://en.wikipedia.org/wiki/User:SoniaG2/sandbox.

If you rather this live on your personal talk page, please copy and paste the code we have to date onto your page.

I hope this doesn’t create too much confusion @Amy, @ Tope, and @Kirin.

Thanks,

Sonia

Posted in After Class Discussion, Assignment.

Tagged with .


Getting Real about getting real

I really liked the concept for this book, but found parts of it troublesome. Meiling certainly touched upon one of the issues I had – trying to compare this philosophy with the demands of academia. We are certainly not expected to “one-down” or “under-do” our peers as far as academic writing and publishing is concerned.

My other problem with this book is that it seemed to take for granted a certain comfort level for designing and implementing software that could easily be applied to new projects. They never touched on the investments one must make to actually learn how to design a GUI, write code, plan a business model, etc. that are necessary steps BEFORE even setting out on a new project. This learning process can take considerable time and money before you even arrive at the stage they’re writing about, and may substantially affect the time and resources you have to beging working on your next-big-thing.

That being said, let me provide a few points that I thought were useful for us as academics and future tech entrepreneurs.

Firstly, their approach to creating a viable and useful product can be applied to academic writing on a smaller scale. When I have an argument to write, the task at hand can seem very daunting. I often have a rough idea of how I want my paper to progress, but it’s never really formalized until I begin writing. And editing. And editing. And editing. I see their approach as similar to the outline approach that I’ve tried to convince myself to do forever, but have only done a few times. Write an outline of your argument – a barebones, only-necessary-material outline. The times that I have done this, my writing process was much smoother and much faster, and required far fewer edits. You can strip away any unnecessary sub-arguments, can identify any extraneous evidence by seeing in advance how little it actually fits with the core of your argument, etc.

Start with your main idea, make it big and far reaching, then strip it down, and down again, until you have a solid argument that can stand on its own and doesn’t try to do too much.

Secondly, and relatedly, the idea of trying to make a piece of software that is 1) initially as simple as possible and 2) only adding complexity when repeatedly requested by users to do so is, at the core, espousing a version of Ockham’s Razor. By starting with something solid that has a definitive function, you can escape unnecessary complexities that can detract from the core functionality of the software. Only when there is a necessity to expand upon the core functionality of the software should there be any additions. I agree that this keeps the software as true to the ‘vision’ as possible, while also making the software less cumbersome to use.

 

Posted in Motivations.

Tagged with , , .


“Getting Real” at odds with “being academic”?

An enjoyable and highly practical read, Getting Real, as a “hands-on” business guide could be one of the most “anti-academic” texts I’ve been asked to read in graduate school. This comment is meant to be a humorous exaggeration, but still worth inspecting. Certainly, the main argument for underdoing and especially, doing less than others is definitely at odds with most of what we’re taught.  On the other hand, “getting it done” has an definite appeal with dissertations looming. Most of all, this made me keep in mind that we are not producing scholar-monk texts for a small circle of specialists – most of us are planning to make useful tools for a broad group of users – students or other communities–that require not only useability but also a certain “marketing appeal” (a concept probably not heard in most of our classes unless one is getting business degree). So my main motivational question in response to this reading is – did it push any of your academic buttons- was any of this advice hard to accept given the anti-commercial indoctrination of the academy?

To volunteer my own response, I found Getting Real refreshing yet sobering in its arguments. Since I spent years before coming back to school working for small start ups (including software companies) I recognized the DIY-bootstrap mentality permeating the text as a likely outcome of decades of trial and error in software developing booms and busts. Most notably, a set of survival strategies coming out of the post-dotcom era, where bloated staffs living on over-venture capitalized budgets burned through money on just an idea and an overdrawn design process before going belly up. Those days are definitely over and this new generation of developers is benefiting as well from what I see as a higher level of understanding from the user – no longer expecting slick, boxed, super feature loaded programs, today’s users seem to accept that their participation helps make the product better, and that anything is always a “work in progress.” Also–that a given program is not going to be the do-all-end-all but that all users create a personalized “mash up” of the tools that work for them. Hence the “human solutions” section (p.55) that advises the entrepreneur to “put it out there before it’s done”and just fix the details later.  I must admit I found this advice, no matter how accurate, the hardest to accept. Knowing my own work process, it’s going to be pretty hard to “go live” with a tool before it feels done. But that will definitely be a moment for going beyond habits that hold back a product from getting to the users–the real point to all of this, and the one best kept in mind. Finally, it was nice to see the emphasis on “passion” in Getting Real and as academically oriented digital innovators we will certainly not come up short on this account!

Posted in Motivations.


The Kitchen Sink

For the Kitchen Sink Utilities reading, I would like you to read that wiki page with two goals: I want you to understand the scope of the tools that are already out there to do that tasks you may need, and I want you to start specifically looking for the tools that will help you with your proposed projects. Also, this is a wiki page, so please edit it and include new resources (for example Scrivener is not on the page, neither is Document Cloud.)

Please post a comment on this thread articulating what tools you may be able to use to execute your project ideas. Describe what each tool does, and how you might be able to use it to solve your problems. Also, please note which tools you added to the wiki page.

A meta-note: All of these project related posts are working towards your midterm project, in which you will have to assemble your user personas, scenarios, short project descriptions, tool selections, and feasibility assessments. For your midterm you will have to do at least two completely different projects, each of which will have no less than 5 permutations total. I will explain the nuts and bolts of this in an assignment post coming later this week, but what you should keep in mind is that I am requiring you to be thinking about multiple projects right now. Don’t be precious! Fail forward!

Posted in Motivations.

Tagged with , .




Skip to toolbar