I’m thinking on how I’m going to implement "projects" in my private weblog. Obviously it would be very different from "projects in companies".
I’ve now implemented a minimal scenario. Whenever there is something that needs be in my mind, I just add a tag "issue" and it ends up in the right-hand column. Obviously the internal system is bigger. Whenever something is done I change the tag to "issue-resolved" and it is gone but kept for history purposes. I did not call it todo because I was thinking on splitting it up further and maybe make more status than just "open" and "closed".
This is not handy because when I have multiple blog posts all related to the same thing actually not the single issue should be there but the project name instead.
So hmmmm…… let’s see….
I think in a private households something never is started as "a project". I think mostly various things happen and suddenly those various things turn into something that we can label as a project meaning: it has a certain lifespan.
I think the following happens:
a) there are several "blog_posts" about something e.g. "mycat" with label "mycat" (if luckily labeled that way)
b) then my cat is ill and I need to arrange all kinds of stuff where I want to blog about so I first do one blog post and add a tag "todo"
c) now I have read some papers from SHCN on cremation of Cats and how to decide what is the best and I want to blog about it but I somehow want to keep these things together.
In the ideal world there would be a project "cat" with a lifecycle behind it and several issues, questions, etc.. in the blogging world these things also include informational posts which is maybe something along the lines of a documentation department or a communication department.
d) so at that moment I define a new custom post-type (new in WordPress 3.0) (I’ve now done quite some code with custom post types, custom fields and custom taxonomies and you can quite some nice stuff with it).
So I now do something "active" and create a new [project] that I name "cat".
The problem now is that I have to back-trace all postings about "cat" and see how they fit in my project because I have convert some of them from build-in post type [blog_post] to e.g. [issue] or [question] etc…
So can I convert a build-in post type to a custom-post type? Yes, pretty easily actually. I just change the type. Now to make that work the handiest is if I make a plugin that lets me front-end change the post-type of "postings" to another type. That’s quite some work.
But in the end I have somewhere under edward.de.leau.net/projects an overview of everything I defined as a project and then a list of "items". These items though have a taxonomy behind them. Not THE wordpress taxonomy but a taxonomy of custom post-types. (and after thinking about it I think every post_type needs to have equal entry in the taxonomy as well). I think they are different than things you would run into in e.g. an IT project where you have RFC’s, Defects etc… it will probably be different kinds of types.
This taxonomy is something that I have to think about because this is obviously related to the taxonomy of a household’s processes.
These custom post types then have relations that I also want to represent e.g. one question could have several answers or "add on posts". defining these relations is handy because in the "GUI" they can be used for all kinds of stuff.
The sidebar is handy for a linkage per type or supertype, as a sort of "also see" but then auto generated based on the relations I have defined.
So we have like a chaos state where all kinds of blogposts come in, hundreds, of all kinds of stuff.
Then during an "active stage" some are ordered into "projects" (and more types, I have to think on that more types e.g. "budget")
Because of that "active stage" we empower ourselves to use extra fields, workflows and relations between other custom post types.
The nice thing about this is this is how humans naturally operate: first we collect stamps and whenever we have a lot of stamps we begin to order them. We like to work in that way and that is how the system will support it.
Because every household is roughly the same this taxonomy and its relations should be defined so that not every user has to go through this him or herself.
I hope its not too complex but furthermore a project never stands on itself. A project in a household is I think always related to a contact, a service, etc… and is always tied to a set of requirements. And in a household these are tied to the set of goals the household sets. But by working from the bottom-up it might do the trick to slowly bottom-up via a hierarchical system come to defining the household goals which can then link to household budget posts which then link to the expenses and revenue system of the household.
The interesting thing about blog posts is that they function as the same kind of thing as a "request" in ALM: it can be all kinds of stuff but we tie it later to "an RFC". But it is also broader: blog posts can be added without being part of a project (or … they are always part of a project but the blogger has really no idea that he is actually doing this as in 99.99% of all weblogs around the web).

At the Height of its Power, Sparta, in 400 BC, had 25.000 citizens and 500.000 slaves. I wonder if that relation (1:20) a) can also be applied to other organizations and b) if it is recursive e.g. if from the 25.000 citizens only 1190 really had the power.

