Comments (9)
One example is F1000: http://f1000research.com/for-authors/article-guidelines/software-tool-articles
from meetings.
@npch has a list that he keeps of some journals that publish software paper, though I don't know if it is categorized.
from meetings.
@danielskatz Great, though I don't have a meaning for the phrase 'Developing a categorization'. Do you mean an annotated / organized list?
from meetings.
I mostly meant organized, though annotated might also be useful
from meetings.
Not sure if you want to begin such a list here, but here's one for computational physics and physical chemistry: Computer Physics Communications
from meetings.
People here are probably aware of this one already, but the SSI has a list with some categorization: http://www.software.ac.uk/resources/guides/which-journals-should-i-publish-my-software
(edit: sorry @danielskatz, I just realized that this list is probably the one you were referring to earlier)
from meetings.
Technically it hasn't actually launched yet, but Research Ideas and Outcomes will publish all research output, including software and data
from meetings.
Regarding successful alternate publishing mechanisms, I can say that in my field one successful example is Cantera.
Originally it was hosted on Google Code but more recently migrated to GitHub, and although it hasn't ever been published in the traditional sense (i.e., there isn't a journal publication that documented its release) the combustion/chemical kinetics community has really started to embrace it in recent years—based on the frequency I see it mentioned in papers, at least. My guess is that its success thus far is due to two main reasons:
- The combination of hosting openly on popular repositories (Google Code -> GitHub) and a supportive developer and user community forum, and
- A vacuum in terms of available free/open-source software that provided similar functionality. Most people used (and many still do) Chemkin, which was originally developed by Sandia and shared openly, but now is sold commercially.
from meetings.
You might find this effort of interest: https://github.com/arceli/charter
from meetings.
Related Issues (20)
- Development: Determining principles for engineering design for sustainable software HOT 1
- Development: Create guidance giving examples of specific metrics for the success of scientific software HOT 13
- Training: Writing a white paper on training for developing sustainable software, and coordinating multiple ongoing training-oriented projects HOT 7
- Training: Developing curriculum for software sustainability, and ideas about where such curriculum would be presented, such as a summer training institute HOT 1
- Credit: Hacking the credit and citation ecosystem (making it work, or work better, for software) HOT 22
- Credit: Developing a taxonomy of contributorship/guidelines for including software contributions in tenure review
- Credit: Documenting case studies of receiving credit for software contributions
- Credit: Developing a system of awards and recognitions to encourage sustainable software
- Publishing: Determining what journals that publish software paper should provide to their reviewers HOT 3
- Reproducibility and testing: Building a toolkit that could allow conference organizers to easily add a reproducibility track
- Reproducibility and testing: Documenting best practices for code testing and code review HOT 1
- Documentation: Develop landing pages that enable the community to easily find up-to-date information on a WSSSPE topic HOT 8
- Executable Papers/Non-Traditional Publishing
- Development: Principles of engineering design for sustainable software
- WSSSPE3 report: citation vs. footnote for links? HOT 5
- Community: Develop guidance on how to build a sustainable community around science software HOT 3
- Activities at WSSSPE4 HOT 1
- WSSSPE4 report: purpose of the Code of Conduct section HOT 7
- WSSSPE4 report: Verifying best practices & metrics for sustainable research software HOT 9
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from meetings.