Skip to content

Problem statements for a hackathon #15

@answerquest

Description

@answerquest

25.10.18: Edit:

Link to the Slides shown onscreen at the meetup


Gathering problem statements for a hackathon.
Guidelines:

  • One problem statement per post. If you have multiple, then make separate posts.
  • Clearly show skillsets required to qualify for participating in the task.
  • Provide reference links if any at bottom.
  • Make it small, not big. We want people to actually finish the task and put out the solution within a half-day or whatever the hackathon's action duration is. If the task is looking big, break it down into multiple tasks.
  • We want to solve real world problems with the task. Hence, provide a realistic use case scenario or better a real life need (mention who needs it)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions