kvalobs:prerelease

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision 		Previous revision
kvalobs:prerelease [2007-09-24 14:52:39]
paule created 		kvalobs:prerelease [2022-05-31 09:29:32] (current)
Line 15: Line 15:
 Also required Also required
  
-   * libpuTools [[http://cvs/cgi-bin/cvsweb/puglocal/src/libs/puTools/|http://cvs/cgi-bin/cvsweb/puglocal/src/libs/puTools/]]+   * libpuTools [[http://cvs/cgi-bin/cvsweb/puglocal/src/libs/puTools/|http://cvs/cgi-bin/cvsweb/puglocal/src/libs/puTools/]] available in subversion at: [[https://svn.met.no/viewvc/metlibs/puTools/|https://svn.met.no/viewvc/metlibs/puTools/]].
  
-The puTools library is to be released under subversion separately (i.e. shared with other projects such as Diana). LpuTools is already an open-source library under LGPL 2.1.+The puTools library is to be released under subversion separately (i.e. shared with other projects such as Diana). puTools is already an open-source library under LGPL 2.1.
  
  
Line 31: Line 31:
  
 **+**Please email kvalobs-dev@met.no with your preference/proposal. **+**Please email kvalobs-dev@met.no with your preference/proposal.
 +
 +
 +**++++++** Consensus of opinion is to use **kvoss** as the name for the full bundle.
  
 One advantage of this is that access to the group of s/w in subversion can be achieved by only setting access to a single folder. One advantage of this is that access to the group of s/w in subversion can be achieved by only setting access to a single folder.
Line 37: Line 40:
 **Proposed structure under subversion**  **Proposed structure under subversion** 
  
- ... using the project name //kvoss// only as an example ...+ ... using the project name //kvoss// 
  
  
Line 68: Line 71:
    - prepare the directories trunk, branches and tags under all projects    - prepare the directories trunk, branches and tags under all projects
    - (kvalobs example) copy from cvs/kvalobs to svn.met.no/kvoss/kvalobs/trunk    - (kvalobs example) copy from cvs/kvalobs to svn.met.no/kvoss/kvalobs/trunk
-   - also tagged copy to svn.met.no/kvoss/kvalobs/tags/kvalobs-oss-launch with --message "first release of project_name as open source software"+   - also tagged copy to svn.met.no/kvoss/kvalobs/tags/kvalobs-oss-launch with --message "copy of first source code available as open source project"
  
  
Line 84: Line 87:
  
  
-Propose that the first versions opened on subversion are classified as a Beta-Version.+Propose that the first versions opened on subversion will be a snapshot of the latest version on cvs. The first repository will not constitute a release and hence will have no explicit versioning applied.
  
-The s/w run at met.no is mature (and for kvalobs it is version 1.1.2.53 for example). The Beta Versioning is to indicate that steps are required to make the s/w more accessible for use in an open-source context. These steps may include: +We should note that the s/w run at met.no is mature (and for kvalobs it is version 1.1.2.53 for example), however steps are required to make the s/w more accessible for use in an open-source context. These steps may include: 
  
 +   - Tidy up source tree
    - Provision of a detailed installation guide    - Provision of a detailed installation guide
    - Removal of any specific met.no environment features (e.g. the kvalobs database has to be run by a user kvalobs)    - Removal of any specific met.no environment features (e.g. the kvalobs database has to be run by a user kvalobs)
    - Provision of an autoconf script or similar autobuild tools.    - Provision of an autoconf script or similar autobuild tools.
  
- +After these steps have been accomplished we can think of having a "release" tagged under subversion.
  
 **Licensing** **Licensing**
  
  
-All software not already under license to be placed under the GNU General Public License (GPL) [[http://www.gnu.org/copyleft/gpl.html|http://www.gnu.org/copyleft/gpl.html]]. In the repository the full license will be imported in the file COPYING e.g. svn.met.no/kvoss/kvalobs/trunk/COPYING+All software, not already under license, to be placed under the GNU General Public License (GPL) [[http://www.gnu.org/copyleft/gpl.html|http://www.gnu.org/copyleft/gpl.html]].
  
-  
-Propose to start with GPL v3. The reasoning is that this is the latest version. Note DIANA is currently using version 2 of GPL. PLEASE DISCUSS. 
  
 +In the repository the full license will be imported in the file COPYING e.g. svn.met.no/kvoss/kvalobs/trunk/COPYING
 +
 + 
 +Propose to start with GPL v2. There are still ongoing discussions about GPL v3 in the open-source community. GPL v2 is sufficient for the needs of kvoss.
  
 Example header: Example header:
Line 109: Line 115:
 Kvalobs - Free Quality Control Software for Meteorological Observations Kvalobs - Free Quality Control Software for Meteorological Observations
  
-$Id: klfilterTest.java,v  BETA September 24 2007+$Id$
  
 Copyright (C) 2007 met.no Copyright (C) 2007 met.no
Line 124: Line 130:
 KVALOBS is free software; you can redistribute it and/or KVALOBS is free software; you can redistribute it and/or
 modify it under the terms of the GNU General Public License as modify it under the terms of the GNU General Public License as
-published by the Free Software Foundation; either version 3+published by the Free Software Foundation; either version 2
 of the License, or (at your option) any later version. of the License, or (at your option) any later version.
  
Line 144: Line 150:
  
  
-** Addition of new copyright**+**Copyright Handling**
  
  
 All code is now issued with "Copyright (C) 2007 met.no."  All code is now issued with "Copyright (C) 2007 met.no." 
-How will the evolution copyright be handled? Open issue. +How will the evolution of the copyright be handled?  
-This needs to be discussed and resolved at an early stage.+ 
 + 
 +Shall we adopt a policy of "Contributor license agreement" or establish a project legal entity, and assign copyright to that?
    
  
  • kvalobs/prerelease.1190645559.txt.gz
  • Last modified: 2022-05-31 09:23:18
  • (external edit)