-
Notifications
You must be signed in to change notification settings - Fork 592
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
organize tools list better #1669
Comments
For @cmnbroad and the 4.0 release milestone. |
Let me know if and how we can help in this @cmnbroad. Just to keep you updated, Sheila and I are spending the next three weeks updating GATK4 documentation. We aim for all documentation to be complete by December 14. It's possible we will organize the forum tool documentation to mirror that of this categorization. There was talk today in a meeting with the engine team that we should propose multiple categorizations, for the (much later, not upcoming release) possibility for listing tools based on user preference, e.g. by functional category or by input file type. So any work you do towards categorization could be useful down the road. Here are some questions that were raised during the meeting:
Because we need to also ensure every tool (excepting Spark and BWA) has a summary description and example command, it would be useful for documentation purposes at least, to have functional categories that take the same or related inputs, e.g. any type of interval list (BED, Picard style or GATK), so that we can group testing of the tool commands and there is minimal context switching. |
Turns out categorization is on the Comms team--I misunderstood. @cmnbroad you are only on the hook for labels and other engineering feats. |
This is being finalized via efforts in #3853 and https://github.com/broadinstitute/dsde-docs/issues/2639. Whether the new categorization schema is better, well, no one has complained so far. |
This is done -- closing. |
right now you get this which is bogus on many levels (duplicated and confusing categories, confusing tool names etc). We need to put more order into this. @vdauwera can you help come up with a better scheme of how to organize tools?
Compare to the ADAM project (much much smaller scope of course but very clean UI: https://github.com/bigdatagenomics/adam)
The text was updated successfully, but these errors were encountered: