From: Gail M. <mu...@cs...> - 2006-04-25 23:30:14
|
Hi, I'd like to propose the following changes which I'm willing to do (coordinate in the case of one): * Change all copyrights to EPL of the form below unless it was a class added by others in which case it should be accurate in the top line, last line: /*************************************************************************** **** * Copyright (c) 2004 - 2006 University Of British Columbia and others. * All rights reserved. This program and the accompanying materials * are made available under the terms of the Eclipse Public License v1.0 * which accompanies this distribution, and is available at * http://www.eclipse.org/legal/epl-v10.html * * Contributors: * University Of British Columbia - initial API and implementation **************************************************************************** ***/ * Switch to a net.sf.jrmtool (etc.) package naming to reflect the fact that others are working on the code. * Add a net.sf.jrmtool.test package for junit tests of non-Eclipse parts of the system * Add a net.sf.jrmtool.eclipse.test package for Eclipse-based tests (perhaps non-automated tests for now) I am emailing with Martin Robillard (creator of FEAT) about creating a separate entry under trunk: trunk/feat (if that's feasible) to incorporate the FEAT code under EPL. Hopefully we'll have an update on that available soon. What is the process we are using on creating branches and doing merges? I'm reluctant to have too many branches outstanding (but maybe that's because I'm a naive subversion user). For instance, it seems like at least the front-end improvements (if they are working) should be merged to trunk before I create a branch to do the copyright change or renaming. Gail. |