From PEAR Wiki

Contents 1 Summary 1.1 Information 1.1.1 Document Information 1.1.2 Author(s) Information 1.1.3 Legal Information 1.1.4 Discussion List 1.2 Introduction 1.3 Summary 1.4 Approach & Requirements 1.5 Definition 1.6 Security Considerations 1.7 Possible Problems

[edit] Summary

[edit] Information

[edit] Document Information

• Title: Plagiarism Policy
• Version: 0.1.0
• Status: Draft
• Type: RFC
• Wiki link: http://wiki.pear.php.net/index.php?title=PlagiarismPolicy
• Last updated: December 20, 2007

[edit] Author(s) Information

• Name: Gregory Beaver
• Email: pear-group@php.net

[edit] Legal Information

• This RFC is under the BSD License

[edit] Discussion List

• pear-group and http://news.php.net/php.pear.dev

[edit] Introduction

This document is to outline the Plagiarism Policy for PEAR.

[edit] Summary

PEAR needs an official policy with regards to plagiarism of code (un-attributed use of external code)

[edit] Approach & Requirements

none.

[edit] Definition

• Plagiarism - using external code without attributing this code to the original author.

PEAR has a zero-tolerance policy of plagiarism. Any code proposed or committed that can be shown to be an un-attributed copy of another developer's code will be immediately deleted without consultation. In addition, developers who propose or commit code that is un-attributed will have their karma immediately revoked, and the PEAR Group will decide which of these actions is most appropriate:

1. all future code must be reviewed prior to commit.
2. a probationary period will be assigned during which all code will be reviewed, with karma restored conditionally upon the end of this period
3. revocation of all privileges and account at PEAR.

[edit] Security Considerations

None

[edit] Possible Problems

None