Skip to content
Snippets Groups Projects
Commit ab8ca0a4 authored by moberhuber's avatar moberhuber
Browse files

This commit was manufactured by cvs2svn to create tag 

'TM_3_0_IP_REVIEW_SUBMISSION'.
parent d97f9680
No related branches found
No related merge requests found
Expand all Hide whitespace changes
Inline Side-by-side
Showing
with 0 additions and 1425 deletions
.cvsignore deleted 100644 → 0
+ 0
− 5
View file @ d97f9680
sample_3col.php
sample_4col.php
sample_busypage.php
sample_list.php
template.php
.project deleted 100644 → 0
+ 0
− 11
View file @ d97f9680
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>www-tm</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
</buildSpec>
<natures>
</natures>
</projectDescription>
.settings/org.eclipse.core.resources.prefs deleted 100644 → 0
+ 0
− 5
View file @ d97f9680
#Wed Mar 05 13:00:00 CET 2008
eclipse.preferences.version=1
encoding//meetingnotes/DSDP-TM_MeetingNotes_20051107.htm=windows-1252
encoding//meetingnotes/ff01_chicago/DSDPTM_Brainstorming_2005-10-14.htm=windows-1252
encoding/<project>=ISO-8859-1
.settings/org.eclipse.ltk.core.refactoring.prefs deleted 100644 → 0
+ 0
− 3
View file @ d97f9680
#Fri Feb 08 19:53:33 CET 2008
eclipse.preferences.version=1
org.eclipse.ltk.core.refactoring.enable.project.refactoring.history=false
TM_press_text_2006_06.php deleted 100644 → 0
+ 0
− 127
View file @ d97f9680
<?php require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php"); $App = new App(); $Nav = new Nav(); $Menu = new Menu(); include($App->getProjectCommon()); # All on the same line to unclutter the user's desktop'
#*****************************************************************************
#
# tm_press_text_2006_06.php
#
# Author: Martin Oberhuber
# Date: 2006-06-09
#
# Description: TM Press Release Jun 2006
#
#
#****************************************************************************
#
# Begin: page-specific settings. Change these.
$pageTitle = "Press Text: Target Management - Jun 2006";
$pageKeywords = "Target, Embedded, Device, Press, Article";
$pageAuthor = "Martin Oberhuber";
# Add page-specific Nav bars here
# Format is Link text, link URL (can be http://www.someothersite.com/), target (_self, _blank), level (1, 2 or 3)
# $Nav->addNavSeparator("My Page Links", "downloads.php");
# $Nav->addCustomNav("My Link", "mypage.php", "_self", 3);
# $Nav->addCustomNav("Google", "http://www.google.com/", "_blank", 3);
# End: page-specific settings
#
# Paste your HTML content between the EOHTML markers!
$html = <<<EOHTML
<div id="maincontent">
<div id="midcolumn">
<h1>$pageTitle</h1>
<h2>Target Management Project</h2>
<p>The Target Management Project is creating frameworks and a consistent UI
for accessing remote compute resources from Eclipse. The current code base
(Remote Systems Explorer, RSE) supports remote file, shell and process
access through a supplied Java based agent, or standard protocols like FTP
and secure shell (ssh). Adopters are currently writing extensions to bring
their own proprietary protocols into the framework for accessing devices
like hardware debuggers. A 1.0 release is planned for October 20, a functional
complete milestone (M3) is planned for June 30. A 2.0 release shall be aligned
with Eclipse 3.3 in June 2007.</p>
<p>For the 2.0 release planning and the longer term future, the TM project
participants are dealing with advanced extensions to the framework in
various technology sub-groups (see
<a href="http://wiki.eclipse.org/DSDP/TM">http://wiki.eclipse.org/DSDP/TM</a>).
Active discussions are also going on for collaboration with other Eclipse
Projects, especially the
<a href="http://www.eclipse.org/cdt">CDT project</a>, the
<a href="http://www.eclipse.org/ecf">Eclipse Communication Framework (ECF)</a>, the
<a href="http://www.eclipse.org/ptp">Parallel Tools Platform (PTP)</a>, and the
<a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/main.html">
Eclipse Platform/Team group.</a>
A comprehensive
<a href="http://www.eclipse.org/dsdp/tm/doc/DSDPTM_Use_Cases_v1.1c.pdf">document
outlining the use-cases</a> and applicability
of the Target Management Project is available from the "Getting Started"
area on the Project Website at
<a href="http://www.eclipse.org/dsdp/tm">http://www.eclipse.org/dsdp/tm</a>.
</p>
<h4>active project participants:</h4>
<ul><li>IBM - 3 committers + 1 contributor, core RSE development</li>
<li>Windriver - 1 committer, contributed ssh services, lots of testing, project lead and communications</li>
<li>PalmSource - contributed CDT Launch</li>
<li>Symbian - bugfixes, about to contribute zeroconf-discovery</li>
<li>PTP Project/LANL - testing on Macintosh, EFS, ssh</li>
</ul>
<h4>active adopters:</h4>
<ul><li>Freescale - writing proprietary wizards for JTAG on RSE</li>
<li>Accelerated Technology - about to write proprietary Services for JTAG on RSE</li>
<li>Montavista</li>
<li>Siemens</li>
</ul>
<h4>features committed to CVS:</h4>
<ul><li>Remote file system access through ssh, ftp or dstore protocols</li>
<li>Remote shell (command) access through ssh or dstore protocols</li>
<li>Remote process access through dstore protocol on Linux</li>
<li>dstore protocol implementation and agent for remote search, remote archive exploring, remote process and other pluggable miners</li>
<li>CDT Remote Launch Integration Example</li>
<li>Common UI - Single consistent view, including filters</li>
<li>Team sharing of connection and filter definitions</li>
<li>Framework for plugging in custom protocols, services and subsystems</li>
</ul>
<h4>what features are coming next:</h4>
<ul><li>user-defined menus and actions for instant access to remote programs</li>
<li>import/export wizards for fast remote file transfer</li>
<li>Apache Commons Net integration for FTP, Telnet</li>
<li>Bring documentation/examples up-to-date</li>
</ul>
<h4>release plans:</h4>
<ul><li>1.0 release planned for October 20
<ul><li>M3 milestone (June 30) to be feature complete</li>
</ul></li>
<li>2.0 release planned with Eclipse 3.3 June 2007</li>
</ul>
<h4>recruiting efforts:</h4>
<ul><li>A lot of companies is already active on the TM project, we continue to lower the bar for using and extending the RSE</li>
<li>Communications with other Eclipse projects, e.g. Platform/Team, TPTP and WTP. They all have some need for remote system access.</li>
<li>RSE ssh tools will be useful for every Eclipse committer, we want to give simple access through an update site (and announce
publicly among all committers) our M3 milestone end of june</li>
</ul>
<h4>quotation from the project lead:</h4>
"The real benefit of RSE is that it gathers lots of totally heterogeneous systems and subsystems under a single consistent view."
<p/>
</div>
</div>
EOHTML;
# Generate the web page
$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
?>
_projectCommon.php deleted 100644 → 0
+ 0
− 140
View file @ d97f9680
<?php
# <modeling variables>
$PR = "dsdp/tm";
$projectName = "Target Management";
$isEMFserver = (preg_match("/^emf(?:\.torolab\.ibm\.com)$/", $_SERVER["SERVER_NAME"]));
$isBuildServer = (preg_match("/^(dsdp|build)\.eclipse\.org$/", $_SERVER["SERVER_NAME"])) || $isEMFserver;
$isBuildDotEclipseServer = $_SERVER["SERVER_NAME"] == "build.eclipse.org";
$isWWWserver = (preg_match("/^(?:www.|)eclipse.org$/", $_SERVER["SERVER_NAME"]));
$isEclipseCluster = (preg_match("/^(?:www.||download.|download1.|build.)eclipse.org$/", $_SERVER["SERVER_NAME"]));
$debug = (isset ($_GET["debug"]) && preg_match("/^\d+$/", $_GET["debug"]) ? $_GET["debug"] : -1);
$writableRoot = ($isBuildServer ? $_SERVER["DOCUMENT_ROOT"] . "/dsdp/includes/" : "/home/data/httpd/writable/dsdp/");
$writableBuildRoot = $isBuildDotEclipseServer ? "/opt/public/dsdp" : "/home/www-data";
$rooturl = "http://" . $_SERVER["HTTP_HOST"] . "/$PR";
$downurl = ($isBuildServer ? "" : "http://www.eclipse.org");
$bugurl = "https://bugs.eclipse.org";
# Set the theme for your project's web pages.
# See the Committer Tools "How Do I" for list of themes
# https://dev.eclipse.org/committers/
# Optional: defaults to system theme
#$theme = "Lazarus";
if (isset ($_GET["skin"]) && preg_match("/^(Blue|EclipseStandard|Industrial|Lazarus|Miasma|Modern|OldStyle|Phoenix|PhoenixTest|PlainText)$/", $_GET["skin"], $regs))
{
$theme = $regs[1];
}
else
{
$theme = "Lazarus";
}
/* projects/components in cvs */
/* "proj" => "cvsname" */
#$cvsprojs = array (); /* should always be empty */
$cvsprojs = array (
"rse" => "org.eclipse.tm.rse"
);
/* sub-projects/components in cvs for projects/components above (if any) */
/* "cvsname" => array("shortname" => "cvs-subname") */
$cvscoms = array(
"org.eclipse.tm.core" => array (
"terminal" => "terminal",
"discovery" => "discovery"
/* add more here */
)
);
/* Readable Project names: "bugzilla component" => "shortname" */
$projects = array(
"RSE" => "rse",
#"TCF" => "tcf",
"Terminal" => "terminal",
#"Core" => "discovery",
);
$bugcoms = array_flip($projects);
$bugcoms = preg_replace("/ /", "%20", $bugcoms);
$extraprojects = array(); //components with only downloads, no info yet, "prettyname" => "directory"
$nodownloads = array("coordinated","jcrm","temporality", "emf4net"); //components with only information, no downloads, or no builds available yet, "projectkey"
$nonewsgroup = array(); //components without newsgroup
$nomailinglist = array(); //components without mailinglist
#$incubating = $projects; // ALL components are incubating
$incubating = array("tcf"); //Only TCF is incubating for now
$hasmoved = array(
"query" => "emf", "transaction" => "emf", "validation" => "emf",
"eodm" => "mdt", "ocl" => "mdt",
"jet" => "m2t", "jeteditor" => "m2t"); // components which have moved, and to where
$nomenclature = "Component"; //are we dealing with "components" or "projects"?
include_once $_SERVER["DOCUMENT_ROOT"] . "/dsdp/includes/scripts.php";
$regs = null;
$proj = (isset($_GET["project"]) && preg_match("/^(" . join("|", $projects) . ")$/", $_GET["project"], $regs) ? $regs[1] : getProjectFromPath($PR));
$projct= preg_replace("#^/#", "", $proj);
$buildtypes = array(
"R" => "Release",
"S" => "Stable",
"I" => "Integration",
"M" => "Maintenance",
"N" => "Nightly"
);
# </modeling variables>
# Define your project-wide Nav bars here.
# Format is Link text, link URL (can be http://www.someothersite.com/), target (_self, _blank), level (1, 2 or 3)
# these are optional
#$Nav->addNavSeparator("Target Management", "/dsdp/tm/index.php");
#$Nav->addCustomNav("About", "/dsdp/tm/about.php", "_self", 2);
#$Nav->addCustomNav("Downloads", "/dsdp/tm/downloads.php", "_self", 2);
#$Nav->addCustomNav("Getting Started", "/dsdp/tm/tutorial/index.php", "_self", 2);
#$Nav->addCustomNav("Development", "/dsdp/tm/development/index.php", "_self", 2);
$Nav->setLinkList(array());
$branding = <<<EOBRANDING
<div id="branding">
<h1><a href="http://eclipse.org/dsdp/tm/">Target Management (RSE)</a></h1>
</div>
EOBRANDING;
$Menu->setProjectBranding($branding);
$Nav->addNavSeparator("Target Management", "/dsdp/tm");
$Nav->addCustomNav("About This Project", "http://www.eclipse.org/projects/project_summary.php?projectid=dsdp.tm", "_self", 1);
#$Nav->addCustomNav("About", "/dsdp/tm/tm-new/about", "_self", 2);
#$Nav->addCustomNav("Team", "/dsdp/tm/tm-new/team", "_self", 2);
$Nav->addCustomNav("Team", "/dsdp/tm/development/contributors.php", "_self", 2);
#$Nav->addCustomNav("Demos", "/dsdp/tm/tm-new/demos", "_self", 2);
#$Nav->addCustomNav("Wiki", "http://wiki.eclipse.org/DSDP/TM", "_self", 2);
$Nav->addNavSeparator("Users", "", "_self", 2);
$Nav->addCustomNav("Getting Started", "/dsdp/tm/tutorial/index.php", "_self", 2);
$Nav->addCustomNav("Downloads", "http://download.eclipse.org/dsdp/tm/downloads/index.php", "_self", 2);
$Nav->addCustomNav("FAQ (wiki)", "http://wiki.eclipse.org/TM_and_RSE_FAQ", "_self", 2);
$Nav->addCustomNav("Newsgroup", "http://dev.eclipse.org/newslists/news.eclipse.dsdp.tm/maillist.html", "_self", 2);
$Nav->addCustomNav("Bugs", "/dsdp/tm/bugs", "_self", 2);
$Nav->addNavSeparator("Integrators", "", "_self", 2);
$Nav->addCustomNav("API Plan", "/dsdp/tm/development/plan.php", "_self", 2);
$Nav->addCustomNav("Documents", "/dsdp/tm/doc/", "_self", 2);
#$Nav->addCustomNav("Release Notes", "/$PR/news/relnotes.php?project=$proj&amp;version=HEAD", "_self", 2);
#$Nav->addCustomNav("Legal", "dsdp/tm/development/tm-log.csv", "_self", 2);
$Nav->addNavSeparator("Contributors", "/dsdp/tm/development/contributors.php", "_self", 2);
$Nav->addCustomNav("Contributing (wiki)", "http://wiki.eclipse.org/TM_and_RSE_FAQ#Working_on_TM_.2F_RSE", "_self", 2);
$Nav->addCustomNav("Mailing List", "https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev", "_self", 2);
$Nav->addCustomNav("CVS", "/dsdp/tm/development/cvs_setup.php", "_self", 2);
$Nav->addCustomNav("Development Tools", "/dsdp/tm/development/", "_self", 2);
$Nav->addCustomNav("Search CVS", "/$PR/searchcvs.php?q=file%3A+org.eclipse.tm%25%2F" . "+days%3A+7", "_self", 2);
$collist = "%26query_format%3Dadvanced&amp;column_changeddate=on&amp;column_bug_severity=on&amp;column_priority=on&amp;column_rep_platform=on&amp;column_bug_status=on&amp;column_product=on&amp;column_component=on&amp;column_version=on&amp;column_target_milestone=on&amp;column_short_short_desc=on&amp;splitheader=0";
#$Nav->addCustomNav("Open Bugs", "$bugurl/bugs/colchange.cgi?rememberedquery=product%3D" . $projectName . (isset ($bugcoms[$proj]) ? "%26component=$bugcoms[$proj]" : "") . "%26bug_status%3DNEW%26bug_status%3DASSIGNED%26bug_status%3DREOPENED%26order%3Dbugs.bug_status%2Cbugs.target_milestone%2Cbugs.bug_id" . $collist, "_self", 2);
#$App->AddExtraHtmlHeader("<link rel=\"stylesheet\" type=\"text/css\" href=\"/dsdp/includes/common.css\"/>\n");
unset ($bugcoms);
?>
about.php deleted 100644 → 0
+ 0
− 125
View file @ d97f9680
<?php require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php"); $App = new App(); $Nav = new Nav(); $Menu = new Menu(); include($App->getProjectCommon()); # All on the same line to unclutter the user's desktop'
#*****************************************************************************
#
# template.php
#
# Author: Martin Oberhuber
# Date: 2006-02-01
#
# Description: Type your page comments here - these are not sent to the browser
#
#
#****************************************************************************
#
# Begin: page-specific settings. Change these.
$pageTitle = "About Target Management";
$pageKeywords = "device, target";
$pageAuthor = "Martin Oberhuber";
# Add page-specific Nav bars here
# Format is Link text, link URL (can be http://www.someothersite.com/), target (_self, _blank), level (1, 2 or 3)
# $Nav->addNavSeparator("My Page Links", "downloads.php");
# $Nav->addCustomNav("My Link", "mypage.php", "_self", 3);
# $Nav->addCustomNav("Google", "http://www.google.com/", "_blank", 3);
# End: page-specific settings
#
# Paste your HTML content between the EOHTML markers!
$html = <<<EOHTML
<div id="maincontent">
<div id="midcolumn">
<h1>$pageTitle</h1>
<h2>Mission Statement</h2>
The Target Management project creates data models and frameworks
to configure and manage remote systems, their connections, and their services.
</P>
<UL>
<LI><I>Remote systems</I> (aka targets) can range from large-scale host computers, multi-board
or multi-core parallel systems to target boards without even a CPU or FPGA (connected
by a hardware debugging box).</LI>
<LI><I>Configuration</I> means dealing with board description files from a variety of sources,
displaying remote system components and manipulating board and connection properties.</LI>
<LI><I>Management</I> means maintaining a list of remote systems which is team
shareable and available to other subsystems, creating groups of systems when appropriate,
and handling access control to targets that are shared in a team (board lab).</LI>
<LI><I>Connections</I> can range from TCP/IP standard protocols like FTP or telnet,
secure encryption, authentication and firewall tunnelling (ssh), to serial line terminal and
vendor-specific protocols for remote agent and on-chip debugging (JTAG) solutions.
We want connection schemes and protocols to be pluggable in our framework.</LI>
<LI><I>Services</I> on remote systems include downloading software and data,
launching single or multiple configurations, starting and stopping cores,
resetting and querying target information.</LI>
</UL>
<P>
Since there are many different vendors and solutions around in the device software
space, the main charter of target management is to provide data models and frameworks
that are flexible and open enough for vendor-specific extensions. Sample implementations
are provided for TCP/IP Secure Shell (ssh) connections, FTP data transfer and gdb remote launching
in the CDT environment. The basis for our implementations is an open-source version
of the <A HREF="http://www.developer.ibm.com/isv/rational/remote_system_explorer.html">
IBM Remote System Explorer</A>. Current releases can be downloaded for evaluation
<a href="http://download.eclipse.org/dsdp/tm/downloads/">here</a>.
<div class="homeitem3col">
<h3>For more information, see the</h3>
<ul>
<li><a href="http://www.eclipse.org/downloads/download.php?file=/dsdp/tm/presentations/2006-9-29_SummitEurope_TMOverview.pdf">
Target Management Overview Slides</a>
which include a diagram of the envisioned components and architecture for our project
(<a href="http://www.eclipse.org/downloads/download.php?file=/dsdp/tm/presentations/2006-9-29_SummitEurope_TMOverview.ppt">PPT</a>
| <a href="http://www.eclipse.org/downloads/download.php?file=/dsdp/tm/presentations/2006-9-29_SummitEurope_TMOverview.pdf">PDF</a>).
</li>
<li><a href="http://live.eclipse.org/node/229">TM Webinar</a>:
goals, architecture, future plans and online demo
(<a href="http://live.eclipse.org/node/229">50 minute full recording</a> |
<a href="http://www.eclipse.org/projects/slides/TM_Webinar_Slides_070412.ppt">PPT slides</a>)
</li>
<li><a href="http://wiki.eclipse.org/DSDP">
DSDP Top-Level Overview Diagrams</a> to understand how the Target Management
Project fits into DSDP, and what its basic building blocks are.</li>
<li><a href="/dsdp/tm/doc/DSDPTM_Use_Cases_v1.1c.pdf">
Target Management Use-Case Document</a>
to understand what scenarios we want to cover with our project.</li>
<li><a href="http://www.developer.ibm.com/isv/rational/rse_pres.pdf">
IBM Remote Systems Explorer (RSE) Presentation</a>
to get a preview of what RSE looks like.
<li><a href="/dsdp/tm/development/plan.php">
Target Management Project Planning</a>
to understand what features and releases are coming next.</li>
</ul>
</div>
</div>
<div id="rightcolumn">
<div class="sideitem">
<h6>Getting started</h6>
<ul>
<li><a href="/dsdp/tm/tutorial/index.php"
target="_self">TM Getting Started</a></li>
<li><a href="http://www.eclipse.org/downloads/download.php?file=/dsdp/tm/presentations/2006-9-29_SummitEurope_TMOverview.pdf"
target="_self">TM Overview Slides</a></li>
<li><a href="http://live.eclipse.org/node/229">TM Webinar</a>
</li>
<li><a href="http://www.eclipse.org/downloads/download.php?file=/dsdp/tm/presentations/TM_2.0_Release_Review.ppt" target="_self">
TM 2.0 Release Review Slides</a></li>
<li><a href="http://wiki.eclipse.org/DSDP"
target="_self">DSDP Overview Diagrams</a></li>
<li><a href="/dsdp/tm/doc/DSDPTM_Use_Cases_v1.1c.pdf"
target="_self">TM Use Cases Document</a></li>
<li><a href="/dsdp/tm/development/plan.php"
target="_self">TM Project Plan</a></li>
</ul>
</div>
</div>
EOHTML;
# Generate the web page
$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
?>
bugs/index.php deleted 100644 → 0
+ 0
− 78
View file @ d97f9680
<?php require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php"); $App = new App(); $Nav = new Nav(); $Menu = new Menu(); include($App->getProjectCommon()); # All on the same line to unclutter the user's desktop'
#*****************************************************************************
#
# index.php
#
# Author: Kevin Doyle
# Date: 2008-01-25
#
# Description: Display a list of bug queries and how to open a new bug
#
#
#****************************************************************************
#
# Begin: page-specific settings. Change these.
$pageTitle = "Target Management Bugs";
$pageKeywords = "target management, remote system explorer, tm, rse, Eclipse, device, target";
$pageAuthor = "Kevin Doyle";
# Add page-specific Nav bars here
# Format is Link text, link URL (can be http://www.someothersite.com/), target (_self, _blank), level (1, 2 or 3)
# $Nav->addNavSeparator("My Page Links", "downloads.php");
# $Nav->addCustomNav("My Link", "mypage.php", "_self", 3);
# $Nav->addCustomNav("Google", "http://www.google.com/", "_blank", 3);
# End: page-specific settings
#
# Paste your HTML content between the EOHTML markers!
$html = <<<EOHTML
<div id="maincontent">
<div id="midcolumn">
<div class="homeitem3col">
<h3>Found a Bug? Have an enhancement idea?</h3>
<ul>
<li>You can submit bugs/enhancement requests though <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Target%20Management&version=unspecified&component=RSE">Bugzilla</a>.</li>
<li>See the <a href="http://wiki.eclipse.org/TM_and_RSE_FAQ#How_do_I_report_a_bug_or_request_a_feature.3F">FAQ</a> for what to include in your bug reports</li>
</ul>
</div>
<div class="homeitem3col">
<h3>Queries</h3>
<ul>
<li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit&field0-0-0=priority&type0-0-0=regexp&value0-0-0=P%5B12%5D&field0-0-1=bug_severity&type0-0-1=regexp&value0-0-1=blocker%7Ccritical%7Cmajor">
Open severe bugs (blocker, critical, major, P1, P2)</a></li>
<li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=normal&cmdtype=doit">
All open bugs with severity normal</a></li>
<li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=minor&bug_severity=trivial&cmdtype=doit">
All open bugs with severity minor or trivial</a></li>
<li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=DSDP&product=Target+Management&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=enhancement&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">
All open enhancement requests</a></li>
<li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=DSDP&product=Target+Management&component=RSE&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">
Remote System Explorer bugs</a></li>
<li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=DSDP&product=Target+Management&component=Terminal&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">
Terminal bugs</a></li>
<li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=DSDP&product=Target+Management&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">
BugDay Bugs</a></li>
<li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=DSDP&product=Target+Management&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=helpwanted&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">
Helpwanted Bugs</a></li>
<li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=DSDP&product=Target+Management&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">
All Resolved Bugs</a></li>
</ul>
<p>
See the <a href="/dsdp/tm/development/bug_process.php">Bug Process Page</a> for more queries and information.
<p>
</div>
</div>
</div>
EOHTML;
# Generate the web page
$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
?>
build/.cvsignore deleted 100644 → 0
+ 0
− 1
View file @ d97f9680
.htaccess
\ No newline at end of file
build/_common.php deleted 100644 → 0
+ 0
− 26
View file @ d97f9680
<?php
require_once ("../../includes/buildServer-common.php");
$options = array (
"BaseBuilderBranch" => "M4_34",
"BranchAndJDK" => array (
"dsdp.eclipse.org=------------,------------",
"3.0.0=HEAD,/opt/sun-java2-5.0",
"2.0.3=R2_0_maintenance,/opt/sun-java2-5.0",
#"1.0.2=R1_0_maintenance,/opt/sun-java2-1.4",
"build.eclipse.org=------------,------------",
"3.0.0=HEAD,/opt/public/common/ibm-java2-ppc-50",
"2.0.3=R2_0_maintenance,/opt/public/common/ibm-java2-ppc-50",
#"1.0.2=R1_0_maintenance,/opt/public/stp/apps/IBMJava2-ppc-142" // bug 178681
),
"Mapfile_Rule_Default" => 0, // 0: "Use Map, No Tagging=use-false" or 1:"Generate Map, No Tagging=gen-false"
"EmailDefault" => "martin.oberhuber@windriver.com", // prefil email contact box with comma-sep'd list
"Users" => array("moberhuber","moberhuber","moberhuber") /* build user, eclipse cvs user, IES cvs user */
);
?>
build/index.php deleted 100644 → 0
+ 0
− 1
View file @ d97f9680
<?php require_once ("_common.php"); require_once ($_SERVER['DOCUMENT_ROOT'] . "/dsdp/build/build-common.php"); ?>
build/log-viewer.php deleted 100644 → 0
+ 0
− 2
View file @ d97f9680
<?php require_once ("../../includes/buildServer-common.php");
require_once ($_SERVER['DOCUMENT_ROOT'] . "/dsdp/build/log-viewer-common.php"); ?>
build/removeRelease.php deleted 100644 → 0
+ 0
− 4
View file @ d97f9680
<?php
require_once ("../../includes/buildServer-common.php");
require($_SERVER["DOCUMENT_ROOT"] . "/modeling/includes/removeRelease-common.php");
?>
build/sideitems-common.php deleted 100644 → 0
+ 0
− 33
View file @ d97f9680
<?php
/* extra sidebar stuff appended at the bottom */
function sidebar()
{
global $PR, $projct, $isBuildServer, $isEMFserver;
if ($isBuildServer)
{
?>
<div class="sideitem">
<h6>Actions</h6>
<ul>
<li><a href="/<?php print $PR; ?>/<?php print $projct ? $projct : "compare"; ?>/build/">Build</a>,
<a href="/<?php print $PR; ?>/<?php print $projct ? $projct : "compare"; ?>/build/promo.php">Promote</a></li>
<li><a href="/<?php print $PR; ?>/downloads/?project=<?php print $projct ? $projct : "compare"; ?>&amp;showAll=0&amp;showMax=5&amp;sortBy=date">See Recent Builds</a></li>
</ul>
</div>
<div class="sideitem">
<h6>Info</h6>
<ul>
<li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?product=Target+Management&amp;component=<?php echo $projct; ?>&amp;bug_status=ASSIGNED">Assigned Bugs</a></li>
<li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?product=Target+Management&amp;component=<?php echo $projct; ?>&amp;bug_status=RESOLVED">Resolved Bugs</a></li>
<li><a href="http://www.eclipse.org/dsdp/tm/searchcvs.php?q=branch%3A+HEAD+days%3A+7">Development This Week</a></li>
<li><a href="http://www.eclipse.org/dsdp/tm/searchcvs.php?q=branch%3A+R+days%3A+7">Maintenance This Week</a></li>
<!-- <li><a href="http://emf.torolab.ibm.com/<?php print $PR; ?>/downloads/downloads.php">Download Stats</a></li> -->
<li><a href="http://wiki.eclipse.org/Modeling_Project_Releng">Modeling Project Releng Help</a></li>
</ul>
</div>
<?php
}
}
?>
conferences/2005_CDT_Conference_DSDP_Update.ppt deleted 100644 → 0
+ 0
− 0
View file @ d97f9680
File deleted
development/.project deleted 100644 → 0
+ 0
− 11
View file @ d97f9680
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>www-tm-development</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
</buildSpec>
<natures>
</natures>
</projectDescription>
development/.settings/org.eclipse.core.resources.prefs deleted 100644 → 0
+ 0
− 3
View file @ d97f9680
#Wed Mar 05 13:00:00 CET 2008
eclipse.preferences.version=1
encoding/<project>=ISO-8859-1
development/bug_process.php deleted 100644 → 0
+ 0
− 377
View file @ d97f9680
This diff is collapsed.
development/committer_guide.php deleted 100644 → 0
+ 0
− 140
View file @ d97f9680
<?php require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php"); $App = new App(); $Nav = new Nav(); $Menu = new Menu(); include($App->getProjectCommon()); # All on the same line to unclutter the user's desktop'
#*****************************************************************************
#
# committer_guide.php
#
# Author: Martin Oberhuber
# Date: 2006-05-10
#
# Description: Committer Guidelines for the DSDP TM Project
#
#
#****************************************************************************
#
# Begin: page-specific settings. Change these.
$pageTitle = "TM Committer Guidelines";
$pageKeywords = "DSDP, Target Management, Committer, Guidelines";
$pageAuthor = "Martin Oberhuber";
# Add page-specific Nav bars here
# Format is Link text, link URL (can be http://www.someothersite.com/), target (_self, _blank), level (1, 2 or 3)
# $Nav->addNavSeparator("My Page Links", "downloads.php");
# $Nav->addCustomNav("My Link", "mypage.php", "_self", 3);
# $Nav->addCustomNav("Google", "http://www.google.com/", "_blank", 3);
# End: page-specific settings
#
# Paste your HTML content between the EOHTML markers!
$html = <<<EOHTML
<div id="midcolumn">
<h1>$pageTitle</h1>
<p>While we do not want to get too process-heavy, there are a few simple
things that will make all our lives easier. See also the
<a href="committer_howto.php">committer HOWTO</a>
for simple cookbook-style instructions for common tasks.</p>
<h2>Bugzilla Guidelines</h2>
<ul>
<li>See the <a href="/dsdp/tm/development/bug_process.php">Bug Process Page</a>
for bugzilla queries to find interesting bugs, and our general bug process
(handling bugzilla states and priorities)<p/></li>
<li>When you check in a fix for a bugzilla entry, <b>please</b> include
the bugzilla number in the commit message. Example:
<b>"[139207] Fix browsing into tar archives by dstore"</b>.<p/></li>
<li>After committing a fix for bugzilla, set the entry <b>FIXED</b>.
Do not set it closed until it has been tested and verified by somebody
else.<p/></li>
</ul>
<h2>Checkin Policies</h2>
<ul><li>When you add a new plugin, feature or other project to your workspace,
please update the <b>Team Project Sets</b> so that other committers or
CVS users can pick up your new project easily: Add the "www-tm-development"
project to your workspace. You can do this most easily by importing the
Team Project set from<ul>
<li><a href="http://www.eclipse.org/dsdp/tm/development/www-tm-development.psf">
http://www.eclipse.org/dsdp/tm/development/www-tm-development.psf</a></li>
</ul>
Update the Project sets there and commit them to the web page:<ul>
<li><a href="http://www.eclipse.org/dsdp/tm/development/rse-committer.psf">
http://www.eclipse.org/dsdp/tm/development/rse-committer.psf</a></li>
<li><a href="http://www.eclipse.org/dsdp/tm/development/rse-anonymous.psf">
http://www.eclipse.org/dsdp/tm/development/rse-anonymous.psf</a></li>
</ul>You can either export a selection as team project set, or edit the
project set manually. For the pserver version, you typically need to replace-all
":extssh:" by ":pserver:".<p/></li>
</ul>
<h2>IP Due Diligence</h2>
When you check in a contributed patch, we <b>have to follow IP Due Diligence
guidelines</b>, as outlined on the
<a href="http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf">
Eclipse IP Process Flowchart</a> and the
<a href="http://www.eclipse.org/projects/dev_process/project-log.php">
Project Log Guidelines</a>:<p/>
<ul>
<li>Check the contribution. In case of any uncertainty, consult the
TM Lead, or Eclipse Legal:
<ul><li>Does the contributor have sufficient <b>rights to contribute</b>?
In other words, is it written by the contributor himself without
referencing any 3rd party materials?</li>
<li>Does the contribution include <b>anything not under EPL,
or amount to &gt; 250 lines of code</b> including all documentation
etc.? If yes, a
<a href="http://www.eclipse.org/legal/ContributionQuestionnairePart1-v1.0.php">
Contribution Questionnaire</a> has to be filled out!
(The 250 line clause can be waived if the contributor is a committer
himeself, and there is a member committer agreement in place for
his employer company; it may also be waived for plain bug fixes).</li><p/>
</ul>
<li>Add the "www-tm-development" project to your workspace. You can do
this most easily by importing the Team Project set
from<ul><li>
<a href="http://www.eclipse.org/dsdp/tm/development/www-tm-development.psf">
http://www.eclipse.org/dsdp/tm/development/www-tm-development.psf</a>
</li></ul>
In the www-tm project, add a line for the contribution in the <b>tm-log.csv</b>
file. There are some sample lines already, so adding one should not be too hard.<p/></li>
<li>Before committing both the code changes and the tm-log.csv, for any files
patched by the contribution, add a <b>credit line for the contributor</b> into the
file's copyright notice. It's good practice to give credit to our contributors.
(when a whole new file is added by the contribution, leave the copyright notice
as is, of course).<p/></li>
<li>Make sure the bugzilla number is part of the commit message.</li>
<li>For more details, see the <a href="/dsdp/tm/development/committer_howto.php#external_contrib">Committer Howto
on applying a patch from an external contributor</a></li>.
</ul>
<h2>Coding Guidelines</h2>
We <b>do not want to be too restrictive right now</b> - especially do not
rewrite existing code just to make it conform to some naming convention.
Most of the RSE code seems to follow proper coding style already. In the
end, we'll want to produce code and APIs of
<a href="http://www.eclipse.org/projects/dev_process/eclipse-quality.php">
Eclipse Quality</a>. Therefore, we better strive for quality early. Which means, try
to follow common accepted guidelines for writing new code<p/>
Some useful references are
<ul><li>The <a href="http://wiki.eclipse.org/API_Central">Eclipse Platform API Central</a></li>
<li>The <a href="http://wiki.eclipse.org/Development_Conventions_and_Guidelines">Eclipse Platform Devlopment Guidelines</a></li>
</ul>
<h2>Other stuff for reference</h2>
The <a href="http://www.eclipse.org/projects/dev_process/Eclipse_Standard_TopLevel_Charter_v1.0.php">
Eclipse Standard Charter</a> (as referenced by the <a href="http://www.eclipse.org/dsdp/dsdp-charter.php">
DSDP Project Charter</a>) has more information about committer rights
and duties, and our development process.<p/>
In particular, this charter says that committers need to agree on the
<a href="/dsdp/tm/development/plan.php">project plan</a> and its modifications,
and that committers can veto code changes.<p/>
</div>
EOHTML;
# Generate the web page
$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
?>
development/committer_howto.php deleted 100644 → 0
+ 0
− 333
View file @ d97f9680
<?php require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php"); $App = new App(); $Nav = new Nav(); $Menu = new Menu(); include($App->getProjectCommon()); # All on the same line to unclutter the user's desktop'
#*****************************************************************************
#
# committer_howto.php
#
# Author: Martin Oberhuber
# Date: 2006-05-23
#
# Description: Committer Howto for the DSDP TM Project
#
#
#****************************************************************************
#
# Begin: page-specific settings. Change these.
$pageTitle = "TM Committer Howto";
$pageKeywords = "DSDP, Target Management, Committer, Howto, Guidelines, IP";
$pageAuthor = "Martin Oberhuber";
# Add page-specific Nav bars here
# Format is Link text, link URL (can be http://www.someothersite.com/), target (_self, _blank), level (1, 2 or 3)
# $Nav->addNavSeparator("My Page Links", "downloads.php");
# $Nav->addCustomNav("My Link", "mypage.php", "_self", 3);
# $Nav->addCustomNav("Google", "http://www.google.com/", "_blank", 3);
# End: page-specific settings
#
# Paste your HTML content between the EOHTML markers!
$html = <<<EOHTML
<div id="midcolumn">
<h1>$pageTitle</h1>
<p>While we do not want to get too process-heavy, there are a few simple
things that will make all our lives easier. Here are a few "howto..."
cookbook-style instructions for performing typical committer tasks.</p>
<p>If you need any background information regarding these instructions,
look at the <a href="committer_guide.php">committer guidelines</a>.
<p>How do I...
<ul>
<li><a href="#check_code">Properly check my code before checkin</a></li>
<li><a href="#format_checkin_comment">Format my checkin comment</a></li>
<li><a href="#checkin_fix">Work with bugs and fixes</a></li>
<li><a href="#external_contrib">Apply a patch from an external contributor</a></li>
<li><a href="#project_log">Edit the TM Project Log (tm-log.csv)</a></li>
<li><a href="#sloccount">Count lines of code in a contribution</a></li>
<li><a href="#legacy_code">Add some legacy code to the project</a></li>
<li><a href="#add_plugin">Add a plugin or other project to the workspace</a></li>
<li><a href="#fix_copyrights">Find missing or incorrect Copyright notices in my code and fix them</a></li>
</ul>
</p>
<a name="check_code"></a>
<h2>Properly check my code before checkin</h2>
<ul>
<li>Ensure that you have <a href="/dsdp/tm/development/compiler_warnings.php">Compiler Warnings
</a> switched on as recommended. For every file that you modify, please ensure that it
compiles without warnings before you check it in.</li>
<li>Keep the <a href="http://wiki.eclipse.org/DSDP/TM/Code_Ownership">
Code Ownership Page</a> up-to-date on the Wiki.</li>
</ul>
<a name="format_checkin_comment"></a>
<h2>Format my checkin comment</h2>
<p>
There are
<a href="http://wiki.eclipse.org/Search_CVS%2C_Release_Notes%2C_%26_Build_News">
tools available</a> which build a MySQL database of all CVS
checkins and allow searching it, or even associate checkins with
bugzilla bugs in order to generate release notes:
for example see the
<a href="http://www.eclipse.org/modeling/emf/searchcvs.php?q=project%3A+org.eclipse.emf+days%3A+7">
EMF Search CVS</a> and
<a href="http://www.eclipse.org/modeling/emf/news/relnotes.php?project=emf&version=HEAD">
EMF Release Notes</a>.</p>
<p>
At the TM project, we'll want to make use of these tools as soon
as possible. In order to associate cvs checkins with bugzilla,
these tools need the bug id properly formatted in the checkin comment.
Multiple formats are supported, but this is the preferred one (see also
<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=164719">
bug 164719</a> and
<a href="http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg00732.html">
this e-mail</a>):
<ul>
<li>All checkin comments should be formatted like this:<br/>
&nbsp;&nbsp;&nbsp;&nbsp;<b>[123456] fixing ugly images</b><br/>
&nbsp;&nbsp;&nbsp;&nbsp;<b>[123456] apply patch from Ewa Matejska for remotecdt-over-dstore</b><p/>
Where the number [123456] references a bugzilla number, of course. Checkins that fix
multiple bugs should have the various bug numbers listed on a separate line of the
checkin comment each.
</ul>
<a name="checkin_fix"></a>
<h2>Work with bugs and fixes</h2>
<ul>
<li>See the <a href="/dsdp/tm/development/bug_process.php">Bug Process Page</a>
for bugzilla queries to find interesting bugs, and our general bug process
(handling bugzilla states and priorities)</li>
<li>Test your fix once to verify that it actually works - if this is
not too difficult. You may also place a note on the bugzilla report,
asking the original submitter to verify.</li>
<li>Ideally, write a JUnit test to make sure the bug will not creep
in again (may not always be applicable).</li>
<li>Commit your fix, <a href="#format_checkin_comment">adding the bugzilla number</a>
to the commit message.
Example: <ul>
<li><b>[139207] fix browsing into tar archives by dstore</b></li>
</ul></li>
<li>Set the <b>bugzilla report FIXED</b> and verify that the bugzilla
<b>Target Milestone</b> reflects the version that your fix is about
to go into. The bugzilla comment along with the state change
should include some help that allows a reader to understand what was done. Some good examples:<ul>
<li><b>Fixed by correcting id in files.ui/plugin.xml</b></li>
<li><b>Fixed in SystemViewPart and other *ViewPart files by using common action handler</b></li>
</ul>
The comment in bugzilla should be short enough so that it is not
much effort creating it. But long enough to help a later
reader find the corresponding change in cvs, and/or get some idea
what the problem actually was and what was done about it:
<ul>
<li>In case a single file was changed, a reference to the filename is sufficient</li>
<li>In case multiple files were changed, the most dominant file is often sufficient</li>
<li>In case lots of files were changed, the plugin or the component is fine</li>
</ul></li>
</ul>
<a name="external_contrib"></a>
<h2>Apply a patch from an external contributor</h2>
<ul>
<li>Ensure that the patch is on <b>bugzilla</b>. If not, ask the contributor
to create a bugzilla entry. This is requird even for patches from
co-workers in your own company!</li>
<li><b>Contact the contributor</b> and ask the following (see the
<a href="http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf">
Eclipse Legal Poster</a>):
<ul><li>If this is the first time the contributor makes a contribution:
Contact information for IP records - Name, Company, E-Mail, Office address, Office phone.</li>
<li>Did you write the contribution yourself?</li>
<li>Did you reference any 3rd party material?</li>
<li>If yes, under what terms (license) did you receive this material?</li>
<li>Are you authorized by your employer to make the contribution?</li>
</ul>
In the typical case (no IP problems expected), the contributor should put
a message like the following on the bugzilla report that holds his/her patch:
<p style="border: thin 1px dashed; background-color: ivory;
padding-top: 2px;
padding-left: 2px;
padding-right: 2px;
padding-bottom: 2px">
Legal Message: I, {name}, declare that I developed attached code from
scratch, without referencing any 3rd party materials except material
licensed under the EPL. {I am authorized by my employer to make this
contribution under the EPL.}
</p>
</li>
<li>Apply the patch in a <b>test workspace</b>, and review the code for any obvious traces
of copyright breaches, blasphemy or "bad words". It makes sense to have a
separate workspace for applying patches only, such that your current work
on other things is not affected negatively.</li>
<li><b>Collaborate with the contributor</b> (i.e. exchange e-mails) until the patch satisfies your needs.
Doing so educates our contributors, keeps the process transparent, and takes work off committers:
<ul><li>Patch works on HEAD (if not: ask contributor to re-base and re-submit the patch)</li>
<li>Contributor''s name added to the Copyright section of all modified files</li>
<li>Coding style appropriate</li>.
</ul></li>
<li>If the contribution is more than 250 lines of code and the contributor
is not from your own company, or there is any
uncertainty about licening and purity of IP and copyrights: fill out
a Contribution Questionnaire (available from the
<a href="https://dev.eclipse.org/committers/">committer tools</a>)</li>
<li>Once IP due diligence is completed: Apply the patch and commit it. Do not
make local modifications between applying and committing, in order to keep the
process transparent. <b>Put the bugzilla number on the commit message</b>.</li>
<li>Add a line describing the contribution to the <b>tm-log.csv</b> Project Log, see
<a href="#project_log">below</a>.</li>
<li>Add the keyword <b>contributed</b> to the bugzilla report that the patch came
from. Verify that the bugzilla <b>Target Milestone</b> reflects the
version that your fix is about to go into, then set the bugzilla report
to <b>FIXED</b>.
</ul>
<a name="project_log"></a>
<h2>Edit the TM Project Log (tm-log.csv)</h2>
<ul>
<li>The Project Log is required as per the Eclipse
<a href="http://www.eclipse.org/projects/dev_process/project-log.php">
Project Log Guidelines</a>. It records every non-committer-contribution
(including legacy code contributions). Please keep it up-to-date.</li>
<li><a name="www_tm_dev"></a>
Add the <b>www-tm-development</b> project to your workspace.
You can do this most easily by importing the Team Project set
from<ul><li>
<a href="http://www.eclipse.org/dsdp/tm/development/www-tm-development.psf">
http://www.eclipse.org/dsdp/tm/development/www-tm-development.psf</a>
</li></ul></li>
<li>When you already have the www-tm-development project in your workspace,
<b>update it</b> before editing -- this saves you from having to merge before checkin.</li>
<li>In the www-tm project, add a line for the contribution in the <b>tm-log.csv</b>
file. There are some sample lines already, so adding one should not be too hard.</li>
<li>For <a href="#sloccount">counting lines of code</a> see the section below.</li>
<li><b>Commit</b> the changed tm-log.csv file.</li>
</ul>
<a name="sloccount"></a>
<h2>Count lines of code in a contribution</h2>
<ul>
<li>For Eclipse IP review bookkeeping, we need to count lines of code in contribution,
INCLUDING xml files, documentation, readmes, property files and so on. Most
known code counters do not fulfill these needs. The simple shellscripts
below count all lines of all text files except empty lines.</li>
<li>We optionally also suppress lines that only contain whitespace, empty comments
or {} charactes. This is in order to account for different coding styles,
which might prefer to have the { characters on a separate line or not.</li>'
<li><img src="http://www.eclipse.org/images/new.gif"/>
We now have scripts to count the lines of code in a contribution. Download
any of the following:
<ul>
<li><a href="http://www.eclipse.org/downloads/download.php?file=/dsdp/tm/div/line_count_scripts-2.0RC1.tar">line_count_scripts-2.0RC1.tar</a>
<li><a href="http://www.eclipse.org/downloads/download.php?file=/dsdp/tm/div/line_count_scripts-2.0RC1.zip">line_count_scripts-2.0RC1.zip</a>
</ul>
These scripts count all lines in either a patch or a list of directories,
suppressing binary files and optionally also empty lines or lines containing
only empty comments. See the script source code for details.
<ul>
<li>UNIX shellscripts should run out of the box. On Windows, Cygwin is
required. Windows .bat files are provided as wrappers if cygwin is
not your primary environment. The .bat files expect the cygwin bin
directory in your PATH or installed in C:\Cygwin\bin - change the
.bat file if you do not like this assumption.</li>
<li>For contributions supplied as an archive, use the
<a href="http://dev.eclipse.org/viewcvs/index.cgi/www/dsdp/tm/development/scripts/lc?root=Eclipse_Website&view=co">
lc script</a>
(plus
<a href="http://dev.eclipse.org/viewcvs/index.cgi/www/dsdp/tm/development/scripts/lc.bat?root=Eclipse_Website&view=co">
lc.bat</a> if you are on Windows). Run it
with one or more directories to count as arguments. <b>Example:</b><br/>
<code>
# Count lines in all RSE plugins, including empty lines<br/>
lc -e org.eclipse.rse.*
</code>
</li>
<li>For contributions supplied as a patch, use the
<a href="http://dev.eclipse.org/viewcvs/index.cgi/www/dsdp/tm/development/scripts/lcp?root=Eclipse_Website&view=co">
lcp script</a>
(plus
<a href="http://dev.eclipse.org/viewcvs/index.cgi/www/dsdp/tm/development/scripts/lcp.bat?root=Eclipse_Website&view=co">
lcp.bat</a> if you are on Windows).
Run it with the patch file as argument. <b>Example:</b><br/>
<code>
# Count lines in contributed patch for bug 12345<br/>
lcp bug12345_patch.diff.txt
</code>
</li>
</ul></li>
</ul>
<a name="legacy_code"></a>
<h2>Add some legacy code to the project</h2>
<ul>
<li>Obtain <b>PMC Member Approval</b>: Write an e-mail to
<a href="mailto:dsdp-pmc@eclipse.org">dsdp-pmc@eclipse.org</a>,
describing the intended contribution. Give the PMC an idea of how large the
contribution is, what it is good for (cryptography?), and if there are
any other licenses than the EPL involved.</li>
<li>PMC Member Approval should be returned by E-Mail.</li>
<li>Create a <b>Bugzilla Entry</b> holding the contribution in a form that is suitable for checkin.
A ZIP archive of all the files/projects affected is fine.</li>
<li>Fill in a Contribution Questionnaire (available from the
<a href="https://dev.eclipse.org/committers/">committer tools</a>)
and wait for EMO approval.</li>
<li>Once approved, check in the contribution. Dont forget to add the <b>bugzilla number
on the commit message.</b> Commit the code verbatim as from the bug entry first,
and make any necessary modifications later.</li>
<li>If project(s) were added, update the <b>*.psf Project Set Files</b> (see
<a href="#add_plugin">below</a>).
<li>Add a line describing the contribution to the <b>tm-log.csv</b> Project Log, see
<a href="#project_log">above</a>.</li>
</ul>
<a name="add_plugin"></a>
<h2>Add a plugin or other project to the workspace</h2>
<ul>
<li>Commit your modifications.</li>
<li>In the <b>www-tm-development</b> project (see <a href="#www_tm_dev">above</a> for how
to get it), update the <b><a href="/dsdp/tm/development/cvs_setup">
team project sets</a></b>.
You can either export a selection as team project set, and sort
the lines afterwards (e.g. in Emacs, do M-X sort-lines). Or, edit the
project set manually. For the pserver version, you typically need to replace-all
":extssh:" by ":pserver:".</li>
<li>Send an <b>E-mail</b> to dsdp-tm-dev, informing everybody that team project sets
have been updated with your new plugins.</li>
<li>For <b>release engineering</b> purposes, it may be necessary to also reference your
new plugins in an existing feature, add new features, modify Mapfiles
and/or the ANT files for nightly builds in the project <tt>org.eclipse.rse.build</tt>.
These tasks can all be accomplished by your build and release engineer,
so this is another reason for sending an <b>E-mail to dsdp-tm-dev</b>
when you added a new plugin.
</ul>
<a name="fix_copyrights"></a>
<h2>Find missing or incorrect Copyright notices in my code and fix them</h2>
<ul>
<!--
<li>Please use the Releng tool from the bottom of the
<a href="http://archive.eclipse.org/eclipse/downloads/drops/R-3.2-200606291905/index.php">
Eclipse 3.2 Download Page</a></li>
<li>See the description there: "6. Fix Copyrights"</li>
-->
<li>Please use the Releng tool from the bottom of the
<a href="http://archive.eclipse.org/eclipse/downloads/drops/R-3.3-200706251500/index.php#org.eclipse.releng">
Eclipse 3.3 Download Page</a></li>
<li>See the description there at the end of the page:
<a href="http://archive.eclipse.org/eclipse/downloads/drops/R-3.3-200706251500/details.php#org.eclipse.releng">Fix Copyright</a></li>
<li>For more detail information about "Fix Copyright" vs. "Advanced Fix Copyrights" also see
<ul><li><a href="http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg01116.html">This message</a> on cross-project-issues-dev</li>
<li><a href="http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg01118.html">This message</a> which was a reply on it</li>
<li><a href="http://dev.eclipse.org/mhonarc/lists/dsdp-tm-dev/msg01214.html">This message</a> on dsdp-tm-dev</li>
</ul></li>
</ul>
<p/>
</div>
EOHTML;
# Generate the web page
$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
?>
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent