Open bmann opened 5 years ago
Starting with Kickback we could generalize for events. The key point in the flow that would benefit from FISSION codes is when the person RSVPs to an event.
But we could further generalize these to the level of any group activity:
Could we further generalize away from an activity?
Availability is a rather common need, ie: an event and a queue, are similar enough in their structures that an availability status would cover both.
We could call it a group?
@hiddentao is iterating on the Kickback architecture -- see https://github.com/wearekickback/KIPs/blob/master/kips/kip-withdrawals.md
Discuss architecture and what common FISSION codes might be a fit to include, vs. which are application specific.
Via Twitter