https://github.com/rasbt/python_reference

The Google group gets virtually no traffic. Almost all of it has migrated to IRC/Slack and to the meetup.com comments. I think we can safely remove it or point people to Slack and the Saturday group instead.

There's no date or location yet but you can say late Spring or early Summer

We should link to our YouTube channel with some of our past talks.

Sections:

• New to Python (recommendations on books, courses, etc) that people here like
• Diving Deeper in Python (topics and links to thinks to research together or as a group... list comprehensions, decorators, etc)... also general resources like Weekly Python Chat and podcasts
• Recommendations on engaging with others at study group. Make comment on the event you'll go to saying what you're interested in learning/doing at the event that day

It might be fun for beginners to improve the SD Python website.

Some ideas:

• Use Django/Pyramid/Flask instead of pelican
• Host on Heroku or somewhere else that's easy to deploy to
• Add setup instructions and add instructions to the website to let beginners know they can improve it
• Add an AUTHORS file (yay credit!)
• Encourage attendees of the Saturday study group to work on the website

I would like to manage the deployment automatically. Whether that goes through a Heroku pipeline or a CI service like TravisCI isn't as important. I just want the site to get deployed from the latest master (or maybe another branch like release).

Given our current setup (see #111), there would be two parts to this although they aren't equally important.

• Firstly, we could have TravisCI write to the gh-pages branch (which github pages uses). This would solve the vast majority of the deployment headaches.
• Secondly, we could have pushing to master (or another branch) on https://github.com/pythonsd/pythonsd-django release that to Heroku

Use letsencrypt to generate a cert. I don't know our hosting details though. cc @macro1

For some reason only Pelican 3.5.0 is available on PyPI, and there are some changes in the way sites are generated and run. We should transition off the old version of Pelican.

Rise mentioned that a place to share notes about the presentations would be useful. Do you think we should keep that on the meetup.com site? Alternatively, we could put something like Disqus on pythonsd.org. Thoughts?

See if one of these widgets can get a feed of upcoming events on our website.

https://github.com/meetup/widgets/

They're shooting to begin crowdfunding on March 15

https://jobs.qualcomm.com/public/jobDetails.xhtml?requisitionId=1938958
https://jobs.qualcomm.com/public/jobDetails.xhtml?requisitionId=1938957

https://news.ycombinator.com/item?id=10657630

Giving a talk is a big deal for some people. I think we should try to give credit and link to the speaking material when possible.

Maybe we should make a "Past Talks" or "Past Events" page on the website?

Or we could summarize the previous month's talks in the next month's newsletter and ask the speaker for their slides or other speaking material so we can link to it.

Ideas?

I created this ticket due to discussion on the IRC/Slack channel. Maybe we don't really need an overhaul and maybe just fixing individual issues and putting an updated theme on top is the answer.

Regardless, I outlined our current setup in this issue.

Current website overview

We currently have two repositories that make up the SD Python website:

• The first is this repo you're looking at: https://github.com/pythonsd/pythonsd.org. This hosts static content built by Pelican, a Python static site generator.
• The second component of the site is here: https://github.com/pythonsd/pythonsd-django. This is a Django powered site and it proxies to the Pelican generated one. It is hosted on Heroku and www.pythonsd.org resolves to here. It adds a few URL shortcuts like http://www.pythonsd.org/coc/. It also proxies some static content to the static site above. Micah (@macro1) is currently paying for the Heroku account and I have access.

We own a number of domains:

• pythonsd.org
• pythonsd.com
• sandiegopython.org

These are all owned by me in my NameCheap account. Whatever we decide, I can redirect those domains. (sandiegopython/pythonsd-django#39)

Things the website does

Anything that replaces this should do all of these

• Featuring our sponsors is important!
• While our past blogs may be of little value, they are kind of nice. I don't want to make that a strict requirement of anything replacing the current site. We also could exclusively proxy requests for old blogs to GH pages.
• Job posting guidelines and how to post to the mailing list
• How to join the IRC/Slack channel
• Host the code of conduct

Things the website should do but doesn't

• The meetup widget is broken (#110).
• The site is not currently HTTPS (#106). This is sort of exacerbated by the fact that we have a non-trivial proxy setup.
• I would like to simplify the setup and deployment. I'd rather we had one repo than two.
• If the project was easier to contribute to, maybe we'd get more contributions (#70). This might be wishful thinking. It might take making the website a study group sprinting project or something.

What do you guys think?

CC by 3.0?

I don't have access to AV equipment, but if somebody does or would like to take point on this, I think it would be a great service to the group.

http://www.voiceofsandiego.org/partner-voices-story/league-of-amazing-programmers-empowers-kids-teaches-the-joy-of-computer-programming/

I frequently instruct attendees of the Saturday meetups how to find the learning material for our last Django TDD workshop.

I think we should link to it more prominently.

Maybe a "Workshops" link in the top bar? Or a large section at the top of the "Getting Started" page that not only mentions the last workshop but promotes the workshop documentation as a standalone tutorial (I think it would work as such).

I'm open to suggestions for solutions.