pyslackers / website Goto Github PK

There is an attack vector in which a malicious user could use our form to send invites to any number of emails. We should implement rate limiting on that endpoint to ensure proper usage only.

• Type
  • Feature Request
  • Bug Report

Description

All tags show up regardless of if there is related content in the blog (https://pyslackers.com/blog/) - they should be hidden if they are not providing value

Description

Write a blog post tidbit style about pyenv.

New Python patch release, we need to update the playbook to move us to the new one.

• Type
  • Feature Request
  • Bug Report
• Operating System
  • Mac
  • Windows
  • Linux (distro: ...)
• Browser
  • Chrome
  • Firefox

Description

When requesting an invite to join the community it would be nice to have check-boxes to choose which channels we would like to join.

If a bug report, please include what you tried, what you expected, and what happened - including a copy of any errors you saw and/or a screenshot of the problem

• Type
  • Feature Request
  • Bug Report

Description

Slack email invites should be sent after going through a standard rule-set:

• Disallow blacklisted domains
  • burner emails (anything valid for a short period)
  • known compromised domains (if any)
• Check for duplicate emails
  • See pyslackers/sirbot-pythondev#70 for context

We've discussed a little around whether we should alert the user or not, the current leaning seems to be no and let it fail silently.

• Type
  • Feature Request
  • Bug Report

Description

As part of PR #77 I added a package.json and associated eslint files to the build to help developers locally ensure their code matches a particular code style. I've grabbed the default Airbnb configuration and added a few overrides for our particular requirements in the .eslintrc file that surfaced as part of discussion in the PR.

It would be good to get input from folks if the Airbnb style is to their liking and then add linting checks to the build process.

Currently the app can't send email, we can use the free tier of send grid.

• Type
  • Feature Request
  • Bug Report

Description

Flake8 seems to not be reporting errors in CI, must be an issue with our tox config

As the application gets bigger we will have more and more dependencies, we should start thinking now about breaking them up into test/dev and prod dependencies and updating the documentation.

Right now the pyslackers repo count is low enough to not matter, but as we grow and do more - this could get overwhelming and we should only show the top N by default, and optionally allow a request for more

The bottom of the blog post page runs right up against the edge of the screen for any moderate length posts. This needs to have some padding (and probably a footer)

Ideally speaking we won't have members with burners in slack or the website, because we want to encourage people to contribute and engage. Accounts with burners won't be able to be recovered if a password is lost, and they can often be used by people to troll or abuse more anonymously.

This move will make it so any app should be able to use the burner domain logic

Swap out matt's token from testing for a community admin representative @pyslackers.admin

The dreaded OOM has arrived, time to figure out what needs to change. Currently the following is running on a 5$ DO server....

• PSQL
• Redis
• Gunicorn (4xWorkers, 4xThreads)
• Celery Scheduler/Worker

We've hit the cap...

Announce new deploys

This isn't really necessary as of today from a performance standpoint, but it would be good to have a solid example of full productionization of a django app for the community to reference.

I think we can include a few things:

• Django Compressor (or similar) to minify assets for prod
• Django-Whitenoise (as long as we have nginx set up to cache for us)
• Change the staticfiles backend to do cache busting

This was a pretty quickly thrown together project, we need to get tests involved to confidently make changes.

Show the number of members on the front page of the site

• Type
  • Feature Request
  • Bug Report
• Operating System
  • Mac
  • Windows
  • Linux (distro: ...)
• Browser
  • Chrome
  • Firefox

Description

https://pyslackers.com/static/img/logo.png return a 404. So a missing image is displayed @ https://pyslackers.com/blog/

If a bug report, please include what you tried, what you expected, and what happened - including a copy of any errors you saw and/or a screenshot of the problem

We should go through the dependency list and ensure all are still in use, I believe honcho is no longer utilized in the project, for example.

The signup page ( #25 ) should have a terms of service, explanation of what data is collected, how data is used, requirements for a user to sign up (>13, etc).

In the end this should have a dedicated page that is linked from the Sign Up page.

Right now there are some management commands dumped into the marketing app, per Julio's suggestion we can make a core app that houses those shared concerns.

Acceptance:

• Create core app
• Move all common management commands into core application

• Type
  • Feature Request
  • Bug Report

Description

Integrate google analytics to give minor insights into page views/etc

This requires a new work of the pyslackers/ansible playbook. We add some new dependencies:

• postgresql
• redis
• a number of config vars

Along with deploying django, which is unique relative to the old site (flask).

Once we get the deploy working ( #6 ) we should make this project CD:

• Build and push to docker hub
• If "master", run playbook for auto deploy

There is no good way to know which version is currently deployed, expose something about the sha and/or container version via a JSON endpoint

Django has built in support for a feed, let's build one in and we can subscribe in the pyslackers newsfeed.

New django release with some security fixes we should upgrade too: https://www.djangoproject.com/weblog/2017/sep/05/security-releases/

• Type
  • Feature Request
  • Bug Report

Description

The github project cache is stale and not refreshing with the nightly job

Aug 29 23:00:00 pyslackers celery[1548]: [2017-08-29 23:00:00,022: ERROR/Beat] Message Error: Couldn't apply scheduled task refresh-github-project-cache: update_github_project_cache() missing 1 required positional argument: 'org'

• Type
  • Feature Request
  • Bug Report

Description

To generate pretty links in these platforms we need to use meta tags for opengraph/twitter/facebook.

Secondarily, whoever implements this should look at including an image, either a default for the site or one the author associates with the post.

It's incredibly common to see this in python applications:

if __name__ == '__main__':
    main()

But it can be a point of confusion for some.

• Type
  • Feature Request
  • Bug Report

Description

The github project list is static and requires manually calling the ./manage.py task - we need a migration added to set this up for any deployment.

You can see an example if adding one of these in marketing/migrations/0002_membership.py (note: rollback migrations are not required at this point).

Due to ignorance I was putting in tasks manually with migrations thinking it was either beat or beat-db based. Silly me.

We'd like to be able to see growth over time, create a job that captures a snapshot of user memberships daily in the database.

The deploy to slack functionality is broken because the format changed of their token they want. This requires an admin to do it

We have a lot of slack related logic, it's probably time to extract it to its own app to de-couple it from core application logic

Slack exposes only a few pieces of info, but a cool one is simply timezones. This data is anonymous enough that it shouldn't pose any real privacy concerns and could show a fun breakdown of the community and our diversity

Look into using tox for testing across versions, enforcing deploys only on the target release