Using Wikis in Software Development

Total Page:16

File Type:pdf, Size:1020Kb

Using Wikis in Software Development open source Editor: Christof Ebert ■ Alcatel ■ [email protected] Using Wikis in Software Development Panagiotis Louridas In only a few years, wikis have become one of the most popular tool shells imaginable based on open source software. You can find them just about everywhere that demands effective col- laboration and knowledge sharing at a low budget. Wikipedia has certainly enhanced their pop- ularity, but they also have a place in intranet-based applications such as defect tracking, re- quirements management, test-case management, and project portals. Panagiotis Louridas describes wiki essentials and nicely distinguishes a variety of types. You’ll find something useful, I’m sure. —Christof Ebert y 1995, Ward Cunningham, a promi- What is a wiki? nent member of the design patterns A wiki is actually two things: community, was experimenting with a hypertext environment to promote the ■ a program that makes it exceptionally easy exchange of the community’s ideas. for anybody to edit Web pages and B ■ The environment was based on the a philosophy regarding how users should then-popular Apple Hyper- go about that editing. Card application. That applica- tion worked well for individual Generally, Web pages are written in HTML. users, but Cunningham was While it’s not difficult to learn HTML, non- looking for a Web-based imple- programmers tend to shy away from it. Even mentation. On 25 March 1995, programmers find it easier to edit text than he posted the Web’s first-ever structured HTML, where linking between wiki, calling it “the simplest pages requires attention to things such as ad- online database that could pos- dresses and anchors. When many people edit sibly work.” the same Web site, you must also pay attention Wiki means “quick” in to how these people collaborate. Hawaiian. To describe the technology powering In a wiki, users write simple text following his Web site, Cunningham chose the name a small number of conventions. The system WikiWikiWeb, primarily because he found it creates the necessary links automatically, so more interesting than saying “quick Web.” Web page editors have much less to worry Also, Hawaiian words are doubled for empha- about. Wikis, however, move beyond offering sis, and Cunningham wanted to stress that his practical help to adopting a particular philos- program was very quick. Moreover, as we will ophy on who can edit material and under see, wikis use doublings as formatting markers. what circumstances. Specifically, just about Finally, he wanted an unusual word for an un- any system user can edit a page written by any usual technology. The fact is, both the technol- other user. ogy and the word have stuck with us ever since, This might seem like a recipe for chaos, but creating new forms of collaboration and knowl- it turns out not to be—primarily because edits edge sharing on the Web and empowering many are visible to all. So if somebody abuses his or people to contribute to online content. her editing rights, another person will edit the 88 IEEE SOFTWARE Published by the IEEE Computer Society 0740-7459/06/$20.00 © 2006 IEEE OPEN SOURCE inappropriate edit. We can witness how such a system works in practice by visiting Wikipedia (http://en.wikipedia. org), whose English version counts 965,042 articles as I write this—proba- bly more than a million by the time you read it. The vast majority of articles are of very high quality. There are many ways to implement a wiki, so we now have a multitude of wiki engines at our disposal—more than 200 at this time. All follow the same fundamental principles, but they differ in both the underlying technology and the assumptions about how they’ll be used. Here, plurality is strength, and somebody wishing to create a wiki is really spoiled for choice. Editing a wiki Figure 1 shows the current Wiki- WikiWeb front page (http://c2.com/ Figure 1. WikiWikiWeb front page. cgi/wiki). Apart from its content, the page includes a set of links for edit- ing it. (Figure 1 doesn’t show the links; they’re at the bottom of the page. Also, depending on the wiki engine, the edit- ing links might look like tabs, and the terminology might differ from what I use here.) Clicking on the edit link opens the wiki page’s source text. To edit the text, we write in a human language that fol- lows a few wiki conventions. For exam- ple, to end a paragraph, we use a blank line (double enter). We use doubled sin- gle-quotes for emphasis (usually italics) and tripled single-quotes for strong em- phasis (usually bold). Putting an asterisk in a line’s first column creates a bulleted item in a list; more asterisks create deeper indenting. Some wikis offer edit- ing tools like spell checkers and pre- viewers that make life even easier. Figure 2 shows the edit text for the Figure 2. WikiWikiWeb edit page. page in figure 1. After we’re done editing, we click much by itself. It must be linked to matically creates a link to the named on the save link (or another mechanism other pages. When we edit our text in page. If the page doesn’t already exist, with similar wording). This makes our the wiki, a joined capitalized word we can click on the link and the wiki changes permanent, and all users of the (LikeThisOne) is a link to a page of that engine will take us to a blank page to wiki will see our edited material from name. Again, the convention changes fill in. now on. This being a wiki, they can depending on the wiki engine; for ex- Wikis are very well documented. In also edit it themselves. This leads to a ample, it can be the name of the page fact, they’re usually documented in their live document, something between a surrounded by double square brackets own wikis. Learning the full conven- mailing list and a Web site. ([[Like This One]]). When we save a tions for formatting and editing is sim- Of course, no Web page is worth page that uses a convention, it auto- ply a matter of going through the wiki March/April 2006 IEEE SOFTWARE 89 OPEN SOURCE input from many participants, who Additional Resources on Wikis might not agree. Setting meeting agen- das and keeping minutes are good ex- The Wiki Way: Quick Collaboration on the Web, by Bo Leuf and Ward Cun- amples. Many projects use wikis for ningham (Addison-Wesley Longman, 2001), is the primary reference on wikis, these tasks. In fact, you can use the cowritten by the creator of the original wiki. same wiki for both these tasks—first Wiki: Web Collaboration, by Anja Ebersbach, Markus Glaser, and Richard to set the agenda, then to capture the Heigl (Springer, 2005), describes the wiki philosophy, presents the main fea- minutes. This is much more practical tures, demonstrates MediaWiki and TWiki, and shows how to use wikis as pro- than the usual procedure of circulat- ject management tools. ing e-mails soliciting input and com- Ward Cunningham’s Artima interview (www.artima.com/intv/wiki.html) is an ments and then trying to merge every- engaging firsthand account of the ideas behind wikis. body’s views. The Wiki Design Principles are available in WikiWikiWeb at http://c2.com/ Moving one step further in func- cgi/wiki?WikiDesignPrinciples. WikiWikiWeb also includes an annotated list of tionality, some platforms are available more than 230 wiki engines (at the time of this writing): http://c2.com/cgi/ that build on wikis and offer many ad- wiki?WikiEngines. ditional content management and proj- A site comparing different wiki engines, from which I gleaned the material in ect management goodies. The goodies table 1, is available at www.wikimatrix.org. range from RSS feeds and blogs to sur- The 2005 International Symposium on Wikis, which took place 16–18 Octo- veys, polls, and issue trackers. ber 2005 in San Diego, included presentations on various uses and aspects of wikis. The proceedings and discussions are available at www.wikisym.org. Rolling out a wiki For those who insist on doing every- thing by hand, you can roll out a cus- tom-made wiki that fits a project’s re- help pages. To assist novices, wikis At the simplest level, you can use quirements exactly. Given that a wiki is usually come with a sandbox—a place wikis as a project documentation repos- a Web-based application, you’ll just in the wiki where edits aren’t perma- itory. You can upload all documenta- have to write some server code to ac- nent, so everybody can experiment at tion to a wiki and link source code to cept and record users’ edit requests. their ease. it. This is straightforward if the devel- The original WikiWikiWeb engine oper team uses a version control sys- was a CGI application written in Perl. Using wikis in software tem that publishes code to the Web (see Today wikis are written in anything development “Version Control,” IEEE Software, from Java to Ruby, Perl, PHP, ASP, and No single correct way exists for us- Jan./Feb. 2006, pp. 104–107). Using a so on. At the minimalistic end of the ing a wiki in software development (nor wiki as a static documentation reposi- spectrum, it’s possible to create a wiki in any other activity, for that matter). tory, however, is missing too much of using only Unix shell commands and Wikis are especially useful in distrib- what it has to offer.
Recommended publications
  • The Ridesharing Revolution: Economic Survey and Synthesis
    The Ridesharing Revolution: Economic Survey and Synthesis Robert Hahn and Robert Metcalfe* January 10, 2017 Paper prepared for Oxford University Press Volume IV: More Equal by Design: Economic design responses to inequality. Eds. Scott Duke Kominers and Alex Teytelboym. Abstract Digital ridesharing platforms, such as Uber and Lyft, are part of a broader suite of innovations that constitute what is sometimes referred to as the sharing economy. In this essay, we provide an overview of current research on the economic efficiency and equity characteristics of ridesharing platforms, and provide a research agenda that includes an examination of the natural evolution toward driverless cars. We have three main findings: first, relatively little is known about either the equity and efficiency properties of ridesharing platforms, but this is likely to change as companies and researchers focus on these issues. Second, we may be able to learn something about the likely diffusion and benefits of these technologies from experience with other policies and technologies. Third, while we believe these platforms will do substantially more good than harm, the measurement, distribution, and size of the gains from these technologies requires further research. * Robert Hahn is professor and director of economics at the Smith School at the University of Oxford, a non-resident senior fellow at Brookings, and a senior fellow at the Georgetown Center for Business and Public Policy. Robert Metcalfe is Postdoctoral Research Scholar in Economics at the University of Chicago. We would like to thank Ted Gayer, Jonathan Hall, Scott Kominers, Jonathan Meer, Alex Teytelboym, Scott Wallsten, and Cliff Winston for helpful comments and Julia Schmitz, Brian Campbell and Samantha van Urk for excellent research assistance.
    [Show full text]
  • Wikis Supporting PLM and Technical Documentation Nils Høimyr, Peter L
    Wikis supporting PLM and Technical Documentation Nils Høimyr, Peter L. Jones, CERN, European Organization for Nuclear Research, Switzerland Abstract Over the last years, Wikis have arisen as powerful tools for collaborative documentation on the Internet. The Encyclopaedia Wikipedia has become a reference, and the power of community editing in a Wiki allows for capture of knowledge from contributors all over the world. Use of a Wiki for Technical Documentation, along with hyper-links to other data sources such as a Product Lifecycle Management (PLM) system, provides a very effective collaboration tool as information can be easily feed into the system throughout the project life-cycle. In particular for software- and hardware projects with rapidly evolving documentation, the Wiki approach has proved to be successful. Certain Wiki implementations, such as TWiki, are project-oriented and include functionality such as automatic page revisioning. This paper addresses the use of TWiki to document hardware and software projects at CERN, from the requirements and brain-storming phase to end-product documentation. 2 examples are covered: large scale engineering for the ATLAS Experiment, and a network management software project. .1 Introduction CERN is currently reaching the installation and commissioning stage of the Large Hadron Collider (LHC) accelerator project as well as the completion of the LHC Experiment Detectors (ATLAS, ALICE, CMS and LHCb) “large as cathedrals”. Along with the Accelerator and Detector hardware, there is the LHC Computing Grid project LCG, to build a worldwide computing grid to allow for simulation and analysis of all the data from the LHC physics experiments by physicists scattered all over the world.
    [Show full text]
  • Analyzing and Visualizing the Semantic Coverage of Wikipedia and Its Authors
    Holloway, Todd, Božicevic, Miran and Börner, Katy. (2007) Analyzing and Visualizing the Semantic Coverage of Wikipedia and Its Authors. Complexity, Special issue on Understanding Complex Systems. Vol. 12(3), pp. 30-40. Also available as cs.IR/0512085. Analyzing and Vis ualizing the S emantic C overage of Wikipedia and Its Authors Todd Holloway Indiana University Department of C omputer S cience 150 S . W oodlawn Ave. Lindley Hall 215 Bloomington, IN 47405, US A P hone: (812) 219-2815 E mail: tohollow@ cs.indiana.edu Miran Božievi Wikipedia Networks Team Multimedia Institute (http://www.mi2.hr) Preradovieva 18 HR-10000 Zagreb Croatia Email: [email protected] Katy Börner* Indiana University, SLIS 10th Street & Jordan Avenue Main Library 019 Bloomington, IN 47405, USA Phone: (812) 855-3256 Fax: -6166 E-mail: [email protected] WWW: http://ella.slis.indiana.edu/~katy * To whom all correspondence and proofs are to be addressed. Keywords Network analysis, link analysis, information visualization Number of text pages: 20 Number of figures: 6 Number of tables: 3 1. Introduction ................................................................................................................................................................3 1.1 Wiki Technology and Wikipedia............................................................................................................................3 1.2 Accuracy, Bias and Persistence ...........................................................................................................................4
    [Show full text]
  • Studying Abroad in Costa Rica
    Studying Abroad in Costa Rica By Joel Winters Travel Tips 1. DO NOT PACK LIGHT a. Bring a lot of comfortable clothes 2. Purchase a flight ticket back to the US within a 90 day period and cancel upon your arrival (some airlines will claim you need a VISA but you don’t and this will help with that) 3. DO NOT FORGET YOUR PASSPORT a. Make copies of your passport and license 4. Pack toiletries, sunscreen, and any of your favorite snacks in a CHECKED BAG a. Sunscreen costs about 15$ USD for a bottle in Costa Rica 5. Exchange USD for colones, have a debit card, and an emergency credit card Arrival Guide You will arrive at Juan Santamaria International airport (SJO), then you will have to go through customs. Show the customs officer your passport, destination, and answer any questions they ask. It is better not to talk unless they ask you a question. It only took me 10 minutes to get through customs but it can take more than an hour at some times. Next you will collect your bags and head out to find your host family (they will have a sign with your name on it). It is helpful to know basic Spanish because the host family will most likely not speak English. If they are talking too fast for you to understand it is okay to ask them to speak slower. I knew many people in the study abroad program that did not know any Spanish at all so knowing the language is not necessary to study abroad but it will make your adjustment easier.
    [Show full text]
  • Wikis with Moinmoin Wiki Creative Group Writing
    KNOW HOW MoinMoin Wiki Building wikis with MoinMoin Wiki Creative Group Writing The members of a project team can profit from collecting their ideas, or any loose ends, in a central repository. Wikis are tailor-made for this task. BY HEIKE JURZIK ay before content manage- ment systems started to Wappear for website manage- ment, Wikis provided a kind of “open door” to HTML pages, allowing any visi- tor to click and edit the HTML content. Wiki is the abbreviation for WikiWiki- Web – “wiki wiki” is derived from Hawaiian and means “quick” or “quickly”. And the open authoring sys- restored at any time, should a page be MySQL, Oracle, or PostgreSQL. The soft- tem certainly is quick. The MoinMoin deleted or damaged by mistake. Also, ware then uses this data to create the Wiki engine is one of the better-known wikis allow you to assign special access public HTML pages. implementations of this technology. controls that can restrict editing to regis- Besides taking a look at the original Users can click to launch the embed- tered users, if required. wiki, you might like to visit what is cur- ded editor and access the content and The first wiki website was published rently the biggest wiki on the Web, the structure of the page they want to mod- by Ward Cunningham in 1995, and it is Wikipedia [3], which offers innumerable ify. Typically, an Edit link is provided to still online [1]. At the time, Cunningham articles on pages in multiple languages. make things easier. wrote an email message saying that he It is an example of how well information In contrast to “real” HTML, which had programmed a new kind of database can be organized with a wiki.
    [Show full text]
  • A Wiki-Based Authoring Tool for Collaborative Development of Multimedial Documents
    MEDIA2MULT – A WIKI-BASED AUTHORING TOOL FOR COLLABORATIVE DEVELOPMENT OF MULTIMEDIAL DOCUMENTS Author Name * Affiliation * Address * Author Name * Affiliation * Address * * Only for Final Camera-Ready Submission ABSTRACT media2mult is an extension for PmWiki developed at our university. It provides functionality for embedding various media files and script languages in wiki pages. Furthermore media2mult comes with a cross media publishing component that allows to convert arbitrary wiki page sequences to print-oriented formats like PDF. This article gives an overview over the offered extensions, their functionality and implementation concepts. KEYWORDS wiki, multimedia, cross-media-publishing, authoring tool, XML 1. INTRODUCTION At least since the founding of the free web encyclopedia Wikipedia and its increasing popularity wiki web , wiki-wiki or just wiki are widely known terms in context of Web 2.0. However, their exact meaning often remains unclear. Sometimes wiki and Wikipedia are actually used synonymously. The crucial functionality of every wiki system is the possibility to edit wiki web pages directly inside a browser by entering an easy to learn markup language. Thus, manual uploads of previously edited HTML files are superfluous here. The user doesn't even have to know anything about HTML or external HTML editors. The browser- and server-based concept makes it possible that several authors can edit and revise common documents without the necessity of exchanging independently written and updated versions. Because most wiki systems offer an integrated version management system, authors can easily merge their changes and revert selected passages to former stages. Thus, accidentally or deliberately applied changes of protected or publicly accessible wiki pages can be taken back in a second.
    [Show full text]
  • Developing a Web 2.0-Based System with User-Authored Content for Community Use and Teacher Education
    Education Tech Research Dev DOI 10.1007/s11423-009-9141-x RESEARCH Developing a Web 2.0-based system with user-authored content for community use and teacher education Lauren Cifuentes • Amy Sharp • Sanser Bulu • Mike Benz • Laura M. Stough Ó Association for Educational Communications and Technology 2009 Abstract We report on an investigation into the design, development, implementation, and evaluation of an informational and instructional Website in order to generate guide- lines for instructional designers of read/write Web environments. We describe the process of design and development research, the problem addressed, the theory-based solution, and the evaluation and testing of that solution. Based on our experience, we then identify sixteen guidelines for future designers and developers of read/write Web-based learning environments. The study demonstrates how read/write Web technologies can be used to address general problems that have intrinsic societal importance; examines implementation of a read/write technology in a real-life context, thereby testing distributed cognitions learning theory; informs the design of similar environments; and provides grounded theory for the design and development of read/write Web learning environments. Keywords Design and development research Á Read/write Web Á Web 2.0 Á Distributed cognitions Á Social constructivism The emergence of read/write Web (Web 2.0) technologies such as wikis, Weblogs, Real Simple Syndication, Webcasts, and interactive photo galleries, has empowered users to actively contribute to the content of the Internet. By 2003, 44% of adult Internet users had participated in the interactive capabilities of the Internet by posting in at least one read/ write Web environment (Lenhart et al.
    [Show full text]
  • Wikis in Libraries Matthew M
    Wikis in Libraries Matthew M. Bejune Wikis have recently been adopted to support a variety of a type of Web site that allows the visitors to add, collaborative activities within libraries. This article and remove, edit, and change some content, typically with­ out the need for registration. It also allows for linking its companion wiki, LibraryWikis (http://librarywikis. among any number of pages. This ease of interaction pbwiki.com/), seek to document the phenomenon of wikis and operation makes a wiki an effective tool for mass in libraries. This subject is considered within the frame- collaborative authoring. work of computer-supported cooperative work (CSCW). Wikis have been around since the mid­1990s, though it The author identified thirty-three library wikis and is only recently that they have become ubiquitous. In 1995, Ward Cunningham launched the first wiki, WikiWikiWeb developed a classification schema with four categories: (1) (http://c2.com/cgi/wiki), which is still active today, to collaboration among libraries (45.7 percent); (2) collabo- facilitate the exchange of ideas among computer program­ ration among library staff (31.4 percent); (3) collabora- mers (Wikipedia 2007b). The launch of WikiWikiWeb was tion among library staff and patrons (14.3 percent); and a departure from the existing model of Web communica­ tion ,where there was a clear divide between authors and (4) collaboration among patrons (8.6 percent). Examples readers. WikiWikiWeb elevated the status of readers, if of library wikis are presented within the article, as is a they so chose, to that of content writers and editors. This discussion for why wikis are primarily utilized within model proved popular, and the wiki technology used on categories I and II and not within categories III and IV.
    [Show full text]
  • Onapp Admin Guide
    2.0 Admin Guide 2.0 Admin Guide Contents 0. About This Guide ............................................................................................... 5 1. OnApp Overview ................................................................................................ 6 1.1 Servers ................................................................................................................... 6 1.2 Networks ................................................................................................................ 7 1.3 Templates .............................................................................................................. 8 1.4 Virtual Machines .................................................................................................... 8 1.5 Scalability .............................................................................................................. 8 1.6 Availability and Reliability .................................................................................... 8 1.7 Security .................................................................................................................. 9 1.8 API and Integration ............................................................................................... 9 2. OnApp Hardware & Software Requirements ................................................. 10 2.1 Hypervisor Servers ............................................................................................. 10 2.2 Control Panel Server ..........................................................................................
    [Show full text]
  • Cities Towards Mobility 2.0: Connect, Share and Go! Smart Choices for Cities Cities Towards Mobility 2.0: Connect, Share and Go!
    Smart choices for cities Cities towards Mobility 2.0: connect, share and go! Smart choices for cities Cities towards Mobility 2.0: connect, share and go! Pictures © Shutterstock, 2016, pages: 1, 7, 10, 13, 16, 21, 24, 27, 34, 38, 39, 42. 2 Smart choices for cities Cities towards Mobility 2.0: connect, share and go! Table of contents Preface. 4 Summary. 5 Introduction . 6 The.new.paradigm.of.Mobility.2 .0:.trends.and.challenges. 9 Shared-mobility.concepts.and.experiences . 13 Car sharing . 15 Bike sharing . 20 Ride sharing . 23 Ride sourcing . 26 Park sharing. 28 Shared freight mobility . 30 Impacts.and.benefits. 36 Environmental impacts: is shared mobility the green option? . 36 Does shared mobility expand social benefits and equity in transport accessibility?. 37 Economic impacts of shared mobility . 38 Role.of.public.authorities. 40 Conclusions. 43 References . 45 Web.references. 48 3 Smart choices for cities Cities towards Mobility 2.0: connect, share and go! Preface The objective of the CIVITAS WIKI project is to provide This new mobility paradigm has relevant impacts on cities information to European city planners, decision-makers and their mobility planning strategies and plans, and gives and citizens on clean urban transport and on the CIVITAS rise to several questions. How can cities best manage the Initiative. With its policy notes, WIKI wants to inform people emergence of these new shared-mobility services? How can in cities on a number of topics that currently play an important the relationship between private and public interests best be role in urban mobility. managed? What benefits and opportunities can be identified and exploited at city level? What challenges and potential This policy analysis focuses on the topic of shared mobility.
    [Show full text]
  • Research Article Constrained Wiki: the Wikiway to Validating Content
    Hindawi Publishing Corporation Advances in Human-Computer Interaction Volume 2012, Article ID 893575, 19 pages doi:10.1155/2012/893575 Research Article Constrained Wiki: The WikiWay to Validating Content Angelo Di Iorio,1 Francesco Draicchio,1 Fabio Vitali,1 and Stefano Zacchiroli2 1 Department of Computer Science, University of Bologna, Mura Anteo Zamboni 7, 40127 Bologna, Italy 2 Universit´e Paris Diderot, Sorbonne Paris Cit´e, PPS, UMR 7126, CNRS, F-75205 Paris, France Correspondence should be addressed to Angelo Di Iorio, [email protected] Received 9 June 2011; Revised 20 December 2011; Accepted 3 January 2012 Academic Editor: Kerstin S. Eklundh Copyright © 2012 Angelo Di Iorio et al. This is an open access article distributed under the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. The “WikiWay” is the open editing philosophy of wikis meant to foster open collaboration and continuous improvement of their content. Just like other online communities, wikis often introduce and enforce conventions, constraints, and rules for their content, but do so in a considerably softer way, expecting authors to deliver content that satisfies the conventions and the constraints, or, failing that, having volunteers of the community, the WikiGnomes, fix others’ content accordingly. Constrained wikis is our generic framework for wikis to implement validators of community-specific constraints and conventions that preserve the WikiWay and their open collaboration features. To this end, specific requirements need to be observed by validators and a specific software architecture can be used for their implementation, that is, as independent functions (implemented as internal modules or external services) used in a nonintrusive way.
    [Show full text]
  • A Buzz Between Rural Cooperation and the Online Swarm
    A Buzz between Rural Cooperation and the Online Swarm Andrew Gryf Paterson1 Abstract This article introduces and explores connections between rural traditions and contemporary projects of voluntary cooperation within emergent online network practices. The key examples are mainly from Finland, the Baltic Sea region, and USA. Reflections are made on the emergence of such connections during a trans- disciplinary seminar organised by the author. The main body of the essay mixes social and network culture history, including rural village community support, known as “talkoot” in the Finnish language, its establishment within cooperative development during the 20th century, and the information communications and technology society of contemporary Finland. Discussions of collaborative web platforms such as wikis, the BitTorrent protocol, and “crowd-sourcing” open up questions considering their relation to older cultural traditions. The paper concludes with contemporary examples of where traditions of rural cooperation have conceptually assisted several Finnish entrepreneurial and activist projects. Throughout the paper “the swarm” is identified as a concept worth exploring further to illustrate where the expansive potential of network culture meets concentrated local action. Introduction I write reflecting upon connections which emerged from planning the Alternative Economy Cultures (Alt.Econ.Cult) programme of Pixelache Festival, during winter 2008-2009 and, in particular, the seminar event on April 3, 2009 in Helsinki. To give some contextual background to this event, Pixelache is both a cultural festival and an organized network.2 It brings together people interested in topics such as: electronic arts; participatory cultures and subcultures, including the exploration of grassroots organizing and networks; politics and economics of media/technology; media literacy and engaging environmental issues.
    [Show full text]