Live data from Hacker News

Banyan, the "GitHub of Science", is now in public beta

blog.banyan.co

51–60 of 104 posts

Re: Banyan, the "GitHub of Science", is now in public beta

#51
post #34
post #24

Earlier quoted context omitted.

The other thing is that, IMHO, private repo for this is not good for academic, instead, make it temporarily private. People write papers to get published. They surely want as many people as possible to see it. The reason they want it to be private is to hide it from others before getting published so the ideas won't get stolen. So I'm thinking maybe set up a time limit for repos being private would be better? After t…

It is one reason. But e.g. in my field (theoretical physics) I am not afraid of theft (well, if someone is smart enough to understand and polish a half-written paper, then (s)he can write much better stuff) but of things that "as of now makes sense only to me" or "there are half-written" (e.g. in some places I changed indices i to i+1, but not in all, making it both frustrating and useless to read) or may simply be f…

Why a time limit? Why not a "publish" button that flips it to public? (And maybe submits it to arXiv at the same time, optionally.)

Re: Banyan, the "GitHub of Science", is now in public beta

#52
post #29
post #25

Earlier quoted context omitted.

Hi zm. What do you mean by the UI elements? Do you mind snapping a screenshot for me?

The nav bar and the commits page are too big I think. There ends up being a lot of space wasted. The commits page especially so. 5 commits should easily fit on a page. There are also two date information fields. One listing how many days ago the commit occurred and the other indicating what date the commit occurred on.

Thank you for the design feedback. I take ux/ui feedback very seriously. I have passed this onto our designer

Re: Banyan, the "GitHub of Science", is now in public beta

#53
post #34

Earlier quoted context omitted.

It is one reason. But e.g. in my field (theoretical physics) I am not afraid of theft (well, if someone is smart enough to understand and polish a half-written paper, then (s)he can write much better stuff) but of things that "as of now makes sense only to me" or "there are half-written" (e.g. in some places I changed indices i to i+1, but not in all, making it both frustrating and useless to read) or may simply be f…

Why a time limit? Why not a "publish" button that flips it to public? (And maybe submits it to arXiv at the same time, optionally.)

Integration with arXiv (i.e. "sent to arXiv" or "get source from arXiv") would be great. And yes, just a button "publish" would be convenient.

Re: Banyan, the "GitHub of Science", is now in public beta

#54
Clicking on either screenshot in the blog post takes me to a new page with a smaller version of the screenshot (http://blog.banyan.co/banyan-is-now-in-public-beta/dashboard...). Then I have to click the image again to see: http://blog.banyan.co/wp-content/uploads/2013/04/Dashboard-B...

Wouldnt a better interaction be to display a larger screenshot on the first click? Thats what I would expect?

Re: Banyan, the "GitHub of Science", is now in public beta

#55

Clicking on either screenshot in the blog post takes me to a new page with a smaller version of the screenshot ( http://blog.banyan.co/banyan-is-now-in-public-beta/dashboard... ). Then I have to click the image again to see: http://blog.banyan.co/wp-content/uploads/2013/04/Dashboard-B... Wouldnt a better interaction be to display a larger screenshot on the first click? Thats what I would expect?

Yes it should! Sorry about that. Just fixed it for you if check it now!

Re: Banyan, the "GitHub of Science", is now in public beta

#56
post #55

Clicking on either screenshot in the blog post takes me to a new page with a smaller version of the screenshot ( http://blog.banyan.co/banyan-is-now-in-public-beta/dashboard... ). Then I have to click the image again to see: http://blog.banyan.co/wp-content/uploads/2013/04/Dashboard-B... Wouldnt a better interaction be to display a larger screenshot on the first click? Thats what I would expect?

Yes it should! Sorry about that. Just fixed it for you if check it now!

Cool. Thanks.

Re: Banyan, the "GitHub of Science", is now in public beta

#57
post #45

Great to see another product in this space ( https://www.scigit.com/ launched not too long ago). As far as writing papers, my old-fashioned P.I. will probably never budge from Microsoft Word, so Google Docs is the best solution at the moment. The fact that they have "Google Scholar" integration for inserting citations into the editor makes it pretty much a no brainer for writing a draft.

Yikes! What field are you in? For most STEM folks, TeX seems to be pretty standard. I'd really love to see a collaborative TeX editor (web based?). Better yet... a collaborative emacs!

Re: Banyan, the "GitHub of Science", is now in public beta

#58
post #34

Earlier quoted context omitted.

It is one reason. But e.g. in my field (theoretical physics) I am not afraid of theft (well, if someone is smart enough to understand and polish a half-written paper, then (s)he can write much better stuff) but of things that "as of now makes sense only to me" or "there are half-written" (e.g. in some places I changed indices i to i+1, but not in all, making it both frustrating and useless to read) or may simply be f…

Why a time limit? Why not a "publish" button that flips it to public? (And maybe submits it to arXiv at the same time, optionally.)

That's true. A "publish" button makes more sense!

Re: Banyan, the "GitHub of Science", is now in public beta

#60
post #57
post #45

Great to see another product in this space ( https://www.scigit.com/ launched not too long ago). As far as writing papers, my old-fashioned P.I. will probably never budge from Microsoft Word, so Google Docs is the best solution at the moment. The fact that they have "Google Scholar" integration for inserting citations into the editor makes it pretty much a no brainer for writing a draft.

Yikes! What field are you in? For most STEM folks, TeX seems to be pretty standard. I'd really love to see a collaborative TeX editor (web based?). Better yet... a collaborative emacs!

TeX is what we are supporting currently, and should be launching shortly. If you drop me an email at toni (at) banyan.co, I will get you beta access in the next few days to our git powered, collaborative latex editor.
Post reply on HN