External events and chapters...

[Sarah Allen]

Hi Bridge Troll experts!

As I've been involved with RailsBridge and Bridge Foundry, we usually refer to a "chapter" as a region that has an team who organizes multiple workshops over time.  There isn't really a chapter, unless at least one or two people are willing to step up an be chapter leaders.  

A few years ago, when we were sorting out the refactoring of our organization, including division of responsibility between Chapters, Bridges and Bridge Foundry, we came up with these definitions (we = all of the Bridge boards and Bridge Foundry board, which I think may have been just RailsBridge and Bridge Foundry, but maybe ClojureBridge. I can't remember.)

In Bridge Troll, an event has_one :organization, through: :chapter, so in order to associate an event that I'm entering in the external events interface with a particular Bridge, I need to create a chapter (even if there isn't one by our organization's definitions).  For the ones I entered last week, I left that blank, but I would like to fill that in -- maybe experiment with graphing workshops per bridge.

I think we can absolutely propose changing definitions or plan for some future alteration of the model.  One idea is to define (in Bridge Foundry operations) an "active chapter" as a group of people who organize local events, or something like that.  This would allow for there to be chapters that include individuals who want to organize a single event, but don't necessarily want to take on the commitment for future events.

This may sound a bit nit-picky, but I haven't spent much time with the admin interface of Bridge Troll.  I want to make sure I'm using it correctly, and I figure its an opportunity for me to notice where we might fix up some inconsistencies.

What do you all think?

Sarah

[Lillie Chilen]

I think Bridge Troll and Bridge Foundry have always had a different definition of what is required to be a chapter, and I think life will remain easier if we stick with that. I like your proposal of adding the concept of an "active chapter" to Bridge Foundry operations so that Bridge Troll can keep using the Chapter model to connect a group of events with an Organization and have special permissions for assigned chapter leaders.

(One way that we could distinguish in Bridge Troll between a chapter that just exists for a workshop and an "active chapter" that exists in the Bridge Foundry sense would be that we only assign chapter leaders when there are multiple workshops / people who want to be the chapter leader for a given chapter. The presence of a chapter leader would then indicate "active chapter" status in Bridge Foundry ops terms.)

Travis put together this nice wiki page a few months ago about the data model and permissions in Bridge Troll; it might be helpful as anyone is thinking through this: https://github.com/railsbridge/bridge_troll/wiki/Permissions-Model.

--
You received this message because you are subscribed to the Google Groups "Bridge Troll" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bridge-troll+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Lillie Chilen
@lilliealbert
('li-lee shuh-'leen)

[Sarah Allen]

The wiki page is a great resource.  I like the idea of having "active chapters" simply being those as ones with leaders -- this syncs up our definitions nicely.  I drafted a PR that attempts to clarify the Bridge Foundry operations guide and added pointers to Bridge Troll.  

I'm meeting with Mary, our operations manager tomorrow, and will ask her to review.  Please comment on the PR if you have any feedback.

Thanks!

Sarah