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

[biocswirl] [biocterm] [dev] [doc] Hackseq second README check #4

Open
lisancao opened this issue Oct 19, 2019 · 0 comments
Open

[biocswirl] [biocterm] [dev] [doc] Hackseq second README check #4

lisancao opened this issue Oct 19, 2019 · 0 comments
Assignees

Comments

@lisancao
Copy link
Owner

lisancao commented Oct 19, 2019

[biocswirl] [biocterm] [dev] [doc] Hackseq second README check

Tasks

[x] Include names & git usernames of ALL your team members
Depending on your project status:
Standing prototype:
[x] README targets end users
[x] Should have clear installation/usage instructions
Ongoing work:
[ ] README targets potential developers
[ ] Should have clear descriptions of the different files/scripts, their relation to each other, and how they should fit together
Other:
[x] README targets people interested in hackseq in general
[x] Should have a description of the task distribution, the work done, and the experience overall
Due 3PM, get feedback by 5PM

Resources

Tag can be

biocswirl(related to course material)
biocterm (interface changes)
dev      (developers only)
file     (changes to file and folder structuring) 
rpkg     (r package/usethis and CRAN documentation changes)
feat     (new feature)
fix      (bug fix)
refactor (refactoring code)
style    (formatting, missing semi colons, etc; no code change)
doc      (changes to documentation)
test     (adding or refactoring tests; no production code change)
version  (version bump/new release; no production code change)
dbg      (Changes in debugging code/frameworks; no production code change)
license  (Edits regarding licensing; no production code change)
hack     (Temporary fix to make things move forward; please avoid it)
WIP      (Work In Progress; for intermediate commits to keep patches reasonably sized)
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

3 participants