Wax Show ‘n’ Tell
Hindawi Limited & Coko Announce Partnership
Coko & eLife partner on first PubSweet fueled journals submission & peer-review platform
Seeding a New Ecosystem: open infrastructure
Take Editoria for a spin
Making decisions in a small team and keeping it fun
A look at the future of journals with xpub
Editoria 1.1: Meet the Automagic Book Builder
A sneak peak at what’s next for PubSweet
Travel the long and winding road to PubSweet
Ink 1.0 is here!
Baby steps to user-centric open source development
Why we’re all in open source now
Getting Started with Coko
Editoria 1.0 preview
Preprints won’t just publish themselves: Why we need centralized services for preprints
INK – the file conversion engine
How we’re building the ‘mountain chalet’ of complex conversions
Sowing the seeds for change in scholarly publishing
Open Source Alliance for Open Science
Editoria Newsletter Out Now!
INK client upgrade
All About INK (explained with cake)
Track Changes (Request for Comments)
Book on Open Source Product Development Method Released!
Italics, Buenos Aires and Coko?
Editoria Update
Where we are with File Conversion
A Typescript for the Web
Coko Celebrates Year One
Editoria – Scholarly Monograph Platform
Adam Hyde’s Blog
Introducing Christos
Introducing Yannis
New PubSweet release
Attribution in Open Source Projects
Open Source for Open Access
Reimagining Preprints: a new generation of early sharing
Introducing Stencila and Nokome Bentley
Reimagining Publishing
Introducing Charlie
PubSweet 1.0 “Science Blogger” alpha 2
PubSweet 1.0 “Science Blogger” alpha, INK 1.0 alpha RELEASES!!!
Collaborative Product Development
Publishing for reproducibility: collaborative input and networked output
Substance Consortium
UCP & CDL Announcement
Release 0.2.0 is here!
CKF receives funding from the Gordon and Betty Moore Foundation to transform research communication
Technology Slows Down Science
[tech post] CSS and Drop Caps
Vote for the pubsweet logo!
Introducing Substance
Digging Collaboration and Cooperation: Code for a New Era
Coko 2015
PubSweet 0.1 Release
Coko Resources
Making science writing smarter
What I Have Learned About Building Community
Introducing the Tech Team
Knowledge and Communication
PKP and CKF Strategic Alliance
CKF Launches
July 21, 2017

A sneak peak at what’s next for PubSweet

Over the course of two days in San Francisco, about 20 of us put our heads together  to talk about upcoming features in PubSweet 2.0, Coko’s platform-building toolkit. (If you want to get up to speed on the 1.0 release, more on that here.)

The first day covered PubSweet 1.0. Jure Triglav, lead developer for PubSweet started by running through where PubSweet is now, we also looked in detail at Editoria and xpub the book and journal platforms constructed from the PubSweet ecosystem.

Editoria has been released as a version 1.0 and xPub is in early development so this was a great time to get input from journal publishers who can shape how xPub will meet their needs for manuscript submission, peer review and article production as well as back-end functions in conversion and enrichment. 

On day two, we split into two groups: one to look at the PubSweet 2.0 request for comments and the other to think through some use cases.  The RFC process was extremely interesting and useful. We slimmed down and prioritized the 2.0 features and made some enhancements.

The final list is as follows:
1.0 beta
  • Add a missing test for the production pubsweet-cli
  • Write a getting started guide for component development
  • Authorization support for filtering
  • Replace bespoke ORM Code
  • Implement GraphQL
  • Simplify Project Structure (if necessary) (waiting for code review)
  • Double check terminal colors
  • Replace bespoke CLI code
  • Extend CLI
    • Automatically write routes based on added/removed components
    • One-line publishing platform installs, e.g. “pubsweet install editoria” or “pubsweet install xpub-journal”
    • Process management (daemonize, kill, ps)
      • “pubsweet updated”
      • “pubsweet upgrade”
      • “pubsweet backup & pubsweet restore”

2.0 – Remove REST endpoints

Towards the end of the meeting, the group broke down several common journal components and worked out requirements for them. We covered everything from submission to configurable HTML-first workflows.  

A diverse set of journal publishers were represented and, interestingly, were able to design several important common components. We’ll begin building these immediately!

We also talked about what being part of an open source community means in terms of business models and sustainability, the need for new types of service providers to step up and how our relationship to technology is changing in the publishing industry.  

Next up: we’ll continue to build out components for a journal and preprint production platform, xPub. Because of PubSweet’s flexible content model, xPub is suitable for other forms of data and content, too.

We’ll be expanding our community to gather more input, so get or stay in touch!