[GRASS-dev] Addons to Ohloh

GRASS GIS GRASS GIS developer
1

Hi,

do you think that GRASS GIS Addons [1] should go to Ohloh [2]? I do, because they are part of the project and should be tracked.

GRASS GIS Addons can be added as additional repository for GRASS GIS project or they can be a separated project at Ohloh. Some projects went this way of having plugins/extension/addons separated. The reasons for this might be that the developers group, used languages or contribution frequency can be really different. What do you think? Or do you know some other ways on Ohloh? (I don’t know much about Ohloh.)

The question also is if grass-addons/ or grass-addons/grass7 or something else should be used. I vote for grass-addons, although there is some duplication. But there are some distinct things and it follows the idea of having there 64 and trunk. But I don’t have a strong opinion on this either.

Vaclav

[1] http://svn.osgeo.org/grass/grass-addons/
[2] https://www.ohloh.net

PS: I was considering for a second if to add also 70 branch besides trunk and the answer is clearly no. This would be definitively a huge duplication (and thus nonsense for Ohloh).

2

On 31 March 2014 01:08, Vaclav Petras <wenzeslaus@gmail.com> wrote:

Hi,

Hi

do you think that GRASS GIS Addons [1] should go to Ohloh [2]? I do, because
they are part of the project and should be tracked.

+1

GRASS GIS Addons can be added as additional repository for GRASS GIS project
or they can be a separated project at Ohloh. Some projects went this way of
having plugins/extension/addons separated. The reasons for this might be
that the developers group, used languages or contribution frequency can be
really different. What do you think? Or do you know some other ways on
Ohloh? (I don't know much about Ohloh.)

I'd like to see it separated from the main code

The question also is if grass-addons/ or grass-addons/grass7 or something
else should be used. I vote for grass-addons, although there is some
duplication. But there are some distinct things and it follows the idea of
having there 64 and trunk. But I don't have a strong opinion on this either.

I also vote for grass-addons

Vaclav

[1] http://svn.osgeo.org/grass/grass-addons/
[2] https://www.ohloh.net

PS: I was considering for a second if to add also 70 branch besides trunk
and the answer is clearly no. This would be definitively a huge duplication
(and thus nonsense for Ohloh).

+1, also because most of the code should pass from trunk....

--
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org

3

On Mon, Mar 31, 2014 at 4:06 AM, Luca Delucchi <lucadeluge@gmail.com> wrote:

> GRASS GIS Addons can be added as additional repository for GRASS GIS
project
> or they can be a separated project at Ohloh. Some projects went this way
of
> having plugins/extension/addons separated. The reasons for this might be
> that the developers group, used languages or contribution frequency can
be
> really different. What do you think? Or do you know some other ways on
> Ohloh? (I don't know much about Ohloh.)
>

I'd like to see it separated from the main code

Any other opinions?

The name would be probably "GRASS GIS Addons". Although, we have some
uncertainty about extension/addon/module/... terminology.

What is the best way to connect two projects together? Homepage link, tags
or just text?

4

On Wed, Apr 2, 2014 at 4:24 AM, Vaclav Petras <wenzeslaus@gmail.com> wrote:

On Mon, Mar 31, 2014 at 4:06 AM, Luca Delucchi <lucadeluge@gmail.com> wrote:

> GRASS GIS Addons can be added as additional repository for GRASS GIS
> project
> or they can be a separated project at Ohloh. Some projects went this way
> of
> having plugins/extension/addons separated. The reasons for this might be
> that the developers group, used languages or contribution frequency can
> be
> really different. What do you think? Or do you know some other ways on
> Ohloh? (I don't know much about Ohloh.)
>

I'd like to see it separated from the main code

Any other opinions?

The name would be probably "GRASS GIS Addons". Although, we have some
uncertainty about extension/addon/module/... terminology.

What is the best way to connect two projects together? Homepage link, tags
or just text?

I can check if I can link it as subproject to the existing GRASS registration.

Markus

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

5

On Wed, Apr 2, 2014 at 1:53 AM, Martin Landa <landa.martin@gmail.com> wrote:

2014-04-02 4:24 GMT+02:00 Vaclav Petras <wenzeslaus@gmail.com>:
> The name would be probably "GRASS GIS Addons". Although, we have some
> uncertainty about extension/addon/module/... terminology.

this name make sense to me. Right, we call in wxGUI addons somethimes
as extensions, this probably confusing.

On Wed, Apr 2, 2014 at 3:55 AM, Markus Neteler <neteler@osgeo.org> wrote:

I can check if I can link it as subproject to the existing GRASS

registration.

I've finally created the GRASS GIS Addons project at (Black Duck) Open Hub
(former Ohloh) [1].

I've used the proposed name and the whole grass-addons repository.

The GRASS GIS project is not linked in any special way; I don't know about
one. However, both are linked through similar projects because of the
similarity in tags.

All, please rate the project and specify that you are using it, e.g. by
adding it to one of your stacks at Open Hub or just clicking on "I use
this" button.

Developers, if you care about your Open Hub statistics, assign your account
to the contributor or contributors. If you don't care, please add at least
aliases [2] if you have more than one SVN user name so that the general
statistics are not distorted. You can have a look to GRASS GIS project
aliases [3]. Please see also post about unifying contributor names in SVN
[4].

Vaclav

[1] https://www.openhub.net/p/grass_gis_addons
[2] https://www.openhub.net/p/grass_gis_addons/aliases
[3] https://www.openhub.net/p/grass_gis/aliases
[4] http://lists.osgeo.org/pipermail/grass-dev/2014-June/069512.html

Here is the current Open Hub "In a Nutshell" report: GRASS GIS Addons...

has had 4,514 commits made by 82 contributors
representing 320,271 lines of code

is mostly written in C
with an average number of source code comments

has a well established, mature codebase
maintained by a large development team
with increasing Y-O-Y commits

took an estimated 85 years of effort (COCOMO model)
starting with its first commit in December, 2006
ending with its most recent commit 4 days ago

6

Hi Vaclav,

2015-01-03 16:36 GMT+01:00 Vaclav Petras <wenzeslaus@gmail.com>:

I've finally created the GRASS GIS Addons project at (Black Duck) Open Hub
(former Ohloh) [1].

cool, thanks! Martin

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.eu/mentors/landa