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

Project timeline for Outreachy #153

Open
matuskalas opened this issue Apr 28, 2021 · 0 comments
Open

Project timeline for Outreachy #153

matuskalas opened this issue Apr 28, 2021 · 0 comments

Comments

@matuskalas
Copy link
Member

This issue documents the hints for creating a project timeline for the Outreachy applicants.

And to answer an FAQ❔ Nope, we don't ask any additional specific question in the final app.😊

The project timeline can start with the onboarding tasks including:

  • A chosen set of "good first issues" which the applicant hasn't finished already during the application period
  • If the candidate is interested, getting familiar with the community and with the minimum basics of open science, biology, open source bioinformatics, etc. (with help from the mentors)

Here are some concrete tasks that could be worked on during the internship, either as the main goals or stretch goals. Please select a not-too-big subsetπŸ˜‰

  • Enable to visualise the usage (counts) of "child" concepts (beyond bio.tools)
  • Adding more resources to show usage (e.g. FAIRsharing if possible)
  • Enable loading the ontology in JSON-LD format
  • Visualisation of ontology details and additional concept details (configurable by users; show|hide attributes; working also with other ontologies than EDAM; improving documentation of how to set up with other ontologies)
  • Enable the generation of pull requests when suggesting an edit or addition to EDAM
  • Enable choosing between multiple ontologies (and versions) to load
  • Optimisation of UX
  • Optionally fixes to the content of the EDAM ontology itself
  • Optionally improving the EDAM webpage (possibly Jekyll-style generation; better UX; better aesthetics; better content; continuous deployment (CD))
  • Updating and improving the EDAM Popovers plugin for Firefox (if inkuzmin is available to help)
  • Optionally improving the edamontology.org Apache web server setup (especially httpd rewrites)
  • Applicants do not need to add additional tasks into their timeline, but they are welcome to do so if they want to (especially if wanting to learn something, experiment with something, get in touch with a specific community, etc.)

It's totally fine if the timeline is brief and high-level! 😸 Good to keep in mind is that the suggested timeline can|will be adjusted during the course of the internship, depending on how the project is evolving. The most important for us mentors is:

  • which weeks the candidate will be unavailable, completely or a big part
  • maybe good to have some kind of a main focus or "milestone" each or each second week (can be a couple of words, no details), so that both the intern and the mentors can plan better and see progress. But this is not mandatory.
  • it would be excellent if the intern could put the 2 mentioned conferences into the timeplan (GCC and ISMB/BOSC(!)). These will both include a CoFest for 2 or more days after the main conference, where intensive work will be done together with a broader community. πŸ™ They're very exciting, and it's highly recommended to reserve a lot of time & energy during those days!!πŸ˜‰πŸ±β€πŸ
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant