Skip to content

Commit

Permalink
Remove Twitter
Browse files Browse the repository at this point in the history
  • Loading branch information
xuanxu committed Nov 20, 2024
1 parent 0b77db8 commit 230ac33
Show file tree
Hide file tree
Showing 6 changed files with 6 additions and 5 deletions.
1 change: 1 addition & 0 deletions app/helpers/application_helper.rb
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,7 @@ def scope_link_for_issue(github_issue)
def social_media_links
links = []
links << link_to("Twitter", "https://twitter.com/#{setting(:twitter)}", target: "_blank", title: "#{setting(:twitter)}").html_safe if setting(:twitter).present?
links << link_to("Bluesky", "https://bsky.app/profile/#{setting(:bluesky)}", target: "_blank", title: "#{setting(:bluesky)}").html_safe if setting(:bluesky).present?
links << link_to("Mastodon", setting(:mastodon_url), target: "_blank", rel: "me", title: "#{setting(:mastodon_url)}").html_safe if setting(:mastodon_url).present?
links
end
Expand Down
2 changes: 1 addition & 1 deletion app/views/home/about.html.erb
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@
<% unless social_media_links.empty? %>
<p>
You can also find <%= setting(:abbreviation) %> at
<%= social_media_links.join(" and ").html_safe %>
<%= social_media_links.to_sentence.html_safe %>
</p>
<% end %>
</div>
Expand Down
2 changes: 1 addition & 1 deletion config/settings-development.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ url: "http://0.0.0.0:3000"
editor_email: "[email protected]"
noreply_email: "[email protected]"
launch_date: "2016-05-05"
twitter: "@JOSS_TheOJ"
bluesky: "joss-openjournals.bsky.social"
mastodon_url: "https://fosstodon.org/@JOSS"
google_analytics: "UA-47852178-4"
github: "openjournals/joss"
Expand Down
2 changes: 1 addition & 1 deletion config/settings-production.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ url: "https://joss.theoj.org"
editor_email: "[email protected]"
noreply_email: "[email protected]"
launch_date: "2016-05-05"
twitter: "@JOSS_TheOJ"
bluesky: "joss-openjournals.bsky.social"
mastodon_url: "https://fosstodon.org/@JOSS"
google_analytics: "UA-47852178-4"
github: "openjournals/joss"
Expand Down
2 changes: 1 addition & 1 deletion config/settings-test.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ url: "http://joss.theoj.org"
editor_email: "[email protected]"
noreply_email: "[email protected]"
launch_date: "2016-05-05"
twitter: "@JOSS_TheOJ"
bluesky: "joss-openjournals.bsky.social"
mastodon_url: "https://fosstodon.org/@JOSS"
google_analytics: "UA-47852178-4"
github: "openjournals/joss"
Expand Down
2 changes: 1 addition & 1 deletion docs/editing.md
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,7 @@ Editors may also be invited to edit over email when an TEiC runs the command `@e

At this point, the handling editor's job is to identify reviewers who have sufficient expertise in the field of software and in the field of the submission. JOSS papers have to have a minimum of two reviewers per submission, except for papers that have previously been peer-reviewed via rOpenSci. In some cases, the editor also might want to formally add themselves as one of the reviewers. If the editor feels particularly unsure of the submission, a third (or fourth) reviewer can be recruited.

To recruit reviewers, the handling editor can mention them in the `PRE-REVIEW` issue with their GitHub handle, ping them on Twitter, or email them. After expressing initial interest, candidate reviewers may need a longer explanation via email. See sample reviewer invitation email, below.
To recruit reviewers, the handling editor can mention them in the `PRE-REVIEW` issue with their GitHub handle, ping them on social media, or email them. After expressing initial interest, candidate reviewers may need a longer explanation via email. See sample reviewer invitation email, below.

**Reviewer Considerations**

Expand Down

0 comments on commit 230ac33

Please sign in to comment.