Bellisseria Event Calendar?

[Nika Talaj]

There have been a few attempts to put together a calendar of Belli events.  @Kitten Kaos started one, it seems to be gone now.  The Bellisserian had an area for events, now gone.  The Pirate DJs calendar is gone. One problem seems to be that, in order to be sure a calendar doesn't get cluttered, calendars are generally maintained by a single person.  When that person gets busy in RL, the calendar disappears.

Bellisseria on Ice wraps up today with DJ sets from10AM to 4, SLT.  Their Google calendar has been really helpful.

https://sites.google.com/view/bellisseria-on-ice/event-calender/event-calender?authuser=0

Google calendars in general are great tools, but they're easier to maintain for a short event like this one.

When I was active in Caledon, their calendar was maintained by a few people.  Some posted for specific interest groups (like the Oxbridge school), some not.  But Caledon is both orders of magnitude smaller and much more close-knit than far-flung Bellisseria.

While writing this message, I've been mulling over how managing a Belli calendar could work:

> Create an avatar called BellisseriaEvents.  The avatar would be managed by a group of avatars (yes, LL would have to approve that) whose typists would also be also approved to update one or more Belli Google calendars; the email account for this avatar would also be shared.   Events would be submitted to this avatar via full perm notecard.  Anyone in the group of maintainers could decide to post or ignore an event.  If your event is not posted, the notecard should be returned with a brief reason for denial.  No appeals - people need to regard listing in the calendar as a favor done by volunteers, not as a right.  At times, events might not be posted because maintainers are all busy.  Life happens.

There should be a policy, a simple bulleted list, of types of events that will and won't be accepted for the calendar.  E.G. No personal celebrations, eg. birthdays, partnerings, remembrances, etc..  It would be great if this policy were short enough to be part of the event submittal form.

Anyone who importunes or otherwise harasses BellisseriaEvents, or any of the calendar maintainers, will be blocked by BellisseriaEvents, and thus have no way to submit calendar requests.

Thoughts?

[Vega Firelyte]

Instead of one av, with people logging on that one individual, would it not work with a small team, working together on their own avs?  For example, a 4-5 person team, with one email or website for people to submit event forms to, for the event calendar?  With Google, you can share documents, so you could create a google doc that would allow for 4-5 people to have access to it, in order keep it updated.  Also, there is the option of maybe a small forum, for events and such, where you have a thread where people could submit their requests, when the request is done and put on calendar, it is shut down by one of the team members.  We did that one for the GTFO hub requests.

[Jadziyah Nova]

Firstly, I absolutely agree there should be a Google Calendar. I'm honestly shocked there isn't one already. Clubs, stores, friend groups, etc in SL use them all the time. I've seen a lot of people in group chat not knowing an event was happening- not all events are posted to NC, or they miss the nc, blah blah. Obviously no personal celebrations, only Belli events. I don't think it'd be too cluttered. As far as how to keep it updated:

On 1/4/2020 at 4:48 PM, Vega Firelyte said:

Instead of one av, with people logging on that one individual, would it not work with a small team, working together on their own avs?  For example, a 4-5 person team, with one email or website for people to submit event forms to, for the event calendar?  With Google, you can share documents, so you could create a google doc that would allow for 4-5 people to have access to it, in order keep it updated.  Also, there is the option of maybe a small forum, for events and such, where you have a thread where people could submit their requests, when the request is done and put on calendar, it is shut down by one of the team members.  We did that one for the GTFO hub requests.

Definitely this instead of one shared SL user. Pick a trusted, interested groups of active users and you're all set.