action #167120
closed
SUSE Hack Week 24 2024-11-18 in the SUSE QE Tools team size:M
Added by okurz 5 months ago.
Updated 3 months ago.
Description
Motivation¶
SUSE conducts a Hack Week and we should use the opportunity for us in the SUSE QE Tools team efficiently.
Acceptance criteria¶
- AC1: Every tools team member has a hack week project
- AC2: Critical roles, e.g. alert duty, are still occupied and executed during Hack Week
- AC3: Results of Hack Week project work by team members have been presented
- AC4: Nobody has to attend regular calls during Hack Week (one can still join e.g. the daily of course)
Suggestions¶
- Ask everybody to think about and decide for a Hack Week project
- Optional: Everybody mention their Hack Week project in the ticket (but can also be shared with the team differently)
- Ask for volunteers for the critical roles for the Hack Week period
- Suggest when and where to present results, e.g. weekly coordination meeting or the Monday after hackweek
- Await the presentation of results
- Conduct a hackweek daily instead of the non-infra daily
- Copied from action #133223: SUSE Hack Week 23 (Nov 6 2023) in the SUSE QE Tools team added
- Subject changed from SUSE Hack Week 24 2024-11-18 in the SUSE QE Tools team to SUSE Hack Week 24 2024-11-18 in the SUSE QE Tools team size:M
- Status changed from New to Workable
- Status changed from Workable to Feedback
- Target version changed from Ready to Tools - Next
So some team members mentioned ideas for their hack week project(s), other not yet. I will bring this up again, e.g. week before hack week.
- Due date set to 2024-11-29
- Status changed from Feedback to In Progress
- Target version changed from Tools - Next to Ready
- Status changed from In Progress to Feedback
hack week was completed. We can wrap up, clean up and plan based on results if there is anything to be continued within our non-hackweek time
I joined to A CLI for Harvester project. The owner was so happy in the first place that someone join his project, after the third day went missing and didn't answer to me at all. I've open 4 pr, but no reviews or feedback was given both on github and slack. Sad, but it was fun fixing dependency and deprecation issues after all.
- Due date deleted (
2024-11-29)
- Status changed from Feedback to Resolved
Also available in: Atom
PDF