FORCE2018 Presentation: Revolutionizing scholarly writing with Manubot

in #science6 years ago


Last month, I traveled to Montreal for the FORCE2018 conference on advancing scholarly communication. This is a fantastic conference that focuses on innovations and practices to improve scientific publishing through greater openness and adoption of technology.

I presented on Manubot, which is a tool I help develop to enable writing scholarly manuscripts using git and GitHub. Manubot is an open source tool that aims to make writing more transparent, open, automated, and decentralized. Learn more at https://manubot.org.

Without further ado, here's the presentation recording on YouTube recorded and posted by the conference:

I'd like to thank the conference for recording my talk and releasing it under a Creative Commons Attribution license, such that I can share or remix it (and so can you) on sites like @dtube. I downloaded the video from YouTube using a great Python utility called youtube-dl. I'm released this DTube upload and my encapsulated presentation under a CC BY 4.0 License.

For a bit more info, here is the abstract for the presentation:

Manubot is a system for writing scholarly documents on GitHub. It aims to transform publishing to be transparent & reproducible, immediate & permissionless, versioned & automated, collaborative & open, linked & provenanced, decentralized & hackable, interactive & annotated, and free of charge. Manubot accomplishes these goals by applying the workflow from open source software to academic writing. This talk will introduce Manubot and its features. Compared to other methods for writing scholarly documents, Manubot is designed for more technical users as well as infrastructure providers. However, we hope many of Manubot's innovations — such as citation-by-identifier and end-to-end reproducibility — will be adopted more broadly. Hence, this talk should engage all conference participants by foreshadowing a future of publishing towards which we strive!

Finally, the slides are online here and archived at Zenodo. P.S. if you've read this far, you might also be interested in my previous post: How I used the Manubot to reproduce the Bitcoin Whitepaper.


▶️ DTube
▶️ IPFS
Sort:  

Great presentation Dan! You look very comfortable and natural in front of the camera and the audience :) You handled the subsequent questions with ease too. Manubot looks like an awesome project, congratulation!

Nice presentation! Question: If I already have one manuscript written in Manubot and want to create a second one, do I have to reconfigure from manubot-rootstock to set up continuous integration? Can't I just clone the first manuscript and change the content files?

Also, the link to your post has an interesting, unconventional tail https://busy.org/@dhimmel/opdk4gax. Is this new?

If I already have one manuscript written in Manubot and want to create a second one, do I have to reconfigure from manubot-rootstock to set up continuous integration? Can't I just clone the first manuscript and change the content files?

Each new manuscript should clone manubot-rootstock, rather than existing manuscripts with added content. Hopefully, the setup process will be a bit easier since you already have the git and Travis gem dependencies configured.

Also, the link to your post has an interesting, unconventional tail

I posted this using @dtube, which assigns short slugs rather than slugs based off the title. If we look at the raw transaction, we see the permlink field is set to opdk4gax. I actually wish frontends would let you set your own permalink.

Also, I like the Manubot's self recursion. Of course the manuscript that describes Manubot is written with Manubot.

Of course the manuscript that describes Manubot is written with Manubot.

Indeed! And of course! This manuscript is available at https://greenelab.github.io/meta-review/.

Here's the cover slide (i.e. DTube snap) I used for the video:

manubot-slides-cover.png

Hi @dhimmel, you have received an upvote from trang. I'm the Vietnamese Community bot developed by witness @quochuy and powered by community SP delegations.

Congratulations @dhimmel! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :

You got more than 700 replies. Your next target is to reach 800 replies.

Click here to view your Board of Honor
If you no longer want to receive notifications, reply to this comment with the word STOP

Support SteemitBoard's project! Vote for its witness and get one more award!

Hi, @dhimmel!

You just got a 17.78% upvote from SteemPlus!
To get higher upvotes, earn more SteemPlus Points (SPP). On your Steemit wallet, check your SPP balance and click on "How to earn SPP?" to find out all the ways to earn.
If you're not using SteemPlus yet, please check our last posts in here to see the many ways in which SteemPlus can improve your Steem experience on Steemit and Busy.





This post has been voted on by the SteemSTEM curation team and voting trail in collaboration with @curie.

If you appreciate the work we are doing then consider voting both projects for witness by selecting stem.witness and curie!

For additional information please join us on the SteemSTEM discord and to get to know the rest of the community!

!

Hey @eduards, can you explain the purpose of this comment on the subsequent upvotes? I do not like when people post unrelated comments on my posts.

Ned Scott is a shareholder. Today Ned Scott received 3 flags !!!
https://steemit.com/steemit/@ned/third-test-livestream-steemit-update

Great post! You've earned a 33.33% upvote from @dolphinbot
Join the DolphinBot Team for Daily Payouts in Steem! Click here: http://bit.ly/dolphinbot

This post has received a $15.77 % upvote from @siditech thanks to: @eduards.
Here's a banana! banana-small.png

You got a 15.15% upvote from @votejar courtesy of @eduards!