- use cases
- might be a need fo folks who are not an admin of the collective to be able to okay expenses for a project
- modulo - each projec tis a workshowp - they want each teacher/student of the workshop to submit expenses there
- tenants united south chicago - using it to create funds as an umbrella under each fund
prioritisation sequencing
-
earmarking and operating a spearate budget is the killer feature, eerything else is nice to have
-
trasnferring budget from collective into a project, and visa versa
-
could alrady run around the back and contribute as the collective to the project,
-
this has the tips flow, but maybe doesn't take sense
-
normally would happen for events at the end of the event, but there's no concept of this for projects
-
goals
-
supported for tiers
-
supported for collectives
-
not put in events at the moment - def an overlap
-
could cause some confusion between projects or tiers
-
could remove tier goals from collectives and state as project goals only,
-
some examples of collectives using this feature at the moment https://opencollective.com/bushwick-ayuda-mutua
-
might need to make a judgetment call on what flow we want to support for the above
-
project tiers should also be supported, to offer benefits
-
currently built from events (minus events like data)
-
currently all admins of a collective are admins of a project
-
low hanging fruit opportunities
-
could be given to all collectives/hosts
-
are projects 'profiles' (first class entities) YUP
-
documentation needed
-
could release it for everyone without 'beta' (but could use this for feedback purposes)
-
could lead with docs and get this out, but add the 'transfer' flow as a nice to have.
-
could lead with docs for the 'transfer to/from'
current onboarding flow:
- need to code the support for all collectives
- need to unblock the current code to add other collectives
missing - unified budget between colleactive and its projects balance does not include balance on the project's - might want to include or exclude this maybe this should map to something like github, one collective for each org an one project for each repo.
used to have the concept of 'super collectives' which was killed we have today 'related collectives' which are a more lightweight association, no sharing of admins, hosts or budgets
feels like we should craete those barreirs, and could use features to do this could build the process through - maybe having supportfor 1-2 'sub admins' but if you need more then you start a collective should we support the growth projects into collectives, or to shrink a collective into a project? could add this to the profile settings page
- should be able to fit that and the settings in plan
- needs: marketing, documentation schnchronisation proejct baord rollout - could make it an opt in instead of roll out
next steps ben to update this issue, create a project board, simplify, tag peeps in and gopher it target to release to collectives on an opt in basis
feedback 'when you want to sell a t shirt maybe the feature should be called somethign else' - we have a lot of generic features. we need to figure this out - feels like are setting ourselves up by looking at the 'add transfer' want to know more from users before diving into this. RELEASE the DIRTY FEATURE WITH DOCS FIRST