Skip to content
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

Manuscript about Best Practices development #18

Open
bgruening opened this issue Sep 7, 2015 · 7 comments
Open

Manuscript about Best Practices development #18

bgruening opened this issue Sep 7, 2015 · 7 comments

Comments

@bgruening
Copy link
Member

bgruening commented Sep 7, 2015

What does the IUC thinks about writing a manuscript about Best Practices of tool development.
We all have seen many bad habits during our tool wrapping work and we gained a lot of experience. I really think this is worth to write down.

My idea is to write about the following ideas:

  • X things you should take into consideration if you code for big data
  • Writing about tools that will run on cluster environments, headless ... (not strictly bound to Galaxy)
  • The necessity to have a best practice guide and code reviews including automated testing
  • A more Galaxy specific section about the IUC and this repository (+planemo and additional community tools to assist in tool development)

Opinions? Ideas?

@hexylena
Copy link
Member

hexylena commented Sep 7, 2015

I'd be in favour of that. Just compiling all of the knowledge we have scattered across PRs and the wiki and here. Also things like the planemo "How do I ... ?" would likely be useful

@bgruening
Copy link
Member Author

Thanks @erasche I updated the original comment, feel free to do this as well.

@peterjc
Copy link
Contributor

peterjc commented Sep 7, 2015

When you say manuscript, do you mean formal journal publication? We could ping Scott Edmunds to see if it would fit the Galaxy series at GigaScience: http://www.gigasciencejournal.com/series/Galaxy

@ScottBGI
Copy link

ScottBGI commented Sep 9, 2015

It most certainly would fit, and would also be very useful for us to then link to it from our author instructions for future Galaxy submissions. To avoid duplication you should consult with the GCC data wranglers as they are putting together a best practices manuscript too, but it sounds like this would be more on the steps before their work.

@bgruening
Copy link
Member Author

@peterjc yes a formal manuscript. I think this can be also interesting for non-Galaxy developers.
Thanks @ScottBGI for commenting!

@blankenberg
Copy link
Member

I am +1 for this. I like the idea of a general primer for writing tools for big data and then showing how following these generic best practices are needed to enable smooth incorporation into analysis pipelines (including wrapping for inclusion in Galaxy as a specific use case).

@bgruening
Copy link
Member Author

@yhoogstrate here it is!

@galaxy-iuc/iuc has anyone time to get this started?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants