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

Core meeting agenda 2020-01-06 #630

Closed
mbargull opened this issue Dec 24, 2019 · 3 comments
Closed

Core meeting agenda 2020-01-06 #630

mbargull opened this issue Dec 24, 2019 · 3 comments

Comments

@mbargull
Copy link
Member

@bioconda/core
Please add/edit agenda items below. When relevant, please create an issue for each topic so off-line discussion can occur there.

  • Updates from the previous meeting(s)
    • GitHub Actions
    • Perl migration
    • CZI sponsorship
    • PY 3.8 migration
    • PY 2.7 EOL handling
    • ISMB 2020 Tutorial
@mbargull
Copy link
Member Author

mbargull commented Jan 6, 2020

Some points discussed (please feel free to add anything I missed!):

  • Community engagement:
    • Plan regular hackathons.
      • E.g., 3-4 times a year.
      • Have certain goals for a hackathon, e.g. "get under X number of issues/PRs".
    • Encourage contributors.
      • Add more incentives for people to merge (bot) PRs.
      • Make (number of) contributions more visible, e.g., on the website.
      • Add some gamification.
        • Top contributors.
        • Number of reviewed/merged PRs.
      • Add a list of requested packages.
    • Attend conferences/hackathons (possibly some of the following).
      • ISMB 2020 (Montréal)
      • ECCB 2020 (Barcelona)
      • GCB 2020 (Frankfurt)
      • BioHackathons (??? - keep an eye out!)
  • Python version support:
    • Add Python 3.8.
      • Check how far conda-forge migration has come.
      • Do this whenever seems appropriate.
    • Deprecate Python 2.7.
      • Remove from default build config.
        • (Check for zip_keys in conda-forge-pinning).
      • Still support building for Py2.7 via conda_build_config.yaml.
      • Open issue about the deprecation and how to use conda_build_config.yaml.
      • Compose list of recipes that are Py2.7 only.
      • Do this together with Py3.8 addition.
  • Support for "other systems":
    • Determine when/if this is needed.
    • Use sparingly, definitely not by default.
    • Try to reuse conda-forge setup if possible.
    • Option "move to conda-forge".
      • E.g. biopython.
      • Problematic if (current/future) dependencies are on bioconda.
  • Next bulk runs:
    • See "Python version support" above.
    • Bioconductor release probably in May.

@mbargull
Copy link
Member Author

mbargull commented Jan 6, 2020

Re Py3.8: We might also want to update conda-forge-pinning to get clang 9 at the same time to avoid additional bulk runs.

@mbargull
Copy link
Member Author

mbargull commented Jan 6, 2020

Re Py2.7: Issue created at bioconda/bioconda-recipes#19549.

@mbargull mbargull closed this as completed Jan 6, 2020
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