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://github.com/ElsevierSoftwareX/SOFTX_2019_219
07 July 2024, 10:26:45 UTC
  • Code
  • Branches (11)
  • Releases (5)
  • Visits
    • Branches
    • Releases
    • HEAD
    • refs/heads/T2
    • refs/heads/develop
    • refs/heads/developCI
    • refs/heads/developCI2
    • refs/heads/developCI3
    • refs/heads/gh-pages
    • refs/heads/master
    • refs/heads/newBuild
    • refs/tags/v0.1
    • refs/tags/v0.11
    • refs/tags/v0.4
    • v0.4.3
    • v0.4.2
    • v0.4.1
    • v0.3
    • v0.2
  • e7c8b4a
  • /
  • contributing.md
Raw File Download
Take a new snapshot of a software origin

If the archived software origin currently browsed is not synchronized with its upstream version (for instance when new commits have been issued), you can explicitly request Software Heritage to take a new snapshot of it.

Use the form below to proceed. Once a request has been submitted and accepted, it will be processed as soon as possible. You can then check its processing state by visiting this dedicated page.
swh spinner

Processing "take a new snapshot" request ...

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
  • revision
  • snapshot
  • release
origin badgecontent badge Iframe embedding
swh:1:cnt:e67446e371b8d0ba1f19c13aea376053cd1884fc
origin badgedirectory badge Iframe embedding
swh:1:dir:e7c8b4a063bad54e8d4c860d564040c430730a79
origin badgerevision badge
swh:1:rev:067df5d8b6b785ff51677fd206eade2d85896c85
origin badgesnapshot badge
swh:1:snp:e6d42e6731ce66e3c09de07ac49964c03139e990
origin badgerelease badge
swh:1:rel:5bfe5972d951ece97af9965fe432220714f212ec
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
  • revision
  • 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 ...
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Tip revision: 067df5d8b6b785ff51677fd206eade2d85896c85 authored by Konrad Werys on 29 October 2019, 14:20:35 UTC
feat: start point 2 params added
Tip revision: 067df5d
contributing.md
# Contributing to TOMATO

We want to make contributing to this project as easy and transparent as
possible.

## Our Development Process

We use GitHub to sync code to and from our internal repository. We'll use GitHub
to track issues and feature requests, as well as accept pull requests.

## Issues

We use GitHub issues to track public bugs. Please ensure your description is
clear and has sufficient instructions to be able to reproduce the issue.

## Report bugs using Github's [issues](https://github.com/MRKonrad/tomato/issues)

We use GitHub issues to track public bugs. Report a bug by [opening a new issue](); it's that easy!


## Pull Requests

We actively welcome your pull requests.

1.  Fork the repo and create your branch from `master`.
2.  If you've added code that should be tested, add tests.
3.  If you've changed APIs, update the documentation.
4.  Ensure the test suite passes.
5.  Make sure your code lints.
6.  Issue that pull request!

## Any contributions you make will be under the MIT Software License

In short, when you submit code changes, your submissions are understood to be under the same
[MIT License](http://choosealicense.com/licenses/mit/) that covers the project.
Feel free to contact the maintainers if that's a concern.

## Coding style

*   Write code compatible with C++98

*   Use underscore (`_variable`) in the name of a class member variable.

*   C++98 does not allow me to use constructor delegation. Using methods like `setAllPointersToNull()` to make up for it.

*   Order of methods in a class definition:
    *   functional (calculation, helpers etc)
    *   getters/setters
    *   disp()
    *   constructors/destructors
    
*   In **copy constructors** copy primitive types, set all pointers to zero.

## License

By contributing to Draft.js, you agree that your contributions will be licensed
under its BSD license.

## References

This document was adapted from the open-source contribution guidelines for
[Facebook's Draft](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)
and [qMRLab](https://github.com/qMRLab/qMRLab/blob/master/CONTRIBUTING.md).

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