Ersilia Book
  • 🤗Welcome to Ersilia!
    • The Ersilia Open Source Initiative
    • Ten principles
    • Ersilia's ecosystem
  • 🚀Ersilia Model Hub
    • Getting started
    • Online inference
    • Local inference
    • Model contribution
      • Model template
      • Model incorporation workflow
      • Troubleshooting models
      • BioModels annotation
    • For developers
      • Command line interface
      • CI/CD workflows
      • Test command
      • Testing playground
      • Model packaging
      • Inputs
      • Codebase quality and consistency
      • Results caching
  • 💊Chemistry tools
    • Automated activity prediction models
      • Light-weight AutoML with LazyQSAR
      • Accurate AutoML with ZairaChem
      • Model distillation with Olinda
    • Sampling the chemical space
    • Encryption of AI/ML models
  • AMR chemical collections
  • 🙌Contributors
    • Communication channels
    • Tech stack
    • Internships
      • Outreachy Summer 2025
      • Outreachy Winter 2024
      • Outreachy Summer 2024
      • Outreachy Winter 2023
      • Outreachy Summer 2023
      • Outreachy Winter 2022
      • Outreachy Summer 2022
  • 📑Training materials
    • AI2050 intro workshop
    • AI2050 AI for Drug Discovery
    • Introduction to ML for Drug Discovery
    • Python 101
    • External resources
  • 🎨Styles
    • Brand guidelines
    • Slide and document templates
    • Scientific figures with Stylia
    • Coding style
  • 🌍About Us
    • Where to find us?
    • Diversity and inclusion statement
    • Code of conduct
    • Open standards and best practices
    • Ersilia privacy notice
    • Strategic Plan 2025-2027
    • Ersilia, the Invisible City
Powered by GitBook

2025, Ersilia Open Source Initiative

On this page
  • Work environment
  • Communication
  • Tech stack
  • Outreach

Was this helpful?

  1. Contributors

Communication channels

How to communicate with Ersilia's team members and start working together!

PreviousAMR chemical collectionsNextTech stack

Last updated 7 months ago

Was this helpful?

Work environment

EOSI’s team is composed of mission-driven individuals from diverse backgrounds, cultures and life experiences. The diversity is what makes EOSI unique, each individual is encouraged to bring its personal touch to the community. We favour remote working and flexibility, without losing collaborative energy. Asynchronous work happens regularly via Slack and team calls are organised weekly to ensure communication and support!

Communication

Ersilia’s main communication channel is Slack. Our Slack community is composed of people actively participating in any capacity in EOSI’s mission. We ask all participants to adhere to our code of conduct and interact respectfully with our peers. If you wish to join our Slack community, message us at hello@ersilia.io and we will send you the link. Additionally, coding-related issues will be discussed via GitHub, to make them visible to the broader community (see below). Finally, we are always reachable via email. We aim to respond to all enquiries within 3 working days. In addition to EOSI’s Slack workspace, we are lucky to be part of a larger network of aligned organisations. This includes Code for Science and Society, Fast Forward, the Software Sustainability Institute, and the Open Life Sciences program. As part of EOSI, you are welcome to reach out to those communities via us.

Tech stack

  • GitHub: all our code lives on GitHub. Each project is associated with a repository on our . We strongly encourage contributors to work as openly as possible, sharing the code daily to facilitate interaction and reproducibility. For code-related issues, bugs, etc., we prefer hosting the conversations on the “issues” section of the relevant GitHub repository, where all the community can see it and provide input. Once you start working with us, we will assign you a member or collaborator role in the organization. If you are not familiar with working in collaboration via GitHub, we recommend checking some starter guides beforehand, or joining a Carpentries or any other open training program.

  • GitBook. We benefit from a pro-bono plan on GitBook, where we develop all documentation related to our tools.

  • Microsoft Visual Studio Code: this is our preferred code editor. Most of our software is written in Python and runs in UNIX and MacOS. We recommend installing a Windows Subsystem for Linux on Windows machines to avoid compatibility issues.

  • Monday.com: we use Monday.com as project management and task tracker. We would like to the extent that this is possible that our collaborators use this tool to update the team on project progress.

  • AirTable: AirTable is the backend of our website and hosts relevant information for social media and other content. Unless you are joining us for marketing-related activities, you do not need to worry about it.

  • Softr: We use Softr as a no-code platform to develop our website.

  • Google Workspace: we benefit from the non-profit Google Workspace. Our meetings happen via Google Meet and our files repository is Google Drive.

  • AWS: our cloud system is currently in development on the AWS servers.

Outreach

We use Twitter () and as our main outreach channels. Both Gemma () and Miquel () are active on Twitter.

🙌
GitHub orgainzation page
@ersiliaio
LinkedIn
@TuronGemma
@mduranfrigola