Changes between Version 22 and Version 23 of OSGeoIncubationChecklist
- Timestamp:
- Mar 29, 2014, 8:15:22 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OSGeoIncubationChecklist
v22 v23 1 [[PageOutline]] 1 = OSGeo Incubation Checklist = 2 2 3 3 This page lists the OSGeo graduation checklist status for rasdaman as per [http://www.osgeo.org/incubator/process/project_graduation_checklist.html OSGeo graduation checklist]; comments and discussion are welcome on the rasdaman-users mailing list (rasdaman-users _@ googlegroups.com). 4 4 5 = Activities management = 5 Overall process coordination: A. Beccati - a.beccati .at jacobs-university .dot de. 6 6 7 Overall process coordination: A. Beccati - a.beccati .at jacobs-university .dot de. 7 [[PageOutline]] 8 9 == Activities management == 8 10 9 11 Open activities have been listed at the beginning of the checklist sections they belong to, using the following format: … … 21 23 '''At this stage, all activities are closed and no open activities are remaining.''' 22 24 23 = Icon legend and media attribution = 25 == Icon legend and media attribution == 26 24 27 [[Image(http://upload.wikimedia.org/wikipedia/commons/1/11/Hourglass.png)]] Waiting for verification. From http://commons.wikimedia.org/wiki/File:Hourglass.png 25 28 … … 33 36 [[Image(http://upload.wikimedia.org/wikipedia/commons/1/1d/Icons-mini-icon_user.gif)]] Assigned and ongoing. From http://commons.wikimedia.org/wiki/File:Icons-mini-icon_user.gif#file 34 37 35 = INCUBATION CHECKLIST (as per OSGeo) =38 == INCUBATION CHECKLIST (as per OSGeo) == 36 39 37 38 == Copyright and License == 40 === Copyright and License === 39 41 40 42 We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps: … … 51 53 52 54 53 == Processes==55 === Processes === 54 56 55 57 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project has code under configuration management. … … 64 66 65 67 66 == Documentation==68 === Documentation === 67 69 68 70 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project has user documentation: … … 73 75 a. Providing sufficient detail for an experienced programmer to contribute patches or a new module in accordance with the project's programming conventions. 74 76 75 76 77 78 == Release Procedure == 77 === Release Procedure === 79 78 80 79 [[Image(http://upload.wikimedia.org/wikipedia/commons/1/1d/Icons-mini-icon_user.gif)]] (A.Beccati - a.beccati .at jacobs-university .dot de): setting up Release Line and semantic versioning adoption … … 84 83 85 84 In order to maintain a consistent level of quality, the project should follow defined release and testing processes. 86 87 88 89 85 90 86 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project follows a defined release process: (patch revision in place, release policy review ongoing) … … 102 98 * Release process makes use of the project trac roadmap feature, paired with the ticket manager. The latter has been extended to support "feature" tickets to ease tracking high-level features and assign them to release milestones. Testing system has been documented on wiki. 103 99 104 105 106 == OSGeo Committees and Community == 100 === OSGeo Committees and Community === 107 101 108 102 The OSGeo Foundation is made up of a number of committees, projects and local chapters. This section gathers up information these groups have requested from OSGeo projects. These expectations are not mandatory requirements before graduation, but a project should be prepared to address them in order to be considered a good OSGeo citizen. 109 103 110 === Board===104 ==== Board ==== 111 105 112 106 The OSGeo Board holds ultimate responsibility for all OSGeo activities. The Board requests: … … 117 111 118 112 119 === Marketing===113 ==== Marketing ==== 120 114 121 115 Access to OSGeo's [http://wiki.osgeo.org/wiki/Marketing_Committee Marketing_Committee] and associated [http://wiki.osgeo.org/wiki/Marketing_Pipeline Marketing_Pipeline] is one of the key benefits of joining the OSGeo foundation. The Marketing Committee requests: … … 129 123 130 124 131 === Projects===125 ==== Projects ==== 132 126 133 127 Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. 134 128 135 Related:136 * [http://www.postgresql.org/ PostgreSQL] 129 [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Related: 130 * [http://www.postgresql.org/ PostgreSQL] (contact with community established, tickets submitted) 137 131 138 === Projects===132 ==== Projects ==== 139 133 140 134 [[Image(http://upload.wikimedia.org/wikipedia/commons/1/1d/Icons-mini-icon_user.gif)]] (A. Beccati - a.beccati .at jacobs-university .dot de ) Project Steering Committee; Consider definition of a PSC to define project direction and overall desired (and undesired) features to better direct development efforts by volunteer contributors. … … 162 156 163 157 164 === SAC===158 ==== SAC ==== 165 159 166 160 The [http://wiki.osgeo.org/wiki/SAC System Administration Committee] is available to help infrastructure and facilities. Information for this committee is collected as part of the [http://wiki.osgeo.org/wiki/Project_Status_Template Project Status Template].
