#softwarereview — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #softwarereview, aggregated by home.social.
-
7/8 📦 Looking to submit your package?
If you have an R package that you believe should undergo peer review, submit it to our open peer review system: https://github.com/ropensci/software-review
Let’s ensure it meets the highest standards of quality and usability! #PeerReviewWeek #OpenSource #SoftwareReview
-
3/8 🛠️ What makes rOpenSci’s peer review special?
Our process goes beyond traditional academic peer review. It focuses on code quality, documentation, and community standards: https://devguide.ropensci.org/
It’s a collaborative effort, with authors, reviewers and editors growing through the process. #SoftwareReview #OpenScience
-
CW: Long, Open peer review, reviewing as authorship
@neuralreckoning @adredish @WorldImagining @mschottdorf @brembs
butting in late on this discussion (thanks all for your thoughts) and as usual I want to inject a little @joss model into the conversation since it's a really good, live, successful experiment in a lot of these ideas.In my experience, none of the "let's let readers provide comment/review if they want" has worked because it's really rare that people want to write the deep-dive that a good review requires
I get this objection, and so I think opportunistic review is just one of many parts of a more functional review system. This should just be trivially possible for any artifact of scholarly work, but it does require shifting what we think 'scholarly publishing' bodies can be. That would require not only moderation of a peer review process, but moderation of a community and place of digital archival-grade discussion - that's more or less what neuromatch.social is an experiment in making. My own experiences with opportunistic review have been really great, with lots of good commentary from domain experts, both supportive and critical, that directly accompanies the work and makes it richer for experts and nonexperts alike.
Really love what @neuralreckoning is saying here:
Here's my suggestion: give authors an easy way to recognise valuable peer reviews that improved a paper by giving them the option to add them as authors.
and think this is another place where JOSS really works. Scientific experiments are different than software in a lot of ways, obviously, but one thing JOSS shows us about structured post-pub peer review is how in addition to raising issues, reviewers can do pull requests and propose contributions to the work. in software this results in automatic credit - you are the author of the commits that were merged - that is strictly positive for both parties: there is no limit on number of contributors, it's super clear what that person did, etc. A really healthy model of review would be one where reviewers could also contribute to the work and were seen as co-contributors.
Experiments have much longer timescales, material restrictions, etc. for making contributions like that, but one could also see that as being part of author responsibility, to make their methods portable/reproducible enough that they could eg. loan some equipment to another lab so they could collaborate and contribute to an experiment. that happens already as collaborations, so you could see how this would be relatively hazy barrier between "peer review" and "working in public."
when i'm reviewing software, I have actually a lot of motivation because i learn a lot from it, and that would be another part - if review was structured in a way to improve the work, then one could imagine a first pass at a review being "methods sharing" - not just evaluating the text, but collaboratively trying to figure out how to make it so the reviewers-as-collaborators could actually recreate the experiment and use that to improve the methods section.
because it's public, i have additional reputational motivation to review, and disincentive to be toxic and rude. Demonstrating a track record of thoughtful feedback and cooperative behavior is super good for being able to look for work - win/win.
The question of legibility to an outside audience is often a matter of process and interface design to me. A marker of "having gone through peer review process x" is meaningful in a way that "being published in venue y" is not, because in the latter case it's an existential question for the work - something can only be in one
yand it must be in someyto exist. Going through a voluntary peer review process with a clear and transparent standards process (alongside the complete artifact of the review) is legible both to "outsiders" (assuming the process has some legible documentation, which is not necessarily a given) and insiders. Labels and open processes are v much not in conflict, but when labels are venues they are just qualitatively different.so all these approaches are complementary to me - opportunistic peer review for everything against a background of collective moderation, structured peer review as a constructive process of trying to get a work to meet some standard with reviewers as both cooperators and adversaries in different roles, but untied to the mere existence of a work.
-
Habt ihr oder euer Team Bedenken, dass bei Software-Reviews möglicherweise Risiken oder auch Schwächen aufgedeckt werden könnten? @StefanZoerner verrät im im dritten Teil unseres 🕸🎙️ LASR-Interviews, warum es genau darum geht. Und wie es mit dem Blick auf positive Ergebnisse & dem richtigen Umgang mit Fehlern gelingt, Teams für die Durchführung eines #Reviews zu motivieren:
🎥 https://www.youtube.com/watch?v=WYglctwWSkk&list=PLnx7kHDr7i_2Jb7IyeEUkeT1Kore7U1L2&index=3
ℹ️ Mehr zu #LASR: https://www.embarc.de/themen/lasr-reviews/
-
Habt ihr oder euer Team Bedenken, dass bei Software-Reviews möglicherweise Risiken oder auch Schwächen aufgedeckt werden könnten? @StefanZoerner verrät im im dritten Teil unseres 🕸🎙️ LASR-Interviews, warum es genau darum geht. Und wie es mit dem Blick auf positive Ergebnisse & dem richtigen Umgang mit Fehlern gelingt, Teams für die Durchführung eines #Reviews zu motivieren:
🎥 https://www.youtube.com/watch?v=WYglctwWSkk&list=PLnx7kHDr7i_2Jb7IyeEUkeT1Kore7U1L2&index=3
ℹ️ Mehr zu #LASR: https://www.embarc.de/themen/lasr-reviews/
-
Habt ihr oder euer Team Bedenken, dass bei Software-Reviews möglicherweise Risiken oder auch Schwächen aufgedeckt werden könnten? @StefanZoerner verrät im im dritten Teil unseres 🕸🎙️ LASR-Interviews, warum es genau darum geht. Und wie es mit dem Blick auf positive Ergebnisse & dem richtigen Umgang mit Fehlern gelingt, Teams für die Durchführung eines #Reviews zu motivieren:
🎥 https://www.youtube.com/watch?v=WYglctwWSkk&list=PLnx7kHDr7i_2Jb7IyeEUkeT1Kore7U1L2&index=3
ℹ️ Mehr zu #LASR: https://www.embarc.de/themen/lasr-reviews/
-
Habt ihr oder euer Team Bedenken, dass bei Software-Reviews möglicherweise Risiken oder auch Schwächen aufgedeckt werden könnten? @StefanZoerner verrät im im dritten Teil unseres 🕸🎙️ LASR-Interviews, warum es genau darum geht. Und wie es mit dem Blick auf positive Ergebnisse & dem richtigen Umgang mit Fehlern gelingt, Teams für die Durchführung eines #Reviews zu motivieren:
🎥 https://www.youtube.com/watch?v=WYglctwWSkk&list=PLnx7kHDr7i_2Jb7IyeEUkeT1Kore7U1L2&index=3
ℹ️ Mehr zu #LASR: https://www.embarc.de/themen/lasr-reviews/
-
Habt ihr oder euer Team Bedenken, dass bei Software-Reviews möglicherweise Risiken oder auch Schwächen aufgedeckt werden könnten? @StefanZoerner verrät im im dritten Teil unseres 🕸🎙️ LASR-Interviews, warum es genau darum geht. Und wie es mit dem Blick auf positive Ergebnisse & dem richtigen Umgang mit Fehlern gelingt, Teams für die Durchführung eines #Reviews zu motivieren:
🎥 https://www.youtube.com/watch?v=WYglctwWSkk&list=PLnx7kHDr7i_2Jb7IyeEUkeT1Kore7U1L2&index=3
ℹ️ Mehr zu #LASR: https://www.embarc.de/themen/lasr-reviews/
-
Call for @joss reviewers:
EdgeVPN.io
repo: https://github.com/EdgeVPNio/evio
pre-review: https://github.com/openjournals/joss-reviews/issues/6355
language: PythonDescription:
EdgeVPN.io is an evolution of the IP-over-P2P (IPOP) project. IPOP started as an IP-based peer-to-peer overlay targeting personal devices, and over time the architecture evolved to adopt various standards, support centralized user/group management, and incorporate software-defined networking, culminating in the current architecture, tailored for research and development in nascent edge computing applications.
...
EdgeVPNio is a research project to build networking for the fog, spanning the network continuum from the cloud to its edge. It builds networking cyber-infrastructure which supports emerging IoT era applications.Looks like this one might be a bit of fun for #p2p people, or i suppose #DistributedSystems people generally. No prior experience reviewing for JOSS is required, experience with Python is required, and some experience with the topic area is preferred. Don't be shy! If you've never done open review before, JOSS is a great place to start. It's a really good way to learn by teaching (or learn by reading!) in a collaborative context. You can reply here or on the pre-review issue to volunteer :)
edit: would love to have some infosec people on this one! even and especially if you are not in academia :)
-
Still looking for a second reviewer for @pyOpenSci
Package: automata
review: https://github.com/pyOpenSci/software-submission/issues/152
repo: https://github.com/caleb531/automata
description: A Python library for simulating finite automata, pushdown automata, and Turing machines.Open reviews are a great way to learn by teaching, see what other people are up to, and make software development a valued and creditable part of academic work. Anyone with familiarity with Python is welcome as a reviewer, experience in the topic domain is a bonus but not required. DM me or reply on the above issue, it's fun, i promise! :)
edit: reviewer found! thank you @iris <3
#PeerReview #SoftwareReview #OpenReview #Python #Automata #TuringMachines #CellularAutomata
-
Still looking for a second reviewer for @pyOpenSci
Package: automata
review: https://github.com/pyOpenSci/software-submission/issues/152
repo: https://github.com/caleb531/automata
description: A Python library for simulating finite automata, pushdown automata, and Turing machines.Open reviews are a great way to learn by teaching, see what other people are up to, and make software development a valued and creditable part of academic work. Anyone with familiarity with Python is welcome as a reviewer, experience in the topic domain is a bonus but not required. DM me or reply on the above issue, it's fun, i promise! :)
edit: reviewer found! thank you @iris <3
#PeerReview #SoftwareReview #OpenReview #Python #Automata #TuringMachines #CellularAutomata
-
Still looking for a second reviewer for @pyOpenSci
Package: automata
review: https://github.com/pyOpenSci/software-submission/issues/152
repo: https://github.com/caleb531/automata
description: A Python library for simulating finite automata, pushdown automata, and Turing machines.Open reviews are a great way to learn by teaching, see what other people are up to, and make software development a valued and creditable part of academic work. Anyone with familiarity with Python is welcome as a reviewer, experience in the topic domain is a bonus but not required. DM me or reply on the above issue, it's fun, i promise! :)
edit: reviewer found! thank you @iris <3
#PeerReview #SoftwareReview #OpenReview #Python #Automata #TuringMachines #CellularAutomata
-
Still looking for a second reviewer for @pyOpenSci
Package: automata
review: https://github.com/pyOpenSci/software-submission/issues/152
repo: https://github.com/caleb531/automata
description: A Python library for simulating finite automata, pushdown automata, and Turing machines.Open reviews are a great way to learn by teaching, see what other people are up to, and make software development a valued and creditable part of academic work. Anyone with familiarity with Python is welcome as a reviewer, experience in the topic domain is a bonus but not required. DM me or reply on the above issue, it's fun, i promise! :)
edit: reviewer found! thank you @iris <3
#PeerReview #SoftwareReview #OpenReview #Python #Automata #TuringMachines #CellularAutomata
-
Still looking for a second reviewer for @pyOpenSci
Package: automata
review: https://github.com/pyOpenSci/software-submission/issues/152
repo: https://github.com/caleb531/automata
description: A Python library for simulating finite automata, pushdown automata, and Turing machines.Open reviews are a great way to learn by teaching, see what other people are up to, and make software development a valued and creditable part of academic work. Anyone with familiarity with Python is welcome as a reviewer, experience in the topic domain is a bonus but not required. DM me or reply on the above issue, it's fun, i promise! :)
edit: reviewer found! thank you @iris <3
#PeerReview #SoftwareReview #OpenReview #Python #Automata #TuringMachines #CellularAutomata
-
🧠🔖 In der druckfrischen Ausgabe 1️⃣2️⃣ unserer Architektur-Spicker geht es um leichtgewichtige Software-Reviews mit dem LASR-Ansatz.
🙌 Lernt auf 4 Seiten PDF, wie ihr mit #LASR Risiken in der Softwarelösung aufdeckt und technische Ideen absichert - im Entwicklungsteam oder notfalls auch allein, ohne viel Vorarbeit und mit Resultaten, die ihr früh teilen könnt:
➡️ 🔗 https://www.architektur-spicker.de#LASR #SoftwareReview #reviews #KompaktesWissen #ArchitekturSpicker #Spicker
-
Putting a call out for @pyOpenSci reviewers :)
Package:
automata- "A Python library for simulating finite automata, pushdown automata, and Turing machines."
https://github.com/pyOpenSci/software-submission/issues/152Looks like a good bit of fun (cellular automata are a recurring love of mine) - we would love to give people who haven't had a chance to review software a go here, but previous reviewers welcome too. You'll be taking on the role of a prospective user and colleague advising and trying to help make a package work as well as it can, reaching some minimum standard via checklist, raising issues and making suggestions as you read and run it.
More on the review process: https://www.pyopensci.org/software-peer-review/how-to/reviewer-guide.html
Reply here or DM me, (though my notifications are getting mauled rn so probably DM)
#Automata #CellularAutomata #TuringMachines #PyOpenSci #SoftwareReview #PeerReview
-
@taylorlorenz
We never had problems with AOL! /sarcasm
But seriously I worked with the developers of lots of software products. Before we would launch them I insisted we bring in a "normal" user & sometimes a former editor of a #SoftwareReview magazine.
They found lots of problems because the developers made assumptions the "everybody knows." But the new users did NOT know. I said
"The user can't read your mind"
This was before 1000's of app store reviews. A bad review in a pub was devastating -
Wanted to give some impressions on #Firefish (or #Calckey if you haven't noticed the rebrand). I'm new to the fediverse, and typically was not a consumer of Twitter, so these might be some "well duh" comments but here goes anyways.
1. One of the features that I really liked about Mastodon was the column layout. This is something I think a lot of Twitter users are probably used to. At first I thought Firefish did not have this support, but you actually can add columns using the + on the right!
2. The columns are highly customizable. I found the "flexible" setting to be the best option for feed-centric columns, but the fixed width for stuff like notifications.
3. WORKSPACES! This is an amazing feature. It's like how you can have different desktops in Mac OS or Linux (hell, maybe even Windows has that feature but I haven't used a Windows OS in a number of years now). Once I had my lists setup, I realized I can have workspace to show me the "typical" feeds list, but then one with my lists so I can just browse those on their own.
4. Speaking of lists, I was happy to find out that I can mute a particular account in my feed, but that does not affect it appearing on a list. The same goes for muted boosts from any user. Those show up in the list but not the feed. Great!
5. I've been using #RadiantApp (iOS) for Mastodon (which is amazing and I highly recommend it!) but it won't connect to my account here on Firefish unfortunately. One of the problems I was having with the progressive web app (PWA) version of Firefish was there didn't appear to be any way to get it to refresh the feed. Pulling down didn't work as expected. BUT Firefish has a way to fix this! You can add a refresh button to your navigation bar. Just go into the settings, go to navigation, then type "reload" in to the list wherever you want that button to appear (I added it to the very top). After you save there's a refresh button you can hit when you load the PWA.
6. Migration was simple. Export from Mastodon and import into Firefish. I suppose this is more of a Mastodon feature than Firefish one, but it works really well so I wanted to point that out.
A few suggestions I have if any Firefish devs happen across this post.
1. Would be nice to have window resizing save. I'd like the window that opens for things to stay the size I set them to last time. For example, the post composition window or when you click a post to see the comments.
2. One thing I didn't note above is that the customizations you make have to be done per browser. So if you add the refresh button to your navigation bar in your desktop browser, you also have to add it on your mobile browser for the PWA. This goes for themes and other settings as well. It would be nice if there were some way to save these preferences to the server for my account so I wouldn't have to recreate them per device. Of course, you'd probably need a way to override settings between devices if there are some that are incompatible on mobile vs desktop, or vice versa.
3. In relation to number 5 above, the name used to add an icon to the navigation bar and the text that the icon is labelled as do not match. The icon is labelled as "refresh" however the text to get it to appear it "reload." While this is a little thing, it would be nice if the nomenclature was consistent.
All in all, I've pretty much moved to Firefish as my permanent home now that I've kind of figured out (some of) the ins and outs. Looking forward to whatever comes next!
#Firefish #Calckey #FediverseTools #SoftwareReview -
If you are a happy OpenProject user and want to inspire others discover all the great features, help us spread the word and leave us a review on a platform of your choice. We've put them all together in one place. https://openproject.org/reviews/
#openproject #opensource #softwarereview
