Vinnl
commented
5 years ago The Do-A-Thon did not generate that much interest; nevertheless, the project has been continuing apace. Here's a small update; if you're reading this in the future, see https://plaudit.pub for the current project status.
First of all, there is a logo now! This was kindly contributed by a designer from eLife. It can be admired at the project website.
There is also now a high-fidelity mock-up of what Plaudit will look like, that is ready for user testing. Work on the implementation is progressing nicely, and we will be launching the first integrations at the start of 2019.
We are still looking for more potential integrators, so if you host research or other academic outputs, let us know! General feedback and ideas are also always welcome. Ping @Flockademic on Twitter, or send an email to Plaudit@Flockademic.com.
Confused? New to Github? Visit the GitHub help page on our site for more information!
[//]: # "======================= Even if you know Github well, we suggest you read this. Anything between these lines you can leave or delete, as they won't display anyway when you post (you can check this via Preview changes). They're here to help you complete issues quickly and in a way that will help other participants. If you're posting a new project, or challenge. We suggest you fill out the Google Forms first. ============================"
At a glance
[//]: # "======================= Please paste the metadata you received after submitting your project or challenge in your Google Form exactly as we sent it to you. You can delete what's there now, it's just there ============================"
Description
[//]: # "======================= Insert a paragraph providing more context for your project or challenge focuses on. For project leads, this is a good place to give some broader context about your project—beyond the scope of the do-a-thon. If you're posting a challenge, this is a good chance to say how the problem arise or why it feels relevant to you. ============================"
The goal of Plaudit is to alleviate the pressure to publish in "high impact" but often paywalled and/or costly journals. It does so by allowing researchers to receive recognition for their work regardless of where it is published, in the form of recognition by peers through public endorsements. By integrating with open access journals and preprint servers, those endorsements are ephemeral to the research they endorse, and can help potential readers to identify interesting research even before it is published in a journal.
What are we working on during the do-a-thon? What kinds of support do we need?
[//]: # "======================= For those leading projects, please give some more information about what type of support you are specifically looking to get done during the do-a-thon day. Note: Challenge leads will not need to fill out this section and can remove it. ============================"
We are currently working on developing and testing an initial prototype, which should be ready in February 2019. However, early feedback is crucial! During the Do-A-Thon, we would like to develop a mock-up of what Plaudit could look like when integrated with different preprint servers, receive feedback from potential users, and gather statements of interest from potential integrators.
Plaudit is also in need of a logo! If you are a designer and would like to try your hand at this, that would be much appreciated. Do note that we can only use it if it is released under an open license, and if source files are made available. The colour scheme we are currently using is: #E5703B, #88A39A, #704E5C and white.
How can others contribute?
[//]: # "======================= Please say what the best way to contribute to the project or challenge is, sometimes that will just be 'lets discuss here' or 'Ive started a Google doc'. If you are a challenge lead, give some context on what design thinking tools you will be using, and how other folks can update their ideas onto the thread. If you are a project lead, and you already have clear ways people can contribute it might be worth linking to them here. Language: If your project is regionally based in a non-English-speaking region, clarify here what language you and contributors will primarily be communicating in. If you're leading a project or challenge participating remotely: Use this space to let people know that this is a remote project and that you are not 'in the room' in Berlin. Let other participants know what the best way to get in touch with you, where the work will happen, and where any updates or outputs will go. If you are at the in-person meeting in Berlin: Be as inclusive as possible to those outside the room. Use this space to give clear instructions to those participating in the do-a-thon remotely on how they can keep up to date and contribute. ============================" This is a remote project. Communication during the Do-A-Thon will happen on the Gitter chat (you can sign in with your GitHub account). If you're interested in contributing or just want to follow along, introduce yourself there, or leave a comment here :)
[//]: # "======================= You're ready to post!!! After posting your issue, the real work begins. Next, you might want to: Tweet a link to this issue with #opencon so others can join in Make another issue to involve people in your work - remember to use your metadata Come back from time to time and update the community on your project. You'll get an email update whenever someone interacts with your issue. ============================"
This post is part of the OpenCon Do-A-Thon. Not sure what's going on? Head here.