From 2638e3a11479d2e54690d087ae74d8d3b3d28084 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jean-S=C3=A9bastien=20Caux?= <git@jscaux.org>
Date: Mon, 11 Mar 2024 18:05:45 +0100
Subject: [PATCH] Last tweak of POSI
---
scipost_django/scipost/templates/scipost/posi.html | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/scipost_django/scipost/templates/scipost/posi.html b/scipost_django/scipost/templates/scipost/posi.html
index 793bc7c24..713fc2d85 100644
--- a/scipost_django/scipost/templates/scipost/posi.html
+++ b/scipost_django/scipost/templates/scipost/posi.html
@@ -230,7 +230,7 @@
<strong class="p-2 bg-success bg-opacity-75">mostly implemented</strong>
</p>
<p>
- This is mostly but not entirely relevant for SciPost. In view of the fact that SciPost's mission has broad and ambitious objectives for reforming academic publishing, we cannot say that we do not lobby to make sure that our initiative survives. On the other hand, it is correct to say that SciPost does not lobby <em>to cement its own position of narrow self-interest</em>, since our interventions with higher instances typically advocate for changes which would benefit the whole community of similarly-spirited academic publishers.
+ This is mostly but not entirely relevant for SciPost. In view of the fact that SciPost's mission has broad and ambitious objectives for reforming academic publishing, we cannot say that we do not lobby to make sure that our initiative survives. On the other hand, it is correct to say that SciPost does not lobby <em>to cement its own position of narrow self-interest</em>, since our interventions with higher instances typically advocate for changes which would benefit similarly-spirited academic publishers. Going further, we will only lobby for changes which are in the interest of the entire research community, to foster access to bleeding-edge research, and providing equal publishing opportunities for all.
</p>
</div>
</div>
@@ -244,8 +244,7 @@
<strong class="p-2 bg-success bg-opacity-50">partly implemented</strong>
</p>
<p>
- SciPost does not have a publicly-visible plan for winding down its operations (our priority is to survive!).
- That said, the most important output of our activities, namely all the publications, would remain accessible beyond SciPost's demise through a <a href="https://clockss.org/">CLOCKSS</a> trigger event. We also have a plan to provide all source material for all our publications through our <a href="https://git.scipost.org">in-house repository server</a>, providing an added layer of redundancy to all the corpus created by our activities.
+ SciPost does not have a publicly-visible plan for winding down its operations (our priority is to survive!). That said, the most important output of our activities, namely all the publications, would remain accessible beyond SciPost's demise through a <a href="https://clockss.org/">CLOCKSS</a> trigger event. We also have a plan to provide all source material for all our publications through our <a href="https://git.scipost.org">in-house repository server</a>, providing an added layer of redundancy to all the corpus created by our activities.
</p>
<h5>Further implementation steps</h5>
<ul>
@@ -306,11 +305,11 @@
<strong class="text-white p-2 bg-danger bg-opacity-100">urgency: high</strong>
</p>
<p>
- We would love to dream of a day where we can count on sufficient support not only to cover our immediate costs, but also to build a bit of a cushion to secure our future and perhaps even turn some of our further development ideas and dreams into reality. In the current APC-pipelining, Diamond-ignoring financial context however, we must be realistic and remain rather pessimistic about achieving this. Once again, although we do have a workable model up for grabs, its fragmented adoption (and accompanying high levels of free-riding on our services) makes the idea of a "surplus" a pipe dream at this stage, and it is true that SciPost suffers a certain degree of stagnation.
+ We would love to dream of a day where we can count on sufficient support not only to cover our immediate costs, but also to build a bit of a cushion to secure our future and perhaps even turn some of our further development ideas and dreams into reality. In the current APC-pipelining, Diamond-ignoring financial context however, we must be realistic and realize that much work is to be done before achieving this (though our business model makes this entirely realizable).
</p>
<h5>Further implementation steps</h5>
<ul>
- <li>beg for sustainability (with surplus!!) (see our <a href="https://scipost.org/news/newsitem/126/">Sustain Our Services campaign</a>)</li>
+ <li>strive for sustainability (with surplus!!) (see our <a href="https://scipost.org/news/newsitem/126/">Sustain Our Services campaign</a>)</li>
</ul>
</div>
</div>
@@ -329,7 +328,7 @@
</p>
<h5>Further implementation steps</h5>
<ul>
- <li>supplicate for sustainability (with reserves!!) (see our <a href="https://scipost.org/news/newsitem/126/">Sustain Our Services campaign</a>)</li>
+ <li>strive for sustainability (with reserves!!) (see our <a href="https://scipost.org/news/newsitem/126/">Sustain Our Services campaign</a>)</li>
</ul>
</div>
</div>
--
GitLab