GRASS-Wiki - User contributions [en]

GRASS 6.3 Feature Plan

2007-10-16T02:32:46Z

⚠️Bradd: /* In progress */

== GRASS 6.3.x feature plan ==
=== About feature plan ===

To make GRASS releases more often and more predictable, here is GRASS next releases feature plan. This feature plan has to be filled by developers working on GRASS 6.3.

=== TODO GRASS 6.3.0 ===
There is the release branch for 6.3.x, see details at [http://grass.itc.it/devel/cvstags.php CVS: tags and branches]. A release branch is considered as "frozen", only bugfixes can be done.

==== Beta0 ====
* complete and stabilize the native [[WinGRASS Current Status|winGRASS port]] (seems to be in a good shape now)

===== Must do =====
* <strike>replace r.proj with r.proj.seg</strike>
* <strike>d.text with d.text.new</strike>
* r.out.gdal sets NoData wrong [http://wald.intevation.org/tracker/index.php?func=detail&aid=405&group_id=21&atid=204 #405]

===== Mostly done? =====
* use GEM for ''GRASS Addons SVN'' - status unclear

===== Wishlist =====

* modify Makefile system to support translated HTML pages. Store translated HTML files in centralized directory with locale specific subdirs, file name is module name.
* Implement [http://freegis.org/cgi-bin/viewcvs.cgi/*checkout*/grass6/doc/vector/TODO vector improvements] as suggested by Radim
* Integrate [http://mpa.itc.it/markus/i_points_auto/ i.points.auto] (merge into i.vpoints) - see also [[Image processing]] - note that A Scianna/Palermo has modernized version
* Make sqlite the default DB? <- needs more testing, for 6.5?
* drop d.m display manager (as now almost unmaintained; there is gis.m and/or a python based GUI)
: Some people still prefer it (see posts to grass-dev) and I will fix bugs in it, but not enhance/add new modules to it without good reason. So I don't see the need to drop it before the WxPython version is ready. It's not hurting us any keeping it. --Hamish
:: We should keep plain d.mon interface but why keep d.m, if gis.m has become really good? Probably we should clearly state, that d.m is UNMAINTAINED and OBSOLETE? [[User:MarisN|MarisN]] 08:24, 16 February 2007 (CET)
* raster maps: implement SQL based [[Time series in GRASS|time series support]]

=== In progress ===
* native MS Windows port
* Database connection for v.out.vtk: --[[User:Huhabla|huhabla]] 20:47, 14 August 2006 (CEST)
** single column support for numerical data (int, float, double)
** GRASSRGB column support (done for ps.map)
** multiple column support for vector data
* rewrite most of the g3d modules to fulfil the grass function naming convention --[[User:Huhabla|huhabla]] 20:47, 14 August 2006 (CEST)
* adding further (organized) keywords to every grass command and script [http://grass.itc.it/pipermail/grass-dev/2006-August/025164.html] and [http://grass.itc.it/pipermail/grass-dev/2006-August/025190.html]:
** display commands
** database commands
** general commands
** imagery commands
** misc commands
** paint commands
** photo commands
** postscript commands
** raster commands
** raster3D commands
** vector commands
* continue with wxpython prototype
* write (Python based?) GUI wizard to create new locations (MN and terrestris.de)
* implement Python-SWIG interface
* less verbose commands
* BLAS/LAPACK updates

[[Category:Development]]
[[Category:Release Roadmap]]

Project jobs

2006-12-15T03:05:53Z

⚠️Bradd: /* Interested people */

== Open jobs in the GRASS project ==

- draft -

The growing infrastructure and extended user support requires more efforts to integrate user contributions and to keep things running. This page contains a list of jobs for which we seek volunteers. These jobs descriptions may appear a bit formal, but shall illustrate the needs.

=== Translations manager ===

The translations manager is responsible for maintaining the translation of GRASS messages
([http://grass.itc.it/devel/i18n.php translation page; [http://grass.itc.it/mailman/listinfo/translations mailing list])

Skills:
* knowledge (or willingness to learn use) of translation tools (kbabel, poEDIT)
* familiarity (or willingness to learn use) with CVS (see [[Working with CVS|instructions]])
* no programming skills required
Tasks:
* work with GRASS CVS-Head (latest GRASS)
* merging translation contributions (with 'msgmerge' of .po files or simply use [http://mpa.itc.it/markus/useful/po_merge.sh po_merge.sh])
* invite translators to contribute (ask regularly, find new), make them use recent GRASS
* create template files for new languages ('make pot')
* update existing translations '''after''' having received latest submissions from translators ('make update-po')
* keep headers of .po files intact and up-to-date
* add new translators to AUTHORS file in source code
Estimated workload:
* in average: 1-2h per week or less
Contact: Markus Neteler

=== Web site contributors ===

Several Web site contributors are desired to update pages and to improve the current structure. A future goal could be the move to a CMS system such as Drupal which would be a major effort.

Skills:
* knowledge of standard HTML (a single PHP function is used to construct menus)
* willingness to use plain text editors to write pages (to avoid that HTML cruft creeps in)
* familiarity (or willingness to learn use) with GRASS Web site CVS (see [[Working with CVS|instructions]])
* no programming skills required
Tasks:
* update outdated pages
* think about and implement "user stories" to make site more attractive
* think about and implement translation of important pages
* simplify structure
* add new screenshots with credits/CC license)
* regularly check if mirror sites work
Estimated workload:
* in average: 1-x h per week
Contact: Markus Neteler

=== Public relations manager ===

Despite the continuous growth of the user community, we seek "GRASS GIS awareness" especially for public administration and companies. A multi-language brochure is needed to promote GRASS in a more effective way. Funding for a high quality print is to be defined.

Skills:
* communication and design skills
Tasks:
* find like-minded people to form a GRASS promotion group
* communicate the existence of the GRASS project
* design of a multi-language brochure (both PDF and printed) in collaboration with the [http://wiki.osgeo.org/index.php?title=VisCom OSGeo-VisCom team]
* create material to illustrate the GRASS functionality
* contact public administration and professionals in a non-spammy way
* collect success stories and render them usable for the Web site
Contact: Markus Neteler

=== Wiki manager ===

The GRASS wiki (you are using it at the moment) requires continuous monitoring.

Skills:
* basic knowledge of mediawiki usage
* no programming skills required
Tasks:
* update outdated pages
* simplify structure where needed (merge pages)
* clean up [[:Special:Lonelypages|Orphaned pages]] (link, merge or remove)
* keep [[:Special:Categories|Categories]] up to date (add at bottom of pages where needed)
* keep an eye on spammers
Estimated workload:
* in average: 1h per week
Contact: Markus Neteler

=== Graphic design lead ===

We need someone with good graphic design skills to maintain the artwork used in the various GUIs and the web site. The initial priority is to rework the icons used in the various GUIs and clean up the screenshot gallery.

Skills:
* Graphic design, graphic design software
* Artistic
* A sufficient level of familiarity with the GIS in order to capture the precise meaning of a button's task in a simple picture.
* No programming experience needed, but it would be helpful if willing to learn a little Tcl in the short term and more wxPython in the long term. (present and future GUI frameworks)
* Manage binary files in CVS. (fairly simple to learn)
Tasks:
* Create new icons for the various GUIs
* Work with website manager to create, solicit, and maintain screenshot gallery
* Work with the GUI team to perfect GUI layout and menu presentation.
* Help promotion and newsletter teams in preparing logo banners, layout ideas, etc.
Estimated workload:
* After initial work on icons: 1hr per week

== Interested people ==

While we have to figure out the process, here a list of interested people. Please add yourself:

* Malte Halbey-Martin: Public relations Manager + Web site contributor
* Dylan Beaudette: Web site contributor (familiar with Drupal CMS)
* Scott Mitchell: Web site contributor, could possibly do the translation job, if nobody with translation tool experience volunteers
* Brad Douglas: Public Relations contributor (co-maintainer)

== Existing jobs ==

* Bug tracker maintainer: Maciej Sieczka
* Newsletter editor: Martin Wegmann
* CVS maintainer: Bernhard Reiter
* Main Web site/[http://freegis.org/cgi-bin/viewcvs.cgi/grass6/doc/infrastructure.txt?rev=HEAD&content-type=text/vnd.viewcvs-markup Infrastructure] manager: Markus Neteler
* Mailing list manager: MN
* Translations manager: MN (see above for open position)
* Wiki manager: MN (see above for open position)
* Binaries packager:
** Fedora RPMs: Brad Douglas
** Mandriva RPMs: Buchan Milne
** Debian: Francesco Lovergine and the [http://pkg-grass.alioth.debian.org/cgi-bin/wiki.pl Debian GIS Project]
** winGRASS native: Huidae Cho, Paul Kelly, Tim Sutton (with QGIS)
** MacOSX: William Kyngesburye, Lorenzo Moretti

GRASS 6.2 Feature Plan

2006-09-04T09:21:59Z

⚠️Bradd: /* Ideas */

== GRASS 6.2.x feature plan ==

There is the release branch for 6.2.x, see details at [http://grass.itc.it/devel/cvstags.php CVS: tags and branches]. A release branch is considered as "frozen", only bugfixes can be done.

=== GRASS 6.2.0 ===

In general 6.2 does not deviate too much from the 6.1.0 to avoid a major delay.

==== TODOs ====

<strike> 
* unlimited number of raster map (r.patch, r.series etc) (Glynn)
* several MinGW fixes for native MS-Windows support (Glynn)
* several fixes for MS-Windows/Cygwin support (Huidae)
* no hardcoded ARCH for Python-SWIG (Markus)
* vector/lidar: added missing includes (Markus)
* g.region b>t bug fixed (Martin)
* GRASS_PAGER (Glynn)
* r.mapcalc rand() (Glynn)
* tcl i18n install fix (Markus)
* LOCALE awk fixes to some scripts (Markus)
* SUN compilation fixes (Glynn)
* user docs fixes (Maciek)
* r.bilinear: Read/write maps as DCELL; Remove +0.5 from result (Glynn)
* NVIZ height update to avoid scene jump (Bob)
* Add the new v.lidar.* tools (needed for FOSS4G2006) (Roberto A. + Markus)
* lidar and simwe compilation issues on MacOSX fixed (William)
* Makefile cleanup for extra libraries (lidar, simwe, lrs) (Glynn + Markus)
* keywords backported from 6.3-CVS (Markus)
* renamed dbmi driver html files to include 'grass-' to avoid package conflicts (Markus)
</strike>

Beta 1:
<strike>
* v.digit: split icons into two rows for 800x600 screens (backport) (Michael, Hamish)
* gis.m fixes (Michael)
* v.proj: treat z as ellipsoidal height (Paul)
</strike>

Beta 2:
<strike>
* g.proj compile fix (Markus)
* NVIZ: Tk8.5 fix (Markus)
</strike>

RC1 (not yet released):
<strike>
* docs improvements (Eric, Trevor, Moritz, Michael)
* v.digit cosmetics (Hamish)
* v.outlier: parameter fix
* NVIZ: off-screen rendering fix for broken openGL drivers
* grass-xterm-wrapper: simplified for broken gnome-terminal
</strike>
* rename v.bspline to v.surf.bspline for consistency

* write impressive press release (best in CVS Web)

WONTFIX? Later?
* r.out.gdal region sensitive
* NVIZ volume problem (test with slovakia3d dataset) - sometimes it works

==== Ideas ====
* do the proposed bug day soon (in October '06)

==== Releases ====
* [http://grass.itc.it/grass62/source/snapshot/ Source code Snapshot]
* 6.2.0beta1 release 28 August 2006
* 6.2.0beta2 release 30 August 2006
* 6.2.0RC1 release 2 September 2006
* It would be great to have it available for the FOSS4G2006 conference in September (so, >= 5th September).

[[Category:Development]]
[[Category:Release Roadmap]]