UX/UI and tasks #516
Comments
|
If I had more time on the Verdun NRP I certainly gone in on this, as it's a
useful analytic on both sides.
…On Thu, Aug 30, 2018, 12:14 AM TiberiusB ***@***.***> wrote:
A discussion about onboarding brought up some issues with Sensorica's
NRP-CAS.
https://groups.google.com/d/msg/sensorica/pfqy3N4z81Q/dkmIrGxiCQAJ
In an open network like Sensorica *we should expect fresh people coming
to project and be able to easily contribute with low barriers to entry.*
Barriers are of different types, and an important one is general knowledge
about the project, where to start, what to do, how to do it, etc.
Projects should be conducted in a way that encourage *stigmergy* - allow
new comers to easily build on someone else's work. Sensorica deals with
that by setting up planning using Recipes and setting up Google docs to
document the work, the progress, what has been done, what's being done and
cues about what others should do next.
When it comes to planning using Recipes, sensoricans create processes that
have time dependencies and input-output dependencies. These processes
contain tasks or Work requirements. People engage by executing these tasks
collaboratively and logging their contributions within these tasks, in
processes, which are set up in a Project context.
From Sensorica's experience, some tasks require minimal knowledge about
the project as a whole or about the Sensorica network as a whole, while
other tasks require a lot of experience with the network or the project.
*New requirement:*
- It would be nice to have these tasks or Work requirements marked
with experience levels.
- New comers can search, find and engage with tasks that demand low
experience.
- Furthermore, we can even imagine the system automatically adjusting
to provide automatic access to new comers to these low experience required
tasks, and block them to engage in tasks that require a lot of knowledge
about the project. As these new comers contribute to the project they
automatically earn the right to engage in higher experience level tasks.
- We can even consider adding weights to different experience level
tasks that can be taken into consideration in the Value Equation.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#516>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFTjLkHJRoDuLPeN7tF1v0bfogufBfYYks5uV2aagaJpZM4WSvyV>
.
|
|
No worries.
I am.continuing to record issues and requirements for later :)
…On Thu, Aug 30, 2018, 14:02 sqykly ***@***.***> wrote:
If I had more time on the Verdun NRP I certainly gone in on this, as it's a
useful analytic on both sides.
On Thu, Aug 30, 2018, 12:14 AM TiberiusB ***@***.***> wrote:
> A discussion about onboarding brought up some issues with Sensorica's
> NRP-CAS.
> https://groups.google.com/d/msg/sensorica/pfqy3N4z81Q/dkmIrGxiCQAJ
>
> In an open network like Sensorica *we should expect fresh people coming
> to project and be able to easily contribute with low barriers to entry.*
> Barriers are of different types, and an important one is general
knowledge
> about the project, where to start, what to do, how to do it, etc.
>
> Projects should be conducted in a way that encourage *stigmergy* - allow
> new comers to easily build on someone else's work. Sensorica deals with
> that by setting up planning using Recipes and setting up Google docs to
> document the work, the progress, what has been done, what's being done
and
> cues about what others should do next.
> When it comes to planning using Recipes, sensoricans create processes
that
> have time dependencies and input-output dependencies. These processes
> contain tasks or Work requirements. People engage by executing these
tasks
> collaboratively and logging their contributions within these tasks, in
> processes, which are set up in a Project context.
> From Sensorica's experience, some tasks require minimal knowledge about
> the project as a whole or about the Sensorica network as a whole, while
> other tasks require a lot of experience with the network or the project.
>
> *New requirement:*
>
> - It would be nice to have these tasks or Work requirements marked
> with experience levels.
> - New comers can search, find and engage with tasks that demand low
> experience.
> - Furthermore, we can even imagine the system automatically adjusting
> to provide automatic access to new comers to these low experience
required
> tasks, and block them to engage in tasks that require a lot of knowledge
> about the project. As these new comers contribute to the project they
> automatically earn the right to engage in higher experience level tasks.
> - We can even consider adding weights to different experience level
> tasks that can be taken into consideration in the Value Equation.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#516>, or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AFTjLkHJRoDuLPeN7tF1v0bfogufBfYYks5uV2aagaJpZM4WSvyV
>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#516 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADu2SXei90RqcJPqtkZGrn29nVw14soDks5uWCi1gaJpZM4WSvyV>
.
|
|
I might have some other work coming up, but if it falls through, I'm
interested in doing this. We'll have to discuss what metrics to use to
quantify experience - we could go very simple (e.g. years or work completed
within the NRP-CAS) but that would seem to miss a lot of cases and cost
people value. Obviously it can't be both perfectly inclusive and
computationally practical, but the new economy is for everyone, right?
In case someone else does end up with this, I'll go ahead and give you my
thoughts so far and hope it helps them. I'll also be happy to consult if
it will be helpful.
There is a feature already implemented that matches agents in the network
to tasks that require their skills and sends email notifications. There
are also several ways to search for work that fits an agent's skills,
though none of them are terribly elegant from a UX perspective. The
principle difference between those functions and the new requirements would
seem to be that skills (encapsulated as work resource types) need to be
graded instead of binary. I.e. "how great can you make lemonade?" instead
of "have you ever made lemonade?". If that's an accurate assessment, it
shouldn't take too long to hunt down and change those functions such that
they discriminate between skill levels. There ought to be only a few view
functions, their corresponding templates, and an additional associative
field in the process model that holds that information.
The value equations and task restrictions are a little trickier, though
absolutely doable once the exact specifications are known. Resources
(including work) have a quality parameter already, but I don't believe it
is used in any of the value equation models or UI. These models have some
hairy, tense code that should be regression tested early and often.
Whoever makes these modifications should also avoid chasing the value
equations algorithms around the rest of the model; that would take forever
and I am maybe 80% certain it won't be necessary.
Hope that helps.
David Hand
[email protected]
…On Mon, Sep 3, 2018, 1:00 AM TiberiusB ***@***.***> wrote:
No worries.
I am.continuing to record issues and requirements for later :)
On Thu, Aug 30, 2018, 14:02 sqykly ***@***.***> wrote:
> If I had more time on the Verdun NRP I certainly gone in on this, as
it's a
> useful analytic on both sides.
>
> On Thu, Aug 30, 2018, 12:14 AM TiberiusB ***@***.***>
wrote:
>
> > A discussion about onboarding brought up some issues with Sensorica's
> > NRP-CAS.
> > https://groups.google.com/d/msg/sensorica/pfqy3N4z81Q/dkmIrGxiCQAJ
> >
> > In an open network like Sensorica *we should expect fresh people coming
> > to project and be able to easily contribute with low barriers to
entry.*
> > Barriers are of different types, and an important one is general
> knowledge
> > about the project, where to start, what to do, how to do it, etc.
> >
> > Projects should be conducted in a way that encourage *stigmergy* -
allow
> > new comers to easily build on someone else's work. Sensorica deals with
> > that by setting up planning using Recipes and setting up Google docs to
> > document the work, the progress, what has been done, what's being done
> and
> > cues about what others should do next.
> > When it comes to planning using Recipes, sensoricans create processes
> that
> > have time dependencies and input-output dependencies. These processes
> > contain tasks or Work requirements. People engage by executing these
> tasks
> > collaboratively and logging their contributions within these tasks, in
> > processes, which are set up in a Project context.
> > From Sensorica's experience, some tasks require minimal knowledge about
> > the project as a whole or about the Sensorica network as a whole, while
> > other tasks require a lot of experience with the network or the
project.
> >
> > *New requirement:*
> >
> > - It would be nice to have these tasks or Work requirements marked
> > with experience levels.
> > - New comers can search, find and engage with tasks that demand low
> > experience.
> > - Furthermore, we can even imagine the system automatically adjusting
> > to provide automatic access to new comers to these low experience
> required
> > tasks, and block them to engage in tasks that require a lot of
knowledge
> > about the project. As these new comers contribute to the project they
> > automatically earn the right to engage in higher experience level
tasks.
> > - We can even consider adding weights to different experience level
> > tasks that can be taken into consideration in the Value Equation.
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub
> > <#516>, or mute the
thread
> > <
>
https://github.com/notifications/unsubscribe-auth/AFTjLkHJRoDuLPeN7tF1v0bfogufBfYYks5uV2aagaJpZM4WSvyV
> >
> > .
> >
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <
#516 (comment)>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/ADu2SXei90RqcJPqtkZGrn29nVw14soDks5uWCi1gaJpZM4WSvyV
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#516 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFTjLtmFk2mZ1Q_HTdJC4CsvfTfY7bDsks5uXLddgaJpZM4WSvyV>
.
|
|
There's a class AgentResourceType with a field called score.
A skill is a ResourceType. The score is updated by EconomicEvents, so if
somebody does something using that skill, their score gets increased by the
quantity of the event.
That was an experiment to start keeping some stats on people's work and
also receipts from suppliers. Hasn't been used much as far as I know. I
also don't know how accurate it is, but it would be easy to regenerate by
replaying the events.
And the score could be computed differently, too. Start using the quality
field, for example.
But it's a place in the model for doing that kind of thing.
…On Tue, Sep 4, 2018 at 11:02 AM, sqykly ***@***.***> wrote:
I might have some other work coming up, but if it falls through, I'm
interested in doing this. We'll have to discuss what metrics to use to
quantify experience - we could go very simple (e.g. years or work completed
within the NRP-CAS) but that would seem to miss a lot of cases and cost
people value. Obviously it can't be both perfectly inclusive and
computationally practical, but the new economy is for everyone, right?
In case someone else does end up with this, I'll go ahead and give you my
thoughts so far and hope it helps them. I'll also be happy to consult if
it will be helpful.
There is a feature already implemented that matches agents in the network
to tasks that require their skills and sends email notifications. There
are also several ways to search for work that fits an agent's skills,
though none of them are terribly elegant from a UX perspective. The
principle difference between those functions and the new requirements would
seem to be that skills (encapsulated as work resource types) need to be
graded instead of binary. I.e. "how great can you make lemonade?" instead
of "have you ever made lemonade?". If that's an accurate assessment, it
shouldn't take too long to hunt down and change those functions such that
they discriminate between skill levels. There ought to be only a few view
functions, their corresponding templates, and an additional associative
field in the process model that holds that information.
The value equations and task restrictions are a little trickier, though
absolutely doable once the exact specifications are known. Resources
(including work) have a quality parameter already, but I don't believe it
is used in any of the value equation models or UI. These models have some
hairy, tense code that should be regression tested early and often.
Whoever makes these modifications should also avoid chasing the value
equations algorithms around the rest of the model; that would take forever
and I am maybe 80% certain it won't be necessary.
Hope that helps.
David Hand
***@***.***
On Mon, Sep 3, 2018, 1:00 AM TiberiusB ***@***.***> wrote:
> No worries.
> I am.continuing to record issues and requirements for later :)
>
> On Thu, Aug 30, 2018, 14:02 sqykly ***@***.***> wrote:
>
> > If I had more time on the Verdun NRP I certainly gone in on this, as
> it's a
> > useful analytic on both sides.
> >
> > On Thu, Aug 30, 2018, 12:14 AM TiberiusB ***@***.***>
> wrote:
> >
> > > A discussion about onboarding brought up some issues with Sensorica's
> > > NRP-CAS.
> > > https://groups.google.com/d/msg/sensorica/pfqy3N4z81Q/dkmIrGxiCQAJ
> > >
> > > In an open network like Sensorica *we should expect fresh people
coming
> > > to project and be able to easily contribute with low barriers to
> entry.*
> > > Barriers are of different types, and an important one is general
> > knowledge
> > > about the project, where to start, what to do, how to do it, etc.
> > >
> > > Projects should be conducted in a way that encourage *stigmergy* -
> allow
> > > new comers to easily build on someone else's work. Sensorica deals
with
> > > that by setting up planning using Recipes and setting up Google docs
to
> > > document the work, the progress, what has been done, what's being
done
> > and
> > > cues about what others should do next.
> > > When it comes to planning using Recipes, sensoricans create processes
> > that
> > > have time dependencies and input-output dependencies. These processes
> > > contain tasks or Work requirements. People engage by executing these
> > tasks
> > > collaboratively and logging their contributions within these tasks,
in
> > > processes, which are set up in a Project context.
> > > From Sensorica's experience, some tasks require minimal knowledge
about
> > > the project as a whole or about the Sensorica network as a whole,
while
> > > other tasks require a lot of experience with the network or the
> project.
> > >
> > > *New requirement:*
> > >
> > > - It would be nice to have these tasks or Work requirements marked
> > > with experience levels.
> > > - New comers can search, find and engage with tasks that demand low
> > > experience.
> > > - Furthermore, we can even imagine the system automatically adjusting
> > > to provide automatic access to new comers to these low experience
> > required
> > > tasks, and block them to engage in tasks that require a lot of
> knowledge
> > > about the project. As these new comers contribute to the project they
> > > automatically earn the right to engage in higher experience level
> tasks.
> > > - We can even consider adding weights to different experience level
> > > tasks that can be taken into consideration in the Value Equation.
> > >
> > > —
> > > You are receiving this because you are subscribed to this thread.
> > > Reply to this email directly, view it on GitHub
> > > <#516>, or mute the
> thread
> > > <
> >
> https://github.com/notifications/unsubscribe-auth/
AFTjLkHJRoDuLPeN7tF1v0bfogufBfYYks5uV2aagaJpZM4WSvyV
> > >
> > > .
> > >
> >
> > —
> > You are receiving this because you authored the thread.
> > Reply to this email directly, view it on GitHub
> > <
> #516 (comment)
>,
> > or mute the thread
> > <
> https://github.com/notifications/unsubscribe-auth/
ADu2SXei90RqcJPqtkZGrn29nVw14soDks5uWCi1gaJpZM4WSvyV
> >
> > .
> >
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#516#
issuecomment-418000523>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AFTjLtmFk2mZ1Q_
HTdJC4CsvfTfY7bDsks5uXLddgaJpZM4WSvyV>
> .
>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#516 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAHKvwQmS1oPB-9MKhRXC1qmdhXIQI2eks5uXqQzgaJpZM4WSvyV>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A discussion about onboarding (instigated by Drew) brought up some issues with Sensorica's NRP-CAS.
https://groups.google.com/d/msg/sensorica/pfqy3N4z81Q/dkmIrGxiCQAJ
In an open network like Sensorica we should expect fresh people coming to project and be able to easily contribute with low barriers to entry. Barriers are of different types, and an important one is general knowledge about the project, where to start, what to do, how to do it, etc.
Projects should be conducted in a way that encourage stigmergy - allow new comers to easily build on someone else's work. Sensorica deals with that by setting up planning using Recipes and setting up Google docs to document the work, the progress, what has been done, what's being done and cues about what others should do next.
When it comes to planning using Recipes, sensoricans create processes that have time dependencies and input-output dependencies. These processes contain tasks or Work requirements. People engage by executing these tasks collaboratively and logging their contributions within these tasks, in processes, which are set up in a Project context.
From Sensorica's experience, some tasks require minimal knowledge about the project as a whole or about the Sensorica network as a whole, while other tasks require a lot of experience with the network or the project.
New requirement:
The text was updated successfully, but these errors were encountered: