Opened 8 years ago

Closed 6 years ago

#3092 closed enhancement (wontfix)

Include experimental modules in GRASS

Reported by: rkrug Owned by: grass-dev@…
Priority: normal Milestone: 7.4.1
Component: Default Version: unspecified
Keywords: addon module beta experimental Cc:
CPU: All Platform: All

Description

Based on the discussion on grass-dev http://permalink.gmane.org/gmane.comp.gis.grass.devel/70427 the suggestion came up to add experimental / beta / alpha modules (addons, ...) to GRASS. As these modules are not stable / extensively used or tested yet and their interfaces and functionality can change, I would suggest the following mechanism:

1) add [experimental] / [beta] / ... behind the in the menu 2) disable the experimental / beta / ... addons by default 3) add an option to enable all the experimental / beta / ... addons, which can than state "experimental, might make your computer explode, use at own risk and only in well ventilated rooms"...

By doing this, not extensively tested addons can be shipped with GRASS and get exposure to wider testing. On the other hand, they would only be available when explicitely asked for and informed about their non-stable natire.

Change History (7)

comment:1 by rkrug, 8 years ago

Based on the discussion on grass-dev ​http://permalink.gmane.org/gmane.comp.gis.grass.devel/70427 the suggestion came up to add experimental / beta / alpha modules (addons, ...) to GRASS. As these modules are not stable / extensively used or tested yet and their interfaces and functionality can change, I would suggest the following mechanism:


1) add [experimental] / [beta] / ... behind the in the menu

2) disable the experimental / beta / ... addons by default

3) add an option to enable all the experimental / beta / ... addons, which can than state "experimental, might make your computer explode, use at own risk and only in well ventilated rooms"...


By doing this, not extensively tested addons can be shipped with GRASS and get exposure to wider testing. On the other hand, they would only be available when explicitely asked for and informed about their non-stable natire.

comment:2 by neteler, 7 years ago

Isn't the GRASS GIS Addons repo exactly the place for experiments and core preparation?

comment:3 by neteler, 7 years ago

Milestone: 7.2.07.2.1

Ticket retargeted after milestone closed

comment:4 by martinl, 7 years ago

Milestone: 7.2.17.2.2

comment:5 by martinl, 7 years ago

Milestone: 7.2.27.4.0

All enhancement tickets should be assigned to 7.4 milestone.

comment:6 by neteler, 6 years ago

Milestone: 7.4.07.4.1

Ticket retargeted after milestone closed

comment:7 by martinl, 6 years ago

Resolution: wontfix
Status: newclosed

Unclear, closing.

Note: See TracTickets for help on using tickets.