vera @vera  ·  2 years ago

I have a suggestion for Bonfire: @BonfireBuilders #bonfire_feedback What is an example circle name with associated boundary name? I'm trying to figure out the best way to structure in my head. I have a circle for "devs" but I'm not sure the best boundary to make or if I can reuse an existing one

Mayel
Mayel @mayel  ·  2 years ago
@vera There are a few examples in the screenshots on the blog post: https://bonfirenetworks.org/posts/introducing_boundaries/



Transcribing them here:


Example circles

  • Besties
  • In-laws
  • Trip mates


Example boundaries

  • Memes & lols
  • Summer '22 trip
  • It takes a village


One way to think about it is circle names are simply about what the people in them have in common, whilst boundary names should probably be more about what kind of content you'll share and what permissions you'll grant over it to whom (note that a boundary can contain multiple circles and individual users, granting different permissions to each).


So extending your example, I could imagine having:


Circles

  • Devs
  • Bonfire devs
  • Techies


Boundaries

  • Tech stuff (granting see/read/interact permissions to those 3 circles)
  • Coding resources (granting the same to the first 2 circles)
  • Bonfire collab (granting additional permissions to Bonfire devs circle, like the ability to edit and delete)
Mayel
Mayel @mayel  ·  2 years ago
@vera There are a few examples in the screenshots on the blog post: https://bonfirenetworks.org/posts/introducing_boundaries/



Transcribing them here:


Example circles

  • Besties
  • In-laws
  • Trip mates


Example boundaries

  • Memes & lols
  • Summer '22 trip
  • It takes a village


One way to think about it is circle names are simply about what the people in them have in common, whilst boundary names should probably be more about what kind of content you'll share and what permissions you'll grant over it to whom (note that a boundary can contain multiple circles and individual users, granting different permissions to each).


So extending your example, I could imagine having:


Circles

  • Devs
  • Bonfire devs
  • Techies


Boundaries

  • Tech stuff (granting see/read/interact permissions to those 3 circles)
  • Coding resources (granting the same to the first 2 circles)
  • Bonfire collab (granting additional permissions to Bonfire devs circle, like the ability to edit and delete)
+ -