From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>,
Pjotr Prins <pjotr2019@thebird.nl>
Cc: gwl-devel@gnu.org
Subject: Re: Next steps for the GWL
Date: Thu, 6 Jun 2019 13:07:08 +0200 [thread overview]
Message-ID: <CAJ3okZ07FyPK00nsCEp5NYpUXc2tui3=ODig+OLQ3BV_TeTdTw@mail.gmail.com> (raw)
In-Reply-To: <87o93eiqvz.fsf@mdc-berlin.de>
Hi,
(+ Pjotr because I am sure he has an interesting opinion but not sure
he closely reads this list ;-)
On Mon, 3 Jun 2019 at 18:18, Ricardo Wurmus
<ricardo.wurmus@mdc-berlin.de> wrote:
> > - what about a bridge with CWL?
>
> I’m open to this idea, but it would need to be well-defined. What does
> it really mean? Generating CWL files from GWL workflows? That really
> shouldn’t be too hard. Anything else, however, is hard for me to
> imagine.
Well, I point out previous threads about this topic:
https://lists.gnu.org/archive/html/guix-devel/2018-01/msg00428.html
https://lists.gnu.org/archive/html/gwl-devel/2019-02/msg00019.html
1-
Generating CWL from GWL should be nice. It should ease the use of
already in-place platform and tools (AWS, etc.)
2-
Use CWL as a process. A lot of work have been done by Pjotr and
reported here [1]
[1] https://guix-hpc.bordeaux.inria.fr/blog/2019/01/creating-a-reproducible-workflow-with-cwl/
All the best,
simon
next prev parent reply other threads:[~2019-06-06 11:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 13:47 Next steps for the GWL Ricardo Wurmus
2019-06-03 15:16 ` zimoun
2019-06-03 16:18 ` Ricardo Wurmus
2019-06-06 11:07 ` zimoun [this message]
2019-06-06 12:19 ` Ricardo Wurmus
2019-06-06 13:23 ` Pjotr Prins
2019-06-06 3:19 ` Kyle Meyer
2019-06-06 10:11 ` Ricardo Wurmus
2019-06-06 10:55 ` zimoun
2019-06-06 11:59 ` Ricardo Wurmus
2019-06-06 13:44 ` Pjotr Prins
2019-06-06 14:06 ` Pjotr Prins
2019-06-06 15:07 ` Kyle Meyer
2019-06-06 20:29 ` Ricardo Wurmus
2019-06-07 4:11 ` Kyle Meyer
2019-06-12 9:46 ` Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ3okZ07FyPK00nsCEp5NYpUXc2tui3=ODig+OLQ3BV_TeTdTw@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=gwl-devel@gnu.org \
--cc=pjotr2019@thebird.nl \
--cc=ricardo.wurmus@mdc-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).