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

Provide an updated list of papers and maybe blog posts, somewhere. #162

Open
ctb opened this issue Sep 13, 2013 · 12 comments
Open

Provide an updated list of papers and maybe blog posts, somewhere. #162

ctb opened this issue Sep 13, 2013 · 12 comments
Milestone

Comments

@ctb
Copy link
Member

ctb commented Sep 13, 2013

No description provided.

@RamRS
Copy link
Contributor

RamRS commented Sep 13, 2013

Maybe create a wiki page with the repo and link to it from README?

@ctb
Copy link
Member Author

ctb commented Sep 13, 2013

I'd like to avoid too much diversification of resources - a wiki is a maintenance headache, and, moreover, not linked into the main version control. Is there a reason not to just keep it in the documentation somewhere?

@RamRS
Copy link
Contributor

RamRS commented Sep 13, 2013

Hmmm, good point. We could create a document and tie it to be rendered as web-page content maybe?

@ctb
Copy link
Member Author

ctb commented Sep 13, 2013

On Fri, Sep 13, 2013 at 06:50:58AM -0700, Ram RS wrote:

Hmmm, good point. We could always create a document and tie it to be rendered as web-page content maybe?

You mean, like the current documentation? Yes, I agree :)

khmer.readthedocs.org

--titus

C. Titus Brown, [email protected]

@RamRS
Copy link
Contributor

RamRS commented Sep 13, 2013

I did not know this was already around! I know the khmer-protocols.readthedocs.org , but not khmer.readthedocs ! We just need to collate a list of sources then!

@mr-c
Copy link
Contributor

mr-c commented Sep 13, 2013

Out of curiosity, why would a wiki be a maintenance headache? A Github hosted wiki, like the one we already have: https://github.com/ged-lab/khmer/wiki/_pages is backed by its own git repository (ex: [email protected]:ged-lab/khmer.wiki.git)

@ctb
Copy link
Member Author

ctb commented Sep 13, 2013

On Fri, Sep 13, 2013 at 07:16:26AM -0700, Michael R. Crusoe wrote:

Out of curiosity, why would a wiki be a maintenance headache? A Github hosted wiki, like the one we already have: https://github.com/ged-lab/khmer/wiki/_pages is backed by its own git repository (ex: [email protected]:ged-lab/khmer.wiki.git)

More places to maintain == bad; we're already drowning in places that
need to be consolidated.

Well maintained wikis are a rarity, and also become a spam pot. Without a good
reason to diversify, why bother?

I also think github online editing and PRs serve basically the same purpose
as a wiki.

--t

C. Titus Brown, [email protected]

@ctb
Copy link
Member Author

ctb commented Oct 5, 2013

Make sure to update README to point out that this is no longer prepublication software, once we have list of papers etc.

@mr-c
Copy link
Contributor

mr-c commented Jan 20, 2014

@mr-c
Copy link
Contributor

mr-c commented Jan 20, 2014

Oh, is this meant to be a list of papers that cite us? Ignore my CITATION comment then.

@ctb
Copy link
Member Author

ctb commented Jan 20, 2014

On Mon, Jan 20, 2014 at 12:46:48PM -0800, Michael R. Crusoe wrote:

Oh, is this meant to be a list of papers that cite us? Ignore my CITATION comment then.

No, you were partly right. But there may be more things (blog posts,
papers) than purely things that should be cited.

--t

C. Titus Brown, [email protected]

@mr-c
Copy link
Contributor

mr-c commented Jan 20, 2014

Great. How to cite our pubs is being tracked by #49

@mr-c mr-c mentioned this issue Mar 10, 2014
@mr-c mr-c modified the milestones: 1.1+ Release, 1.0 release Apr 2, 2014
@mr-c mr-c modified the milestones: 1.2 Release, 1.2+ Aug 19, 2014
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