Hi @ankursinha

WDYT about: https://zenodo.org/communities/fedoraproject

??

What another thing we need to create the citation?
(Sorry very first time, i only have 4 papers)

Hi @ankursinha
WDYT about: https://zenodo.org/communities/fedoraproject

+1 Looks awesome! :sparkles:

What another thing we need to create the citation?
(Sorry very first time, i only have 4 papers)

We now need to create a new citation for the F29 release: click "New upload" and fill in the details.

Ideally we should have a citation for each release that people can cite ---I'll file a ticket with the FPgM to add this to the release tasks,

Thanks very much :)

@bt0dotninja++

@ankursinha Is there any other inputs you require from Mindshare as a whole? This look kinda complete to me.. WDYT?

I may have missed something but the citation for F29 has not yet been set
up yet, has it?

looking how to do it...

@bt0dotninja can you document the process for creating a citation. For the next one we need, lets get someone who isn't you to do it from your docs to see if there are holes. Lets ask @bcotton to link to this doc from the task so we have this knowledge where needed.

We can store the docs on our docs site.

+1, thanks @bt0dotninja @bex !

Any update @bt0dotninja ?

I am going to work on this with a friend of mine from the UT School of information. I'll pick it up from here and if @bt0dotninja gets time to work on it, then we can work it together.

From my friend:

here are two sources of citation formats:
https://www.acm.org/publications/authors/reference-formatting
https://www.mybib.com/tools/ieee-citation-generator
it appears that there is not a way to cite a piece of software other than using a URL, or, perhaps a DOI from, say, zenodo.org (a preservation repository, probably not what you want or need).

So using the ieee citation generator, I got the following from chasing a specific release:

[1]Fedoraproject.org, 2022.  https://dl.fedoraproject.org/pub/fedora/linux/releases/36/Cloud/aarch64/images/Fedora-Cloud-Base-36-1.5.aarch64.raw.xz (accessed Oct. 07, 2022).

I am wondering if the preservation repository is actually helpful at this point?

Hi @davdunc, thanks for continuing the work here.

So, there are a few reasons for doing this.

• to ensure that when Fedora is used in the sciences, the community gets credit for all the work it does
• to ensure that there are permanent identifiers (DOIs) that Fedora users can use to cite a release: we cannot create a DOI ourselves---there are services that provide these (below)
• to ensure that all Fedora releases are archived (I believe this is done by the infra team already, and any one can request a copy of the Fedora sources etc.)

From a scientific/research perspective, it is important that users be able to cite a particular Fedora release, and that this release be obtainable in the future because this information is required to validate/reproduce the results that users generate.

There are a number of ways to go about this:

• zenodo is nice because it gives permanent DOIs, and a new DOI for each release. This is for libNeuroML for example. You'll see there's a permanent one that one can use, but each release also gets a new DOI. Zenodo provides enough space to upload sources---but we can decide what it is we want to upload here. It could just be ISOs of the release products (workstation/server etc.)
• there's https://www.softwareheritage.org/ which also allows archival (I think it even does automatic archival, but I'm not sure how this works).
• there's also the journal of open source software, but I don't think they do general operating systems---I mostly see individual tools here.

Here's a recording of a recent talk that the members of the Software Citation working group had presented about citing software, which explains it all much better :)

https://training.incf.org/lesson/software-citation-principles

understood. I'll update the work and put a build script together. Figshare.com is also a possibility.

moved https://gitlab.com/fedora/mindshare/home/-/issues/17