2018 Highlights!

Our Digital Experiences track is back for 2018, along with some great MXP sessions! We'll also present a overview of all the new features in Mura CMS 7.1, as well as some of the top speakers in the Mura community.

Knowledge

MuraCon is the only user conference focused solely on Mura CMS. You'll get two tracks over two full days of presentations by both Mura Team members and the best the Mura community has to offer.

Community

Yep. Community. The heart of every open source project. From newbies to power users, MuraCon gives you the opportunity to share and learn from all of them.

Networking

MuraCon will be held in Sacramento, CA, and will be attended by Mura CMS core developers, along with other key members of the Mura community.

Venue

MuraCon will be hosted at The Sheraton Grand Sacramento Hotel, located at 1230 J Street, Sacramento, CA 95814. It's just minutes away from the California state capitol building and everything else Sacramento has to offer. The conference will run from 8:00 a.m. until 5:00 p.m. on both Thursday, April 5, and Friday, April 6, 2018. Continental breakfast and a lunch will be provided on both days, and are included with your registration fee.

Pricing

MuraCon 2018 has limited capacity, and we expect to sell out well in advance. We strongly encourage early registration.

Hotel Info

We highly recommend booking a room ASAP due to other conferences occurring during the same time frame.

Sponsors

Thank you to each of our sponsors!

MuraCon invites you to take advantage of our sponsorship opportunities. Allow us to help you increase exposure and heighten awareness of your organization with our audience of highly experienced developers, managers, engineers, and executives. Contact Malcolm O'Keeffe at (916) 608-8608 for more information.

Blue River

Platinum Sponsor

Blue River

Blue River developes online user experiences and tools to help companies connect with users, solve technological challenges, and increase revenue and profit. Blue River is also the creator and curator of Mura CMS, an open source Content Management System, powering thousands of sites around the world for top brands and organizations.

Slatwall Commerce

Platinum Sponsor

Slatwall Commerce

Slatwall is the commerce platform you will never outgrow. Designed from the ground up for maximum flexibility, Slatwall enables you to execute marketing strategies that will allow you to capitalize on emerging opportunities. And as you continue to grow, Slatwall excels at integrating with other systems so you can keep your options open.

Open CFML Foundation

Platinum Sponsor

Open CFML Foundation

The mission of the Open CFML Foundation is to increase the awareness and adoption of open source CFML solutions via advocacy and education, to provide support to select open source CFML projects, and to promote the growth and development of the CFML language and related technologies.CFML is at a crossroads, and we believe that open source is essential to the future of CFML.

About

MuraCon 2018 will occur on April 5 & 6, 2018. Featuring two tracks over two full days, MuraCon is the user conference for the Mura Platform. One track will feature sessions by top developers from throughout the Mura community, showing off the latest developments and features in the Mura Platform, while the other will be focused on Digital Marketing and showcase the role content plays in delivering valuable digital experiences.

Location

Sheraton Grand Hotel

Code of Conduct

MuraCon is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.

Sponsors at the conference, sponsor tables, or similar activities are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.

If it is determined that a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund. If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately. Conference staff can be identified by their Badges saying Staff. Also look for us at the Registration Table.

Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.

We expect participants to follow these rules at all conference venues and conference-related social events.

Contact & Emergency Information

If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.

If the matter is especially urgent, please call/contact any of these individuals:

Attendee Procedure for Incident Handling

Keep in mind that all MuraCon staff will be wearing badges with Mura Team or Blue River on it. The conference personnel will also be prepared to handle the incident. All of our MuraCon staff members are informed of the code of conduct policy and guide for handling harassment at the conference. There will be a mandatory staff meeting onsite at the conference when this will be reiterated.

Report the harassment incident (preferably in writing) to conference personnel. All reports are confidential. Please do not disclose public information about the incident until the staff has had sufficient time in which to address the situation. This is as much for your safety and protection as it is the other attendees.

When reporting the event to staff, try to gather as much information as available but do not interview people about the incident. Staff will assist you in writing the report/collecting information.

The important information consists of:

Identifying information (name/badge information) of the participant doing the harassing

The behavior that was in violation

The approximate time of the behavior (if different than the time the report was made)

The circumstances surrounding the incident

Other people involved in the incident

The staff is well informed on how to deal with the incident and how to further proceed with the situation.

If everyone is presently physically safe, involve law enforcement or security only at a victim's request.

If you do feel your safety in jeopardy please do not hesitate to contact local law enforcement by dialing 911. If you do not have a cell phone, you can use any phone or simply ask a MuraCon staff member.

Note: Incidents that violate the Code of Conduct are extremely damaging to the community, and they will not be tolerated. The silver lining is that, in many cases, these incidents present a chance for the offenders, and the community at large, to grow, learn, and become better. The MuraCon staff requests that they be your first resource when reporting a MuraCon related incident, so that they may enforce the Code of Conduct and take quick action toward a resolution.

Staff Procedure for Incident Handling

Also have a good understanding of what is expected from an attendee that wants to report a harassment incident.

Try to get as much of the incident in written form by the reporter. If you cannot, transcribe it yourself as it was told to you. The important information to gather includes the following:

Identifying information (name/badge info) of the participant doing the harassing

The behavior that was in violation

The approximate time of the behavior (if different than the time the report was made)

The circumstances surrounding the incident

Other people involved in the incident

Prepare an initial response to the incident. This initial response is very important and will set the tone for MuraCon. Depending on the severity/details of the incident, please follow these guidelines:

If there is any general threat to attendees or the safety of anyone including conference MuraCon staff members is in doubt, summon security or police

Offer the victim a private place to sit

Ask "is there a friend or trusted person who you would like to be with you?" (if so, arrange for someone to fetch this person)

Ask them "how can I help?"

Provide them with your list of emergency contacts if they need help later

If everyone is presently physically safe, involve law enforcement or security only at a victim's request

There are also some guidelines as to what not to do as an initial response:

Do not overtly invite them to withdraw the complaint or mention that withdrawal is OK. This suggests that you want them to do so, and is therefore coercive. "If you're OK with it [pursuing the complaint]" suggests that you are by default pursuing it and is not coercive.

Do not ask for their advice on how to deal with the complaint. This is a MuraCon staff member's responsibility.

Do not offer them input into penalties. This is the MuraCon staff member's responsibility.

Once something is reported to a staff member, immediately meet with the conference chair and/or event coordinator. The main objective of this meeting is to find out the following:

What happened?

Are we doing anything about it?

Who is doing those things?

When are they doing them?

After the MuraCon staff member meeting and discussion, have a MuraCon staff member (preferably the MuraCon Event Director, or Blue River CEO if available) communicate with the alleged harasser. Make sure to inform them of what has been reported about them. Allow the alleged harasser to give their side of the story to the staff. After this point, if the report stands, let the alleged harasser know what actions will be taken against them.

Some things for the staff to consider when dealing with Code of Conduct offenders:

Warning the harasser to cease their behavior and that any further reports will result in sanctions

Requiring that the harasser avoid any interaction with, and physical proximity to, their victim for the remainder of the event

Ending a talk that violates the policy early

Not publishing the video or slides of a talk that violated the policy

Not allowing a speaker who violated the policy to give (further) talks at the event now or in the future

Requiring that the harasser not volunteer for future events your organization runs (either indefinitely or for a certain time period)

Requiring that the harasser immediately leave the event and not return

Banning the harasser from future events (either indefinitely or for a certain time period)

Removing a harasser from membership of relevant organizations

Publishing an account of the harassment and calling for the resignation of the harasser from their responsibilities (usually pursued by people without formal authority: may be called for if the harasser is the event leader, or refuses to stand aside from the conflict of interest, or similar, typically event MuraCon staff member have sufficient governing rights over their space that this isn't as useful)

Give accused attendees a place to appeal to if there is one, but in the meantime the report stands. Keep in mind that it is not a good idea to encourage an apology from the harasser.

It is very important how we deal with the incident publicly. Our policy is to make sure that everyone aware of the initial incident is also made aware that it is not according to policy and that official action has been taken - while still respecting the privacy of individual attendees. When speaking to individuals (those who are aware of the incident, but were not involved with the incident) about the incident it is a good idea to keep the details out.

Depending on the incident, the conference chair, or designate, may decide to make one or more public announcements. If necessary, this will be done with a short announcement either during the plenary and/or through other channels. No one other than the conference chair or someone delegated authority from the conference chair should make any announcements. No personal information about either party will be disclosed as part of this process.

If some attendees were angered by the incident, it is best to apologize to them that the incident occurred to begin with. If there are residual hard feelings, suggest to them to write an email to the conference chair or to the event coordinator. It will be dealt with accordingly.