2022 Week 44 release

[mr-c]

No description provided.

[mr-c]

My initial review.

It would be nice if more of this was caught during the original PRs, @tetron

Also, the commit messages are very uninformative. Either PRs should be squashed and the commit message updated, or contributors should be asked to clean up their commits.

[mr-c]

Suggested change

	If a command-line tool is written manually in CWL v1.1+, there is a need to
	specify when network access is required.
	Starting with CWL v1.1, you must document the requirement for network access if it is required.

[mr-c]

Suggested change

	or v1.2 get Network Access automatically.
	or v1.2 get `networkAccess: true` set automatically.

[mr-c]

Hmm, the placement of this new section seems awkward. None of the other CommandLineTool specific requirements are documented in this section.

I think a new section about network access is fine. We should also explain why network access using steps should be avoided: hurts portability, increases the fragility of the workflow (external service can go away, or change format of responses). We should also present alternatives like putting the URL for an input File in the input object's location field instead of a curl or wget using CommandLineTool; and in general separating the automated batch steps from data acquisition and data publishing steps.

[swzCuroverse]

Could we add this now and then make a ticket to add this information. The ticket just said to add this specifically. #249

[swzCuroverse]

I think probably CommandLineTools are mentioned when they pop up in the context of using them - but I am not sure where this one might pop up in the context of the user guide. The possible options are (1) Keep it where it is for now (2) Add it here -- http://www.commonwl.org/user_guide/introduction/basic-concepts.html#processes-and-requirements or (3) Add it to the FAQ

[mr-c]

Best not to link directly to the WSL2 install docs, as users will click that first and not follow all of the linked cwltool MS Windows installation directions

Suggested change

	If you are using Windows, you will have to install the [Windows Subsystem for Linux 2](https://learn.microsoft.com/en-us/windows/wsl/install) (WSL2).
	Visit the `cwltool` [documentation](https://github.com/common-workflow-language/cwltool/blob/main/README.rst#ms-windows-users)
	for details on installing WSL2.
	If you are using Windows, you will have to install the Windows Subsystem for Linux 2 as documented in the
	[`cwltool` documentation for Microsoft Windows users](https://github.com/common-workflow-language/cwltool/blob/main/README.rst#ms-windows-users).

[swzCuroverse]

My initial review.

It would be nice if more of this was caught during the original PRs, @tetron

Also, the commit messages are very uninformative. Either PRs should be squashed and the commit message updated, or contributors should be asked to clean up their commits.

@mr-c you point out several issues where people have including v1.0, command-line or FAQ titles that aren't questions. However that was done all ready in the user guide. So, I am not sure why @tetron was responsible for pointing them out since they are already inconsistent in the User Guide which you reviewed. I think if you want a standard or consistent use (1) you should document it (2) you should make sure it is in the User Guide correctly. Otherwise, there is no way people will know that is what you want.

[mr-c]

Suggested change

	### Cwl-runner Python Module
	### Cwl-runner Python Module

Suggested change

	### Cwl-runner Python Module
	### Generic ``cwl-runner`` alias

[kinow]

The current text may (very likely!) have been written by me 😬 The suggested text is less technical and easier to understand IMHO, so +1

[tetron]

@mr-c I believe branch protection on main is interfering with "Update branch" and "Commit suggestion" buttons, so I was going to close this pull request and make a new branch called staging.

[tetron]

See #373