Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add requirements for Use Case presentation at the ELIXIR FHD community call #30

Merged

Conversation

malloryfreeberg
Copy link
Contributor

Description

Added/modified content to address issue #27:

  • Added a new section (3. Complete steps to join Federated EGA) to the governance/legal topic to create a separate space for the requested changes
  • Added description of requirements to satisfy governance/legal steps indicated in "pathway" diagram, specifically the step "Present use cases to ELIXIR FHD Community" which was the step that prompted creation of Describe requirements for Use Case presentation at the ELIXIR FHD community call #27.
  • Added links to examples of presentations that satisfy the "Present use cases..." step

Additional changes to improve clarify of website content:

  • Modified "How do I start?" narrative to make it more clear what the actions are to start (Join mailing list; Attend community calls)
  • Added content to "What does the journey look like?" section to describe the figure in more detail

Motivation and Context

Addresses #27. Explaining in more detail and providing example presentations for this step in the "path to becoming a full FEGA member" would be beneficial to interested nodes so that they can prepare an appropriate presentation. It would help guide them in explaining their node's use case to the FHD community, and engage more efficiently with the FHD/FEGA communities. This information (and examples) is not secret, so it can definitely be shared in the onboarding materials website.

How has this been tested?

Changes have not been tested as they won't deploy to the website until after they are merged (OK for now).

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New content (non-breaking change which adds new content)
  • Modified content (non-breaking change which modifies existing content)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • I have read the CONTRIBUTING.md guide.
  • My changes follow the code style of this project.
  • I have updated supporting documentation, if required.
  • I have added my details to the CONTRIBUTORS.yaml file.

@malloryfreeberg malloryfreeberg added the documentation Improvements or additions to documentation label Aug 8, 2022
Copy link
Collaborator

@M-casado M-casado left a comment

Choose a reason for hiding this comment

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

LGTM, again, just a few comment.s


<img src="../../assets/img/Path-to-becoming-FEGA-member-v1.0.svg" alt="Colored diagram with icons and descriptions of technical and governance steps an interested Federated EGA node needs to complete to join the Network." width="1200" align="right" />

* **Contact FEGA with intent to join**. This step can be accomplished by engaging in the ELIXIR FHD Community ("[How do I start?](https://ega-archive.github.io/FEGA-onboarding/#how-do-i-start)") or by contacting Mallory Freeberg or Amy Curwin.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should we include here both of your emails as hyperlinks or something? Or between brackets at least.

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 wanted to avoid having my email on this site if I could. What we need to do is create a mailing list, probably, that redirects to myself, Amy, maybe others in the future. Our emails can be found pretty easily online, so I don't think it's a major issue to not include them here.

* [Switzerland](https://drive.google.com/file/d/1QPqO_4-5utYt6G761KdPSMT7uOzMllxn/view?usp=sharing)
* [Sweden](https://drive.google.com/file/d/1PzcC--fCTJ75sPVjOfemxwN2PkWisGIZ/view?usp=sharing)
* **Perform FEGA Maturity Model self-assessment**. This step can be accomplished by [evaluating your node against the Maturity Model](https://ega-archive.github.io/FEGA-onboarding/topics/maturity-model/#2-evaluate-against-the-fega-maturity-model).
* **Sign FEGA Legal Agreement**. Also called the "FEGA Collaboration Agreement", this is the final step to official join the Federated EGA.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I feel like there is a reference missing here to, either the content of that agreement, or the document itself. If we have them, of course.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, there is meant to be a link to the legal agreement at line 56 above, but there is some work to do on it before we post it publicly. I'll make sure this is tracked in an issue so we don't forget to link it.

@malloryfreeberg malloryfreeberg merged commit a0e2ace into EGA-archive:main Aug 9, 2022
@malloryfreeberg malloryfreeberg deleted the docs/use-case-present-reqs branch August 9, 2022 07:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Describe requirements for Use Case presentation at the ELIXIR FHD community call
2 participants