Bake status

[philip reed]

John et al,

Upon reflecting on the tools that we have at our disposal, I figured
that I'd be most comfortable assembling my portion of the manual on
the project's wiki. This gives everyone in the project a real-time
view of where I stand.

http://cakeforge.org/plugins/wiki/index.php?Bake&id=53&type=g

Right now, I've only thought out a sketchy 4.5-step plan, sketched out
a very rough introductory sentence, and pasted in some screen output.

I'll plan to continue giving weekly status e-mails, John, of which
I'll consider this the first -- unless you'd rather I use some other
venue besides the wiki to do this.

I also created an enhancement task, which I don't have privileges to
assign to myself, representing the bake section of the manual.
Again, feel free to correct me if this is an inappropriate use of the
tools that CakeForge provides.

Thanks,

Philip

--
Philip Reed, Web developer

http://philipreedtech.com

Web. Made simple.

[simonell...@googlemail.com]

Wiki makes a lot of sense. Wasn't this pretty much why wiki's got
invented?

Anyway, I see from the examples there that you're using a fairly old
version of bake (the latest 'release' has a bunch of new options). I
take it we're documenting based on current latest 1.2 release, or do
people think it would be better to keep up with the day-to-day of the
svn trunk?

simon

[philip reed]

Simon,

I appreciate the feedback, both on the usefulness of the wiki and on
my use of an outdated bake.

Since I posted that yesterday, it occurred to me to use the latest 1.2
trunk for writing doc. But it sounds like you're unsure whether
that's the best course of action, right? I find it hard to believe
that the functionality of bake will change much before release but if
so then you may have a point.

Thanks,

Philip

On Nov 20, 2007 8:21 PM, simonell...@googlemail.com

[John David Anderson]

On Nov 20, 2007, at 2:02 PM, philip reed wrote:

>
> John et al,
>
> Upon reflecting on the tools that we have at our disposal, I figured
> that I'd be most comfortable assembling my portion of the manual on
> the project's wiki. This gives everyone in the project a real-time
> view of where I stand.
>
> http://cakeforge.org/plugins/wiki/index.php?Bake&id=53&type=g
>
>
> Right now, I've only thought out a sketchy 4.5-step plan, sketched out
> a very rough introductory sentence, and pasted in some screen output.

I'll keep an eye on it. I'm not really picky about what format the
content takes - this should work fine.

> I'll plan to continue giving weekly status e-mails, John, of which
> I'll consider this the first -- unless you'd rather I use some other
> venue besides the wiki to do this.

I appreciate that - it makes it nice when someone emails me, rather
than me having to send a reminder. :)

> I also created an enhancement task, which I don't have privileges to
> assign to myself, representing the bake section of the manual.
> Again, feel free to correct me if this is an inappropriate use of the
> tools that CakeForge provides.

We don't really need to create Trac tickets... the wiki at cakeforge
allows me to see what's next to do well enough.

-- John