ACDEFGHIJKLMNOPQRSTUVWXYZAA
1
This document is for proposing topics for discussion during the forum. Please nominate anything you'd like to talk about, with a brief explanation/description, and whether you'd like it as a full group or breakout discussion. Add extra lines as needed.
2
3
If you see a topic already in the list that you're interested in, upvote it for inclusion by adding a "1" in the Upvote column. If we don't have time to cover everything, we'll focus on the items with most votes.
4
5
Morning
6
PresentationsSee abstracts
7
8
9
After lunch
10
11
Proposed topics for discussion
Description of topic
Upvote
Takeaways - 3 key points per topic
12
13
Whole Group
14
Future meetingsThis is a one-off event, but should it grow into more? If so, how often, what kind of activity, where, who will lead/champion.2
15
Building a research software developers communityExpanding on above. Meetings are one way of building a community, but what other actions can we take. Do we even want a software developers community?5
16
ChatGPT and AIAre AI tools impacting on your software development. Are you using them to write code for you. What are other current and short-term implications5
17
18
19
20
21
22
Breakout Groups
Takeaways - 3 key points per topic
23
Software sustainabilityHow do I keep my app running/maintained after the grant runs out?8Issue:
Grants are research output focused.
Storage of data has a cost
Code is cheap to store, but has maintenance cost.		Grant based:
Sneak funding as part of other grants.
Reframe/Repackage/Rename projects as a 'new' one.
Grants that have software dev and community engagement as outputs.		Community based:
Create good documentation, good build, integrated tests, promoting it to the right audience, a good name, open repo, encourage peer-support and grow the community to self-manage.		External entity:
Attach it to infrastrucutre of ongoing external entity, an institution, government, or a collection of software projects.		Reframe existing projects as 'new'funding from Grants for software is hard. some 'sneak' in money as part of other grants.Deployable code is cheap to maintain, services/storage are expensive to maintain.become part of a collection of software projectsLeave code in a maintainable stateCombining projectsResearch infrastructure staff to assist reseachers to transfer their prototype to a functional piece of external infrastructure.Better promotion to connect with the audience who would benefit
24
Scaling projectsGrowing from a one-lab application to widespread adoption - what are the infrastructure, code, maintenance needs4^ https://www.sciencedirect.com/science/article/pii/S1359028613000764 great paper to read in this context
25
Programming languaguesDiscuss tips with colleagues who use your favourite programming language7vscode is coolcompiled languages are easier to maintain, but dynamic languages have more community buy inwsl is lovely 😍"IT hellscape"choose the language for the job (but you have to fit in with the community)stability is hard
26
Software demosOpportunity for participants to showcase their software3^ +1 from the jobs table
33
Career progression and professional developmentAre there common challenges that we can addess better together: recruitment/retention, promotion, long-term propects, ongoing learning and development opportunties?5Develop soft skills! Selling your research, ChatGPT for interdisciplinary bridgingRecalibrate the value in where your skills lie, especially the transferability of your skillsMake sure to get traditional academic outputs out of your code if you want to stay in academia!Contribute to your user community and get recognition for that!.
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