-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #142 from ARGOeu/devel
Version 1.0.5
- Loading branch information
Showing
43 changed files
with
32,549 additions
and
915 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
# This CITATION.cff file was generated with cffinit. | ||
# Visit https://bit.ly/cffinit to generate yours today! | ||
|
||
cff-version: 1.2.0 | ||
title: EOSC Recommender System Metrics | ||
message: A framework for evaluating EOSC Recommender System. Use of additional diagnostic metrics and visualizations offering deeper and sometimes surprising insights about the models performance. | ||
type: software | ||
authors: | ||
- given-names: Kostas | ||
family-names: Kagkelidis | ||
email: kaggis@admin.grnet.gr | ||
affiliation: GRNET S.A. | ||
- given-names: Nikolaos | ||
family-names: Triantafyllis | ||
email: ntriantafyl@admin.grnet.gr | ||
affiliation: GRNET S.A. | ||
- given-names: Themis | ||
family-names: Zamani | ||
email: themis@admin.grnet.gr | ||
affiliation: GRNET S.A. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,73 @@ | ||
# Contributor Covenant Code of Conduct | ||
|
||
## Our Pledge | ||
|
||
In the interest of fostering an open and welcoming environment, | ||
we as contributors and maintainers pledge to making participation | ||
in our project and our community a harassment-free experience for everyone, | ||
regardless of age, body size, disability, ethnicity, gender identity and | ||
expression, level of experience, nationality, personal appearance, race, | ||
religion, or sexual identity and orientation. | ||
|
||
## Our Standards | ||
|
||
Examples of behaviour that contributes to creating a positive environment include: | ||
|
||
* Using welcoming and inclusive language | ||
* Being respectful of differing viewpoints and experiences | ||
* Gracefully accepting constructive criticism | ||
* Focusing on what is best for the community | ||
* Showing empathy towards other community members | ||
|
||
Examples of unacceptable behaviour by participants include: | ||
|
||
* The use of sexualised language or imagery and unwelcome sexual attention or | ||
advances | ||
* Trolling, insulting/derogatory comments, and personal or political attacks | ||
* Public or private harassment | ||
* Publishing others' private information, such as a physical or electronic | ||
address, without explicit permission | ||
* Other conduct which could reasonably be considered inappropriate in a | ||
professional setting | ||
|
||
## Our Responsibilities | ||
|
||
Project maintainers are responsible for clarifying the standards of acceptable | ||
behaviour and are expected to take appropriate and fair corrective action | ||
in response to any instances of unacceptable behaviour. | ||
|
||
Project maintainers have the right and responsibility to remove, edit, | ||
or reject comments, commits, code, wiki edits, issues, and other contributions | ||
that are not aligned to this Code of Conduct, or to ban temporarily | ||
or permanently any contributor for other behaviours that they deem | ||
inappropriate, threatening, offensive, or harmful. | ||
|
||
## Scope | ||
|
||
This Code of Conduct applies both within project spaces and in public spaces | ||
when an individual is representing the project or its community. | ||
Examples of representing a project or community include using an official | ||
e-mail address, posting via an official social media account, or acting | ||
as an appointed representative at an online or offline event. | ||
|
||
## Enforcement | ||
|
||
Instances of abusive, harassing, or otherwise unacceptable behaviour may be | ||
reported by contacting the CESSDA Main Office at support AT cessda DOT eu. | ||
The project team will review and investigate all complaints, and will respond | ||
in a way that it deems appropriate to the circumstances. | ||
The project team is obligated to maintain confidentiality with regard to the | ||
reporter of an incident. | ||
Further details of specific enforcement policies may be posted separately. | ||
|
||
Project maintainers who do not follow or enforce the Code of Conduct | ||
in good faith may face temporary or permanent repercussions as determined | ||
by other members of the project's leadership. | ||
|
||
## Attribution | ||
|
||
This Code of Conduct is adapted from the [Contributor Covenant][homepage], | ||
version 1.4, available at [http://contributor-covenant.org/version/1/4][version] | ||
|
||
[homepage]: http://contributor-covenant.org | ||
[version]: http://contributor-covenant.org/version/1/4/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
# Contributing to ARGOEU Open Source Software | ||
|
||
Thank you for considering contributing to ARGOEU Open Source Software. | ||
|
||
Please note that we welcome all forms of user feedback and are generally open | ||
to many forms of collaboration, | ||
but please read this document carefully before proceeding. | ||
|
||
## User feedback | ||
|
||
### Reporting problems | ||
|
||
We welcome all feedback you may have when using any of our tools and services. | ||
|
||
If you encounter a problem, please use the "Report a problem" button you find | ||
at the lower right corner of the respective tool or service | ||
and choose "Bug" as the value of the Components field. | ||
|
||
### Suggesting Enhancements | ||
|
||
To suggest new functionalities and possible future developments, | ||
please use the "Report a problem" button you find at the lower right corner of | ||
the respective tool or service | ||
and choose "New Feature" or "Improvement" as the value of the Components field. | ||
|
||
## Contributing to the development | ||
|
||
Development of all ARGOEU tools and services is aligned with our roadmap and | ||
any functional requirements we have. | ||
|
||
External contributions can be accepted, if they provide functionality ARGOEU | ||
deems appropriate and are of acceptable quality. | ||
Specific requirements and criteria may apply to specific tools. | ||
|
||
If you want to contribute to ARGOEU tools and services, | ||
please contact argoeu [AT] grnet.gr before proceeding. | ||
|
||
### Practical matters | ||
|
||
ARGOEU reserves the right to accept or reject any contribution. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.