document available architecture/python versions in introduction of docs

[croth1]

I think it would be helpful to add a list of currently supported architectures and python/R versions, etc in the "Brief introduction" section of the docs.
It would be worthwhile to add a note that not all packages are available for all architectures and how users can find out whether their package system is supported by conda-forge.

[ForgottenProgramme]

@croth1 , hey! :)
Yes. This makes sense.
I liked the suggestion that the list of supported architectures should go on the 'brief introduction' page. That way if we do not (yet) support what the user is looking for, their time is saved.

[ForgottenProgramme]

Maybe we can add a 'Supported Languages' heading below this :
https://conda-forge.org/docs/user/introduction.html#display-conda-forge-packages-in-anaconda-navigator heading.

[ForgottenProgramme]

@croth1

@beckermr thinks it would be a good idea to first discuss what we mean by 'support'.

#1287 (comment)

Also, issue #1287 seems to be a duplicate of this issue.

[croth1]

I agree with @beckermr that support needs a qualifier. I think one can liken this to software and plugins. Sometimes we only ship the software (=interpreter/compiler), but not the plugins (=packages).

The section could contain at least following information:

1. What software are we providing and what versions are currently supported.
2. Do we package plugins and if not how can users install 3rd party plugins into their conda environments.
3. If no version is currently supported a link to how people can take over maintainer roles.

What do you think?

[viniciusdc]

I agree with @beckermr that support needs a qualifier. I think one can liken this to software and plugins. Sometimes we only ship the software (=interpreter/compiler), but not the plugins (=packages).

The section could contain at least following information:

1. What software are we providing and what versions are currently supported.
2. Do we package plugins and if not how can users install 3rd party plugins into their conda environments.
3. If no version is currently supported a link to how people can take over maintainer roles.

What do you think?

We should also update this section as well: https://conda-forge.org/docs/orga/guidelines.html?highlight=languages#language-versions

[viniciusdc]

Also, as we are talking about the general architecture/package stuff here, it's best to link #986 here too

[PrernaSingh587]

@croth1 @viniciusdc
Hey! I was wondering if I can work on documenting this section. Could you please provide me with some pointers to begin compiling the useful information?

[beckermr]

See the discussion above. We cannot make progress on this until we come up with what we want to say in terms of support.

[viniciusdc]

yeah, actually I would like to follow @croth1 comments here and break this into different issues (because we might need some big discussions here and there about this: software and versions currently provided by us.) The maintainer role is being discussed somewhere else, so what do you think @beckermr? this way we can start moving forward to the true meaning of support here...

[beckermr]

We'll need to chat with all of core. I suggest we add this as an agenda item for tomorrow's meeting

[Martins-O-U]

Hello @beckermr and @viniciusdc, Outreachy Applicant here. Please confirm that the "Support" has now been properly defined at your meeting as I'd like to work on documenting this information as a section titled "Supported Languages" on the Brief Introduction page and on the Guidelines section as my contribution.

[ForgottenProgramme]

Hello @beckermr and @viniciusdc, Outreachy Applicant here. Please confirm that the "Support" has now been properly defined at your meeting as I'd like to work on documenting this information as a section titled "Supported Languages" on the Brief Introduction page and on the Guidelines section as my contribution.

Welcome to conda-forge, @Martins-O-U ! :)

[Martins-O-U]

Thank you @ForgottenProgramme
Let's create awesomeness!