Skip to main content
  • Home
  • Development
  • Documentation
  • Donate
  • Operational login
  • Browse the archive

swh logo
SoftwareHeritage
Software
Heritage
Archive
Features
  • Search

  • Downloads

  • Save code now

  • Add forge now

  • Help

https://doi.org/10.5281/zenodo.594223
07 February 2025, 11:54:05 UTC
  • Code
  • Branches (0)
  • Releases (4)
  • Visits
    • Branches
    • Releases
      • 4
      • 4
      • 3
      • 2
      • 1
    • c501fcf
    • /
    • rubenarslan-formr.org-0797b20
    • /
    • CONTRIBUTING.md
    Raw File Download
    Permalinks

    To reference or cite the objects present in the Software Heritage archive, permalinks based on SoftWare Hash IDentifiers (SWHIDs) must be used.
    Select below a type of object currently browsed in order to display its associated SWHID and permalink.

    • content
    • directory
    • snapshot
    • release
    origin badgecontent badge Iframe embedding
    swh:1:cnt:085fcc687da70b6c1df8c399084edab7ee5fcfc0
    origin badgedirectory badge Iframe embedding
    swh:1:dir:a4f1bf3ec890c395b3ff7526e731387c533a85bd
    origin badgesnapshot badge
    swh:1:snp:fc5be6ea36d914a465ae83272994afb6f8ba2d7d
    origin badgerelease badge
    swh:1:rel:bce81870630aa4105bba65651a8ea173973c44c0
    Citations

    This interface enables to generate software citations, provided that the root directory of browsed objects contains a citation.cff or codemeta.json file.
    Select below a type of object currently browsed in order to generate citations for them.

    • content
    • directory
    • snapshot
    • release
    Generate software citation in BibTex format (requires biblatex-software package)
    Generating citation ...
    Generate software citation in BibTex format (requires biblatex-software package)
    Generating citation ...
    Generate software citation in BibTex format (requires biblatex-software package)
    Generating citation ...
    Generate software citation in BibTex format (requires biblatex-software package)
    Generating citation ...
    CONTRIBUTING.md
    # How to improve formr
    formr is open source software. You are welcome to help improve it. Depending on your technical background, there are several options.
    
    ## Improve the software
    If you know the relevant software stack (e.g., R, PHP, JavaScript, CSS, HTML), you can send us pull requests on Github to quash bugs, add features, add tests, etc.
    
    If you want to test formr or contribute to its development, follow our [instructions](https://github.com/rubenarslan/formr.org/blob/master/INSTALLATION.md).
    
    The setup instructions are not suitable for production, i.e. running a secure formr installation on the public web.
    
    ## Improve the documentation
    formr allows for very complex study designs. Not all of the potential use cases are documented. In some places, the documentation is out of date or hard to understand.
    
    ### Add your own use case
    If you have implemented a study in formr, especially if you've done something difficult, we and other users would greatly appreciate, if you write up a case study.
    
    Ideally, that would consist of some description of the study design, a link to the preprint or publication if applicable, as well as the exported study JSON file (Run->Export).
    
    ### Ask and answer questions in the Github Discussions
    We use [Github Discussions](https://github.com/rubenarslan/formr.org/discussions) for community support. We try to find the time to answer questions. If you answer some of the questions we didn't get to yet, we'll try especially hard to answer your own questions. We also appreciate if you post back with the solution, if you found one yourself.
    
    ### Improve the documentation
    Unfortunately, our documentation currently lives in four places:
    
    - The old [Google Group](https://groups.google.com/g/formr) which we closed down because of the spam.
    - The new [Github Discussions](https://github.com/rubenarslan/formr.org/discussions)
    - The [repository Wiki](https://github.com/rubenarslan/formr.org/wiki) which is intended for case studies, brief tutorials, frequently asked questions, and so on.
    - The [documentation on the website](https://formr.org/documentation) itself, which is accessible while using formr.
    
    Editing the Github and the Wiki should be easy. We use Markdown, which is basically plain text.
    
    The documentation files for the website are on [Github](https://github.com/rubenarslan/formr.org/tree/master/templates/public/documentation). Even if you are not a technical person, the documentation is just plain HTML, so easy to edit. You can edit it directly on Github using the "Pencil" button. This will create a pull request, i.e. we get a chance to review your change before it makes it into the website.
    
    We appreciate any efforts to move questions/solutions from the Google Group to the Wiki or website documentation, or from the Wiki to the website documentation.

    back to top

    Software Heritage — Copyright (C) 2015–2025, The Software Heritage developers. License: GNU AGPLv3+.
    The source code of Software Heritage itself is available on our development forge.
    The source code files archived by Software Heritage are available under their own copyright and licenses.
    Terms of use: Archive access, API— Contact— JavaScript license information— Web API