Thanks for your feedback. My comments are below...
> This is a nice intro - thanks for the info. After giving a runway twirl of
> ClueMapper features, it leaves me wondering about some things that may lead
> to other screencasts.
Yeah, this was intended to be an intro to Cluemapper with the
expectation that most people watching the screencast would already be
familiar with Trac. So I focused on showing the features which are
unique to Cluemapper and enhance Trac in some way.
But I agree that making some screencasts for those unfamiliar with how
things work in Trac is essential.
Gerry also suggested breaking the 8 min video out into smaller
segments, probably 2 min or less which show a particular subset of
features. That way, folks could jump around and just watch the
screencasts of the features they're most interested in.
> In particular, I would want to know how to use it to actually organize work.
>
> Perhaps a way to organize could be more task/goal oriented:
> 1. set up a new project (ie create project, add users, etc)
Yes, this was covered in this intro screencast but it could be a
separate video called "Getting started" or something like that.
> 2. organize work (gather and enter requirements, organize into
> milestones/iterations, make estimates, etc)
This is the part that hasn't been fully fleshed out yet. We are
expecting that Agilo might satisfy some of these goals (requirements,
stories, iteration planning, etc) but we still have to kick the tires
of Agilo to see if it's something we want to commit to including with
Cluemapper. The way Rocky is going with Dojo, we might end up writing
this functionality all in AJAX since it makes for a very pleasant user
experience.
> 3. daily maintenance (logging time, checking progress, finding your tasks, etc)
This was also covered to some degree in the screencast, at least
booking hours and seeing what tasks are assigned to you. The overall
progress is indicated on the Roadmap screen which shows how many
active tickets are remaining for the current iteration. This is a
mockup of how we envision the personal dashboard looking when you
visit the start page of a particular project.
http://flickr.com/photos/cluemapper/2786203120/sizes/o/
> Ok, well now I am going to check out our screencast script for agilito and
> see if we applied the same logic :D
Do you have a URL to the Agilito screencast? I'd like to take a look
at it. Also, is the code publicly available? It's built with Django,
right?
Nate
Hi Chris,
Thanks for your feedback. My comments are below...
Yeah, this was intended to be an intro to Cluemapper with the
> This is a nice intro - thanks for the info. After giving a runway twirl of
> ClueMapper features, it leaves me wondering about some things that may lead
> to other screencasts.
expectation that most people watching the screencast would already be
familiar with Trac. So I focused on showing the features which are
unique to Cluemapper and enhance Trac in some way.
But I agree that making some screencasts for those unfamiliar with how
things work in Trac is essential.
Gerry also suggested breaking the 8 min video out into smaller
segments, probably 2 min or less which show a particular subset of
features. That way, folks could jump around and just watch the
screencasts of the features they're most interested in.
Yes, this was covered in this intro screencast but it could be a
> In particular, I would want to know how to use it to actually organize work.
>
> Perhaps a way to organize could be more task/goal oriented:
> 1. set up a new project (ie create project, add users, etc)
separate video called "Getting started" or something like that.
This is the part that hasn't been fully fleshed out yet. We are
> 2. organize work (gather and enter requirements, organize into
> milestones/iterations, make estimates, etc)
expecting that Agilo might satisfy some of these goals (requirements,
stories, iteration planning, etc) but we still have to kick the tires
of Agilo to see if it's something we want to commit to including with
Cluemapper. The way Rocky is going with Dojo, we might end up writing
this functionality all in AJAX since it makes for a very pleasant user
experience.
This was also covered to some degree in the screencast, at least
> 3. daily maintenance (logging time, checking progress, finding your tasks, etc)
booking hours and seeing what tasks are assigned to you. The overall
progress is indicated on the Roadmap screen which shows how many
active tickets are remaining for the current iteration. This is a
mockup of how we envision the personal dashboard looking when you
visit the start page of a particular project.
http://flickr.com/photos/cluemapper/2786203120/sizes/o/
Do you have a URL to the Agilito screencast? I'd like to take a look
> Ok, well now I am going to check out our screencast script for agilito and
> see if we applied the same logic :D
at it. Also, is the code publicly available? It's built with Django,
right?