I had to publish a little website explaining the project and what happened as per GSOC 2017 rules.
I decided that a good format was a little blog with one post for each "deadline" and went with that. I think
it's a good documentation of what the process looks like and what student can expect. It references what
work was done, it points to the PR and mailing list threads where we discussed them.
Obviously it's more personal than a press release but you never know who lands on this press page.
openwisp-qa-check --skip-checkmigrations
```
SUCCESS: Blank endline check successful!
Skipped 1 files
SUCCESS: Isort check successful!
All done! ✨ 🍰 ✨
2 files would be left unchanged.
SUCCESS: Black check successful!
SUCCESS: Flake8 check successful!
Your commit message does not follow our commit message style guidelines:
- missing prefix in the commit short description
Eg: "[feature/fix/change] Action performed"
Please read our guidelines at: http://openwisp.io/docs/developer/contributing.html#commit-message-style-guidelines
Checked commit message:
add link to personal blog for the GSOC 2017 project
ERROR: Commit message check failed!
File manage.py not found, skipping Make Migration Check.
```
I had to publish a little website explaining the project and what happened as per GSOC 2017 rules.
I decided that a good format was a little blog with one post for each "deadline" and went with that. I think it's a good documentation of what the process looks like and what student can expect. It references what work was done, it points to the PR and mailing list threads where we discussed them.
Obviously it's more personal than a press release but you never know who lands on this
press
page.