Skip to content

Conversation

@baharmon
Copy link
Contributor

@baharmon baharmon commented Jul 6, 2025

This pull request addresses issue #6033.
Changes to the citation file include:

  • Updated abstract
  • Replaced family-names with name for GRASS Development Team
  • Removed affiliation for GRASS Development Team
  • Used double quotes for strings with special characters

@baharmon
Copy link
Contributor Author

baharmon commented Jul 6, 2025

Validated with ccffconvert.

@github-actions github-actions bot added the docs label Jul 6, 2025
@neteler neteler changed the title Updated citation file doc: Updated citation file CITATION.cff Jul 15, 2025
CITATION.cff Outdated
email: [email protected]
affiliation: Open Source Geospatial Foundation (OSGeo)
- name: "GRASS Development Team"
email: "[email protected]"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This email is basically phased out and replaced by [email protected], yet it requires registration.
Any suggestion for an alternative?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't this we should have "team" here at all. The very people who are part of it are in the list below.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need an email either, but I do like the "Team" there. This is the citation for R, for example:

@Manual{,
    title = {R: A Language and Environment for Statistical Computing},
    author = {{R Core Team}},
    organization = {R Foundation for Statistical Computing},
    address = {Vienna, Austria},
    year = {2023},
    url = {https://www.R-project.org/},
  }

Can we use a URL instead of an email?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is an author entity website field that could be used for the url:

authors:
  - name: "GRASS Development Team"
    website: "https://grass.osgeo.org/"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@veroandreo This is different. We have team as the first one of many. R has it as the only one AFAIU.

@neteler neteler added this to the 8.5.0 milestone Jul 15, 2025
@neteler neteler added the backport to 8.4 PR needs to be backported to release branch 8.4 label Jul 15, 2025
Copy link
Member

@wenzeslaus wenzeslaus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer to remove the "team" author in a follow up PR, so I don't really care much about updating or not updating the email. To make this PR complete, the email change makes sense.

CITATION.cff Outdated
email: [email protected]
affiliation: Open Source Geospatial Foundation (OSGeo)
- name: "GRASS Development Team"
email: "[email protected]"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't this we should have "team" here at all. The very people who are part of it are in the list below.

@baharmon
Copy link
Contributor Author

baharmon commented Aug 3, 2025

So should we use [email protected] for the email? And how about adding the year? The suggested citations on the website and in the about panel of GRASS have the year.

@baharmon baharmon requested a review from wenzeslaus October 10, 2025 00:54
CITATION.cff Outdated
cff-version: 1.2.0
title: GRASS GIS
message: If you use this software, please cite it using the metadata from this file.
title: "GRASS GIS"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we still called GRASS GIS now?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will change the title in the citation file to GRASS. Note that the releases and thus Zenodo archives are still titled GRASS GIS.

CITATION.cff Outdated
repository-code: "https://github.com/OSGeo/grass"
license: "GPL-2.0-or-later"
doi: "10.5281/zenodo.4621728"
date-released: 2024-07-27
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Double-check it is still up-to-date

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@echoix That DOI is wrong. We should fix it as soon as possible. I propose updating the citation to GRASS 8.4.1 released on February 24, 2025 with DOI 10.5281/zenodo.14918754.

CITATION.cff Outdated
message: If you use this software, please cite it using the metadata from this file.
title: "GRASS GIS"
message: "If you use this software, please cite it using the metadata from this file."
version: 8.4.0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is this supposed to match? The latest released version or the one in development?

Copy link
Contributor Author

@baharmon baharmon Oct 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The latest released version which has a DOI. I think the question is whether to cite major or minor releases. Minor would be better, but will be more work to keep up to date. Automation would help with that.

I will update the version to 8.4.1 and update the release date and DOI to match.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport to 8.4 PR needs to be backported to release branch 8.4 docs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants