Help Grandma Out

Submitting

4 min read

Go through this list before you hit submit. Grandma will.

This is the checklist for the day you ship. Read it before you are tired and in a hurry. The hand-in note has the same boxes, and every one of them has to be ticked.

The checklist

The most important ones come first.

  • Your project follows the demands Grandma gave you, and a reviewer can check every one of them.
  • You started it after you talked to Grandma.
  • It is not an old project with a new name. If you reused an old repository, say why in your description.
  • No other program has counted these hours or this work.
  • It is your own work, in your own time: not a copied tutorial, not someone else's code, not school work, not paid Hack Club work.
  • Everything your description says it does is true and works.
  • Your link opens for anyone in a private window with no login (or you gave demo logins in your description), on a host that stays awake. A newcomer can try it in two minutes without compiling anything.
  • Your repository is public and opens without signing in.
  • Your README says what it is, how to set it up, and how to run, play or build it.
  • Your commits grew while you worked. One giant upload at the end looks suspicious.
  • Your hours are real work on this project: no idle timer, no scripts, nothing from other projects. They come from Hackatime.
  • AI took less than 30% of your total time, and you can explain every part of your project.
  • Your screenshot is a still picture of the real project. A recording, if you have one, is on YouTube, Vimeo or a plain mp4 link, not Google Drive.
  • Your art, models and sound took at most a quarter of your hours, unless they are the heart of the project.
  • You read the rules.

Hours are not paid word for word

Warning

A reviewer may reduce your hours if they look inflated. Grandma can only prove what she can verify, and Hackatime is not proof of work. Honest hours, a repository that shows the work, and a project that matches the number are your best friends. After Grandma has handed over a result, you see how much Hackatime tracked and how many hours the reviewer approved, and so does everyone who opens your project page; if the reviewer approves less, the note says why.

After you submit

Once you hand a project in, nothing you handed in can be changed.

The moment you hand a project in you may start the next one: it does not wait for the reviewers. You can have several projects handed in and waiting at once. Grandma tells you each result herself, one at a time, the next time you visit.

A reviewer looks at your project and says one of three things:

  • Approved. You collect your cookies from Grandma.
  • Changes requested. The reviewer writes what to change. No cookies yet, because only the round that gets approved pays. Grandma reads you the note and you collect it from her like any result.
  • Turned down for good. Rare, for cheating or spam. The project is finished.

Fixing a project

A project with changes requested shows on your dashboard with a Fix it button, and with the note. Press it, change the project, and hand it in again: that is the next round, with its own hand-in note. The note starts filled in from your last round, but the screenshot has to be added again and the boxes ticked again.

You can fix it whenever you like, there is no clock, and you can do it while you are building a new project. A project usually gets at most 3 rounds, and Grandma tells you how many goes are left. On the last one the reviewer can only say yes or no.

The note about what to change is public, like everything else about a project. Once you have collected it from Grandma, anybody with the link to your project page can read it.

People need to be able to use your project. The link must not point to a host that goes to sleep when nobody visits, such as Streamlit or the free tier of Render. A reviewer who clicks a sleeping link just sees a loading screen, and Grandma does not wait for loading screens. The hand-in note refuses the hosts Grandma knows about, and so does a notebook on Colab: that is a page to read, not a project to try.

The AI declaration

When you submit, you say how you used AI. The limit is under 30% of your total time, and you must understand what you hand in. Be honest. It is much easier than being caught. How this site was made is on its own page.

The screenshot and the recording

The screenshot shows what it looks like. The short recording shows it working, so the reviewer can check your demands in about a minute. Some demands, like Audio Only or Undo Everything, are really hard to check without one.

The code

Your repository must be public, with a README. A licence is a nice idea but not a must.

Stuck on something? Ask in #grandma-help.