General Issue: Browse Hackathon Code

[StefanThoma]

Background Information

Look through the code uploaded by hackathon participants.
Identify usages which differ from our intended usage of admiral.
Can we generate new use cases / ideas from that usage?
Should documentation be adjusted / clarified?

Contact me to get access to the files.

Definition of Done

Write a summary of insights and remarks gained from the admiral hackathon files.
Identify discussion points and bring them to a meeting.
Discuss whether any changes / updates are required.

[bms63]

Could you put these files into the Phuse teams site. Maybe the backlog group could review these? @bundfussr @zdz2101 @manciniedoardo

[bms63]

Moving this to a discussion - as it is a big topic.

[manciniedoardo]

Conversation about this discussion topic at the core dev team standup today:

• There are potential benefits in attacking this task as we could see what end-users are doing with admiral - what functions are they using/omitting? What are some common methods and mistakes?
• However review would have to be done by "veteran" team member(s) because only they would be able to glean the above info. This would require a big time commitment from whoever took this on.
• One option would be to do a statistical approach rather than reviewing everything manually.

Decision

• This issue feels like a lower priority compared to other open tasks at the moment. No-one should feel forced to work on it over other priority tasks.
• Keep this open for a while (at least until @StefanThoma is back) but close if it gets staler and there is no progress on it.

[manciniedoardo]

Closing due to inactivity.