This repository was archived by the owner on Jun 17, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathatom.xml
160 lines (153 loc) · 6.72 KB
/
atom.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>scite.github.io</title>
<link href="https://scirate.github.io/atom.xml" rel="self" />
<link href="https://scirate.github.io" />
<id>https://scirate.github.io/atom.xml</id>
<author>
<name>Scirate Team</name>
<email>[email protected]</email>
</author>
<updated>2018-10-06T00:00:00Z</updated>
<entry>
<title>How You Can Contribute to SciRate</title>
<link href="https://scirate.github.io/posts/2018-10-06-How-You-Can-Contribute-To-SciRate.html" />
<id>https://scirate.github.io/posts/2018-10-06-How-You-Can-Contribute-To-SciRate.html</id>
<published>2018-10-06T00:00:00Z</published>
<updated>2018-10-06T00:00:00Z</updated>
<summary type="html"><![CDATA[<div class="info">
Posted on October 6, 2018
by Noon van der Silk
</div>
<div>
<p>Since 2017, I’ve been managing and funding SciRate on my own. But SciRate hasn’t survived, since it’s inception <a href="https://dabacon.org/pontiff/?p=1418">2007</a>, through entirely the time and money of one person. Any community needs involvement from community members to thrive. It’s actually quite a great example of an open-source projcet that has changed hands several times over the years.</p>
</div>
<div>
<p>I’d now like to invite participation from you, the community, and outline a few ways in which you can become involved.</p>
</div>
<div>
<h2 id="milestone-feature-development">1. Milestone Feature Development</h2>
</div>
<div>
<p>The biggest feature on the roadmap is: integrating other services.</p>
</div>
<div>
<p>Here is my order of preference:</p>
</div>
<div>
<ul>
<li><div>
<a href="https://github.com/scirate/scirate/issues/205">ECC (scirate/github issue 205)</a>
</div></li>
<li><div>
<a href="https://github.com/scirate/scirate/issues/346">ChemRxiv (scirate/github issue 346)</a>
</div></li>
<li><div>
<a href="https://github.com/scirate/scirate/issues/206">Cryptology ePrint Archive (scirate/issue 206)</a>
</div></li>
<li><div>
<a href="https://github.com/scirate/scirate/issues/206">bioRxiv (scirate/issue 206)</a>
</div></li>
<li><div>
<a href="https://github.com/scirate/scirate/issues/206">PeerJ (scirate/issue 206)</a>
</div></li>
</ul>
</div>
<div>
<p>Presently, SciRate acts <em>only</em> as a front for the arXiv; but the dream was always to add more back-end services. The more such services that are added, the more useful SciRate will be as a service for paper discovery.</p>
</div>
<div>
<p>Luckily, the team that developed the present version of SciRate (mostly <a href="https://mispy.me/">Jaiden Mispy</a>) did an excellent job, and the database structure is essentially in place for this kind of integration to be done. The main task in any integration is working out how to bring in their paper feed into our database. The best place to look is <a href="https://github.com/scirate/scirate/blob/3225f14960024816f514fa3236738c644c92124f/lib/tasks/arxiv_paper_sync.rake">here</a> and <a href="https://github.com/mispy/arxivsync">here</a>.</p>
</div>
<div>
<p>I’d estimate about ~2 weeks of full-time work, for someone moderately experienced with Ruby to pull this off. If you’re keen to work on this, then get in touch with me and I can help guide you through it, but putting some more details in the relevant issues.</p>
</div>
<div>
<h2 id="bug-fixing-issue-reporting-feature-requests">2. Bug Fixing, Issue Reporting, Feature Requests</h2>
</div>
<div>
<p>There’s a bunch of minor things that can be worked on by people familiar with Ruby: <a href="https://github.com/scirate/scirate/issues">scirate issues on GitHub</a>.</p>
</div>
<div>
<p>I’ve been very-slowly attempting to highlight the easier tasks with the “help wanted” tag on GitHub: <a href="https://github.com/scirate/scirate/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22">github/scirate issues - “help wanted”</a>.</p>
</div>
<div>
<p>Contributing to fixing minor bugs in SciRate is actually how I first started my involvement in the site, way back when <a href="http://intractable.ca/bill/">Bill Rosgen</a> was managing it.</p>
</div>
<div>
<p>We’re also very happy to receive pull requests adding new features!</p>
</div>
<div>
<h2 id="community-leadership">3. Community Leadership</h2>
</div>
<div>
<p>SciRate has a small group of moderators, and I’m open to more people joining. If you’re interested, get in touch via the <a href="https://groups.google.com/forum/#!forum/scirate">mailing list</a>.</p>
</div>
<div>
<p>I’m also open to other community engagements, such as a slack channel, for more free-flowing conversations, or guest blogs, as mentioned in the previous post. If you have an interest in any of this, then get in touch.</p>
</div>
<div>
<p>Please also have a careful read of the (new!) <a href="https://scirate.com/conduct">Code of Conduct</a>.</p>
</div>
<div>
<h2 id="funding-and-sponsorship">4. Funding and Sponsorship</h2>
</div>
<div>
<p>As I mentioned, presently SciRate is funded entirely by me, with no academic or corporate backing. If you’re an institution or organisation and you’d like to:</p>
</div>
<div>
<ul>
<li><div>
Reach a large community of researchers (5000+, and growing by hundreds each month),
</div></li>
<li><div>
Support our open-science mission and Improve the way science is done,
</div></li>
</ul>
</div>
<div>
<p>Then please <a href="mailto:[email protected]">email me</a>; it’d be amazing to have your support!</p>
</div>
]]></summary>
</entry>
<entry>
<title>Welcome to the SciRate Blog!</title>
<link href="https://scirate.github.io/posts/2018-08-26-Welcome-To-The-Scirate-Blog.html" />
<id>https://scirate.github.io/posts/2018-08-26-Welcome-To-The-Scirate-Blog.html</id>
<published>2018-08-26T00:00:00Z</published>
<updated>2018-08-26T00:00:00Z</updated>
<summary type="html"><![CDATA[<div class="info">
Posted on August 26, 2018
by Noon van der Silk
</div>
<div>
<p>Welcome to the new official blog of <a href="https://scirate.com">SciRate</a>.</p>
</div>
<div>
<p>I’ve started this blog for a few purposes:</p>
</div>
<div>
<ol style="list-style-type: decimal">
<li><div>
Engagement with people that use SciRate,
</div></li>
<li><div>
Provide status updates,
</div></li>
<li><div>
Provide commentary on topics that are of interest to us,
</div></li>
<li><div>
Be a platform for people that want to contribute to the ecosystem.
</div></li>
</ol>
</div>
<div>
<p>I’d like to hear from you, the users of SciRate, for what you’d like to see here. You can reach me via <a href="mailto:[email protected]">email</a>. One idea I’d like to explore is guest blog-posts providing coverage of particular research areas.</p>
</div>
<div>
<p>Thanks!</p>
</div>
]]></summary>
</entry>
</feed>