Hi,
> Maybe an approach would be to "limit" attendance to the codeathon side (tract?)
> to those who have projects in mind ahead of time?
This sounds reasonable to me; I suggest that we go this way.
My main goal with documentation this time would be to work on the infrastructure so that we get the auto-builds in place as far as it gets.
When that is done, then it is hopefully clearer how to write and publish documentation so that it can be linked together.
> I say "limit" since people who have shown up to past codeathons without projects
> often got pointed to documentation tasks.
Yes...and then the newcomers are expected to figure out what the programmer had in mind when writing the code and explain it in clear text so that everybody understands __
Timo
On 2023-05-03, 22:45, "Michael Davidsaver" <mdavidsaver at gmail.com <mailto:mdavidsaver at gmail.com>> wrote:
On 5/2/23 08:12, Timo Korhonen via Core-talk wrote:
> Hello,
>
> We have an OK for Docu/Code-athon at ESS on the week 35 (28.August to 1. September) this year.
>
> Before announcing it on tech-talk and the website(s), I wanted to check about codeathon.
>
> There was some discussion if we can have enough topics for an IOC Core codeathon, as the previous one at Diamond is still quite recent.
>
> Opinions?
My answer is both "never" and "always". There is always work to be done.
At the same time, finding tasks suitable for a newcomer to do in a week is
always a challenge.
Maybe an approach would be to "limit" attendance to the codeathon side (tract?)
to those who have projects in mind ahead of time?
I say "limit" since people who have shown up to past codeathons without projects
often got pointed to documentation tasks. So more about setting expectations.
> We have been asked to (try to) stay under/around 20 participants; I do not think this will be a big issue.
This seems like a good idea. While I think the recent DLS codeathon turned
out well, I was initially intimidated by the size of the participant list.
- References:
- Docu-Code-athon Timo Korhonen via Core-talk
- Re: Docu-Code-athon Michael Davidsaver via Core-talk
- Navigate by Date:
- Prev:
Build failed: EPICS Base 7 base-7.0-919 AppVeyor via Core-talk
- Next:
RE: OPI updates when enum strings/values change Mark Rivers via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
<2023>
2024
- Navigate by Thread:
- Prev:
Re: Docu-Code-athon Michael Davidsaver via Core-talk
- Next:
Build completed: EPICS Base 7 base-7.0-917 AppVeyor via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
<2023>
2024
|