First of all I would like to say that I like voo2doo very much. It
takes a little time getting used to the interface and how it works,
but as soon as i figured out a good procedure for myself, it worked
like a charm.
Also the philosophy of Joel Spolsky on which the hour registration is
based is very good. Although he states that this philosophy is now
replaced by new insights, for me is still works very good.
I tried out his software which is also free for a max of 2 users, but
it has grown to a 'over the top' bugtracking tool in which i get
totally lost. The only reason why i tried it out, was that it has
multiuser functionality.
So, could this be possible in voo2doo ? I know that there is the
collaborators functionality, but i couldnt get it to work as i liked.
In my case i work in Holland and i have two 'collegues' (indepent
programmers) who work in Poland.
At the moment i just send them emails with the task descriptions and
they send me emails back with their hours etc.
What i would like very much, is that they can login to voo2doo and
besides their own personal tasks , the can see the tasks that i
assigned to them. So, my idea would be : groups.
Suppose i could create a new group and invite other users to this
group.
Then i would add projects to this group. And then create taksk and
assign them to various members of this group.
The next step could maybe be: Generate simple reports per user per
project to see how much hours they spent on their tasks in a project.
Another idea is : customized style sheets. Although the functionality
of voo2doo is abolutely great. The userinterface could use a little
styling ;-) . And since this is a matter of taste, why not let people
create their own style sheets ?
> First of all I would like to say that I like voo2doo very much. It
> takes a little time getting used to the interface and how it works,
> but as soon as i figured out a good procedure for myself, it worked
> like a charm.
> Also the philosophy of Joel Spolsky on which the hour registration is
> based is very good. Although he states that this philosophy is now
> replaced by new insights, for me is still works very good.
> I tried out his software which is also free for a max of 2 users, but
> it has grown to a 'over the top' bugtracking tool in which i get
> totally lost. The only reason why i tried it out, was that it has
> multiuser functionality.
> So, could this be possible in voo2doo ? I know that there is the
> collaborators functionality, but i couldnt get it to work as i liked.
> In my case i work in Holland and i have two 'collegues' (indepent
> programmers) who work in Poland.
> At the moment i just send them emails with the task descriptions and
> they send me emails back with their hours etc.
> What i would like very much, is that they can login to voo2doo and
> besides their own personal tasks , the can see the tasks that i
> assigned to them. So, my idea would be : groups.
> Suppose i could create a new group and invite other users to this
> group.
> Then i would add projects to this group. And then create taksk and
> assign them to various members of this group.
> The next step could maybe be: Generate simple reports per user per
> project to see how much hours they spent on their tasks in a project.
> Another idea is : customized style sheets. Although the functionality
> of voo2doo is abolutely great. The userinterface could use a little
> styling ;-) . And since this is a matter of taste, why not let people
> create their own style sheets ?
> First of all I would like to say that I like voo2doo very much. It
> takes a little time getting used to the interface and how it works,
> but as soon as i figured out a good procedure for myself, it worked
> like a charm.
> Also the philosophy of Joel Spolsky on which the hour registration is
> based is very good. Although he states that this philosophy is now
> replaced by new insights, for me is still works very good.
> I tried out his software which is also free for a max of 2 users, but
> it has grown to a 'over the top' bugtracking tool in which i get
> totally lost. The only reason why i tried it out, was that it has
> multiuser functionality.
> So, could this be possible in voo2doo ? I know that there is the
> collaborators functionality, but i couldnt get it to work as i liked.
> In my case i work in Holland and i have two 'collegues' (indepent
> programmers) who work in Poland.
> At the moment i just send them emails with the task descriptions and
> they send me emails back with their hours etc.
> What i would like very much, is that they can login to voo2doo and
> besides their own personal tasks , the can see the tasks that i
> assigned to them. So, my idea would be : groups.
> Suppose i could create a new group and invite other users to this
> group.
> Then i would add projects to this group. And then create taksk and
> assign them to various members of this group.
> The next step could maybe be: Generate simple reports per user per
> project to see how much hours they spent on their tasks in a project.
> Another idea is : customized style sheets. Although the functionality
> of voo2doo is abolutely great. The userinterface could use a little
> styling ;-) . And since this is a matter of taste, why not let people
> create their own style sheets ?
I'm wondering if the multi-user aspect could work by having contexts
within contexts (lets call them groups). For example, our accounts
could have a group of contexts for executive and a group of contexts
for workers, where the executives would have all contexts in their
group and the workers would only have a subset of the contexts.
On Aug 20, 5:24 pm, Pastor Joe <mills....@gmail.com> wrote:
> I also work in a colaborative development environment where a multi-
> user aspect would be useful.
> On Aug 17, 7:07 am, Arno <arno.eaglee...@gmail.com> wrote:
> > Hi everyone,
> > First of all I would like to say that I like voo2doo very much. It
> > takes a little time getting used to the interface and how it works,
> > but as soon as i figured out a good procedure for myself, it worked
> > like a charm.
> > Also the philosophy of Joel Spolsky on which the hour registration is
> > based is very good. Although he states that this philosophy is now
> > replaced by new insights, for me is still works very good.
> > I tried out his software which is also free for a max of 2 users, but
> > it has grown to a 'over the top' bugtracking tool in which i get
> > totally lost. The only reason why i tried it out, was that it has
> > multiuser functionality.
> > So, could this be possible in voo2doo ? I know that there is the
> > collaborators functionality, but i couldnt get it to work as i liked.
> > In my case i work in Holland and i have two 'collegues' (indepent
> > programmers) who work in Poland.
> > At the moment i just send them emails with the task descriptions and
> > they send me emails back with their hours etc.
> > What i would like very much, is that they can login to voo2doo and
> > besides their own personal tasks , the can see the tasks that i
> > assigned to them. So, my idea would be : groups.
> > Suppose i could create a new group and invite other users to this
> > group.
> > Then i would add projects to this group. And then create taksk and
> > assign them to various members of this group.
> > The next step could maybe be: Generate simple reports per user per
> > project to see how much hours they spent on their tasks in a project.
> > Another idea is : customized style sheets. Although the functionality
> > of voo2doo is abolutely great. The userinterface could use a little
> > styling ;-) . And since this is a matter of taste, why not let people
> > create their own style sheets ?
Thanks everyone for your suggestions regarding collaboration via Voo2do. I've been thinking about enhancing Voo2do's collaboration features, and considering ways to add in these improvements without making Voo2do overwhelming for people who just need a simple tool for individual use.
I'd like to propose one way I've been thinking about to achieve this, and see if it sounds reasonable to you and other folks on this list.
The basis of collaboration will be a Group Space. A Group Space is kind of like a Voo2do user account - it can contain contexts, projects, and tasks - but instead of logging into it, you create or join a Group Space using your existing (or new) Voo2do account.
- All tasks / projects / contexts / notes in a group space are visible to all members of the group. Contexts from the group space appear on each user's dashboard page. (Perhaps there is a way for each user to quickly toggle the display of various groups on their dashboard.)
- Like the current collaborative contexts, tasks in group spaces will have an "owner" column, which can be edited to identify who in the group is responsible for the task. Ideally, the value of this column would autocomplete with the names of group members, but could also be typed in if you wanted to assign it to someone external, or to a generic role like "QA".
- Each member of the group can either be an administrator, regular member, or read-only viewer. Only administrators can add/remove members. Regular members can add, edit, and view tasks, and read-only viewers can only view.
- Because it's important to have a "what's new" page where you can catch up on what other group members have done while you were away, I think an important feature would be a "group home page" that shows recent changes -- new tasks, notes / modifications to existing tasks, etc. Something like: * task "implement foo widget": owner changed from 'QA' to 'bob' by bob.
This sort of change tracking might actually be useful to Voo2do users outside of the group feature, but I think is especially important when multiple people can potentially be modifying the same tasks.
There are other features I can think of that might be potentially useful, like having a general group notes section or file storage. Initially, though, I think it would be best to focus on the task tracking that is Voo2do's strength rather than trying to be everything for groups.
I'd love to hear what people who do group work think of this general approach: - does this sound like something you would use? - what would make it better? - are there any ways to make it simpler? is there something unnecessary that could be left out (at least, left out of the initial version)?
That sounds great Shimon!
So we could concider our own area, "Our Space" and these new "Group
Spaces" as you call them are shared with various people. Sounds
perfect, most everyone I work with now has switched to Voo2Do, so
it'll be extremely easy to get them on top of things if we share a
space. It doesn't sound too complex, the only thing I am wondering
about is of course the creator would be n the Admin level, but how do
you invite other users?
On Aug 23, 7:40 pm, Voo2do Support <voo2dosupp...@gmail.com> wrote:
> Thanks everyone for your suggestions regarding collaboration via
> Voo2do. I've been thinking about enhancing Voo2do's collaboration
> features, and considering ways to add in these improvements without
> making Voo2do overwhelming for people who just need a simple tool for
> individual use.
> I'd like to propose one way I've been thinking about to achieve this,
> and see if it sounds reasonable to you and other folks on this list.
> The basis of collaboration will be a Group Space. A Group Space is
> kind of like a Voo2do user account - it can contain contexts,
> projects, and tasks - but instead of logging into it, you create or
> join a Group Space using your existing (or new) Voo2do account.
> - All tasks / projects / contexts / notes in a group space are visible
> to all members of the group. Contexts from the group space appear on
> each user's dashboard page. (Perhaps there is a way for each user to
> quickly toggle the display of various groups on their dashboard.)
> - Like the current collaborative contexts, tasks in group spaces will
> have an "owner" column, which can be edited to identify who in the
> group is responsible for the task. Ideally, the value of this column
> would autocomplete with the names of group members, but could also be
> typed in if you wanted to assign it to someone external, or to a
> generic role like "QA".
> - Each member of the group can either be an administrator, regular
> member, or read-only viewer. Only administrators can add/remove
> members. Regular members can add, edit, and view tasks, and read-only
> viewers can only view.
> - Because it's important to have a "what's new" page where you can
> catch up on what other group members have done while you were away, I
> think an important feature would be a "group home page" that shows
> recent changes -- new tasks, notes / modifications to existing tasks,
> etc. Something like:
> * task "implement foo widget": owner changed from 'QA' to 'bob' by bob.
> This sort of change tracking might actually be useful to Voo2do users
> outside of the group feature, but I think is especially important when
> multiple people can potentially be modifying the same tasks.
> There are other features I can think of that might be potentially
> useful, like having a general group notes section or file storage.
> Initially, though, I think it would be best to focus on the task
> tracking that is Voo2do's strength rather than trying to be everything
> for groups.
> I'd love to hear what people who do group work think of this general approach:
> - does this sound like something you would use?
> - what would make it better?
> - are there any ways to make it simpler? is there something
> unnecessary that could be left out (at least, left out of the initial
> version)?
I think the invitation process would work by you entering the
invitee's email address. Voo2do would email them a special
one-time-use link that offers them the option to join your group
space. If they have a Voo2do account already, they would be prompted
to join your space using their existing account. If they didn't want
to do that, or didn't have a Voo2do account, they could create one,
and once signup was completed, they'd again be prompted to join the
group space.
When adding a member, you'd specify whether they should be an admin,
regular member, or read-only viewer. Admins would also be able to
change permissions for existing users, with the only constraint being
that at least one user must be classified as an administrator for the
group space.
> That sounds great Shimon!
> So we could concider our own area, "Our Space" and these new "Group
> Spaces" as you call them are shared with various people. Sounds
> perfect, most everyone I work with now has switched to Voo2Do, so
> it'll be extremely easy to get them on top of things if we share a
> space. It doesn't sound too complex, the only thing I am wondering
> about is of course the creator would be n the Admin level, but how do
> you invite other users?
> On Aug 23, 7:40 pm, Voo2do Support <voo2dosupp...@gmail.com> wrote:
>> Thanks everyone for your suggestions regarding collaboration via
>> Voo2do. I've been thinking about enhancing Voo2do's collaboration
>> features, and considering ways to add in these improvements without
>> making Voo2do overwhelming for people who just need a simple tool for
>> individual use.
>> I'd like to propose one way I've been thinking about to achieve this,
>> and see if it sounds reasonable to you and other folks on this list.
>> The basis of collaboration will be a Group Space. A Group Space is
>> kind of like a Voo2do user account - it can contain contexts,
>> projects, and tasks - but instead of logging into it, you create or
>> join a Group Space using your existing (or new) Voo2do account.
>> - All tasks / projects / contexts / notes in a group space are visible
>> to all members of the group. Contexts from the group space appear on
>> each user's dashboard page. (Perhaps there is a way for each user to
>> quickly toggle the display of various groups on their dashboard.)
>> - Like the current collaborative contexts, tasks in group spaces will
>> have an "owner" column, which can be edited to identify who in the
>> group is responsible for the task. Ideally, the value of this column
>> would autocomplete with the names of group members, but could also be
>> typed in if you wanted to assign it to someone external, or to a
>> generic role like "QA".
>> - Each member of the group can either be an administrator, regular
>> member, or read-only viewer. Only administrators can add/remove
>> members. Regular members can add, edit, and view tasks, and read-only
>> viewers can only view.
>> - Because it's important to have a "what's new" page where you can
>> catch up on what other group members have done while you were away, I
>> think an important feature would be a "group home page" that shows
>> recent changes -- new tasks, notes / modifications to existing tasks,
>> etc. Something like:
>> * task "implement foo widget": owner changed from 'QA' to 'bob' by bob.
>> This sort of change tracking might actually be useful to Voo2do users
>> outside of the group feature, but I think is especially important when
>> multiple people can potentially be modifying the same tasks.
>> There are other features I can think of that might be potentially
>> useful, like having a general group notes section or file storage.
>> Initially, though, I think it would be best to focus on the task
>> tracking that is Voo2do's strength rather than trying to be everything
>> for groups.
>> I'd love to hear what people who do group work think of this general approach:
>> - does this sound like something you would use?
>> - what would make it better?
>> - are there any ways to make it simpler? is there something
>> unnecessary that could be left out (at least, left out of the initial
>> version)?
Sounds perfect. I can't wait for this option to be implemented. Thank
you Shimon for the ever useful Voo2Do and for expanding upon it as
your users need.
On Aug 24, 9:52 am, Shimon Rura <shi...@rura.org> wrote:
> I think the invitation process would work by you entering the
> invitee's email address. Voo2do would email them a special
> one-time-use link that offers them the option to join your group
> space. If they have a Voo2do account already, they would be prompted
> to join your space using their existing account. If they didn't want
> to do that, or didn't have a Voo2do account, they could create one,
> and once signup was completed, they'd again be prompted to join the
> group space.
> When adding a member, you'd specify whether they should be an admin,
> regular member, or read-only viewer. Admins would also be able to
> change permissions for existing users, with the only constraint being
> that at least one user must be classified as an administrator for the
> group space.
> > That sounds great Shimon!
> > So we could concider our own area, "Our Space" and these new "Group
> > Spaces" as you call them are shared with various people. Sounds
> > perfect, most everyone I work with now has switched to Voo2Do, so
> > it'll be extremely easy to get them on top of things if we share a
> > space. It doesn't sound too complex, the only thing I am wondering
> > about is of course the creator would be n the Admin level, but how do
> > you invite other users?
> > On Aug 23, 7:40 pm, Voo2do Support <voo2dosupp...@gmail.com> wrote:
> >> Thanks everyone for your suggestions regarding collaboration via
> >> Voo2do. I've been thinking about enhancing Voo2do's collaboration
> >> features, and considering ways to add in these improvements without
> >> making Voo2do overwhelming for people who just need a simple tool for
> >> individual use.
> >> I'd like to propose one way I've been thinking about to achieve this,
> >> and see if it sounds reasonable to you and other folks on this list.
> >> The basis of collaboration will be a Group Space. A Group Space is
> >> kind of like a Voo2do user account - it can contain contexts,
> >> projects, and tasks - but instead of logging into it, you create or
> >> join a Group Space using your existing (or new) Voo2do account.
> >> - All tasks / projects / contexts / notes in a group space are visible
> >> to all members of the group. Contexts from the group space appear on
> >> each user's dashboard page. (Perhaps there is a way for each user to
> >> quickly toggle the display of various groups on their dashboard.)
> >> - Like the current collaborative contexts, tasks in group spaces will
> >> have an "owner" column, which can be edited to identify who in the
> >> group is responsible for the task. Ideally, the value of this column
> >> would autocomplete with the names of group members, but could also be
> >> typed in if you wanted to assign it to someone external, or to a
> >> generic role like "QA".
> >> - Each member of the group can either be an administrator, regular
> >> member, or read-only viewer. Only administrators can add/remove
> >> members. Regular members can add, edit, and view tasks, and read-only
> >> viewers can only view.
> >> - Because it's important to have a "what's new" page where you can
> >> catch up on what other group members have done while you were away, I
> >> think an important feature would be a "group home page" that shows
> >> recent changes -- new tasks, notes / modifications to existing tasks,
> >> etc. Something like:
> >> * task "implement foo widget": owner changed from 'QA' to 'bob' by bob.
> >> This sort of change tracking might actually be useful to Voo2do users
> >> outside of the group feature, but I think is especially important when
> >> multiple people can potentially be modifying the same tasks.
> >> There are other features I can think of that might be potentially
> >> useful, like having a general group notes section or file storage.
> >> Initially, though, I think it would be best to focus on the task
> >> tracking that is Voo2do's strength rather than trying to be everything
> >> for groups.
> >> I'd love to hear what people who do group work think of this general approach:
> >> - does this sound like something you would use?
> >> - what would make it better?
> >> - are there any ways to make it simpler? is there something
> >> unnecessary that could be left out (at least, left out of the initial
> >> version)?
Your proposal sounds great ! I hope you can get it implemented
soon ;-)))
I have one suggestion. An extra option (checkbox) where the owner of
the task can enable/disable editing certain aspects of the task for
other admin level users.
For example, changing owner of the task. In some cases, i would want
to remain owner.
I think i would call it : "task access" full / limited (along
those lines ;-)
