You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As promised Thursday, the note on running workflows in github:
40M developers on github woke up last week with a new tab, “actions”, and a workflow engine integrated in their developer environment – which already includes hosting web applications and authentication services, all of this with versioning and a marketplace where workflows can be published and found. So the conversation Thursday was about creating a BCO example in this environment to establish its FAIR use. I suspect most developers (definitely most students) have already migrated to serverless execution environments and having a one-click place where to validate, and disseminate, a workflow manifest/language, really is the place to be if you want to reach them. So the suggestion is to have a simple and compelling example of a BCO as a github action others can fork and investigate.
Keynote at github universe explaining workflow actions: Here’s a link to a video
I left the same comment in gitter [this one 😄] in case you want to discuss it further (not a fan of email conversations here …)
The text was updated successfully, but these errors were encountered:
From: De Almeida, Jonas (NIH/NCI) [E]
Hi Charles,
As promised Thursday, the note on running workflows in github:
40M developers on github woke up last week with a new tab, “actions”, and a workflow engine integrated in their developer environment – which already includes hosting web applications and authentication services, all of this with versioning and a marketplace where workflows can be published and found. So the conversation Thursday was about creating a BCO example in this environment to establish its FAIR use. I suspect most developers (definitely most students) have already migrated to serverless execution environments and having a one-click place where to validate, and disseminate, a workflow manifest/language, really is the place to be if you want to reach them. So the suggestion is to have a simple and compelling example of a BCO as a github action others can fork and investigate.
References:
I left the same comment in gitter [this one 😄] in case you want to discuss it further (not a fan of email conversations here …)
The text was updated successfully, but these errors were encountered: