-
-
Notifications
You must be signed in to change notification settings - Fork 68
2022 Week 41 release #281
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
2022 Week 41 release #281
Conversation
* Show cwltool --make-template to users in the chapter where we introduce the inputs objects * Add a troubleshooting section for the cachedir docs Co-authored-by: Michael R. Crusoe <[email protected]>
* Link to #$include in the note * 'Important' box wasn't terminated properly Co-authored-by: Michael R. Crusoe <[email protected]>
…mmand output lines (#247) * Highlight lines of interest in the command outputs * Rename "Advanced Inputs" to "Inclusive and Exclusive Inputs" * Add text about the exclusive input parameters and expressions * explain why itemC was chosen when both are provided Co-authored-by: Michael R. Crusoe <[email protected]>
…into update-content
"pip install -e .[all]" doesn't work if you don't have setup.py. We're using a declarative package config so we need to invoke it slightly differently.
Adjust install instructions
Typo fix
update note content and add windows OS and link to install cwltool
Co-authored-by: Michael R. Crusoe <[email protected]> Co-authored-by: “gathoni-k” <“[email protected]”>
* modified sentence * modified quick-start.md
* Increase navigation depth to 3 * Expand left sidebar * Revert "Expand left sidebar" This reverts commit a3dc19b. Co-authored-by: “gathoni-k” <“[email protected]”>
Co-authored-by: “gathoni-k” <“[email protected]”> Co-authored-by: SWZ <[email protected]>
* Update README with current render * update README with released and RTD user guide
The json file has a different DOI than the readme -- do we want the json to point to the latest release but the readme to point to the general zenodo which houses all the releases, or should they match. Additionally, who is in charge of putting the zenodo entry to match the zenodo.json file in the GitHub repository? I know there exist github actions for zenodo but don't know if he have them set up or not. @kinow perhaps you know? |
as we no longer use them
The Zenodo JSON file points to multiple related DOIs. Line 20 in 0c1df15
is a reference to the template we used to use from the Carpentries, and thus can be removed. Line 29 in 0c1df15
Is a reference to the "all versions of this resource" parent DOI for the User Guide, as detailed at https://help.zenodo.org/#versioning The badge will show the DOI for the latest release of the user.
So there is no reason to update the Zenodo JSON file. Each new GitHub release automatically uploads to Zenodo. P.S. You deleted a comment I made in response to your earlier inquiry (and that inquiry itself). Continued deletion of my comments will undermine your retaining write privileges in this and any other CWL repository. |
README.md
Outdated
[Released User guide for CWL v1.2.0](https://www.commonwl.org/user_guide/) : This is the released version which corresponds to the release branch. | ||
[Read The Docs User guide for CWL v1.2.0](https://common-workflow-languageuser-guide.readthedocs.io/en/latest/) : This is the Read The Docs(RTD) version which corresponds to the main branch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use plain URL links here, please. The link text is too similar to each other.
RTD
is defined here and never used again, so remove that abbreviation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe it was added because we in tickets and other places (like chat) use RTD so people were wondering what that meant. So, I think even though not used in the README again, it might be nice to somehow tell me what common acronyms people are using. Not sure if this is the place to do this - but just an FYI.
I assume you mean the Zenodo entry since you have a ticket to update the .json file. Documentation of this and the release process would be welcome. Also, it seems like the release is a moving target. So it would be nice to know if we now have a complete list for the release. |
Co-authored-by: Michael R. Crusoe <[email protected]>
@bamiwoaluko , @Gathoni-K, and @Mackenzie-OO7: Under which name shall we list you in the |
Co-authored-by: Michael R. Crusoe <[email protected]>
I don't think we should require people to give their formal names to be listed as authors. I think it is fine if they do - but it shouldn't be an obligation. People may for several reasons not be using their legal names and/or not want their names (legal or not) to be made available on a project. |
Agreed, I already listed them by their GitHub handles as shown in c757074 ; just giving them a chance to choose how they will be represented. |
Makes sense to me. |
Mary Gathoni |
Bamiwo Aluko |
Levai Mackenzie Agbara |
@Mackenzie-OO7 To confirm, should it be Line 20 in 864f866
|
It should be |
For review & deploy Friday, October 14th ish.
This PR will update automatically as additional contributions are merged into the
main
branch.Outstanding issues: