# eScience Center Fellowship Closing event

This Document is synchronized as you type, so that everyone viewing this page sees the same text.

Link to this doc: https://tinyurl.com/FellowsClosing2023

## 🗓️ Agenda
| | 25 May, 2023 |
|-|-|
|12:00| **Welcome + Lunch**
|13:00| **Showcase your Fellowship projects**
|14:00| **Writing the end report**
||[link](https://nlesc.sharepoint.com/:w:/s/FellowshipProgramme/EVt5ztyt3zdCpKzw75JQ0IcBgGL4QKIfreZGLf-q1WMDlQ?e=YECTc7), [translation](https://nlesc.sharepoint.com/:w:/s/FellowshipProgramme/Ef6osckD-d9AtUUd5O5bMiQBbdSyGVMfTx0OXhhp_qYRKg?e=DJ2eVW)
|15:00| :coffee: break
|15:15| **Alumni network discussion**
|15:45| **Speedblogging**
|16:45| drinks

## :clipboard: Code of Conduct

Attendees are expected to follow those guidelines:
* Use welcoming and inclusive language.
* Be respectful of different viewpoints and experiences.
* Gracefully accept constructive criticism.
* Focus on what is best for the community.
* Show courtesy and respect towards other community members.

## 👩‍💻🎓 Fellowship Coordination team

Carlos Martinez-Ortiz, Lieke de Boer
Contact us at [e-mail]

## Notes:question:

- What are you most proud of during your fellowship? (something to show? Pictures? Links? Etc?)
- What was the best part of being a fellow?
- What would you change of the whole process?

### Mariken
People push back when you ask them to put in the effort of document their software. Ask GPT was built by postdoc, and is a tool that helps document software in a way which is inclusive. Most proud of awareness raising on the importance of inclusivity.

Will organise a meetup on inclusive collaboration as an NL-RSE meetup.

I think of myself more of an Ambassador.

### Maarten
Training my team, and changing the culture in our group. Lots of individual meetings, because it is different for every researcher: where they are in their PhD, etc. All doing code refinery training. For some it is directly beneficial, for others it is more disconnected (working on software they did in the past). Will do code reviewing session in July. Most proud of feeling more and more an Ambassador in my research area.

We could have been used more as a resource.

### Roelant
Most of my work was not educating how to use git, but getting them to use existing system. Worked with student (<name?>) and for her sharing her work was trivial (just the script)

What I would change is getting more our of the eScience center -- learning more from other (and past) eScience projects that already worked in a particular area. SIGs could be more open -- work in progress.

### Daniela
Most proud of -- baby! (Yay!)

Second most proud of: workshop that I ran. What does reproducibility mean is very different for different people and it gets very much into the details of specific computer science fields.

Best part of being a fellow is having a reason to talk to colleagues about their work.

What I would change about the process is what to do with the money.

### Joshua
Something to show:
https://j-ptrson.github.io/Single-Cell-Core/

Most proud of having something to show. Developed a couple of tutorials that can help users with data processing and analysis. One of the challenges is how to communicate the complexity to people who do not have right background.

Haven't discussed much with 'lab people', but hopefully will be adopted.

I liked the fellowship provided me opportunities for personal growth.

### Davide
Also have a link:
https://neural-data-science-course.github.io/index.html

Building and organising material for neural data science. It is a series of lessons for masters. Lessons are Jupyter notebooks which can be downloaded and used for learning. Building these materials I learned a lot about neuro science. I had a chance to learn a lot in interaction with my mentor.

What I would change: I would like to have more interaction with the eScience center and other fellows.

### Ana
Started with an overtly optimistic list of things to do. I am proud that I will continue to work on this. Plan to attend conference which is very open science oriented. Also started working with R packages, and it was nice to receive help on that (setting up GH actions, etc). It has also helped me gain confidence and recognition. The community part is important to me.

I would have wanted to have more interaction (even if I didn't take any proactive steps). Maybe pairing up fellows. Since we were the first cohort, it was not possible to have some expectation of what was realistic and what it was considered sufficient.

In the money front, it would be nice if it could be increased and cover part of the salary?

### Dörte

https://pypi.org/project/discuit/
Project (also) went different than planned. Used eScience template (cookiecutter) -- now can pip install my package.
> [name=Carlos] it works!

I liked the meetings, even if travelling takest time.

It is nice that the name 'fellowship' gets some recognition.

It would be nice to have more interaction.

### Serkan
Goal was to increase the visibility of the eScience center in my university. This was done mainly via trainings.
> [name=Carlos] we should share your slide on twitter :heart_decoration:

This was also a good opportunity to give recognition to ITC staff who have been developing software for a long time.

Workshops were well attended -- had to stop registration after 120 participants. Did use the money and the hours -- even overspent.

Nice collaboration with Burcu and Claudiu. It was the fellowship programme that made our paths cross. This community aspect is really important.

### Jan
https://tilbot.io (outdated website ;))

Tilbot when I applied -- nobody using it yet. New version is ready. Old version is being used, new version as well.

Every time we met I learned something new: learned about Zenodo, and that you can use it to get a DOI for software.

Attended conference (even if I didn't use the full budget.)

Listing Tilbot on RSD has also improved findability https://www.google.com/search?q=tilbot&oq=tilbot -- first hit!

Chat GPT is related (but not completely), somehow complementary.

### Claudiu
https://rbanism.github.io/Rbanism/
https://github.com/Rbanism - incl. repositories of the fellowship activities

### General
- Fellowship Programme could be suffering from other calls that are also open
- Rejected applicants from other calls forward to Fellowship?
- Training, workshop, community developments
- Other calls are fulfilling these needs
- Lack of visibility of outputs of first round
- Make sure we have a mechanism that makes output from all Fellows visible
- Sustainable software call / maybe in the way of this > look at timing!

## Speed blogging topic suggestions
#### Put your name behind one of the topics, or feel free to add your own topic after having seen the Fellows' presentations today. We will put you into groups.

- How to put research software on the agenda at your institution -- Maarten, Ana, Daniela
- How to run an alumni network for Fellows -- Mariken
- Lessons learned from creating lesson material -- Joshua, Davide, Claudiu
- Recognition and rewards for research software (engineers) -- Mariken, Dörte, Roelant
- Teaching good practices: from preaching to implementing
- How the Fellowship Programme helped me / things I learned
- Lessons learned on community building in science -- Maarten
- How chatGPT affected my project -- Serkan, Jan
- What is good mentoring?

In the first five minutes, you should choose a Chair, a Note-taker. The Chair's role is to make sure that everyone's voice is heard, and keep everyone on topic. The Note-taker clicks the link for the collaborative note (below) taking and blog template for their group from the Discussion Topics list and uses that to note down the pertinent points from the discussion that can then be used as the basis for constructing the speed blog about the session (everyone in the group should help contribute to the notes and speed blog).

|Group|members|link to collab doc|
|-|-|-|
|Group 1| Maarten, Ana, Daniela | [link](https://tinyurl.com/blogging-group1)
|Group 2| Serkan, Jan | [link](https://tinyurl.com/blogging-group2)
|Group 3| Mariken, Roelant, Dörte | [link](https://tinyurl.com/blogging-group3)
|Group 4| Joshua, Davide, Claudiu | [link](https://tinyurl.com/blogging-group4)
|Group 5| Lieke, Carlos | [link](https://tinyurl.com/blogging-group5)

## notes on alumni network
- Pairing up Fellows locally
- Conference

Ana: List of ways in which to be involved. Indicate availability there. Avoid offering to do things that aren't needed.

Daniela: Become part of the selection committee (but clearly indicate the time commitment that's expected)

Serkan: Limited places available for that, what activities can we think of that involve everyone? Annual CW to bring alumni together.

Mariken: Some sort of board of advisors role would be helpful for career development. Would not mind this every now and then. Narrative CV plus.

Carlos: More regular smaller events like NL-RSE meetups, coworking sessions / community calls?

Daniela: Morning programme around a topic, afternoon working on projects.

Jan: Would also be nice to have project partners be a part of these events / this network also.

Mariken: Unconference too vague.

Dorte: Easy for me to commit when I have to travel. Means I am away, book the travel.

Serkan: Keep connection with eScience Center somehow. Keep continuing to interact. Connection will weaken unless the topic stays alive. How can the Fellows keep contacting the eScience Center?

Carlos: Fellows can continue to attend SIGs. Fellowship kickoff day. June 7th.

Dorte: December event was nice, could be an opportunity to mingle between cohorts.

Daniela: Directory of names / affiliations / projects / 2 or 3 hashtags with interests / application text / final report.

Serkan: Provide hours of RSEs for Fellows? Reserve some hours in budget per year.

Connect interested Fellows with current Fellows.

Maarten: This is another community in my network. People will come because the day and people are interesting. One day within the year.

Joshua: Walking distance from station

Roelant: Retreat - would give more time for socializing.

Joshua; Asking for a lot to do a retreat. Following up has to come from people themselves.

## Parking lot

- Ambassador more than getting a grant.
At the SSI, initially called "agents". eScience Center spy network?

- Pairing fellows -- maybe on domain, maybe geographic.

- Demand on your time
- How to spend let-over money?
-