Lessons learnt from developing a multi-year RSE project

ghisvail commented 1 year ago

This is a proposal for a shorter version of the talk I gave at RSECon22 focusing on the lessons learnt from developing a long-running RSE project. I got loads of questions on this specific part during and after the talk, which motivated this submission.

Title of the contribution:

It is a:

[ ] Short talk (10 minutes including discussion)
[x] Longer talk (20 minutes including discussion)
[ ] Discussion (up to 70 minutes)
[ ] Demonstration (up to 70 minutes)
[ ] Workshop (up to 70 minutes)
[ ] ReproHack (up to 70 minutes)
[ ] Something else (up to 70 minutes)

Do you need help?

[ ] I would like someone to help me plan the contribution

Would you be comfortable if your event was recorded?

[x] Yes
[ ] No

Please indicate on which day(s) the contribution can happen (tick both if you don't mind which one):

[ ] October 18
[x] October 19

By submitting a contribution you agree that

[x] Your name and abstract of the contribution will be published in our program
[x] Your contribution respects the Code of Conduct

Give a short description of your contribution:

Academia is operating on a set of constraints that makes sustained development of durable software particularly challenging, such as limited resources, frequent staff turnover and lack of training. In this presentation, I reflect on the journey of Clinica, a successful neuroimaging software project, which has been in development for 6 years and counting. First born as a side-project used internally at the Aramis Lab, Clinica has become a mature software project developed in the open and fostering a growing community of users. I will share the major lessons we have learnt during this successful journey and touch on various topics such as coding best practices, technical debt and project management. Although Clinica is developed in Python, most takeaways will be transferable to other projects written with a different software stack.

ghisvail commented 1 year ago

I apologize for the last minute submission, I actually saw the Twitter annoucement only recently. I hope this is ok 🙏

bast commented 1 year ago

dear Ghislain, thanks a lot! Nothing to apologize. Last-minute submissions is exactly what we wanted. Thank you!

lucaferranti commented 1 year ago

Hi @ghisvail, on the second day we have two slots: 13:10 CET and 14:10 CET (you can see the schedule here.

Do you have preferences on the time slot (currently they are both equally populated). Once you let me know, I can add your title and abstract to the schedule.

Looking forward for this

ghisvail commented 1 year ago

Could be after you on the 13:10 CET slot?

ghisvail commented 1 year ago

@lucaferranti does the thumbs-up mean it's ok for the time slot? It's still not listed in the schedule so I am a bit confused.

lucaferranti commented 1 year ago

Hi @ghisvail ,

I was supposed to add your talk to the schedule on Friday, but I forgot. I have not opened the PR: https://github.com/nordic-rse/nordic-rse.github.io/pull/397

the talk will appear on the website once the PR is merged (tomorrow morning at latest).

Apologies for the weak follow-up

ghisvail commented 1 year ago

No problem, thanks for confirming :+1:

nordic-rse / conference-contributions