Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 36 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,8 +31,43 @@ If you have questions or need help, please check out our documentation for a [li
## conda-forge dev meetings

Our documentation contains a section with [minutes from previous dev meetings]([https://conda-forge.org/docs/minutes/00_intro.html]). These meetings occur every two weeks on Wednesday from 17:00-18:00 UTC.
A link to the google calendar item can be found [here](https://calendar.google.com/event?action=TEMPLATE&tmeid=Z2lraDk2a205cGUxdDkxYmNybXQxMGIxMGtfMjAxOTA3MjRUMTcwMDAwWiBzY29wYXR6QG0&tmsrc=scopatz%40gmail.com&scp=ALL).
A link to the google calendar item can be found [here](https://calendar.google.com/event?action=TEMPLATE&tmeid=Z2lraDk2a205cGUxdDkxYmNybXQxMGIxMGtfMjAxOTA3MjRUMTcwMDAw

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Your link to the calendar is broken and doesn't work. You just need to make sure the line below is connected to the line above and it should be fine.

WiBzY29wYXR6QG0&tmsrc=scopatz%40gmail.com&scp=ALL).

We use https://hackmd.io/ for taking meeting minutes and will upload the resultant markdown file after the meeting has concluded.

There is a template provided in [`misc/DEV_MEETING_TEMPLATE.md`](https://github.com/conda-forge/conda-forge.github.io/tree/main/misc/DEV_MEETING_TEMPLATE.md) that you should use to create a new hackmd document.


## conda-forge CODE OF CONDUCT ([https://conda-forge.org/docs/orga/governance.html#code-of-conduct])

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Looks like all of your links from line 42 to the end are incorrect. The link text should be in square brackets, while the actual link should be in parentheses. See line 39 above.


Conda-forge adheres to the NumFOCUS Code of Conduct.([https://www.numfocus.org/code-of-conduct])

THE SHORT VERSION
>> Be kind to others. Do not insult or put down others. Behave professionally. Remember that harassment and sexist, racist, or exclusionary jokes are not appropriate for NumFOCUS.

>> All communication should be appropriate for a professional audience including people of many different backgrounds. Sexual language and imagery is not appropriate.

>> NumFOCUS is dedicated to providing a harassment-free community for everyone, regardless of gender, sexual orientation, gender identity and expression, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of community members in any form.

Thank you for helping make this a welcoming, friendly community for all.

The Code of Conduct Reporting Form can be accessed here ([https://numfocus.typeform.com/to/ynjGdT])

Code of Conduct Table of Contents

>> Diversity Statement([https://numfocus.org/code-of-conduct#diversity-statement])
>> Code of Conduct Introduction & Scope([https://numfocus.org/code-of-conduct#introduction])
>> Standards for Behavior([https://numfocus.org/code-of-conduct#standards-behavior])
>> Unacceptable Behavior([https://numfocus.org/code-of-conduct#unacceptable-behavior])
>> Reporting Guidelines([https://numfocus.org/code-of-conduct#reporting-guidelines])
>> How to Submit a Report([https://numfocus.org/code-of-conduct#how-to-report])
>> Reporting Form([https://numfocus.org/code-of-conduct#report-form])
>> Person(s) Responsible for Resolving Complaints([https://numfocus.org/code-of-conduct#persons-responsible])
>> Conflicts of Interest([https://numfocus.org/code-of-conduct#conflicts-of-interest])
>> Reporting at NumFOCUS Events([https://numfocus.org/code-of-conduct#reporting-at-events])
>> What to Include in a Report([https://numfocus.org/code-of-conduct#what-to-include])
>> Enforcement: What Happens After a Report is Filed?([https://numfocus.org/code-of-conduct#enforcement])
>> Appealing a Decision([https://numfocus.org/code-of-conduct#appeal])
>> Timeline Summary([https://numfocus.org/code-of-conduct#timeline])
>> License([https://numfocus.org/code-of-conduct#license])
20 changes: 20 additions & 0 deletions src/maintainer/knowledge_base.rst
Original file line number Diff line number Diff line change
Expand Up @@ -270,6 +270,26 @@ A package that needs all five compilers would define

.. _cdt_packages:

Activation recipes

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Did you mean for this file to also be in this PR? Seems unrelated.

1. GCC - https://github.com/conda-forge/ctng-compiler-activation-feedstock
2. Clang, OSX - https://github.com/conda-forge/clang-compiler-activation-feedstock
3. gfortran, OSX - https://github.com/conda-forge/gfortran_osx-64-feedstock

Implementation packages

1. GCC - https://github.com/conda-forge/ctng-compilers-feedstock

2. gfortran, OSX - https://github.com/conda-forge/gfortran_impl_osx-64-feedstock

3. clang
https://github.com/conda-forge/llvmdev-feedstock
https://github.com/conda-forge/libcxx-feedstock
https://github.com/conda-forge/clangdev-feedstock
https://github.com/conda-forge/openmp-feedstock
https://github.com/conda-forge/tapi-feedstock

4. OSX - https://github.com/conda-forge/cctools-and-ld64-feedstock

Core Dependency Tree Packages (CDTs)
------------------------------------

Expand Down