Hi,
Thanks Johan for this summary.
I definitely second your statement: it was a successful meeting with a very high output /
organization overhead ratio.
For those interested in the details of this output:
- the framapad: https://bimestriel.framapad.org/p/SageReviewDay3
- trac tickets with keywords rd3: https://trac.sagemath.org/query?keywords=~rd3
Just a few more remarks/suggestions for further editions
- numerous tickets of various difficulty should be open (i.e. problems identified) before the
beginning of the meeting.
- I found slack quite unfriendly to the user, due to popups (e.g. when writing #...) and weird
scrolling behaviour. We might want to use gitter next time.
- This format of meeting is very likely less convenient for newcommers to join the project: the
short time frame and the distance make communication work best with experienced developpers. IIRC,
dev 1 (2008!) was already in this spirit : mostly directed to developpers with some experience already.
I'm planning to organize another such online dev meeting in the near future for linear algebra and
linbox interface related topics.
Best
Clément
Le 08/02/2017 à 09:21, Johan S. H. Rosenkilde a écrit :
Hi sage-devel
Yesterday we held Sage Review Day 3, and it was a big success. I just
wanted to briefly share my experience with this.
Overall, 8 developers participated, most of them all day. We
communicated using Slack, Framapad and Trac. We got 14 tickets
positively reviewed, and had good progress on 3 more tickets.
Planning:
Minimal. We started as 5 developers who wished to give an extra push on
coding theory. We set a date, created a Sage wiki page, and announced on
sage-devel, as well as sending emails to participants of SD75. Just
before the event, we made sure the coding theory dev page on Trac,
https://trac.sagemath.org/wiki/SageCodingRoadMap, was updated; we
created a Slack team page; and a framapad with skeleton information.
During the day:
Communication was four-fold:
1) The coding theory dev page on trac served as a static list of tickets
needing work - everyone looked at that list for tasks.
2) Slack served as live chat and gave a nice atmosphere of working
together. Devs announced work, needs reviews, positive reviews, asked
for assistance, and made jokes. It was a huge motivator.
3) Framapad was a live reference list of what people were working on and
what had already been done.
4) Trac tickets were as always where "official" discussions were taking
place (posts/push followed by a poke on Slack usually).
Aftermath:
For me, this was a great way to set aside a well-defined amount of time
for Sage development. It was also much more efficient than usual
scattered efforts, since context switching takes a lot of time.
Interaction btw. developer and reviewer was immediate, and getting
response on a ticket 5 mins after posting the code is immensely
satisfying.
I feel that this is a fruitful, informal way to coordinate work on Sage.
There really was a mini-Sage Days feeling over it! One reason for the
big feeling of success was that coding theory had so many outstanding
tickets waiting review. Actual designing and serious implementation
would lead to much fewer tickets being finished, and perhaps less
dynamic interaction on the live chat. Perhaps this type of event is
therefore best for a "Review/Bug Day", or at least very focused type of
development.
I'm hoping that the other participants will chime in, or anyone else
with experience of similar events to share.
Best,
Johan
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
