People and their projects

[fosterlynn]

Some food for thought: Right now there are two ways (that I can think of) we can tell if a person relates to a project:

1. They have an explicit relationship with the project, PersonX isAffiliateOf ProjectY.
2. They have done some work on the project, i.e. they have work events of any kind recorded for the project.
3. Is this a third? They have contributed financially to a project, perhaps bought components etc.

In practice, most people are affiliates only of Sensorica (the parent of projects), although there are a couple projects where there are direct affiliates: Breathing Games (which originated outside of Sensorica) and NRP UI/UX. :) This is because of the history of the workflow and the software development though. Now a few central people are the only people assigning people to projects, and it basically happens when someone asks to become affiliated with Sensorica up front.

We could feed data to the new project page based on one or both or all methods.

But we also have a chance to change the workflow if we want. For example, people could join projects themselves in a new UI/UX. Possible advantage: They could then get notifications and/or more easily see what is going on in the project before they have actually done any work, thus making it easier to find the project for their first contribution logging.

[Jshcwn]

Hi, @fosterlynn wrote:

But we also have a chance to change the workflow if we want. For example, people could join projects themselves in a new UI/UX. Possible advantage: They could then get notifications and/or more easily see what is going on in the project before they have actually done any work, thus making it easier to find the project for their first contribution logging.

FWIW, I'm in favour of making projects more easily to find no matter where someone is in the process. I actually see project affiliation as way more important info. than org. affiliation especially if recipes and plans span networks.