Skip to main content
12 events
when toggle format what by license comment
Jun 29, 2018 at 17:28 comment added haff @dbliss "why not make a cleaned up version of the repo public with just the things that the users want." I guess just because of the extra work involved, but I think this is the right approach.
Jun 29, 2018 at 17:26 vote accept haff
Jun 29, 2018 at 13:35 comment added abcd no one is going to care to spend time digging into the evolution of your manuscript . . . and it's very common (in my field) for authors to post PDFs of their finished manuscripts on their personal websites . . . so i don't see a problem with this . . . at the same time, it does seem like extra bulk to the repo that most people interested in your code won't need/want to look at . . . why not make a cleaned up version of the repo public, with just the things that users want?
Jun 29, 2018 at 9:19 comment added AppliedAcademic Why do you use the word 'expose'? It seems to have a negative connotation here, which would imply that you have some misgivings about it already. On the other hand, you apparently like to share your code. Why the distinction (besides legality/publisher guidelines)?
Jun 29, 2018 at 9:18 answer added Ian Sudbery timeline score: 2
Jun 29, 2018 at 0:42 history tweeted twitter.com/StackAcademia/status/1012496377467801600
Jun 28, 2018 at 20:27 comment added Nate Eldredge Related: academia.stackexchange.com/questions/18426/…
Jun 28, 2018 at 20:21 answer added Nate Eldredge timeline score: 12
Jun 28, 2018 at 20:16 comment added FuzzyLeapfrog You definitely have to check the publisher guidelines. It's like depositing you peer-reviewed author's manuscript in a public repository.
Jun 28, 2018 at 19:31 comment added aaaaa says reinstate Monica it might be publisher-specific. You should consult them
Jun 28, 2018 at 19:24 comment added Oleg Lobachev That's almost too open for my taste, but why not?
Jun 28, 2018 at 19:04 history asked haff CC BY-SA 4.0