A better python cheese shop. What would you change?

-
Often whilst visiting bars, or night clubs I play a game with whomever I am with. It's called 'the perfect night club'. What we would do if we ran a night club? I'd add in vending machines for non-alcaholic drinks, I'd add in plenty of couches, I'd add in twice as many girls toilets... etc etc.

Looking through the cheese shop today I started playing the same game. Here's my top three changes I'd like to see:

1. What's changed? What has changed in this release of software? This is probably the most useful information missing for people tracking the cheese shop. Freshmeat has another useful piece of change information - a change summary. So you can quickly tell the focus of the release: bug fixes, security fixes, feature changes, etc. Other people don't find the cheese shop release information as useful as it could be too... planetpy blog

2. Faster browsing. The website is a bit slow. Mainly when browsing through the categories. I think caching would help a lot here. Since there seems to be only five changes a day - caching should be quite useful.

3. Screen shots. Not all packages need screen shots, however it would be very useful for some packages. Any package with a GUI, or that produces graphics. Even IPython has screen shots. One step further would be screen casts.


Those are my top three changes I'd like to see. Pygame.org has a nice project listing section which could also be inspirational. One of the better parts of it, is that you can comment on releases. This gives authors more feedback than they would otherwise get. Freshmeat is probably the best place to look for inspiration.

What would you do if you made a better cheese shop?





Melbourne Web Developer Written by a Melbourne web developer. Available for your projects - php, mysql, e commerce, javascript, CMS, css, flash, actionscript, python, games, postgresql, xml.

Comments

Unknown said…
Maybe add too the screencast. Every project has too screencasts with screenshot.
7:06 AM
Scott Kirkwood said…
Yes it should definitely be more like Freshmeat.

The only other thing I'm getting annoyed by are these libraries that output every little thing as a separate announcement. If those could be grouped under a parent project perhaps that would be better.
11:12 PM
Post a Comment

Popular posts from this blog

Draft 3 of, ^Let's write a unit test!^

-
Image
So, I started writing this for people who want to 'contribute' to Community projects, and also Free Libre or Open source projects. Maybe you'd like to get involved, but are unsure of where to begin? Follow along with this tutorial, and peek at the end in the "what is a git for?" section for explanations of what some of the words mean. Draft 1, 2018/07/18 - initial draft. Draft 2, 2019/11/04 - two full unit test examples, assertions, making a pull request, use python 3 unittest substring search, "good first issue" is a thing now. Started "What is a git for? Jargon" section. Draft 3, 2020/12/12 - default branch name is main. What's first? A test is first. A unit test is a piece of code which tests one thing works well in isolation from other parts of software. In this guide, I'm going to explain how to write one using the standard python unittest module, for the pygame game library. You can apply this advice to most python pr...
Read more

Is PostgreSQL good enough?

-
Image
tldr; you can do jobs, queues, real time change feeds, time series, object store, document store, full text search with PostgreSQL. How to, pros/cons, rough performance and complexity levels are all discussed. Many sources and relevant documentation is linked to. Your database is first. But can PostgreSQL be second? Web/app projects these days often have many distributed parts. It's not uncommon for groups to use the right tool for the job. The right tools are often something like the choice below. Redis for queuing, and caching. Elastic Search for searching, and log stash. Influxdb or RRD for timeseries. S3 for an object store. PostgreSQL for relational data with constraints, and validation via schemas. Celery for job queues. Kafka for a buffer of queues or stream processing. Exception logging with PostgreSQL (perhaps using Sentry) KDB for low latency analytics on your column oriented data. Mongo/ZODB for storing documents JSON (or mangodb for /dev/null replacemen...
Read more

post modern C tooling - draft 6

-
Image
Contemporary C tooling for making higher quality C, faster or more safely. DRAFT 0 - 10/11/18,  DRAFT 1 - 9/16/19, 7:19 PM, I'm still working on this, but it's already useful and I'd like some feedback - so I decided to share it early. DRAFT 2 - 10/1/19, mostly additions to static analysis tools. DRAFT 3 - 10/4/19, updates on build systems, package management, and complexity analysis.  DRAFT 4 - 10/6/19, run time dynamic verification and instrumentation, sanitizers (asan/ubsan/etc), performance tools, static analyzers. DRAFT 5 - C interpreter(s).  DRAFT 6 - 11/6/19 , mention TermDebug vim,  more windows debugging tools, C drawing for intro. In 2001 or so people started using the phrase "Modern C++". So now that it's 2019, I guess we're in the post modern era? Anyway, this isn't a post about C++ code, but some of this information applies there too. No logo, but it's used everywhere. Welcome to the post modern era. S...
Read more