You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/page/submit-to-bosc-2025.md
+11-16Lines changed: 11 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,16 +49,23 @@ Please see below for submission instructions.
49
49
50
50
# Submission guidelines
51
51
52
-
{{< columns>}}
52
+
{{< columns>}}
53
53
54
54
### What to submit
55
55
56
-
- Please describe how your work fits into the open source / open science ecosystem. We like to see examples of biological applications of your work, and a summary of the current and/or projected community aspects of your project.
57
56
- A 250-word short abstract (text only) is required for ALL submissions (talk and/or poster).
58
57
- If you want to be considered for a talk, you also MUST attach a 1-2 page "long abstract" as a PDF. Figures welcome as long as the total length is 2 pages or less.
59
-
-Your abstract PDF should include the title, author name(s), open source license, and code or project URL (even though this information is also requested on the submission form).
58
+
-In your long abstract, please describe how your work fits into the open source / open science ecosystem. We like to see examples of biological applications of your work, and a summary of the current and/or projected community aspects of your project.
60
59
61
-
{{< column >}}
60
+
<divclass="well">
61
+
62
+
Watch a video of [BOSC organizing committee member Jason Williams discussing how to write a great BOSC abstract](https://youtu.be/DwJRrh1Tpew)!
@@ -82,18 +89,6 @@ In addition to the requirements listed above, we consider the following when sel
82
89
-**Examples**: We like abstracts with examples of how your approach works (e.g. a figure showing the output of a visualization tool, an example of software input/output, or benchmarks on relevant data).
83
90
-**Runnable**: Although we are happy to consider abstracts that describe early-phase projects, our reviewers are likely to look at your code and try to run it. Reviewers like projects that they are able to download and run, and that are well-documented and easy to use.
0 commit comments