DOCSLIB.ORG

A Delphi Study of the Influences on Innovation Adoption and Process

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Delphi Study of the Influences on Innovation Adoption and Process Department of Computer Science and Information Systems College of Informatics and Electronics A Delphi study of the influences on innovation adoption and process evolution in a large open-source project The case of Debian Martin F. Krafft, B.A.hons Lero — the Irish Software Engineering Research Institute <[email protected]> — http://phd.martin-krafft.net A dissertation submitted for the degree of Doctor of Philosophy at the University of Limerick, Ireland Under the supervision of Prof. Dr. Brian Fitzgerald and Dr. Kieran Conboy 6 Apr 2010 ii To infinity, and beyond! iv Contents List of tables x List of figures xii Abstract xiii Originality note xiv Version history xv Copyright & Licence xvi Acknowledgements xvii 1 Introduction 1 1.1 Motivation . 1 1.2 Research question and objectives . 4 1.3 Outline of the thesis . 7 I Background and literature review 2 Debian 10 2.1 Introducing Debian . 10 2.2 The Debian community . 11 2.2.1 Project members and contributors . 12 2.2.2 Debian governance . 13 2.2.3 The role of volunteers . 14 2.2.4 Stereotypical traits of Debian developers . 15 2.2.5 Freedom and independence . 20 2.2.6 Debian derivatives and Ubuntu . 22 v Contents Krafft: Ph.D. dissertation 2.2.7 Communication basics . 23 2.2.8 Relation to organisational theory . 25 2.3 Debian packaging . 32 2.3.1 Tools, techniques, processes, approaches, solutions, and methods . 32 2.3.2 The Debian packaging workflow . 33 2.4 Process improvement and volunteers . 35 2.5 Previous research on Debian . 37 3 Assessing diffusions 39 3.1 History and terminology . 39 3.1.1 Innovation and invention . 40 3.1.2 Diffusion, adoption, and critical mass . 42 3.1.3 Adoption process and innovation stages . 43 3.1.4 Network externalities and excess inertia . 46 3.2 Diffusion frameworks . 46 3.2.1 In search of a framework . 48 3.2.2 An overview of existing frameworks . 50 3.2.3 A framework for influences to adoption behaviour in the Debian Project 58 3.3 Related studies . 59 II Research approach 4 Introduction 61 4.1 Philosophical considerations . 63 4.1.1 Positivism vs. interpretivism . 64 4.1.2 Research dichotomies . 68 4.2 Research objectives . 70 4.3 Secondary objectives . 70 4.3.1 Sub-objective 1: Data from the Delphi study . 70 4.3.2 Sub-objective 2: The Delphi method in the FLOSS context . 71 5 The Delphi method 73 5.1 The Delphi process . 74 5.2 Suitability for this research . 75 5.2.1 Delphi and asynchronous communication in FLOSS . 76 5.2.2 Benefits of controlled feedback in a FLOSS context . 78 5.2.3 Reasons for a Delphi approach . 80 5.3 Variants and modifications . 81 5.4 Design considerations . 83 5.4.1 Choice of the specific Delphi method . 84 5.4.2 “Experts” . 85 5.4.3 Participant selection . 85 vi Krafft: Ph.D. dissertation Contents 5.4.4 Panel size . 89 5.4.5 Degree of anonymity . 90 5.4.6 Communication medium . 91 5.4.7 Consensus vs. disagreement . 94 5.4.8 Question design . 95 5.4.9 Participant dropout and non-response . 96 5.4.10 Bias . 99 5.5 Sending e-mails to Debian contributors . 100 5.5.1 Avoiding the bulk-mail character . 100 5.5.2 Dealing with spam filters . 101 5.6 Deciding against a mock study . 102 6 Research approach details 105 6.1 Details of the participant selection process . 106 6.1.1 Picking nominators . 106 6.1.2 Calling for nominations . 107 6.1.3 Soliciting applications to the panel . 109 6.1.4 Questioning potential participants . 111 6.1.5 Selecting the panellists . 112 6.1.6 Declining applications . 115 6.2 Details of the Delphi study . 116 6.2.1 The first round: brainstorming influences . 116 6.2.2 Wrapping up the first round . 119 6.2.3 Preparing the second round . 120 6.2.4 Round two: discussing influences . 124 6.2.5 Wrapping up round two . 125 6.2.6 Preparing the third and final round . 126 6.2.7 Round three: identifying salient influences . 129 6.2.8 Design of the third-round email . 130 6.2.9 Wrapping up round three . 131 III Analysis 7 Results 134 7.1 Framing the results . 136 7.1.1 Individual and organisational adoption timelines . 136 7.1.2 A stage model for adoptions in the Debian Project . 138 7.2 Influences to Debian Contributors’ adoption decisions . 142 7.2.0 On the role of pioneers . 146 7.2.1 Stage one: knowledge . 147 7.2.2 Stage two: individual persuasion . 168 7.2.3 Stage three: individual decision . 184 7.2.4 Stage four: individual implementation . 195 vii Contents Krafft: Ph.D. dissertation 7.2.5 Stage five: organisational adaptation . 206 7.2.6 Stage six: organisational acceptance . 216 7.2.7 Stage seven: use-performance-satisfaction, individual confirmation . 221 7.2.8 Stage eight: incorporation . 223 7.2.9 Stage nine: organisational initiation . 231 8 Conclusion 236 8.1 Research contribution . 236 8.1.1 Influence salience . 238 8.1.2 A stage model of adoption in the Debian Project . 239 8.1.3 Specificity of results and stage model . 240 8.1.4 Secondary research objectives . 246 8.2 Implications for practice . 247 8.3 Review of the research approach . 250 8.3.1 Bias . 251 8.3.2 Design issues . 258 8.4 Review of the design . 266 8.4.1 Intuition and self-involvement . 266 8.4.2 Compensation for participation . 268 8.4.3 Feedback from the panellists . 269 8.5 Recommendations for future research . 276 8.5.1 Comprehensiveness and salience of influences . 277 8.5.2 Longitudinal diffusion studies . 278 8.5.3 Executive decision-making . 279 8.5.4 Consequences of innovation . 279 8.5.5 Investigation of single stages . 279 8.5.6 Needs and technology . 280 8.5.7 Information flow and channel effectiveness . 281 8.5.8 Revolutions and evolutions . 282 8.5.9 Corporate affiliation and credibility . 282 8.5.10 Elegance . 283 8.5.11 Level of abstraction . 283 8.5.12 On-line diffusion theory . 284 Bibliography 287 A Background information on Debian 306 A.1 Terminology . 306 A.1.1 System . ..
Load more

Recommended publications
  • SFLC V Conservancy
    Trademark Trial and Appeal Board Electronic Filing System. http://estta.uspto.gov ESTTA Tracking number: ESTTA863914 Filing date: 12/11/2017 IN THE UNITED STATES PATENT AND TRADEMARK OFFICE BEFORE THE TRADEMARK TRIAL AND APPEAL BOARD Proceeding 92066968 Party Defendant Software Freedom Conservancy Correspondence PAMELA S CHESTECK Address CHESTEK LEGAL P O BOX 2492 RALEIGH, NC 27602 UNITED STATES Email: [email protected] Submission Motion for Summary Judgment Yes, the Filer previously made its initial disclosures pursuant to Trademark Rule 2.120(a); OR the motion for summary judgment is based on claim or issue pre- clusion, or lack of jurisdiction. The deadline for pretrial disclosures for the first testimony period as originally set or reset: 07/20/2018 Filer's Name Pamela S Chestek Filer's email [email protected] Signature /Pamela S Chestek/ Date 12/11/2017 Attachments Motion for SJ on affirmative defenses-signed.pdf(756280 bytes ) Kuhn-Declara- tion_summary-judgment_as-submitted_reduced-size-signed.pdf(2181238 bytes ) Sandler-declara- tion_summary-judgment_as-submitted-reduced-size-signed.pdf(1777273 bytes ) Chestek declaration_summary-judgment-signed-with-exhibits.pdf(2003142 bytes ) IN THE UNITED STATES PATENT AND TRADEMARK OFFICE BEFORE THE TRADEMARK TRIAL AND APPEAL BOARD In the Mater of Registraion No. 4212971 Mark: SOFTWARE FREEDOM CONSERVANCY Registraion date: September 25, 2012 Sotware Freedom Law Center Peiioner, v. Cancellaion No. 92066968 Sotware Freedom Conservancy Registrant. RESPONDENT’S MOTION FOR SUMMARY JUDGMENT ON ITS AFFIRMATIVE DEFENSES Introducion The Peiioner, Sotware Freedom Law Center (“SFLC”), is a provider of legal services. It had the idea to create an independent enity that would ofer inancial and administraive services for free and open source sotware projects.
    [Show full text]
  • Assignment of Master's Thesis
    ASSIGNMENT OF MASTER’S THESIS Title: Git-based Wiki System Student: Bc. Jaroslav Šmolík Supervisor: Ing. Jakub Jirůtka Study Programme: Informatics Study Branch: Web and Software Engineering Department: Department of Software Engineering Validity: Until the end of summer semester 2018/19 Instructions The goal of this thesis is to create a wiki system suitable for community (software) projects, focused on technically oriented users. The system must meet the following requirements: • All data is stored in a Git repository. • System provides access control. • System supports AsciiDoc and Markdown, it is extensible for other markup languages. • Full-featured user access via Git and CLI is provided. • System includes a web interface for wiki browsing and management. Its editor works with raw markup and offers syntax highlighting, live preview and interactive UI for selected elements (e.g. image insertion). Proceed in the following manner: 1. Compare and analyse the most popular F/OSS wiki systems with regard to the given criteria. 2. Design the system, perform usability testing. 3. Implement the system in JavaScript. Source code must be reasonably documented and covered with automatic tests. 4. Create a user manual and deployment instructions. References Will be provided by the supervisor. Ing. Michal Valenta, Ph.D. doc. RNDr. Ing. Marcel Jiřina, Ph.D. Head of Department Dean Prague January 3, 2018 Czech Technical University in Prague Faculty of Information Technology Department of Software Engineering Master’s thesis Git-based Wiki System Bc. Jaroslav Šmolík Supervisor: Ing. Jakub Jirůtka 10th May 2018 Acknowledgements I would like to thank my supervisor Ing. Jakub Jirutka for his everlasting interest in the thesis, his punctual constructive feedback and for guiding me, when I found myself in the need for the words of wisdom and experience.
    [Show full text]
  • Customization of an Enterprise Request Management System
    ISSN (Online) 2393-8021 ISSN (Print) 2394-1588 International Advanced Research Journal in Science, Engineering and Technology Vol. 2, Issue 2, February 2015 Customization of an Enterprise request Management System 1 2 3 4 Ashna Shah , Chinmay Balutkar , Bhargavee Singh , Rajesh. B. Singh Student, Computer Department, Sinhgad Institute Of technology, Lonavala, India 1,2,3 Associate Professor, Computer Department, Sinhgad Institute Of technology, Lonavala, India4 Abstract: Information provided in issue reports are relevant and complete in order to help resolve issues quickly. However, often such information trickles to developers after several iterations of communication between End user and reporters. This paper addresses the concerns of Customization of an Enterprise management system by proposing for handling of the issues such as bugs, query and enhancements. As a proof-of-concept, we also demonstrate a prototype interactive enterprise request management system that gathers relevant information from the user and identifies files that need to be fixed to resolve the issues. The main contribution of this application is in the domain of business as we are developing Enterprise request Management System. Keywords: Bugs, Issues, query, enhancement. I. INTRODUCTION The use of Enterprise Request Management Systems as a to the issue and again will report the issue to the reporter. tool to organize maintenance activities is widespread. The Developer then will handle the issues and will fix them. systems serve as a central repository for monitoring the This system will help to manage the issues in the business progress of issue reports, requesting additional information domain by fixing them. The issues might be a bug, query from reporters, and discussing potential solutions for or the enhancement.
    [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]
  • E-BUG TRACKING SYSTEM GUIDE: Mrs
    E-BUG TRACKING SYSTEM GUIDE: Mrs. Sathya Priya R1 R.B. Babu2, R. Marimuthu3, G. Gowtham4, V. Prakash5 1Assistant Professor, KSR Institute for Engineering and Technology, Tiruchengode. 2,3,4,5Department of Computer Science And Engineering, KSR Institute for Engineering and Technology, Tiruchengode. ABSTRACT This is the world of information. The ever-growing field Information Technology has its many advanced notable features which made it what it was now today. In this world, the information has to be processed, clearly distributed and must be efficiently reachable to the end users intended for that. Otherwise, we know it led to disastrous situations. The other coin of the same phase is it is absolutely necessary to know any bugs that are hither-to face by the end users. The project “e-bug tracking system” aims to provide the solution for that. The Bug Tracker can be made from any two types. The first one being the system side, the other being the services side. Our project deals with the second one. The paper is wholly dedicated to tracking the bugs that are hither- by arise. The administrator maintains the master details regarding to the bugs id, bugs type, bugs description, bugs severity, bugs status, user details. The administrator too has the authority to update the master details of severity level, status level, etc, modules of the paper. The administrator adds the users and assign them responsibility of completing the paper. Finally, on analysing the paper assigned to the particular user, the administrator can track the bugs, and it is automatically added to the tables containing the bugs, by order of severity and status.
    [Show full text]
  • Debian 1 Debian
    Debian 1 Debian Debian Part of the Unix-like family Debian 7.0 (Wheezy) with GNOME 3 Company / developer Debian Project Working state Current Source model Open-source Initial release September 15, 1993 [1] Latest release 7.5 (Wheezy) (April 26, 2014) [±] [2] Latest preview 8.0 (Jessie) (perpetual beta) [±] Available in 73 languages Update method APT (several front-ends available) Package manager dpkg Supported platforms IA-32, x86-64, PowerPC, SPARC, ARM, MIPS, S390 Kernel type Monolithic: Linux, kFreeBSD Micro: Hurd (unofficial) Userland GNU Default user interface GNOME License Free software (mainly GPL). Proprietary software in a non-default area. [3] Official website www.debian.org Debian (/ˈdɛbiən/) is an operating system composed of free software mostly carrying the GNU General Public License, and developed by an Internet collaboration of volunteers aligned with the Debian Project. It is one of the most popular Linux distributions for personal computers and network servers, and has been used as a base for other Linux distributions. Debian 2 Debian was announced in 1993 by Ian Murdock, and the first stable release was made in 1996. The development is carried out by a team of volunteers guided by a project leader and three foundational documents. New distributions are updated continually and the next candidate is released after a time-based freeze. As one of the earliest distributions in Linux's history, Debian was envisioned to be developed openly in the spirit of Linux and GNU. This vision drew the attention and support of the Free Software Foundation, who sponsored the project for the first part of its life.
    [Show full text]
  • Linux on the Move
    Guest Editors’ Introduction What is Linux? And why should you care? This focus section has insights for both newcomers and diehard fans. Linux on the Move Terry Bollinger, The Mitre Corporation Peter Beckman, Los Alamos National Laboratory inux is a free, open-source operating system that looks like Unix, L except that it runs on PCs as well as other platforms. Linux was created by Linus Torvalds in 1991. Today, Linux is cooperatively improved by Torvalds and thousands of volunteers from around the world using open-source development methods. At this point in time, “Linux” generally refers to the entire suite of software in a distribution, from the operating system kernel to the Web server and graphical user interface. When we say that Linux is “free” we mean, well…free. You do not need to pay money to get a copy of it, although it is usually more convenient to buy an inexpen- sive CD-ROM copy than download an entire distribution over the Internet. Once you get a copy of Linux, you also have the right to make as many copies of it as you want. 30 IEEE Software January/February 1999 0740-7459/99/$10.00 © 1999 . DEFINING TERMS GETTING RESULTS By “open source”we mean that you also have the The only traditional software practice that open- right to get copies of all the source code from which source software developers do follow is peer review, Linux and its associated tools were originally com- and they do that with a vengeance. Each piece of piled. There are no magical, mysterious binary files, source code is placed on display in front of a global although you can of course get the Linux system precompiled if you prefer.
    [Show full text]
  • A Library Oriented Wiki Engine (Talk)
    AmuseWiki: a library oriented wiki engine (talk) Marco Pessotto (melmothX) September 3, 2015, Granada . How does it look like? . Scenario Digital library with more than 2000 texts, including full-length books Long term archiving (not fire and forget texts), control revision Quality output required (read: LaTeX output) Imposing of PDF for home-printing EPUB output for mobile devices Preference for a flat file storage (like ikiwiki or MoinMoin) Creation of collections (like on mediawiki) One-man project . The lightweight markup No standard, even if Markdown seems to be the winner (but with dialects) Emacs Muse: project kind of dead, but the markup is compact and expressive, documented, and has a reference implementation. https://www.gnu.org/software/emacs-muse/ Some incompatibilities have been introduced, but they are documented (to address corner cases where the syntax can be confusing). Bottom line: all these markups are easy to use and it takes 5 minutes to learn one of them, as long as it is documented. Our own dialect of Emacs Muse Manual: http://www.amusewiki.org/library/manual Module: Text::Amuse (produces LaTeX and HTML) Ill-suited for technical papers, though. No math support, no syntax highlight, but well-suited for general prose and even poetry. It has every feature one could expect from a lightweight markup: images, sectioning, footnotes, simple tables, bold, italics, subscript, superscript, lists, verbatim, quotations. So far proved itself good and expressive. Importing Legacy library had the texts in filtered HTML People usually have the texts in Word format or copy and paste from HTML pages The javascript HTML editor CKEditor has a “paste from Word” feature http://ckeditor.com/ Need to convert the HTML to Muse, preserving as much as possible the logical structure of the document (and discarding the noise).
    [Show full text]
  • Organising Sysadmin Documentation Jon Dowland Information Systems and Services Newcastle University Overview
    organising sysadmin documentation Jon Dowland Information Systems and Services Newcastle University Overview • History and first attempt • Findings • Next generation • Conclusion History and first attempt Introduction • Newcastle University o ~4,800 staff; ~20,000 students • Information Systems and Services o ~160 people • Diverse ecosystem ISS UNIX Team small, 5 people widely varying age and experience responsibilities system administration and infrastructure higher-level (user-facing) services sister teams: networks, windows, SAP legacy systems Inherited situation directory full of text files categorization by directory lots of out-of-date information lots of undocumented stuff What do we keep in there? • Procedure documents • HOWTOs Existing experience • wikipedia editing • webteam-based mediawiki hosting service • version control (CVS, SVN) First-cut requirements • import existing data • support reviewing material • version control • online • multimedia • integrated with SSO Mediawiki Mediawiki • <http://www.mediawiki.org/> • powers wikipedia • LAMP • GPL (v2) • CMS SSO integration Shibboleth SSO software <http://shibboleth.internet2.edu/> mediawiki Shibboleth plugin <http://www.mediawiki.org/wiki/Extension:Shibboleth_Authentication> Apache configured with mod_shibd AuthType shibboleth ShibRequireSession On require eppn [email protected] ... Mediawiki markup • simple • proprietary Categories a tagging mechanism adding the following to the 'Sandbox' page [[Category: Example]] yields the page 'Category:Example' Importing data • one
    [Show full text]
  • Box Cover Design
    Debconf5 DVD v1.1 http://meetings-archive.debian.net/pub/debian-meetings/2005/debconf5/dvd/ Disc 1 28 OpenOffice.org in Debian 22 Structural Evolution Chris Halls and Rene Engelhard Bdale Garbee Debian Day, July 9th 29 Writing Enterprise-Ready 23 Ending Flamewars with 1 Greetings Martin-Éric Racine, Software Petter Reinholdtsen Polygen Enrico Zini Andreas Schuldei and 30 Linda – a Debian Package 24 Programs, Debconf, Man Branden Robinson Checker Written in Python Pages Translation Using 2 What is Debian? Jaldhar Vyas Steve Kowalik Gettext: a Tutorial 3 What is Free Software? 31 Securing the Testing Christian Perrier Gunnar Wolf Distribution Joey Hess 25 Debian-Edu – Upgrading a 4 Linux Aktivaattori Preconfigured CDD Martin-Éric Racine Disc 2 Petter Reinholdtsen 5 Custom Debian Distributions Sessions on July 14th Sessions on July 17th and Debian Derivatives 1 Shared Library Packaging Aigars Mahinovs 26 Next-Generation Debian (BOF) Junichi Uekawa Initscripts (round table) 6 From Pigs to Stripes: a 2 Ubuntu Mark Shuttleworth Henrique de Moraes Holschuh Travel Through Debian 3 Debian Website (round table) Juan Jose Amor 27 Debian Free Software Frank Lichtenheld 7 Debian Release Processes Guidelines (BOF) 4 Zen and the Art of Free Matthew Garrett Andreas Barth Software Enrico Zini 28 Volatile Archive for Debian 8 gnuLinEx Project 5 Autobuilding Experimental Dario Rapisardi and Pedro Pérez Andreas Barth Andreas Barth 29 Free Standards (BOF) 9 Getting Involved as an End 6 Debian Kernel Team Matt Taggart User Alexander Schmehl Overview and Status
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • The Cursor — Page 2 — June 18, 2011 Continued from Page 1 Bio: Stan Has Been Active with Personal Computers Behavior
    TThhee CCuurrssoorr Monthly Newsletter of the Washington Area Computer User Group Meeting Location: Next Meeting: OLLI, 4210 Roberts Road June 18, 2011 Fairfax, VA Presidential Bits by Geof Goodrum President, Washington Area Computer User Group In May, Paul Howard and Bill Walsh demonstrated the Skype videoconferencing and PC screen sharing system with help from Mel Mikosinki, Roger Fujii and others. Paul showed how the free Skype software (http://www.skype.com/) on a PC allowed several people to make video phone calls and have a meeting over the Internet and local network with tiled live video feeds from each. Several tips, though: invest in a good quality headset (headphone/microphone) to make PC Problem? video or phone calls; mute your microphone when you walk away from Bring it to the PC Clinic! your computer or don’t need to talk. Likewise, don’t forget that you are June 18 on “candid camera,” so mind your appearance and anything behind that you that might not want visible. And if you are doing a Skype demo Table of Contents with two systems in the same room with a speaker system like we Lloyd’s Web Sites...............2 were, definitely use headphones or mute your mikes – our apologies to User’s View of the iMac.....3 those who experienced the thrill of audio feedback when Mel joined the Linux News........................ 3 Skype video call with Paul across the room! GNU/Linux Distributions...4 The Skype demo was particularly timely, given Microsoft’s May 10th Linux Software...................5 announcement that it entered a deal to acquire Skype for an estimated Word Tips..........................
    [Show full text]