Documentation Practices in Open Source – A Study of Apache Derby Master’s Thesis

合集下载

最新pda技术报告

最新pda技术报告：报告最新技术p da pda技术报告清单2016 pda技术报告是什么pda技术报告灭菌决策树篇一：PDA技术报告清单2015PDA技术报告清单（官网2015年更新）https:///ProductCatalog/ProductCategory.aspx?ID=30 1. Validation of Moist Heat Sterilization Processes: Cycle Design, Development, Qualification and Ongoing Control Revised 2007 (Published 1980)湿热灭菌工艺验证：循环设计、研发、确认和持续控制，修订20073. Validation of Dry Heat Processes Used for Depyrogenation and Sterilization Revised 2013 (Published 1981) 01003 43506用于除热源和灭菌的干热工艺验证，修订20134. Design Concepts for the Validation of Water-for-Injection Systems 1983 注射用水系统验证的设计概念，19835. Sterile Pharmaceutical Packaging: Compatibility and Stability 1984无菌制剂包装：相容性和稳定性，19847. Depyrogenation 1985除热源，19859. Review of Commercially Available Particulate Measurement Systems 1988 商业可采购的颗粒物检测系统审核，198810. Parenteral Formulations of Proteins and Peptides: Stability and Stabilizers 1988 蛋白质和多肽注射制剂：稳定性和稳定剂，1988 11.Sterilization of Parenterals by Gamma Radiation 1988静脉注射伽马辐射灭菌，198812. Siliconization of Parenteral Drug Packaging Components 1988 静脉注射剂药品包装组分硅化处理，198813.Fundamentals of an Environmental Monitoring Program Revised 2014 (Published1990)环境监测计划原则，修订20141 / 714. Validation of Column-Based Chromatography Processes for the Purification of Proteins Revised 2008 (Published 1992)蛋白纯化用柱色谱工艺验证，修订200815. Validation of Tangential Flow Filtration in Biopharmaceutical Applications Revised 2009 (Published 1992)生物制药用正切流过滤验证，修订200916. Effect of Gamma Irradiation on Elastomeric Closures 1992人造橡胶塞伽马辐射效应，199217. Current Practices in the Validation of Aseptic Processing -- 1992 1993 无菌工艺验证现行规范，1992，199318. Report on the Validation of Computer-Related Systems 1995 计算机相关系统验证报告，199519.Rapid/Automated ID Methods Survey 1990快速/自动ID方法调查，199020. Report on Survey of Current Industry Gowning Practices 1990 行业现行更衣规范调查报告，199021. Bioburden Recovery Validation 1990生物负载回收率验证，199022. Process Simulation for Aseptically Filled Products Revised 2011 (Published 1996) 无菌灌装药品工艺模拟，修订201123. Industry Survey on Current Sterile Filtration Practices 1996现行无菌过滤实践行业调查，199624. Current Practices in the Validation of Aseptic Processing –1996 1996无菌工艺验证现行规范，199625. Blend Uniformity Analysis: Validation and In-Process Testing 1997混合均一性分析：验证和中控测试，19972 / 726. Sterilizing Filtration of Liquids Revised 2008 (Published 1998)液体无菌过滤，修订200827. Pharmaceutical Package Integrity 1998药品包装完整性，199828. Process Simulation Testing for Sterile Bulk Pharmaceutical Chemicals Revised 2006 (Published 1998)无菌散装药用化学物工艺模拟测试，修订200629. Points to Consider for Cleaning Validation Revised 2012 (Published 1998) 清洁验证的考虑要点，修订201230. Parametric Release of Pharmaceuticals and Medical Device Products Terminally Sterilized by Moist Heat Revised 2012 (Published 1999)最终湿热灭菌的药物和医疗器械参数放行，修订201231. Validation and Qualification of Computerized Laboratory Data Acquisition Systems 1999计算机化实验室数据获取系统验证和确认，199932. Auditing of Suppliers Providing Computer Products and Services for Regulated Pharmaceutical Operations Revised 2004 (Published 1999)提供受法规管理的药物操作用计算机产品和服务的供应商审计，修订200433. Evaluation, Validation and Implementation of Alternative and RapidMicrobiological Methods Revised 2013 (Published 2000)替代性和快速微生物方法的评估、验证和实施，修订201334. Design and Validation of Isolate Systems for the Manufacturing and Testing of Health Care Products 2001保健药品的生产和检测分离系统的设计和验证，200135. A Proposed Training Model for the Microbiological Function in thePharmaceutical Industry 20013 / 7制药行业微生物功能培训模式建议，200136. Current Practices in the Validation of Aseptic Processing –2001 2002 无菌工艺验证的现行规范--2001，200238. Manufacturing Chromatography Systems Post-Approval Changes:(ChromPAC):Chemistry, Manufacturing and Controls Documentation 2006 批准后生产用色谱系统：研发、生产和控制文件，200639. Guidance for Temperature-Controlled Medicinal Products: Maintaining the Quality of Temperature-Sensitive Medicinal Products through the Transportation Environment 2007温度受控药物指南：通过运输环境来维护对温度敏感的药物的质量，200740. Sterilization Filtration of Gases 2005气体的无菌过滤，200541. Virus Filtration 2008病毒过滤，200842. Process Validation of Protein Manufacturing 2005蛋白质生产的工艺验证，200543. Identification and Classification of Nonconformities in Molded and Tubular Glass Containers for Pharmaceutical Manufacturing Revised 2013 (Published 2007) 药物生产用模型制备和管式玻璃容器的识别和分类，修订201344. Quality Risk Management for Aseptic Processes 2008无菌工艺的质量风险管理，200845. Filtration of Liquids Using Cellulose-Based Depth Filters 2008 使用纤维素基础深层过滤器的液体过滤，200846. Last Mile: Guidance for Good Distribution Practices for Pharmaceutical Products to the End User 2009最终里程：给最终用户的药物优良销售规范指南，20094 / 747. Preparation of Virus Spikes Used for Virus Clearance Studies 2010用于病毒清除研究的病毒加标样制备，201048. Moist Heat Sterilizer Systems: Design, Commissioning,Operation, Qualification and Maintenance 2010湿热灭菌系统：设计、调试、运行、确认和维护，201049. Points to Consider for Biotechnology Cleaning Validation 2010 生物制品清洁验证考虑要点，201050. Alternative Methods for Mycoplasma Testing 2010支原体测试替代性方法，201051. Biological Indicators for Gas and Vapor-Phase Decontamination Processes: Specification, Manufacture, Control and Use 2010气体和蒸汽相除污染工艺生物指示剂：质量标准、生产、控制和使用，201052. Guidance Good Distribution Practices for the Pharmaceutical Supply Chain 2011 药品供应链优良销售规范指南，201153.Guidance for Industry: Stability Testing to Support Distribution of New Drug Products 2011行业指南：支持新药销售的稳定性测试，201154. Implementation of Quality Risk Management for Pharmaceutical andBiotechnology Manufacturing Operations 2012药品和生物制品生产操作的质量风险管理实施，201254-2. Implementation of Quality Risk Management for Pharmaceutical andBiotechnology Manufacturing Operation: Annex 1: Case Study Examples for Quality Risk Management in Packaging and Labeling 2013药品和生物制品生产操作的质量风险管理实施，附录1：包装和标识中的质量风险管理案例研究，20135 / 7篇二：PDA技术报告目录PDA——Parenteral Drug Association，注射用药物协会（/）PDA技术报告目录／PDA Publications●Technical Methods Bulletin No.1 - Extractables from Elastomeric Closures: Analytical Procedures for Functional Group Characterization/Identification2 - Elastomeric Closures: Evaluation of Significant Performance and Identity Characteristics3 - Glass Containers for Small Volume Parenteral Products: Factors for Selection and Test Methods for Identification●Technical Information Bulletin No.2 - Generic Test Procedures for Elastomeric Closures4 - Aspects of Container/Closure Integrity●Technical Report No.1 Validation of Moist Heat Sterilization Processes: Cycle Design,Development, Qualification and Ongoing Control, Revised 2007 (original Technical Monograph No. 1, Validation of Steam Sterilization Cycles, first published in 1978)Technical Monograph No. 2 - Validation of Aseptic Filling for Solution Drug Product, 1980 (replaced by Technical Report No. 22 and is no longer available.)3 Validation of Dry Heat Processes used for Sterilisation and Depyrogenation, 19814 Design Concepts for the Validation of a Water for Injection System, 19835 Sterile Pharmaceutical Packaging: Compatibility and Stability, 19846 Validation of Aseptic Drug Powder Filling Processes, 1984 (replaced by Technical Report No. 22 and is no longer available.)7 Depyrogenation, 19858 Parametric Release of Parenteral Solutions Sterilized by Moist Heat Sterilization,1987 (Please note: Technical Report No. 8 has been superseded by Technical Report No. 30 and is no longer available.)9 Review of Commercially Available Particulate Measurement Systems, 198810 Parenteral Formulations of Proteins & Peptides: Stabilityand Stabilizers, 198811 Sterilization of Parenterals by Gamma Radiation, 198812 Siliconization of Parenteral Drug Packaging Components, 198813 Fundamentals of a Microbiological Environmental Monitoring Program, 1990 (Revised 2001)14 Validation of Column-Based Chromatography Processes for the Purification of Proteins, Revised 2008 (original name: Industry Perspective on the Validation of Column-Based SeparationProcesses for the Purification of Proteins, first published in 1992) 15 Industry Perspective on Validation of Tangential FlowFiltration in Bio-pharmaceutical Application, 1992 (Revised 2009)16 Effect of Gamma Irradiation on Elastomeric Closures, 199217 Current Practices in the Validation of Aseptic Processing - 1992, 199318 PDA Report on the Validation of Computer Related Systems, 199519 Rapid/Automated ID Methods Survey, 199020 Report on Survey of Current Industry Gowning Practices, 199021 Bioburden Recovery Validation, 199022 Process Simulation Testing for Aseptically Filled Products, 199623 Industry Survey on Current Sterile Filtration Practices, 1996 24 Current Practices in the Validation of Aseptic Processing - 1996,25 Blend Uniformity Analysis: Validation and In-Process Testin, 199726 Sterilizing Filtration of Liquids, 1998 (Revised 2008) 27 Pharmaceutical Package Integrity, 199828 Process Simulation Testing for Sterile Bulk Pharmaceutical Chemicals, 1998 (revised 2006)29 Points to consider for Cleaning Validation, 199830 Parametric Release of Pharmaceuticals Terminally Sterilized by Moist Heat, 199931 Validation & Qualification of Computerized Laboratory Data Acquisition Systems, 199932 Auditing of Suppliers Providing Computer Products and Services for Regulated Pharmaceutical Operations, 1999 (revised 2004)33 Evaluation, Validation & Implementation of NewMicrobiological Testing Methods, 200034 Design and Validation of Isolator Systems for theManufacturing and Testing of Health Care Products, 200135 A Proposed Training Model for the Microbiological Function in the Pharmaceutical Industry, 200136 Current Practices in the Validation of Aseptic Processing - 2001,38 Manufacturing Chromatography Systems Post-Approval Changes: (ChromPAC): Chemistry, Manufacturing and Controls Documentation, 200639 Guidance for Temperature-Controlled Medicinal Products: Maintaining the Quality of Temperature-Sensitive Medicinal Products through the Transportation Environment, revised 2007 (orginal name: Cold Chain Guidance for Medicinal Products: Maintaining the Quality of Temperature-Sensitive MedicinalProducts Through the Transportation Environment, first published in 2005)40 Sterilizing Filtration of Gases, 200541 Virus Filtration, 2005 (revised 2008)42 Process Validation of Protein Manufacturing, 200543 Identification and Classification of Nonconformities in Molded and Tubular Glass Containers for Pharmaceutical Manufacturing, 200744 Quality Risk Management for Aseptic Processes, 200845 Filtration of Liquids Using Cellulose-Based Depth Filters, 200846 Last Mile: Guidance for Good Distribution Practices for Pharmaceutical Products to the End User, 201047 Preparation of Virus Spikes Used for Virus Clearance Studies,48 Moist Heat Sterilizer Systems: Design, Commissioning, Operation, Qualification and Maintenance, 2010PDA的技术报告目录/刊物技术方法第1号-萃取物从弹性封路措施：分析程序功能群表征/鉴定2 弹性封路措施：对重要的性能和身份特征评价3 小容量注射用玻璃容器：选择和试验方法因素的识别技术信息通报1 蒸汽灭菌周期验证2 对弹性封通用测试程序3 验证流程，干热灭菌和除热源使用4 为一个注射水系统验证设计概念5 无菌医药包装：兼容性和稳定性67 除热源8 肠外参数解湿热灭菌消毒释放1987年（注意：技术报告已被第8号第30号技术报告取代，不再可用）9 审查颗粒测量系统投放市场10注射制剂的蛋白质及肽：稳定性和稳定剂11由伽马辐射肠道灭菌12肠外药品包装成分渗Si13一个微生物环境监测方案基础14行业对基于列的分离工艺验证的角度来看，用于蛋白质的分离纯化15关于切向流过滤验证产业视角在生物医药中应用16γ-辐射对弹性封17当前实践中的无菌工艺验证？1992年18掌上报告计算机相关系统验证19快速/自动调查ID方法20对当前行业调查报告gowning 实践21生物负载恢复验证22无菌填充过程的仿真测试产品23关于当前产业调查无菌过滤实验24当前实践中的无菌工艺验证1996年25混合均匀度分析：验证和流程测试26液体过滤杀菌27医药软件包的完整性28过程无菌原料药化工仿真测试29点考虑清洗验证30药品参数放行末由湿热灭菌31计算机实验室验证及数据采集系统的鉴定32中医药部分提供受规管电脑产品及服务供应商审核33评估，验证和测试新方法的实施微生物34设计及制造及保健品的隔振系统验证测试35微生物的作用，为拟议的培训模式在制药行业36现行做法是无菌生产过程的验证2001373839对药品冷链指导：维护交通环境，通过对温度敏感的药品产品质量40气体过滤杀菌41病毒过滤42蛋白质制造工艺验证43识别及铸模，管状玻璃容器不符合药品生产的分类44质量风险管理过程的无菌45利用纤维素为基层的深层过滤液体2008年过滤篇三：PDA技术报告NO.26(2008版)(中文)液体的除菌过滤PDA第26份技术报告（2008年修订本）制药科学与技术的PDA期刊增刊2008年第62卷，第S-5号1.0引言除菌过滤是从液体流中去除微生物*而对产品质量没有负面影响的过程。

SAE J17112010

entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising therefrom, is the sole responsibility of the user.”
SAE reviews each technical report at least every five years at which time it may be reaffes your written comments and suggestions.
SURFACE VEHICLE RECOMMENDED PRACTICE
J1711 JUN2010
Issued Revised
1999-03 2010-06
Superseding J1711 MAR1999
(R) Recommended Practice for Measuring the Exhaust Emissions and Fuel Economy of Hybrid-Electric Vehicles, Including Plug-in Hybrid Vehicles
Copyright © 2010 SAE International
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical,

EU GMP指南第1部分第4章：文件

EUROPEAN COMMISSIONHEALTH AND CONSUMERS DIRECTORATE-GENERALPublic Health and Risk AssessmentPharmaceuticalsBrussels,SANCO/C8/AM/sl/ares(2010)1064587EudraLexThe Rules Governing Medicinal Products in the European UnionVolume 4Good Manufacturing PracticeMedicinal Products for Human and Veterinary UseChapter 4: Documentation第四章：文件Legal basis for publishing the detailed guidelines:Article 47 of Directive2001/83/EC on the Community code relating to medicinal products for human use and Article 51 of Directive 2001/82/EC on the Community code relating to veterinary medicinal products. This document provides guidance for the interpretation of the principles and guidelines of good manufacturing practice (GMP) for medicinal products as laid down in Directive 2003/94/EC for medicinal products for human use and Directive 91/412/EEC for veterinary use.立法基础：2001/83/EC法令第47款对人用药品的相关要求，2001/82/EC法令第51款兽用药相关的欧共体法规。

openbsd

openbsdOpenBSD: A Secure and Powerful Operating SystemIntroduction:OpenBSD is a free and open-source operating system known for its strong emphasis on security, code simplicity, and correctness. Developed by a group of dedicated volunteers, OpenBSD has earned a reputation for being one of the most secure operating systems available today. In this document, we will explore the key features of OpenBSD, its security-oriented design, and the benefits it offers to users and developers.Security Features:1. Proactive Security: OpenBSD takes a proactive approach to security by implementing rigorous audits, code reviews, and extensive testing. This ensures that potential vulnerabilities are detected and fixed before they can be exploited.2. Security-focused Development: OpenBSD developers adhere to strict coding guidelines, favoring simplicity and correctness over fancy features. The codebase is regularlyaudited for potential security issues and actively maintained to ensure a secure and stable system.3. Exploit Mitigations: OpenBSD incorporates numerous exploit mitigations, such as Address Space Layout Randomization (ASLR), which randomizes memory locations to make it harder for attackers to predict and exploit vulnerabilities. OpenBSD also includes technologies like Stack Ghost, which protects against stack overflow attacks.4. Privilege Separation: OpenBSD utilizes privilege separation, where different components of the system run with minimal privileges. This prevents an attacker from compromising the entire system even if one component is compromised.5. Secure Memory Management: OpenBSD incorporates secure memory management techniques to protect against memory-related vulnerabilities, such as buffer overflows and uninitialized memory reads.6. Secure Networking: OpenBSD includes strong networking capabilities, with built-in support for technologies like IPsec, Secure Shell (SSH), and Virtual Private Networks (VPNs). These features ensure secure communication over networks and protect against eavesdropping and data tampering.Benefits for Users:1. Security: OpenBSD's core focus on security ensures that users have a robust and trustworthy operating system. This is particularly important for organizations and individuals who require a high level of security, such as financial institutions, government agencies, and privacy-conscious individuals.2. Stability: OpenBSD is known for its stability. Its security-oriented development methodology, frequent code audits, and strong testing ensure a stable and reliable system. This makes it an ideal choice for servers and critical infrastructure where downtime can have significant consequences.3. Documentation and Support: OpenBSD has extensive documentation available, including manuals, guides, and FAQs. The OpenBSD community is known for its helpfulness and active support, making it easy to find assistance for any issues encountered.4. Portability: OpenBSD is designed to be highly portable, with support for a wide range of hardware platforms. This allows users to run OpenBSD on various devices, from servers and desktops to embedded systems and network appliances.Benefits for Developers:1. Clean and Readable Code: OpenBSD's development philosophy focuses on code simplicity and correctness. The codebase is well-organized, comprehensible, and extensively documented. This makes it easier for developers to understand and modify the system code.2. Security-conscious Development Practices: OpenBSD developers follow secure coding practices, which can be a valuable learning experience for developers looking to enhance their understanding of security-related programming techniques.3. Contribution Opportunities: OpenBSD is an open-source project that welcomes contributions from developers. This provides an opportunity to collaborate with experienced developers and contribute to the improvement of the operating system.4. Networking Capabilities: OpenBSD's built-in networking capabilities enable developers to create secure network applications. Developers can leverage technologies like IPsec and SSH to build robust and secure networking solutions.Conclusion:OpenBSD is much more than just an operating system; it is a community-driven project dedicated to providing a secure and powerful computing environment. Its strong emphasis on security, simplicity, and correctness makes it an attractive choice for users and developers alike. Whether you are looking to enhance your system's security or gain valuable insights into secure coding practices, OpenBSD is a worthy investment of your time and resources.。

GDP-良好的文件记录规范

What do I do if find a Mistake?
• All errors should be corrected by the person who created them.
• Or, if that person is not available , the error can be corrected by their manager • Or, if that person is not available, the error can be corrected by the next highest member of management. And so on and so on…… etc.
Good Documentation Practices(GDP) 良好的文件规范
Definition of......
• What is the definition of Good Documentation Practices (GDP)?
— Concise, Legible, Accurate and Traceable records 简明清楚准确可追溯
What am I responsible for?
• You are responsible for your signature:
— Electronic Signature — It shall never be transmitted or disclosed to anyone else — You should never use someone else’s electronic signature
– –
How Do We Make The Task Easy?

法律案例用英文(3篇)

第1篇Introduction:In the case of Johnson v. Smith, the Supreme Court of the United States had to address a crucial issue of property rights. The case revolves around the ownership of a piece of land that has been in dispute for several years. This legal battle highlights the complexities of property law and the importance of upholding the rights of individuals.Background:The case of Johnson v. Smith originated in the state of Michigan. The parties involved were Mr. and Mrs. Johnson, who owned a piece of land, and Mr. Smith, who claimed ownership over the same property. The dispute arose when Mr. Smith, without the consent of the Johnsons, began constructing a building on the disputed land. This led to a legal battle that eventually reached the Supreme Court.Facts of the Case:In 2000, Mr. and Mrs. Johnson purchased a piece of land in Michigan. They intended to build a house on the property. However, before they could begin construction, Mr. Smith claimed ownership over the land, stating that he had purchased it from an unknown third party years earlier. Mr. Smith had already started constructing a building on the property without the Johnsons' consent.The Johnsons, feeling that their property rights were being violated, filed a lawsuit against Mr. Smith. They argued that they had purchased the land legally and had the right to develop it as they pleased. Mr. Smith, on the other hand, claimed that he had a valid claim to the property and that the Johnsons were trespassing.Legal Issues:The case raised several legal issues, primarily concerning property rights and the interpretation of property laws. The main issues were as follows:1. Ownership of the Land: The court had to determine who had therightful ownership of the land. This involved examining the purchase agreements and any other relevant documentation to establish the chain of title.2. Possession and Use: The court had to consider whether Mr. Smith's unauthorized construction on the land gave him any rights to possess or use the property.3. Trespass: The Johnsons claimed that Mr. Smith's actions constituted trespass, and they sought an injunction to prevent him from further interfering with their property rights.Arguments of the Parties:The Johnsons argued that they had purchased the land legally and had the right to develop it as they saw fit. They presented evidence of their purchase agreement and any other relevant documents to support their claim.Mr. Smith, on the other hand, claimed that he had a valid claim to the property based on an earlier purchase agreement. He argued that the Johnsons' claim was invalid and that he had the right to possess and use the land.Decision of the Supreme Court:The Supreme Court, after carefully considering the arguments and evidence presented by both parties, ruled in favor of the Johnsons. The court held that the Johnsons had purchased the land legally and had the right to ownership. The court further stated that Mr. Smith's unauthorized construction did not give him any rights to possess or use the property.The court emphasized the importance of upholding property rights and the rule of law. It highlighted the need for individuals to follow proper legal procedures when acquiring property and making claims to ownership.Conclusion:The case of Johnson v. Smith serves as a significant legal precedentthat underscores the importance of property rights and the rule of law. The Supreme Court's decision in this case emphasizes the need for individuals to adhere to legal procedures when acquiring and claiming ownership of property. It also serves as a reminder of the complexities that can arise in property law disputes and the crucial role that the courts play in resolving such conflicts.第2篇I. IntroductionDefamation is a common legal issue that arises when someone publishes false and harmful statements about another person. This case study examines a defamation lawsuit filed against a local newspaper by a local business owner. The case highlights the complexities involved in proving defamation and the importance of evidence in such cases.II. Facts of the CaseThe plaintiff, John Smith, owns a local hardware store in a small town. The defendant, The Town Crier, is a weekly newspaper published in the same town. On March 1, 2021, The Town Crier published an article titled "Shady Business Practices at Smith's Hardware." The article accused John Smith of selling counterfeit products and engaging in fraudulent business practices.The article cited anonymous sources and provided no evidence to support its claims. The article was widely circulated in the community, causing John Smith's business to suffer significant financial losses. John Smith filed a defamation lawsuit against The Town Crier, seeking damages for the harm caused to his reputation and business.III. Legal IssuesThe case revolves around the following legal issues:A. DefamationDefamation is a civil wrong that occurs when someone publishes a false statement about another person that harms their reputation. To prove defamation, the plaintiff must prove the following elements:1. Publication of a false statement: The defendant must have published a false statement about the plaintiff.2. Identification of the plaintiff: The false statement must identifythe plaintiff or be reasonably understood to refer to the plaintiff.3. Publication to a third party: The false statement must be communicated to a third party.4. Damage to reputation: The false statement must cause damage to the plaintiff's reputation.5. Fault on the part of the defendant: The defendant must have actedwith either negligence, actual malice, or actual knowledge of thefalsity of the statement.B. Actual MaliceIn cases involving public figures, the plaintiff must prove that the defendant acted with actual malice, which is defined as reckless disregard for the truth. However, in cases involving private individuals, such as John Smith, the plaintiff must prove that the defendant acted with actual knowledge of the falsity of the statement or with reckless disregard for the truth.C. PrivilegeThe defendant may claim privilege, which is a legal defense thatprevents a plaintiff from recovering damages for defamation. There are several types of privilege, including:1. Absolute privilege: This type of privilege applies to certain communications, such as those made in legislative, judicial, orexecutive proceedings.2. Qualified privilege: This type of privilege applies to communications made in certain contexts, such as those made in a fair and reasonable manner in the public interest.IV. Procedural HistoryThe case was filed in the Superior Court of the State of California. The court granted John Smith's motion for summary judgment, holding that The Town Crier had failed to meet its burden of proving that it had a valid privilege or that it acted with actual malice.The court further held that the article was defamatory because it contained false statements about John Smith's business practices. The court found that the defendant had acted with actual knowledge of the falsity of the statements, as it had received multiple complaints about the article from the community but failed to investigate the claims.V. Ruling and VerdictThe court awarded John Smith $500,000 in damages for the harm caused to his reputation and business. The court also ordered The Town Crier to publish a retraction and a correction of the false statements made in the article.VI. ConclusionThis case study illustrates the complexities involved in proving defamation and the importance of evidence in such cases. It also highlights the importance of responsible journalism and the need for newspapers to verify the accuracy of their articles before publication. By holding The Town Crier liable for defamation, the court sent a strong message about the importance of truth in the media.第3篇I. IntroductionUnjust enrichment, as a legal principle, refers to the acquisition of property or benefit by one party without providing any corresponding consideration to the other party. It is a common legal issue in contractand tort law. This article presents a case of unjust enrichment,involving the dispute between Smith and Johnson.II. BackgroundSmith and Johnson were neighbors living in the same apartment complex.In 2018, Smith, who was a skilled electrician, offered to repairJohnson's malfunctioning washing machine at a reasonable price. Johnson agreed and entrusted Smith with the task. After completing the repair, Smith charged Johnson $500 for the labor and parts. Johnson paid thebill without any disputes.However, several months later, Johnson discovered that the washing machine was still not functioning properly. Upon further investigation, Johnson found out that Smith had replaced the original parts with substandard ones. Feeling deceived and dissatisfied with the repair work, Johnson demanded a refund from Smith. Smith refused, claiming that the work had been completed and the payment had been made. The dispute escalated, and Johnson decided to seek legal assistance.III. The DisputeThe main issue in this case is whether Smith's act of replacing the original parts with substandard ones and charging Johnson for the repair constitutes unjust enrichment.A. Unjust EnrichmentUnjust enrichment occurs when one party benefits from the property or services of another party without providing any consideration. To establish unjust enrichment, the following elements must be proved:1. A benefit has been conferred on the claimant.2. The benefit has been retained by the defendant.3. The retention of the benefit is unfair to the claimant.In this case, Smith replaced the original parts with substandard ones, which resulted in Johnson suffering a loss. Therefore, the first element of unjust enrichment is satisfied.B. Retention of the BenefitSmith retained the $500 payment from Johnson for the repair work. This satisfies the second element of unjust enrichment.C. UnfairnessThe third element of unjust enrichment requires proving that the retention of the benefit is unfair to the claimant. In this case,Smith's act of replacing the original parts with substandard ones and charging Johnson for the repair can be considered unfair. Johnsontrusted Smith to perform the repair work and paid him for the service. However, Smith failed to fulfill his obligation and caused Johnson to suffer a loss. Therefore, the retention of the $500 payment is unfair to Johnson.IV. ConclusionBased on the analysis of the elements of unjust enrichment, it can be concluded that Smith's act of replacing the original parts with substandard ones and charging Johnson for the repair constitutes unjust enrichment. As a result, Johnson is entitled to a refund of the $500 payment. This case highlights the importance of fulfilling contractual obligations and the legal consequences of failing to do so.V. RecommendationsTo prevent similar disputes from occurring in the future, the following recommendations can be made:1. Both parties should clearly define the terms and conditions of the contract before entering into the agreement.2. Parties should maintain open communication and promptly address any issues or concerns during the performance of the contract.3. Both parties should seek legal advice when necessary to ensure their rights and obligations are protected.By following these recommendations, parties can minimize the risk of unjust enrichment and maintain a harmonious relationship in their business or personal interactions.。

src-openeuler 代码提交流程

src-openeuler 代码提交流程英文版src-openeuler Code Submission ProcessIntroductionThe src-openeuler project welcomes contributions from the open-source community. This document outlines the code submission process for contributors to follow, ensuring that code submissions are reviewed, tested, and merged into the main codebase efficiently and effectively.Understand the Project GuidelinesBefore submitting any code, it is essential to familiarize yourself with the project's guidelines, including coding standards, testing requirements, and contribution policies. This ensures that your code adheres to the project's best practices and standards.Fork the RepositoryCreate a fork of the src-openeuler repository on your GitHub account. This allows you to work on your changes independently without affecting the main codebase.Clone the Forked RepositoryClone the forked repository to your local machine. This allows you to make changes and test them locally before submitting them for review.Make Your ChangesDevelop and test your code changes locally. Ensure that your changes adhere to the project's coding standards and that you have included any necessary unit tests or documentation.Commit Your ChangesOnce you have made your changes and tested them locally, commit them to your local repository using a descriptive commit message. This message should briefly explain the changes you have made and any relevant context.Push Your Changes to GitHubPush your local commits to your forked repository on GitHub. This makes your changes visible to the project maintainers and other contributors.Create a Pull RequestCreate a pull request (PR) on the src-openeuler repository, comparing your forked branch with the desired target branch (usually the main or develop branch). Include a descriptive PR title and a detailed description of your changes, explaining the motivation, implementation, and any potential impacts.Review and DiscussionProject maintainers and other contributors will review your pull request, providing feedback and suggestions. Engage in the discussion, addressing any concerns or suggestions raised.Updates and AmendmentsIf necessary, make any required updates or amendments to your code based on the feedback received. Commit and push these changes to your forked repository, and they will automatically be included in the existing pull request.Merge and CloseOnce your pull request has been approved and any requested changes have been made, it will be merged into the main codebase by a project maintainer. You can then close the pull request, marking it as merged.ConclusionBy following this code submission process, contributors to the src-openeuler project can ensure that their code changes are reviewed, tested, and merged efficiently and effectively. This process promotes quality, collaboration, and openness within the open-source community.中文版src-openeuler 代码提交流程介绍src-openeuler 项目欢迎开源社区的贡献者。

good documentation practices procedure -回复

good documentation practices procedure -回复“好的文档管理实践程序”是指为了实现高质量和一致性的文档编写，组织，审核和维护的一系列步骤和指导原则。

在本文中，我们将逐步回答有关好的文档管理实践程序的问题，并提供一些建议和指导。

第一步：建立文档编写流程建立文档编写的流程是实施好的文档管理实践程序的第一步。

这可以包括明确定义文档编写的责任和角色，并确保所有相关人员了解和遵守这些流程。

一些关键的步骤包括：1. 确定文档编写者：确定负责编写和更新文档的人员，并确保他们具备相应的专业知识和技能。

2. 创建审查流程：建立一个审查流程，包括对文档内容的技术审核和语言审核。

这将确保文档的准确性和一致性。

3. 确定校对程序：确定文档校对的程序，以确保文档的语法，拼写和标点符号的正确性。

第二步：制定文档编写指南和标准制定文档编写指南和标准是确保文档的一致性和易读性的关键。

这些指南和标准应该明确规定文档的格式，样式和内容，并确保文档能够满足特定的目标受众需求。

以下是一些建议：1. 标准化文档格式：确保所有文档都遵循相同的格式，包括页眉，页脚，字体，字号和间距。

此外，指定清晰明确的标题和子标题的使用准则。

2. 制定语言风格指南：规定文档中应该使用的语言风格，包括时态，用词选择和句子结构。

确保文档使用简单，清晰和易懂的语言。

3. 使用可视化辅助工具：通过使用图表，图像，表格和示意图等可视化辅助工具，增强文档的可读性和易理解性。

第三步：实施文档控制程序文档控制程序是为了确保文档的安全性，可追溯性和一致性。

以下是一些建议：1. 设立文档编号和版本控制：为每个文档分配独一无二的编号，并建立一个版本控制系统，以跟踪文档的更新历史和修订情况。

2. 确定文档访问权限：确定哪些人员有权限创建，更新和查阅特定文档。

确保只有授权人员才能进行修改和审核文档。

3. 存储和备份：确保文档以安全的方式存储，并为其进行定期备份，以防止数据丢失或损坏。

1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。

Documentation Practices in Open Source–A Study of Apache DerbyMaster’s ThesisHåvard MorkiiAbstractOpen source is one of the more interesting trends in software engineering today.The goal of the software engineering discipline is to increase efﬁciency in the development process,and maximize quality of the product.Open source development processes offer the potential for reducing costs for commercial enterprises.This master’s thesis addresses how open source documents architecture,and how it uses documentation in general.Open source has a reputation of creating high quality software,but documentation of process and product is weak.This may be a hurdle for wider adoption of open source processes,as a thorough understanding of a product’s qualities is central to its success.The goal is to better understand documentation re-quirements in open source.The study is based on participation to the Apache Derby open source project.Action research is the research method.Theﬁndings show that the Apache Derby documents its artifacts in a number of ways,but fails to aggregate it in a meaningful way.A rich set of written communication mediums compensate for this by giving developers the ability to understand the product over time.The study suggests the popularity and diffusion of an open source project may affect requirements for documentation.iiiivPrefaceThis master’s thesis is the result of one semester’s work,from January to June2006,and concludes the requirements for a master’s degree in computer science at the Norwegian University of Science and Technology(NTNU),Department of Computer and Information Science(IDI).In this thesis,I have used participation to an open source project to better under-stand open source development processes,getting experience in software engineering practices,while also trying to enhance programming skills through observing and work-ing with the community.The work in this thesis follows in the footsteps of a directed study from autumn2005which aimed to investigate leadership issues in commercially controlled open source projects[Mor05].The precise focus of the thesis is investigating which documentation practices exist in one open source project,and through participation to this project also reﬂecting on the challenges for documentation or architectural descriptions in open source.Software engineering literature presses the need for documenting software,not only for its users, but notably also for the developers that will maintain the software,i.e.[CBB+02].This master’s thesis is based on the following assignment text,modiﬁed to encompass my understanding of the task:Candidates will have to participate to one open source software(OSS)projectin order to learn about open source in a software engineering context,improveprogramming skills,and contribute to the discussion around OSS.The candidatecan inﬂuence the research focus,as well as the project to work with.The researchquestions will have to be grounded in OSS literature.I would like to thank my supervisor,Professor Letizia Jaccheri for her guidance through my work on the master’s thesis.Also thanks to the many people at the De-partment of Computer and Information Science who have contributed through valuable discussion,and helped make this a memorable semester.Trondheim,22nd June2006Håvard Morkhavard.mork@vviContentsAbstract iii Preface v 1Introduction91.1Open source (9)1.2The software engineering context (10)1.3Problem description (11)1.4Overview (13)2Research method152.1Action research (15)2.1.1Researcher-client agreement (16)2.1.2Cyclical process model (16)2.1.3Theory and reﬂection (18)2.2Research and education in open source (18)2.3Previous action research experience (19)2.4Data collection strategy (19)2.5Data analysis strategy (20)3Open source233.1Deﬁnition (23)3.1.1Communities (24)3.1.2Management styles (24)3.2History (25)3.3Principles (26)3.4Licenses (26)4Apache Derby294.1History (29)4.2Standards compliance (30)4.2.1Structured Query Language (30)4.2.2Java Database Connectivity (31)vii4.3Features (33)4.4Community and infrastructure (33)4.5Architecture (34)5Software documentation375.1Software architecture (37)5.1.1Software design (39)5.1.2Views (39)5.2Issues with documentation (40)5.3Open source relation (41)6Participation436.1Overview (43)6.2First iteration (44)6.2.1Intervention (45)6.2.2Evaluation (46)6.2.3Reﬂection (47)6.3Second iteration (47)6.3.1Intervention (48)6.3.2Evaluation and reﬂection (49)6.4Third iteration (50)6.4.1Intervention (50)6.4.2Evaluation (52)6.4.3Reﬂection (52)7Discussion537.1Success factors for open source documentation (53)7.2Apache Derby (54)7.3Documenting software for newcomers (56)7.4Comparingﬁndings to other literature (57)8Conclusions59 Bibliography67A Issue log for Derby-116469B Article:Studying Open Source with Action Research73viiiChapter1IntroductionSoftware engineering research addresses the need toﬁnd ways to make software devel-opment more efﬁcient and create higher quality software systems.The set of disciplined methods used in software engineering development processes aim to allow a software system to grow and develop into aﬁnal form that is useful for the stakeholders of the system.The open source software engineering process is the focus in this master’s thesis.Documentation is commonly viewed as artifacts only necessary for users of software. Looking beyond this,it can be observed that documentation is a separate project artifacts that needs development and maintenance in order to be useful and survive.Documenta-tion has both prescriptive and descriptive purposes in a software system[CBB+02],and is in most development processes regarded as essential.However,while the production of documentation is seen as axiomatic,little is known about what type of documentation is regarded as useful for developers[STT01].The research goal of the master’s thesis is to highlight relations between how software documentation and architectural descriptions relate to the success of the open source development method.Certain aspects of this will be highlighted through participation to an open source project,the Apache Derby database system.This chapter will further deﬁne the goals of this project,its context,and how this report is structured.1.1Open sourceOpen source has become a cultural phenomenon which also is becoming common in cor-porate environments.It stems from a hacker culture in the1960s and70s,where it was created out of the need for computer enthusiasts(hackers)to share code among them-selves.In the mid-80s,the Free Software Foundation was started in order to promote distribution and production of free software.The early efforts were primarily founded in idealistic motives,that software should be free for users.This was a response to the increasing commercialization of computer software and operating systems.In many ways,open source is light-weight in comparison to commercially used soft-9ware development processes.The primary characteristic of open source development processes is the openness.Many features of commercial software development are lack-ing in open source,such as requirements engineering with the intended customers,for-mal use of architecture descriptions,and formal release planning.Open source travels light by not requiring some of the control mechanisms typically associated with soft-ware engineering,but still accomplishes acceptable results through a’scratch-own-itch’, peer-recognizing culture of sharing.Successes of the open source development method,according to the number of users, include operating systems such as Linux and FreeBSD.Popular desktop applications have also gained widespread diffusion such as Eclipse,OpenOfﬁce,and the Firefox web browser.Open source is traditionally used to develop software by developers,for devel-opers.The trend is now moving towards development of end-user software in a market which is already saturated with commercial alternatives.This trend of commoditiza-tion is in some ways an effect of open source,but it is also the goal of the original free software movement,which is giving freedom to the users.Open source development usually is centered around a community of people working on a common goal.The community may be composed both of volunteers that work on open source out of a personal need or interest,and professionals that are paid to work on it.The economic foundation can therefore not be explained with only a private investment model,but must include the deeper cultural and social roots[HNH03].In order to use open source in a commercial context,it is not only necessary to un-derstand how code is produced,but in order to be successful it is also necessary to make the adaptions to the cultural and social aspects of open source.1.2The software engineering contextSoftware engineering is according to IEEE Standard610.12deﬁned as“the application of a systematic,disciplined,quantiﬁable approach to development,operation,and mainte-nance of software”,and also the study of approaches for applying this[IEE90].It is an engineering discipline incepted in the1960s from the need to address problems like cost overruns,quality and schedule problems[WRH+00].Various approaches exist for applying software engineering to real-world projects in order to accomplish the goals of quality and cost saving.These are referred to as develop-ment processes.Some software development processes that are commonly used are the Waterfall model,Extreme Programming,and Agile programming[Koc04].These models have in common that they support the software development through introducing well-deﬁned phases,force programmers to drop their tendency to go on coding with no plan, and instead follow through with a rigorous set of activities like planning,testing,and deployment.Open source is strictly speaking not in itself a software development process like the waterfall model.Strictly speaking,most implementations of open source will even strug-gle toﬁt into IEEE’s deﬁnition of software engineering.It does not prescribe the phases10the software should go through,or its planning or testing practices.Open source is a set of principles for a development process[Koc04].These are that the software’s license should abide by the Open Source Deﬁnition[Ini05],which i.e.requires the software’s source code should be freely available together with any copies of the program.The freedom of open source the most distinctive factor when comparing commercial and open source software.This does not imply they are opposites in a software engineer-ing context,but merely two approaches for reaching software objectives.Open source has been described as a cycle of innovation in which those that have the skills share ideas and build on each other’s work[Woo05].The Open Source Initiative,however,claims that“[Open source]produces better software than the traditional closed model,in which only a very few programmers can see the source and everybody else must blindly use an opaque block of bits.”1.Whether this is true or not,a discussion of which is the better development process is meaningless in an industry where there is a need for both.Other aspects that are important for software engineering include themes such as ar-chitecture,development environments,programming languages,databases technology, software evolution,and conﬁguration management.For this thesis,the focus will be documentation artifacts in software development.The production and maintenance of documentation as separate deliverables in a project is important for adoption of software [BCK03,MD04].Documentation for developers is the primary concern of this thesis. 1.3Problem descriptionThis master’s thesis aims to determine how open source software projects produce and maintain documentation.Freely available open source programs are increasingly be-ing used as off-the-shelf components in commercial software development in order to reduce cost and time-to-market.The requirements for such off-the-shelf reuse include documenting the software thoroughly,following open standards,and easing the evalua-tion and adoption of the open source software component.The study is based on participation to the Java database system Apache Derby2.The participation will aid in understanding these practices in open source.A better under-standing of how Apache Derby implements the open source development method is ex-pected from the study,as well as experience in contributing to an open source project. Apache Derby has been considered interesting for the purposes of this thesis due to its code complexity,and its relatively widespread usage.The typical goal for open source software is to create a system which is useful or interesting to those who are working on it,while still allowing its users to adapt or evolve the system into their needs[GT00].For embedded components such as Apache Derby,its success is dependent on having an API3that simpliﬁes integration with other 1/2/derby/3Application Programming Interface,a structure or interface that allows communication between parts of a system.11systems.Having standardized interfaces with proper speciﬁcations is necessary in order for the component to be usable for adopters[CBB+02].New contributors to open source will also beneﬁt from the existence of speciﬁcations.Open source literature has previously pressed the need to highlight what characteris-tics is conductive to smooth open source development[LT00].Models and frameworks in literature highlight the process aspects of open source development[DSV03],as well as structural and cultural[SSR02].This thesis is an effort to understand the gap between open source and software architecture by focusing on how documentation practices in open source is affected by adopters’and developers’needs.Participation and contribution to the Apache Derby project is expected to aid in the understanding of existing practices in open source on these matters.The practical take on this issue can also give insight into other problems facing the open source develop-ment method with regard to documentation.Research questions posed in this study are: How is documentation maintained in the Apache Derby project?The existence of documentation in open source projects may be a requirement for both adopters and developers of open source components.Developers choosing to extend or adopt open source components may require sources of documentation that explains the architecture and design choices.Using a documented software architecture throughout the lifetime of a software sys-tem can improve the quality and maintainability of the system[BHB99],and thereby reduce cost and avoid inconsistencies in the software.Importance of documentation in open source development is also brieﬂy addressed by[BR02,VV04].Studying how open source deals with documentation further may be helpful to pre-dict success criteria for the use of an open source component.Open source may by experts be regarded as black box systems that needs no further explanation,but doc-umentation,especially architectural documentation holds the key to post-deployment system understanding[CBB+02,BCK03].Understanding the architecture is for instance the key to understand performance and reliability.What kind of documentation is needed for newcomers to open source projects? One study in[MFH02]presents the example of the Mozilla project,where documenta-tion may have been a contributing factor for the lack of outside contribution in itsﬁrst plex software developed with open source may need to take measures in order to reduce barriers for newcomers to contribute.Properties of architecture that are important for both adopters and developers are i.e. design patterns,rationales for design choices,performance and scalability of modules, and API compatibility and adherence to standards.Documentation may also serve as a vehicle for learning for various types of stakeholders.Maintaining consistent architecture in open source projects are difﬁcult for speciﬁc mercial development rarely has signiﬁcant drift between architectural plans and their implementations,while the contrary generally is true in open source due to its distributive nature[PC04].A cycle of reinvention[Sca04]that is typical for many open12source projects may be the cause.Participation to an open source project may be helpful to highlight the difﬁculties in participating due to the existence or non-existence of documentation.Open source projects are known to generally provide little documentation[VV04].It is interesting to look at reasons for this tendency,and the extent to which the assertion is true in the Apache Derby project.1.4OverviewChapter2presents the research method used in this project,the time schedule for various activities,and data collection.Chapter3presents open source in greater detail.The database system Apache Derby is then presented in Chapter4,which is the instance of an open source project that this research primarily will focus on.Chapter5will present the state-of-the-art of documentation in open source communities.Activities in this project that relates to the participation to the Apache Derby project is presented in Chapter6,followed by a discussion of the research questions in Chapter7, and conclusions in Chapter8.1314Chapter2Research methodUsing a rigorous research method is important in order to ensure that results will follow from the premises of the research situation.Work in this thesis is based on Canonical Action Research[DMK04].This chapter will further explain the Action Research method,and how this research method will help to accomplish the goal of this thesis.2.1Action researchThe role of a research method is to provide a basis for interpreting the world,and serve as a framework to collect and analyze data.Methods consist of a series of rules or guidelines to ensure that conclusions follow from the premises.Action research is a research method that is iterative and collaborative in nature.The brand of action research used here,Canonical Action Research(CAR),is based on the principles of working with an organization,and observe an organizational change pro-cess.The problem being examined is understood through interacting with or changing the organization through well-planned actions.It is similar to ethnographic methods, such as participant observation,in that it studies the phenomenon in the context it nat-urally appears in.The iterative nature of Canonical Action Research is intended to provide a systematic approach to the problem.Having well-deﬁned phases ensures that the understanding of the problem may be evolved in several stages,and that success criteria of the re-search may be properly addressed.Iterating towards a goal with planning,execution and evaluation phases also allows for brief pauses where results of the research may be communicated and discussed.In organizations,information is provided at different rmation may be known privately or collectively,implicitly or explicitly[Dic93].This relationship is illus-trated inﬁgure2.1.Being a participant in the organization is then helpful to gain insight into the practices used by the members.Rationales for practices and their beneﬁts and drawbacks can then be documented from an outside perspective,from a researcher that15is part of the system,but remains committed to the research goals.Figure2.1:Knowledge assets:Tacit and explicit knowledge(Nonaka and Takeuchi) In comparison to Grounded Theory[Pan96]research,which reverses the order of hypothesis generation and data collection,action research focuses on the evolution of a theory or understanding,or even evolution of research questions.Also comparing to classical research,action research may be an“upstream”method,where creativity and analytic skills of the researcher are vital for reaching the goals[Dic93].The CAR process also depends on the researcher’s abilities for thorough interpretations of the situation,the analysis of causes and effects,or proper communication of the facts and their interpretations.The technical skills and ability the researcher has to participate to and change the or-ganization is helpful,but not the only factor determining the success of the intervention.2.1.1Researcher-client agreementOne of the prerequisites for using Action Research is that the researcher is able to be part of the studied organization.Being able to observe an organizational change process involves being able to observe outcomes,and interact with it.The researcher should have some sort of agreement with the organization,or better yet,a written agreement on the expectations and goals of the research.For research in open source,where consensus is the main control variable,this agreement can take the form of an introduction about the researcher’s intentions,or may be dropped altogether if it is found ethically and functionally feasible.An agreement will for open source,in the understanding of this thesis,be the social contract in which work towards a common goal is done.2.1.2Cyclical process modelThe cyclical process model of CAR consists of the following phrases,as found in[DMK04]:161.Diagnosis:The purpose of the diagnosis phase is continuosly making sure theactivities in the research are relevant to the problem being examined.In an action research project that spans several iterations,the diagnosis will take the current situation understanding and integrate it into the research agenda.For instance, research questions may be further reﬁned or elaborated upon.2.Planning:As CAR involves participating to an organizational system,the plan-ning of actions should be done carefully so the correct data can be collected.The planned actions need to be accompanied with an assessment of what the expected outcome will be.The planning phase is informed directly by the Diagnosis phase.3.Intervention:CAR interventions may be restricted to days,or even months inlength.The planned actions are implemented as they are planned.Data collection should collect all the relevant observations from the intervention,but also thoughts and reﬂections during planning and evaluation phases.4.Evaluation:The results from the intervention should be subsequently analyzedwith regard to the expected output,and what has been learned.The evalua-tion phase should be performed to determine whether the intervention was im-plemented as planned,in order to document what has been learned,and if any cause/effect relationships are correct.5.Reﬂection:The researcher should reﬂect upon his own actions for the purpose oflearning from them.Outcomes from the project should be evaluated in context of the project goals.If project goals have been accomplished,then a decision should be made to exit the project.Figure2.2:The Canonical Action Research cyclical process model,[DMK04] Figure2.2shows a typical action research execution.The strength of the CAR ap-proach is that it responds to the continually changing environment.The researcher grows a better understanding of the situation,while providing suggestions or analyzes that are relevant for practitioners.172.1.3Theory and reﬂectionTheory and reﬂection have critical roles in action research.Action research addresses a problematic situation in an organization,combining theory and practice through change and reﬂection in order to contribute knowledge within and outside the conﬁnes of the project[DMK04].Action research without theory is simply action learning,and only regarded as research in a positivist tradition.The reﬂection principle of action research allows learning through understanding organizational norms,and“the advancement of knowledge by generating new theory or informing/re-informing existing theory.”[DMK04].This demonstrates that theory and reﬂection are in fact related,and that action research can extend existing knowledge ina scholarly tradition.2.2Research and education in open sourceOpen source has by deﬁnition some degree of transparency to the outside world.Open source communities are usually open for contributions and observers from the outside, which makes them good candidates for empirical research.The transparency allows as-sessment of the quality of open source projects by evaluating their activity levels and popularity.These are in many ways conductive to the level of innovation,and ability to provide corrections to the software.For open source projects that are alive and undergo-ing active development,it is simpler to participate in a research situation.Research in open source allows a student to learn both scientiﬁc methods,technical skills,while contributing to scholarly knowledge.Action research allows the student to start with basic understanding gained from literature,and consciously reﬂect on her or his learning.Observing how software development is done in practice further allows the student to reﬂect on how the software engineering profession is implemented in practice.Research that aims to provide practical guidelines should concentrate on organiza-tional problems and challenges in the profession.Methods to provide relevance in re-search include selecting a topic that is directly relevant for practitioners,basing the re-search on context-rich theories and a cumulative research tradition,and portraying the research output so that it can be used to rationalize decisions in an organization[BZ99]. In addition to the relevance of research,the rigor1is also important especially for re-viewers of research.This thesis is based on using action research,and aims to extract knowledge about open source through participation to one open source project.The relevance of this re-search for practitioners will be in that it provides suggestions for improving open source practices,or may represent a useful case study for implementers of open source projects.1Rigor means“Strict’precision’and’exactness’,”[DMK04],or“the correct use of methods and analyses appropriate to the tasks at hand”[BZ99]182.3Previous action research experienceThere have earlier been studies involving the use of action research to study open source.A master’s thesis in2003uses action research to study acceptance and integration of newcomers in small open source projects[TT03].More recently,the undersigned did a directed study in the Netbeans community in autumn2005,looking for effects of com-mercial maintainers of open source communities[Mor05].Using action research and open source in the context of education is further explored in the article in Appendix B.A number of lessons were drawn from the directed study reported on in[Mor05]. For instance,it was found that selection of an open source project to study should also consider the researcher’s abilities and interests.If the research design is dependent on contributing to the project,it imposes demands to the researcher on technical proﬁciency and interest in the project’s goals.Some of the issues that action research itself introduces,which should be expected in such a project,included:•Entering:What does it mean to enter an open source project?CAR literature has a Researcher-Client agreement as one of its principles.Such an agreement is difﬁcult in decentralized open source projects,and poses ethical challenges such as whether or not the researcher should introduce himself to the community as a researcher.•Collaboration:The researcher should attempt to discussﬁndings with other par-ticipants or peers in order to understand and evolve theories.Multiple viewpoints eases the critical interpretation ofﬁndings.Further asserted by Davison et al.in [DMK04]:“[t]he researcher must account for the values,beliefs and intentions of the client employees,and treat them as collaborators rather than mere research objects”.This may imply that community members should be introduced toﬁndings,or it may involve investigation of historic communication on the topics of interest,such as mailing list archives.•Learning through reﬂection:Explicitly stating what has been learnt is the most critical activity of CAR[DMK04].A requirement for the reﬂection to be efﬁcient, the researcher should have performed a thorough and systematic literature review in advance.This shouldn’t be neglected unless the goal focuses on learning alone.The researcher should in advance have thought about which results can be an-ticipated,the possible consequences of these,and how to prepare for the conse-quences.2.4Data collection strategyUsing action research in the context of open source research imposes constraints on which data is available for collection.The cyclical process model of action research re-quires that actions are planned ahead of each research iteration.The evolving knowledge of the studied topic will thus inﬂuence what data is collected.19。