Panda Bear Database Manifesto

An infinitely scalable database written in python.

What Are We Deeply Passionate About?

We care about allowing anyone with basic technology skills to setup a scalable database.

What Drives Our Economic Engine?

Cost per unit of storage. Lower is better.

What Can We Be the Best In the World At?

We can be the best scalable relational database application.

Core Values

1. Configuration is bad. Self optimizing applications are good.
2. Restarts are bad. Online upgrades are good. Adding resources shouldn't mean interruptions.
3. Safety is good. Having easy and fast backups makes us feel safe.
4. Redundancy is good. Let's keep multiple copies of data.
5. Metrics and statuses are good. It's even better if they're presented in a pretty way.
6. Testing is good. I like to sleep at night. Let's use unit tests and functional tests whenever we can.
7. Easy setup is good. We don't want to spend time on dependencies or compiling.
8. Documentation is good. Accessible documentation is better. Succinct documentation is best. Brevity is the soul of wit.
9. Interopability is good. Defining our own protocols is bad. Let's be drop in replacements for everyone else.
10. Open source is good. Let's get everyone in on this party. Let's make sure we take care of our contributors.
11. Be nice to people. Let's treat each other with respect.
12. Things that make the world better are good. Let's help people who are doing that.
13. People who use our work are good. Let's make sure they're taken care of.
14. Python is great. Let's do everything in python.

Higher Purpose

We want to enable world class breakthroughs by providing the best storage application possible.

Version 0.0 Requirements

Version 0.0 will be pure vaporware. The output is documentation, branding and a plan for releases 0.1 to 0.4.

Version 1.0 Requirements

The first major release will be a drop in replacement for MySQL, memcached, and potentially redis for both master/slave configurations with an emphasis on compatability with Ruby on Rails/Django.

Todo

1. Create a hierarchy of necessary responsibilities within the project.
2. Decide on which open source license to work with.
3. Create a document describing code structure (which directories/files go where?) and documentation structure (how are we going to store and organize documents?).
4. Create a structure for deciding what goes into each release.
5. Create a document that describes how others can contribute.
6. Create functional requirements for release 0.1.
7. Create functional requirements for release 0.2.
8. Create functional requirements for release 0.3.
9. Create functional requirements for release 0.4.
10. Create a logo.
11. Add the created documentation and plan to the website.