I understand this has been taken care for Arizona meetings but this could be a question that others have regarding the 12-step meeting list by Code 4 Recovery. Yes there are a few different way the plugin can be used. We do not use it like AA. Other 12-step fellowships use is as we do.
Version one of he 12-step meeting list can be used as a central database system maintained by volunteer(s) allowing for oversight and continuity to the lists.
a. This the method used by our fellowship so that an overall continuity can be maintained.
b. Each local group is responsible for local maintenance of the local list.
c. Each local group is responsible to also pass the local meeting information on to the CMA-GSO registrar. Sample: Los Angeles has a form to update meetings for new meetings, updating current meetings of making notice to delete a meeting. It is similar to the CMA-GSO update system except it sends it’s information to both the local group registrar and to CMA-GSO registrar.
Only about 1/3 of CMA local websites are built using a compatible operating system. This is the way CMA meeting lists have always worked for all CMA meetings.
Version two of the 12-step meeting list can be used to read in-person only local intergroup in-person meeting lists or only the on-line aa-intergroup on-line meeting list. This requires local group to maintain and publish a public list of in-person only local meetings. This system is generally used for two separate feeds types to an apps for mobile devices. One feed is “in-person” only meeting types. The second feed serves the on-line community (sample: aa-intergroup.org)
You will note the only worldwide meeting list for AA is on an mobile App. Either (the Meeting Guide) for local in-person AA meetings and (Everything AA) for everything online. This means on-line only and hybrid meetings are both responsible to inform aa-intergroup of their existence.
-
This reply was modified 2 weeks, 4 days ago by
Pete S.
-
This reply was modified 2 weeks, 4 days ago by
Pete S.
-
This reply was modified 2 weeks, 4 days ago by
Pete S.