The reason for the rejection was that Freerse's GitHub repository lacked development and update records.
This was because the development had previously been done locally. The code was only uploaded to GitHub when applying for funding.
Discussion
I am now going to start committing every line of code individually so I can get more funding.
GitHub last updated on: "Semisol is typing" 🤣
You've mastered the secret. You will succeed. 😂
I wonder if you can just backfill "activity" by just setting the time on your commits:
Generate a list of all the files in the git repo.
Delete the .git dir
git init
Commit each file with a date in the past with some kind of bash one liner feeding each file into:
git add filename && git commit --date "X day ago" -m "wrote filename"
git remote add origin
git push -f -u origin main
Moss, just do that. Start committing a bunch of small changes and reapply. This is the type of hoop jumping that has to be done in the fiat world to get around nonsense regs. Ironically very similar vibes here.
Should make a commit announcing the completion of a feature, but then over the course of 6 months every day commit again. Each commit is a bug fix and slightly obfuscates your code, with each commit being a small patch becoming reading more haggered and despaired. At the end, the commit messages just read "please work, just this once"
Productivity™️
Do we get extra grants for nice art in commit contribution graph?
Thats the spirit! 😂
Just because you are developing locally doesn't mean you wouldn't have a large number of commits over a long period of time when you do push it.
I don't know how you can build something non-trivial if you aren't doing commits every time you solve a problem. If you don't work this way, how do you step through commits for debugging etc, and how do you checkout a previous commit to figure out where something broke?
We actually developed Freerse in a private GitLab repository, and only made the code publicly available on GitHub when applying for OpenSats funding.
Our development workflow included numerous local and private commits, which is why the full development history isn’t visible on GitHub.
The stability and full functionality of the Freerse app, along with real user feedback, are the clearest proof of our continuous development work—even if the commit history wasn’t publicly visible from the start.