Making software-projects-successful-nicar-2013
Download as pptx, pdf2 likes4,371 views
The document discusses factors that contribute to the success of open source software projects based on research of 174,000 projects. Key factors included having a clearly defined vision and audience, modular design, and communication tools like websites and mailing lists. The research found that adding developers from other continents and enabling users to also be developers were surprising indicators of success. Project licensing and governance models mattered less. Overall, the research provided a framework for evaluating open source project success based on user adoption and continued development.
1 of 10
Downloaded 10 times
Ad
Recommended
Engineering Culture and Infrastructure
Engineering Culture and InfrastructureSchubert Zhang
?
The document discusses Google's engineering culture and infrastructure. It provides an overview of Google's practices around code review, team programming using tools like Gerrit, and the engineering pipeline. It also shares personal stories from software engineers and principles for balancing process with creativity.Osgeo incubation-2014
Osgeo incubation-2014Jody Garnett
?
The document outlines the OSGeo Foundation's incubation process for open source geospatial software projects, emphasizing its mission to support collaborative development and promote widespread use. It highlights key elements including community engagement, code safety, and available resources for projects, while encouraging participation without limiting options. Various committees and support mechanisms are presented to assist both new and existing projects in their development journey.Welcome to the FOSS4G Community
Welcome to the FOSS4G CommunityJody Garnett
?
The document welcomes participants to the FOSS4G community, emphasizing the importance of open data, open standards, and open source collaboration in geospatial software. It discusses the value of interoperability, community involvement, and various open source licenses that govern usage and distribution. The document also highlights the role of software foundations in providing governance and legal protection for open source projects.Open Source Impact on Digital Transformation
Open Source Impact on Digital TransformationHarsha Kumara
?
The document discusses the significance of open source in digital transformation, emphasizing its role in fostering integration agility, innovation, and quality software. It highlights how open source technologies enable organizations to rapidly adapt to changing market demands while avoiding the pitfalls of traditional proprietary solutions. Additionally, it underscores the collaborative nature of the open source community, which contributes to better security, transparency, extensibility, and customizability in software development.The Growing Research that Open Source Owns the Future in Cloud
The Growing Research that Open Source Owns the Future in CloudAll Things Open
?
The document discusses the increasing importance of open source software in cloud computing, highlighting its benefits for software developers, including enhanced skills, career growth, and improved product quality. A survey of developers reveals that skills related to open source technologies are seen as more beneficial than those linked to specific vendors, with a large majority preferring open source-based cloud platforms. IBM's findings and insights underscore the significant role that open source plays in innovation, community support, and competitive hiring in the tech industry.How open source is driving DevOps innovation: CloudOpen NA 2015
How open source is driving DevOps innovation: CloudOpen NA 2015Gordon Haff
?
The document discusses how open source principles drive innovation in DevOps by emphasizing automation, collaboration, and continuous integration and deployment workflows. It highlights the importance of culture in fostering trust and cooperation within organizations, as well as the role of various tools and governance models in supporting these practices. Open source not only contributes code but also provides guidance on leadership, transparency, and incentives that enhance DevOps efforts.What is open source?
What is open source?Ahmet Bulut
?
Open source refers to the process by which software is created, not the software itself. The open source process involves voluntary participation where anyone can contribute code freely and choose what tasks to work on. It relies on collaboration between many developers worldwide who are motivated to scratch an itch, avoid reinventing the wheel, solve problems in parallel, and leverage the law of large numbers through continuous beta testing. Documentation and frequent releases are also important aspects of open source development.Experiences with the Apache Software Foundation
Experiences with the Apache Software Foundation marpierc
?
The document discusses strategies for sustainable software development, emphasizing the Apache Software Foundation as a model for improving academic software longevity. It outlines essential elements for sustainable software, including community support, project management, and open licensing. Additionally, it provides guidance on initiating projects within the Apache incubator and stresses the importance of connections within the Apache community.Open source technology, freeware drone (by Joris Kr¨¹se)
Open source technology, freeware drone (by Joris Kr¨¹se)Verhaert Masters in Innovation
?
This document discusses the impact of open source technology in innovation, particularly in fields like 3D printing, robotics, and unmanned systems. It highlights various initiatives and companies, such as Arduino and Sparkfun, that are leveraging open hardware for rapid product development and community engagement. Additionally, it mentions the importance of co-creation and DIY learning experiences in fostering an innovative environment.The Agile and Open Source Way (AgileTour Brussels)
The Agile and Open Source Way (AgileTour Brussels)Alexis Monville
?
The document discusses the integration of Agile methodologies with open source software development, emphasizing principles such as customer satisfaction, collaboration, and responsiveness to change. It outlines the Agile manifesto, contrasting it with open source practices, which allow for shared code and community contributions. Additionally, the document describes the OpenStack project and its structured six-month release cycle, alongside the role of technical leads and community participation in the development process.Expertise in Software Development
Expertise in Software DevelopmentQAware GmbH
?
The document outlines Dr. Sebastian Baltes' expertise in software development and its implications for understanding code plagiarism and expertise development among software developers. It discusses the characteristics that distinguish expert software developers, factors affecting expertise development, and findings from surveys regarding code attribution practices on platforms like Stack Overflow. The document also provides recommendations for developers and employers to foster a supportive work environment that enhances motivation and expertise.Bringing Commercial Software to Open Source
Bringing Commercial Software to Open SourceAll Things Open
?
The document outlines strategies for transitioning commercial software to open source, emphasizing key decisions regarding ownership, licensing, and governance models. It details Pivotal's experience with open source projects, including Apache Geode and HAWQ, while presenting various business models for open source software. Additionally, it highlights case studies, including those of Sun Microsystems and Pivotal, and discusses the importance of intellectual property management and community engagement in open source development.Open-Source Software Panel - IP Track
Open-Source Software Panel - IP TrackAaron G. Sauers, CLP
?
The document discusses open source software (OSS) and its implications for the scientific and industrial communities, focusing on copyright, licensing types, and security risks associated with OSS. It highlights a governmental OSTP memo aimed at increasing transparency and efficiency through the use of OSS in federal agencies, particularly in software development. The presentation reinforces the necessity for labs and organizations to adapt to the growing prevalence of OSS and the associated challenges in maintaining code quality and compliance.Lyra Infosystems - GitLab Overview Deck 2020
Lyra Infosystems - GitLab Overview Deck 2020Lyra Infosystems Pvt. Ltd
?
Lyra Infosystems is a technology services and IT consulting company based in Bangalore, focusing on areas such as software composition analysis and DevOps. They are authorized partners of GitLab in India and ASEAN, and aim to enhance businesses' performance through complete DevOps solutions, automating the software development lifecycle. Their offerings facilitate collaboration among developers and operators, driving better customer experiences and faster release cycles, all integrated under a single platform.The Aspects of Choosing Open Source Versus Closed Source
The Aspects of Choosing Open Source Versus Closed SourceJeet Prakash
?
The document discusses open source and closed source software development. Open source software is developed by a distributed network of individuals contributing voluntarily, while closed source refers to proprietary software owned and developed by a single entity. The key advantages of open source include more contributors improving quality and fixing bugs, as well as users having the freedom to modify software for their needs. However, open source also faces challenges of coordination, lack of obligation for developers to remain with a project, and difficulties providing support and updates.Building software: the lessons from open source
Building software: the lessons from open sourceArnaud Porterie
?
This document summarizes Arnaud Porterie's presentation on lessons from open source for building software. Some key points include:
- Open source projects follow patterns of "wise crowds" like having a strong mission, free entry for contributors, transparency, and fair authority to scale effectively.
- These patterns can help improve closed source software development by fostering greater collective intelligence within companies.
- Applying concepts like inner source allows companies to benefit from open source practices internally by opening codebases and encouraging cross-team contributions under shared maintainers.
- A practical checklist is proposed for implementing inner source based on principles like giving all employees access to code, having documented missions and contribution processes, and enforcing consistent processes.Go Faster - Remove Inhibitors to Rapid Innovation
Go Faster - Remove Inhibitors to Rapid InnovationFred George
?
The document discusses the evolution and competitive landscape of technology in software development, focusing on microservices, cloud computing, and agile methodologies. It emphasizes the need for rapid iteration, innovation, and organizational change to keep pace with modern business demands and competition. Key insights include the importance of using disruptive technologies, decentralized processes, and appropriate metrics for measuring success.Next-gen IDE v2 - OpenSlava 2013-10-11
Next-gen IDE v2 - OpenSlava 2013-10-11Jorge Hidalgo
?
The document is a presentation by Jorge Hidalgo discussing the importance and evolution of Integrated Development Environments (IDEs) for various types of developers, including newbies, enterprise developers, and hardcore developers. It highlights the current capabilities and wish-list improvements for IDEs, such as better documentation, collaboration tools, and cloud support. The takeaway emphasizes mastering IDEs to enhance coding productivity, quality, and learning across all development phases.intro to DevOps
intro to DevOpsMujahed Al-Tahle
?
This document provides an introduction to DevOps including:
- A brief history of DevOps from 2007-2011 when the term was coined and practices began emerging.
- Definitions of DevOps focusing on bridging development and operations teams and delivering software faster.
- Why DevOps is used, particularly for large distributed applications, to increase delivery speed and reduce failures.
- Key DevOps principles of automation, continuous delivery, and measuring outcomes.
- Common DevOps practices like infrastructure as code, containerization, microservices, and cloud infrastructure.Hydra Project Management Survey
Hydra Project Management SurveyMark Notess
?
The survey results show that Hydra projects have an average team size of 6 people. Agile Scrum is the most commonly used methodology. Jira and GitHub are popular tools for managing requirements and source control. The main benefits of Hydra cited are the active community for sharing knowledge and best practices, and the reusable technology including Ruby on Rails and Fedora. The biggest challenges are obtaining resources and avoiding technical debt as the software evolves.Agile Upstream and Downstream Webinar - English
Agile Upstream and Downstream Webinar - EnglishCollabNet
?
The document presents an overview of CollabNet's approach to achieving enterprise agility through agile upstream and downstream practices, facilitated by their TeamForge platform. It outlines the challenges companies face in scaling agile, as well as the essential practices necessary for integration, continuous delivery, and collaboration across teams. Additionally, it emphasizes the importance of culture change in implementing agile methodologies effectively.Agile Offsharing: Using Pair Work to Overcome Nearshoring Difficulties
Agile Offsharing: Using Pair Work to Overcome Nearshoring DifficultiesMobileSolutionsDTAG
?
This document discusses using distributed pair programming (DPP) to overcome challenges with nearshoring software development. It proposes "Agile Offshoring" which maximizes cross-site communication through DPP instead of separating technical work by location. Key steps include finding pairing volunteers, establishing technical infrastructure like Saros for distributed editing, arranging knowledge transfer tasks between pairs, and refining the process through reflection. Research shows competent pairs can work fluently with DPP and it facilitates knowledge transfer, though awareness limitations must be addressed. The approach was deemed plausible by experts and is being evaluated further.Creating and Maintaining an Open Source Library
Creating and Maintaining an Open Source LibraryNicholas Schweitzer
?
The document outlines best practices for creating and maintaining open source libraries, emphasizing the importance of code quality, documentation, and project management. It highlights considerations for consumers, such as active development, unit testing, and maintaining clear documentation, while also detailing necessary tools and services for versioning, CI/CD, and licensing. Additionally, the document provides guidance on project communication and encouraging contributions, along with specific examples of successful open source projects.SIM RTP Meeting - So Who's Using Open Source Anyway?
SIM RTP Meeting - So Who's Using Open Source Anyway?Alex Meadows
?
The document details a meeting about the use of open source software, including its history, philosophy, and various business models. It highlights the increasing adoption of open source in companies, the benefits it offers, and the skills needed in the workforce. Panel discussions also address challenges, community engagement, and the impact of open source on future technology trends.Software Craftsmanship VS Software Engineering
Software Craftsmanship VS Software EngineeringAndy Maleh
?
Software craftsmanship and software engineering both aim to deliver high-quality, reliable software, but differ in their approaches. Software engineering focuses on macro goals and processes, while craftsmanship emphasizes mastering skills through experience. Both are used at Groupon, where engineering practices like architecture, testing and iteration are combined with craftsmanship techniques including apprenticeships and pair programming.Agile Software Development and DevOps 21092019
Agile Software Development and DevOps 21092019Ahmed Misbah
?
This document provides an overview of Agile software development and DevOps. It begins with an introduction to software engineering principles. It then covers Agile concepts like values, principles and methods including Scrum, Kanban, and lean. Scrum roles, artifacts, and events are defined. Kanban and lean concepts like limiting work in progress and value streams are explained. Finally, DevOps is introduced as the convergence of development and operations to enable continuous delivery through automation. The document aims to give attendees a foundation in Agile and DevOps best practices for software development.DevOps Patterns Distilled: Implementing The Needed Practices In Practical Steps
DevOps Patterns Distilled: Implementing The Needed Practices In Practical StepsCA Technologies
?
The document discusses the importance of DevOps practices and methodologies in accelerating adoption and improving outcomes in IT organizations. It highlights key strategies, such as enhancing cooperation between development and operations, implementing continuous integration and deployment, and fostering a culture of experimentation and feedback. The author, Gene Kim, emphasizes that high-performing organizations can achieve significant improvements in deployment frequency, reliability, and overall business outcomes.Application Security Epistemology in a Continuous Delivery World
Application Security Epistemology in a Continuous Delivery WorldJames Wickett
?
The document discusses the integration of application security within the context of DevOps, emphasizing that security practices should evolve similarly to operational practices over the past years. It identifies three key approaches to enhancing security: at development, during deployment, and at runtime, while also highlighting the importance of culture and collaboration among developers and security teams. The author argues for a shift from traditional security practices to more agile, telemetry-driven methods that improve resilience and accountability in software development.Patent US20100045425 - data transmission of sensors - Google Patents
Patent US20100045425 - data transmission of sensors - Google PatentsLaurent Chivallier
?
This patent application describes a method for securely transmitting data between a sensor module and a mobile device. The method involves authenticating the sensor module using the mobile device by comparing security keys stored on each. It then establishes communication between the devices and securely transmits data from the sensor module to the mobile device once authentication is complete by matching the security keys. The application also describes a system for carrying out this secure data transmission method between a sensor and mobile device.More Related Content
What's hot (20)
Open source technology, freeware drone (by Joris Kr¨¹se)
Open source technology, freeware drone (by Joris Kr¨¹se)Verhaert Masters in Innovation
?
This document discusses the impact of open source technology in innovation, particularly in fields like 3D printing, robotics, and unmanned systems. It highlights various initiatives and companies, such as Arduino and Sparkfun, that are leveraging open hardware for rapid product development and community engagement. Additionally, it mentions the importance of co-creation and DIY learning experiences in fostering an innovative environment.The Agile and Open Source Way (AgileTour Brussels)
The Agile and Open Source Way (AgileTour Brussels)Alexis Monville
?
The document discusses the integration of Agile methodologies with open source software development, emphasizing principles such as customer satisfaction, collaboration, and responsiveness to change. It outlines the Agile manifesto, contrasting it with open source practices, which allow for shared code and community contributions. Additionally, the document describes the OpenStack project and its structured six-month release cycle, alongside the role of technical leads and community participation in the development process.Expertise in Software Development
Expertise in Software DevelopmentQAware GmbH
?
The document outlines Dr. Sebastian Baltes' expertise in software development and its implications for understanding code plagiarism and expertise development among software developers. It discusses the characteristics that distinguish expert software developers, factors affecting expertise development, and findings from surveys regarding code attribution practices on platforms like Stack Overflow. The document also provides recommendations for developers and employers to foster a supportive work environment that enhances motivation and expertise.Bringing Commercial Software to Open Source
Bringing Commercial Software to Open SourceAll Things Open
?
The document outlines strategies for transitioning commercial software to open source, emphasizing key decisions regarding ownership, licensing, and governance models. It details Pivotal's experience with open source projects, including Apache Geode and HAWQ, while presenting various business models for open source software. Additionally, it highlights case studies, including those of Sun Microsystems and Pivotal, and discusses the importance of intellectual property management and community engagement in open source development.Open-Source Software Panel - IP Track
Open-Source Software Panel - IP TrackAaron G. Sauers, CLP
?
The document discusses open source software (OSS) and its implications for the scientific and industrial communities, focusing on copyright, licensing types, and security risks associated with OSS. It highlights a governmental OSTP memo aimed at increasing transparency and efficiency through the use of OSS in federal agencies, particularly in software development. The presentation reinforces the necessity for labs and organizations to adapt to the growing prevalence of OSS and the associated challenges in maintaining code quality and compliance.Lyra Infosystems - GitLab Overview Deck 2020
Lyra Infosystems - GitLab Overview Deck 2020Lyra Infosystems Pvt. Ltd
?
Lyra Infosystems is a technology services and IT consulting company based in Bangalore, focusing on areas such as software composition analysis and DevOps. They are authorized partners of GitLab in India and ASEAN, and aim to enhance businesses' performance through complete DevOps solutions, automating the software development lifecycle. Their offerings facilitate collaboration among developers and operators, driving better customer experiences and faster release cycles, all integrated under a single platform.The Aspects of Choosing Open Source Versus Closed Source
The Aspects of Choosing Open Source Versus Closed SourceJeet Prakash
?
The document discusses open source and closed source software development. Open source software is developed by a distributed network of individuals contributing voluntarily, while closed source refers to proprietary software owned and developed by a single entity. The key advantages of open source include more contributors improving quality and fixing bugs, as well as users having the freedom to modify software for their needs. However, open source also faces challenges of coordination, lack of obligation for developers to remain with a project, and difficulties providing support and updates.Building software: the lessons from open source
Building software: the lessons from open sourceArnaud Porterie
?
This document summarizes Arnaud Porterie's presentation on lessons from open source for building software. Some key points include:
- Open source projects follow patterns of "wise crowds" like having a strong mission, free entry for contributors, transparency, and fair authority to scale effectively.
- These patterns can help improve closed source software development by fostering greater collective intelligence within companies.
- Applying concepts like inner source allows companies to benefit from open source practices internally by opening codebases and encouraging cross-team contributions under shared maintainers.
- A practical checklist is proposed for implementing inner source based on principles like giving all employees access to code, having documented missions and contribution processes, and enforcing consistent processes.Go Faster - Remove Inhibitors to Rapid Innovation
Go Faster - Remove Inhibitors to Rapid InnovationFred George
?
The document discusses the evolution and competitive landscape of technology in software development, focusing on microservices, cloud computing, and agile methodologies. It emphasizes the need for rapid iteration, innovation, and organizational change to keep pace with modern business demands and competition. Key insights include the importance of using disruptive technologies, decentralized processes, and appropriate metrics for measuring success.Next-gen IDE v2 - OpenSlava 2013-10-11
Next-gen IDE v2 - OpenSlava 2013-10-11Jorge Hidalgo
?
The document is a presentation by Jorge Hidalgo discussing the importance and evolution of Integrated Development Environments (IDEs) for various types of developers, including newbies, enterprise developers, and hardcore developers. It highlights the current capabilities and wish-list improvements for IDEs, such as better documentation, collaboration tools, and cloud support. The takeaway emphasizes mastering IDEs to enhance coding productivity, quality, and learning across all development phases.intro to DevOps
intro to DevOpsMujahed Al-Tahle
?
This document provides an introduction to DevOps including:
- A brief history of DevOps from 2007-2011 when the term was coined and practices began emerging.
- Definitions of DevOps focusing on bridging development and operations teams and delivering software faster.
- Why DevOps is used, particularly for large distributed applications, to increase delivery speed and reduce failures.
- Key DevOps principles of automation, continuous delivery, and measuring outcomes.
- Common DevOps practices like infrastructure as code, containerization, microservices, and cloud infrastructure.Hydra Project Management Survey
Hydra Project Management SurveyMark Notess
?
The survey results show that Hydra projects have an average team size of 6 people. Agile Scrum is the most commonly used methodology. Jira and GitHub are popular tools for managing requirements and source control. The main benefits of Hydra cited are the active community for sharing knowledge and best practices, and the reusable technology including Ruby on Rails and Fedora. The biggest challenges are obtaining resources and avoiding technical debt as the software evolves.Agile Upstream and Downstream Webinar - English
Agile Upstream and Downstream Webinar - EnglishCollabNet
?
The document presents an overview of CollabNet's approach to achieving enterprise agility through agile upstream and downstream practices, facilitated by their TeamForge platform. It outlines the challenges companies face in scaling agile, as well as the essential practices necessary for integration, continuous delivery, and collaboration across teams. Additionally, it emphasizes the importance of culture change in implementing agile methodologies effectively.Agile Offsharing: Using Pair Work to Overcome Nearshoring Difficulties
Agile Offsharing: Using Pair Work to Overcome Nearshoring DifficultiesMobileSolutionsDTAG
?
This document discusses using distributed pair programming (DPP) to overcome challenges with nearshoring software development. It proposes "Agile Offshoring" which maximizes cross-site communication through DPP instead of separating technical work by location. Key steps include finding pairing volunteers, establishing technical infrastructure like Saros for distributed editing, arranging knowledge transfer tasks between pairs, and refining the process through reflection. Research shows competent pairs can work fluently with DPP and it facilitates knowledge transfer, though awareness limitations must be addressed. The approach was deemed plausible by experts and is being evaluated further.Creating and Maintaining an Open Source Library
Creating and Maintaining an Open Source LibraryNicholas Schweitzer
?
The document outlines best practices for creating and maintaining open source libraries, emphasizing the importance of code quality, documentation, and project management. It highlights considerations for consumers, such as active development, unit testing, and maintaining clear documentation, while also detailing necessary tools and services for versioning, CI/CD, and licensing. Additionally, the document provides guidance on project communication and encouraging contributions, along with specific examples of successful open source projects.SIM RTP Meeting - So Who's Using Open Source Anyway?
SIM RTP Meeting - So Who's Using Open Source Anyway?Alex Meadows
?
The document details a meeting about the use of open source software, including its history, philosophy, and various business models. It highlights the increasing adoption of open source in companies, the benefits it offers, and the skills needed in the workforce. Panel discussions also address challenges, community engagement, and the impact of open source on future technology trends.Software Craftsmanship VS Software Engineering
Software Craftsmanship VS Software EngineeringAndy Maleh
?
Software craftsmanship and software engineering both aim to deliver high-quality, reliable software, but differ in their approaches. Software engineering focuses on macro goals and processes, while craftsmanship emphasizes mastering skills through experience. Both are used at Groupon, where engineering practices like architecture, testing and iteration are combined with craftsmanship techniques including apprenticeships and pair programming.Agile Software Development and DevOps 21092019
Agile Software Development and DevOps 21092019Ahmed Misbah
?
This document provides an overview of Agile software development and DevOps. It begins with an introduction to software engineering principles. It then covers Agile concepts like values, principles and methods including Scrum, Kanban, and lean. Scrum roles, artifacts, and events are defined. Kanban and lean concepts like limiting work in progress and value streams are explained. Finally, DevOps is introduced as the convergence of development and operations to enable continuous delivery through automation. The document aims to give attendees a foundation in Agile and DevOps best practices for software development.DevOps Patterns Distilled: Implementing The Needed Practices In Practical Steps
DevOps Patterns Distilled: Implementing The Needed Practices In Practical StepsCA Technologies
?
The document discusses the importance of DevOps practices and methodologies in accelerating adoption and improving outcomes in IT organizations. It highlights key strategies, such as enhancing cooperation between development and operations, implementing continuous integration and deployment, and fostering a culture of experimentation and feedback. The author, Gene Kim, emphasizes that high-performing organizations can achieve significant improvements in deployment frequency, reliability, and overall business outcomes.Application Security Epistemology in a Continuous Delivery World
Application Security Epistemology in a Continuous Delivery WorldJames Wickett
?
The document discusses the integration of application security within the context of DevOps, emphasizing that security practices should evolve similarly to operational practices over the past years. It identifies three key approaches to enhancing security: at development, during deployment, and at runtime, while also highlighting the importance of culture and collaboration among developers and security teams. The author argues for a shift from traditional security practices to more agile, telemetry-driven methods that improve resilience and accountability in software development.Viewers also liked (18)
Patent US20100045425 - data transmission of sensors - Google Patents
Patent US20100045425 - data transmission of sensors - Google PatentsLaurent Chivallier
?
This patent application describes a method for securely transmitting data between a sensor module and a mobile device. The method involves authenticating the sensor module using the mobile device by comparing security keys stored on each. It then establishes communication between the devices and securely transmits data from the sensor module to the mobile device once authentication is complete by matching the security keys. The application also describes a system for carrying out this secure data transmission method between a sensor and mobile device.ÃÀ‡ø»¥Â“¾WÚ…„ݼ°Œ¦Ì¨ž³Åc´óê‘Web 20®a˜IÖ®Ó°í‘
ÃÀ‡ø»¥Â“¾WÚ…„ݼ°Œ¦Ì¨ž³Åc´óê‘Web 20®a˜IÖ®Ó°í‘mr65210
?
¸ÃÎĵµÌÖÂÛÁË2008-2009ÄêÃÀ¹ú»¥ÁªÍøÇ÷ÊƼ°Æä¶Ǫ̂ÍåºÍ´ó½Web 2.0²úÒµµÄÓ°Ïì¡£Ëü·ÖÎöÁËÖڶ໥ÁªÍø¹«Ë¾ºÍ´´ÒµÕߵľÀú£¬ÒÔ¼°Web 2.0µÄÌØÐÔºÍÌôÕ½£¬Ç¿µ÷Éç½»ÍøÂçµÄÁ¦Á¿ÓëÊг¡Ç±Á¦¡£ÎÄÖл¹Ìá¼°ÁËÈ«Çò»¥ÁªÍøÓû§µÄ¶Ô±ÈÒÔ¼°³É¹¦°¸ÀýºÍÓªÏú²ßÂÔ¡£Com¨¦rcio InternacionalJane34
?
O documento fornece um resumo sobre conceitos b¨¢sicos de com¨¦rcio internacional, incluindo acordos internacionais, institui??es intervenientes no Brasil, classifica??o de mercadorias, modalidades de opera??o, transporte internacional, importa??o, exporta??o e outros t¨®picos. As principais institui??es mencionadas s?o o Conselho Monet¨¢rio Nacional, a C?mara de Com¨¦rcio Exterior e o Banco Central do Brasil.Measuring digital success with web and social analytics (Local Media Assn., M...
Measuring digital success with web and social analytics (Local Media Assn., M...Rich Gordon
?
The document discusses key performance indicators (KPIs) that publishers should track to measure their online performance. It recommends tracking visits, new visits as a percentage of total visits to measure loyalty, and pages per visit to measure engagement. Other proposed KPIs include traffic sources like search, referral, social media and the number of pageviews from each. Social media metrics like followers, likes and engagement on Facebook and Twitter are also important. Consistently measuring and aligning KPIs to business goals can help publishers improve online performance over time.Logros promocionales de matematicasandavipe
?
El documento contiene los logros alcanzados por los estudiantes de primero a und¨¦cimo grado en las asignaturas de matem¨¢ticas, geometr¨ªa y estad¨ªstica durante el a?o escolar. Para cada asignatura y grado, eval¨²a si el estudiante alcanz¨® todos los logros, la mayor¨ªa de los logros, algunos logros con dificultad o no alcanz¨® los logros propuestos.Ad
Similar to Making software-projects-successful-nicar-2013 (20)
Practical Open Source Software for Libraries (part 1)
Practical Open Source Software for Libraries (part 1)Nicole C. Engard
?
The document discusses practical open source software options for libraries, providing examples of open source operating systems like Ubuntu and Qimo for Kids that can be used for patron computers, as well as virtual machines, email clients like Thunderbird, and web browsers like Firefox that offer security and customization benefits over proprietary alternatives. Concerns about open source are addressed, noting that with support options and no greater risks, libraries are a natural fit for open source software.Software recycling
Software recyclingAristotle University of Thessaloniki
?
The document presents an overview of software recycling, focusing on the Open-SME project, which aims to enhance the reuse of open-source software for small and medium-sized enterprises (SMEs) through various tools and techniques. It discusses the current inefficiencies in the software industry regarding the use of closed source applications and highlights the potential benefits and challenges of software recycling. The Open-SME initiative seeks to provide a structured approach to identifying, adapting, and integrating open-source components into new software systems by establishing a service operated by SME associations.Open source evolution analysis
Open source evolution analysisIzzat Alsmadi
?
This document discusses analyzing open source code evolution using source code metrics. It describes developing a tool to gather metrics from C/C++, C#, and Java source codes. The tool is used to analyze selected open source projects, studying their release evolutions and comparing characteristics between releases and across projects. Different programming languages and development styles are examined.Providing Services to our Remote Users: Open Source Solutions
Providing Services to our Remote Users: Open Source SolutionsNicole C. Engard
?
This document discusses open source solutions that can be used to provide services to remote library users. It begins with an outline and definitions of open source software. It then discusses specific open source products that libraries commonly use, including content management systems like Drupal, Joomla and WordPress, as well as communication tools, media tools and library applications. Examples of library applications mentioned include the Blacklight OPAC. Throughout it addresses common concerns about open source software and provides statistics on open source use.Intro to open_source
Intro to open_sourceShiwang Kalkhanda
?
The document provides a comprehensive overview of open source software, its history, and its significance in modern technology. It traces the evolution of open source from its academic origins in the 1960s to its popularization in the late 1990s, highlighting key projects like the GNU and Linux. The text emphasizes the importance of participation in open source through contributions and outlines various categories including open software, open hardware, and open content.Foss final seminar
Foss final seminarSmit Patil
?
The document discusses the history and development of free and open source software (FOSS). It describes how early software was freely shared among academic institutions and companies. Richard Stallman founded the GNU project in 1983 to develop free software and started the free software movement. Linux, developed by Linus Torvalds, expanded interest in FOSS using an open "bazaar" development model. Eric Raymond's 1997 essay promoted this decentralized model and helped popularize Linux. The document also outlines India's support for FOSS through initiatives like the National Resource Center for Free and Open Source Software.Foss final seminar
Foss final seminarSmit Patil
?
The document discusses the evolution of software from early computers, emphasizing the shift from a collaborative, open-source culture to proprietary models, particularly through the influence of Richard Stallman and Linus Torvalds. It contrasts the 'cathedral' and 'bazaar' development models, highlighting how open development increases bug-fixing efficiency and encourages community involvement in software creation. It also notes the rise of free and open source software (FOSS) in various countries and its impact on the economy and public sector.Perspectives on Open
Perspectives on OpenTim O'Reilly
?
This document discusses openness and open source principles. It provides examples of how O'Reilly Media has helped spread knowledge about new technologies. It discusses key open source concepts like free software, the Cathedral and the Bazaar development model, and the architecture of participation enabled by Unix and the Internet. It argues that to be successful, online education should embrace open source principles like using commodity components, providing customization, developing in public, and having an architecture that allows community participation.Open Source, Sourceforge Projects, & Apache Foundation
Open Source, Sourceforge Projects, & Apache FoundationMohammad Kotb
?
The document discusses open source software and SourceForge. It provides definitions of open source, describes the four freedoms of open source software, and discusses licenses like the GNU GPL. It also discusses SourceForge as a source code repository and hosting platform for open source projects, including its features and history. Alternative platforms like Tigris.org, RubyForge and JavaForge are also briefly mentioned.Free Libre Open Source Software - Business Aspects of Software Industry
Free Libre Open Source Software - Business Aspects of Software IndustryFrederik Questier
?
This document provides an overview of a presentation about free libre open source software (FLOSS). The presentation discusses the ethics of software freedom, different software and development models, and various business models for FLOSS. It provides examples of successful FLOSS projects like Linux, Firefox, OpenOffice, Drupal, and others. The presentation addresses why FLOSS is not used more widely and argues that its total cost of ownership can be lower than closed source software.The Development of Open Source E-Learning Environments: the Chamilo Experience
The Development of Open Source E-Learning Environments: the Chamilo ExperienceFrederik Questier
?
The document discusses the evolution of open source e-learning platforms, particularly focusing on the Chamilo experience and the significance of free and open source software (FLOSS) in education. It outlines the historical context, development strategies, community engagement, and the competitive advantages of transitioning from proprietary systems to open source solutions. Key insights include the importance of collaboration and user involvement in the development process and the potential for educational institutions to innovate through shared resources.Open Source Software for Entertainment
Open Source Software for Entertainmentletiziajaccheri
?
The document summarizes an ICEC2012 tutorial on open source software for entertainment. The tutorial covered inspiration from art and technology, open source software tools like Processing and Arduino, and experiences running maker workshops. The goal was to inspire participants to experience open software practices and tools through creative sessions divided into technical, artistic, and open sub-goals. Participants would cooperate, learn new media prototyping tools, and explore the relationship between open source software and entertainment. The intended audience was software engineers, researchers, and PhD students interested in creative technologies and processes.Libraries Developing Openly
Libraries Developing OpenlyNicole C. Engard
?
This document summarizes Nicole Engard's presentation on libraries developing openly with open source software. She discusses key concepts of open source like collaborative development, transparency, and community contribution. Engard advocates that libraries should create open source solutions from the start to benefit from peer review. She provides examples of successful library open source projects like Blacklight, Koha and Evergreen that were developed through community collaboration.Open Source, Sourceforge Projects, & Apache Foundation
Open Source, Sourceforge Projects, & Apache FoundationMohammad Kotb
?
The document discusses open source software, emphasizing the freedoms associated with access to source code, including the ability to use, modify, and distribute software. It highlights SourceForge as a key repository for open source projects and presents the Apache Software Foundation as a significant player in the open source community. Various version control systems, such as CVS and Subversion, are also introduced, emphasizing their role in collaborative software development.Financing Freedom ºÝºÝߣs - Final
Financing Freedom ºÝºÝߣs - FinalMis Tribus
?
This document discusses strategies for organizing and funding free culture projects. It notes that many free culture projects fail due to a lack of resources. By focusing on raising funds through methods like donations, merchandise, and grants, projects can increase their chances of survival. Successful foundations and projects employ modern internet marketing strategies to build communities and attract financial support through various channels like websites, email, conferences, and social media.Open Source for an Open World
Open Source for an Open WorldElizabeth Thomsen
?
The document discusses open source software and its benefits and challenges. It notes that while software development is difficult due to problems like incomplete testing and user errors, open source software relies on collaborative communities to tackle these issues. Open source emerged from hacker cultures in the 1960s-70s and businesses now contribute to and use open source projects. The document predicts that open source library systems will become more viable options for libraries in the next two years.GoOpen 2010: Reidar Conradi
GoOpen 2010: Reidar ConradiFriprogsenteret
?
1. The document discusses cross-disciplinary challenges in open source software (OSS). It provides background on the IDI Department at NTNU, which conducts research related to OSS.
2. Traditional software reuse within companies is compared to the OSS phenomenon, which enables distributed and cooperative innovation on a global scale. Selection of OSS components and classification schemes are challenging due to the diversity of projects and lack of standardized information.
3. Effective use of OSS requires new models for cooperation between organizations in software development. The linear development model is being replaced by a more networked model with interdependent projects and components.Why FLOSS is a Java developer's best friend: Dave Gruber
Why FLOSS is a Java developer's best friend: Dave GruberJAX London
?
The document outlines the landscape of open-source software (OSS), detailing the number of repositories and projects across various platforms such as GitHub and SourceForge. It emphasizes the importance of project activity and maintenance, finding that less than 5% of analyzed projects are considered 'live' with ongoing contributions. Additionally, it discusses best practices for evaluating OSS projects, the benefits of inner sourcing, and the necessity for organizations to actively contribute back to the community to enhance the sustainability and evolution of OSS.Open Source: Freedom and Community
Open Source: Freedom and CommunityNicole C. Engard
?
This document discusses open source software and its relevance to libraries. It provides an overview of open source, including definitions of open source and free software. It addresses common misconceptions about open source. The document outlines benefits of open source like collaboration, transparency, and cost savings. It discusses how open source is widely used in business, government, and education. Finally, it addresses how open source aligns with library values and how libraries can get involved with open source.Open.source.innovation.20070624
Open.source.innovation.20070624Vu Hung Nguyen
?
This document summarizes key aspects of free and open source software (FOSS). It defines FOSS and provides examples like Linux, Eclipse, and Firefox. It describes FOSS processes as globally collaborative with distributed development and iterative releases. FOSS technologies allow for fast innovation through community testing and contributions to new topics. FOSS quality benefits from source code availability and review as well as free testing. FOSS architectures are evolutionary and modularize components. Successful FOSS business models offer services around packaging, support, customization and refactoring of open source projects.Ad
Making software-projects-successful-nicar-2013
- 1. How can we get the widest impact out of software projects? NICAR 2013 Rich Gordon
- 2. The problem: much code is never re-used Dan Schultz We keep reinventing the wheel. ¡°Wouldn't it be nice if all these new wheels could Alberto Ibarguen be used again and "We want to see actual improved upon use with actual readers over time?¡± in actual communities with sustainability." ? Rich Gordon | Knight Lab, Northwestern University 2013
- 3. How can we measure the success of a software project? ? Key question: Do end users make use of it? ? Metrics: ¨C Downloads ¨C Installations ¨C Continued development activity ¨C Posts to project discussion boards/email lists ¨C Addition of one or more developers ¨C Releases beyond initial version ¨C Buzz /attention / high-profile successes ? Rich Gordon | Knight Lab, Northwestern University 2013
- 4. They wrote the book on open-source success ? Studied 174,000 projects shared on Charles SourceForge Schweik ? Surveyed 1,400 open source developers ? Success = 3+ releases, value for ¡°at least Robert English a few users¡± Open source projects: Success vs. abandonment Could assess success vs. abandonment 83,694 Abandoned: initiation stage (pre-1st release) 37,320 44.6% Abandoned: growth stage 30,592 36.6% Success 15,782 18.9% ? Rich Gordon | Knight Lab, Northwestern University 2013
- 5. The framework for evaluating success ? Rich Gordon | Knight Lab, Northwestern University 2013
- 6. What matters: Schweik / English research ? Clearly defined vision Charles ? Clearly defined audience Schweik ? Well-articulated and clear goals ? Modular software design Robert English ? Tasks of various sizes are available for developers to work on ? Rich Gordon | Knight Lab, Northwestern University 2013
- 7. What matters: Schweik / English research ? Good project communication ¨C A good website Charles Schweik ¨C Bug-tracking system ¨C Email list, forum or other communication system Robert English ¨C Documentation ? Developers are users, too: ¡°Developers participate because they themselves are users of the software or because the organization they work for depends on it.¡± ? Rich Gordon | Knight Lab, Northwestern University 2013
- 8. The biggest surprise: Schweik / English research ? When a project added a developer ¡ Charles 58% of the added developers were on Schweik a different continent than the lead developer Robert ? The Internet has enabled ¡°intellectual English matchmaking¡± ? ¡°Regardless of where a programmer lives in the world, people can find software projects¡± related to their needs. ? Rich Gordon | Knight Lab, Northwestern University 2013
- 9. What doesn¡¯t matter: Schweik / English research ? Which operating system the code Charles was written for Schweik ? How many developers were involved Robert English ? Formalized governance system ¨C Most open-source projects are small (not like Linux) ? Which open-source license was used ? Rich Gordon | Knight Lab, Northwestern University 2013
- 10. Different forms of open-source licenses ¡°Copyleft¡± licenses ¡°Non-copyleft¡± licenses (open-source restrictions are passed on with the code) (restrictions not passed on) Athero Public GPL GPL LGPL MPL Apache BSD/MIT domain GPL applies Copyleft applies Copyleft applies File-level copyleft; ¡°Do what you like, even if you to entire application; to software ¡°library¡±; common for don¡¯t sue us; ¡°Do what you like, interact with if application the problem, browser software. if you contribute don¡¯t sue us¡± the code remotely contains GPL code especially If you incorporate code patented code (and don¡¯t you must release for JS projects, is into a new file, you can to the project, incorporate in source code defining what a keep those changes we can use it, your code) (not just binaries) ¡°library¡± is to yourself too under GPL As you move toward the left of this graph, the restrictions on commercial use become tighter; toward the right, limitations are removed until you get to ¡°public domain¡¯ ¨C code anyone can use without restriction ? Rich Gordon | Knight Lab, Northwestern University 2013