forked from workflowscommunity/workflowscommunity.github.io
-
Notifications
You must be signed in to change notification settings - Fork 0
/
contribute_events.html
59 lines (56 loc) · 3.09 KB
/
contribute_events.html
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
---
layout: page
title: "Contribute: Events"
permalink: /events/add
---
<div class="row justify-content-center mb-5 pb-5">
<div class="col-md-7 text-center heading-section ftco-animate mb-5">
<span class="subheading">Register a conference, workshop, meeting, etc. relevant to the workflows community</span>
<h2 class="mb-4">How to Publicize an Event</h2>
<a href="/events" class="btn btn-primary mt-3 py-3 px-5">All Events</a>
</div>
<div class="col-md-12">
<p>
The Workflows Community Initiative (WCI) provides a curated list of <strong>workflow-related</strong>
community events suitable for workflow researchers, developers, and users. We invite all members of
the workflows community to publicize their events through this list.
</p>
<h3 class="mt-5">Adding a Workflow-Related Event</h3>
<p>
To add an event, you only need to add the framework information into an YAML file hosted as part of the <a
href="https://github.com/workflowscommunity/workflowscommunity.github.io" target="_blank">WCI GitHub
repository</a>. The preferred way to submit your changes is via creating a pull request with the
changes.
To this end, these are the recommended steps for adding an event:
</p>
<ol>
<li><strong>Fork</strong> the WCI GitHub repository</li>
<li><strong>Clone</strong> your forked repository:
<pre class="bg-light p-3">git clone https://github.com/<your_username>/workflowscommunity.github.io</pre>
</li>
<li><strong>Edit</strong> the <code>_data/events.yml</code> file, and add the information
regarding the event:
<pre class="bg-light p-3">
- name: "Event Name"
series: "Event Series or Acronym" <span style="color: #999"># optional</span>
location: "Event Location" <span style="color: #999"># format: "City, Country" or "Virtual"</span>
start_date: <event_start_date> <span style="color: #999"># format: YYYY-MM-DD</span>
end_date: <event_end_date> <span style="color: #999"># format: YYYY-MM-DD</span>
url: <event_url>
type: <event_type> <span style="color: #999"># options: Conference, Workshop, Summit, Forum, Meeting, Other</span>
deadlines: <span style="color: #999"># optional: provide up to 3 deadlines</span>
- name: "Deadline Title 1"
date: <deadline_date_1> <span style="color: #999"># format: YYYY-MM-DD</span>
- name: "Deadline Title 2"
date: <deadline_date_2> <span style="color: #999"># format: YYYY-MM-DD</span>
- name: "Deadline Title 3"
date: <deadline_date_3> <span style="color: #999"># format: YYYY-MM-DD</span>
</pre>
</li>
<li><strong>Commit</strong> the changes, and create a <strong>pull request</strong> for the WCI GitHub
repository.</li>
<li>The WCI team will then evaluate your pull request, and merge the changes if the event is considered
relevant to the community.</li>
</ol>
</div>
</div>