@galaxyproject/iuc can the following PRs be addressed? The vSNP suite consists of 6 tools, with individual tools not being useful unless the full suite is available. In fact, the suite of tools are most useful within a workflow that I will contribute (somewhere??) when the PRs have all been merged.
In the meantime, I am having to maintain 2 sets of these tools (one with owner greg and the other with owner iuc) since I am not able to update the many vSNP workflows that I maintain that use these tools.
Significant effort has already gone into reviewing these PRs, so I'm not sure significantly more investment is beneficial, and I'd hate to see these PRs end up languishing here indefinitely.
galaxyproject/tools-iuc#3407 - I think this can be merged without too much invested into a review. It simply fixes tools that have already been reviewed and merged. The only question is if another test is desirable - if so, the test dataset is fairly large.
galaxyproject/tools-iuc#3405 - I think the only question about this is if there is a better way to do what the tool is doing.
I believe the only questions about this galaxyproject/tools-iuc#3404 and this galaxyproject/tools-iuc#3381 is that they accept collections on input, so Galaxy will not split the collections across jobs. The reason that the tools accept collections is because the outputs must be merged instead of split across nested collections, and the Galaxy framework does not yet support merging outputs when the non-collection inputs are split across jobs. The Python multiprocessing library is used to help with this shortfall.
Anyway I apologize for not being able to not have the last word, I should be in therapy.
I can help with that ;) You are assuming users are technical people, but that is questionable. From my experience there are a lot of Galaxy users that are happy if nifty details can be hidden as much as possible and this is considered a good UX. In this sense implicit > explicit, even if we as technical people have hard times to understand this.
"Yay, I love being able to not understand where data is coming from - that lack of transparency makes this all really usable for me".
I guess its useless to discuss this further on that level. Lets postpone it again a few years :)