From 24fd46fcbf1680bf674c61921de9520d27671593 Mon Sep 17 00:00:00 2001 From: Christopher Brousseau Date: Tue, 24 Feb 2026 02:25:09 +0000 Subject: [PATCH 1/2] Update CoC policy page and remove reporting branch --- .../code-of-conduct-policy/contents.lr | 16 ++++-- .../code-of-conduct-reporting/contents.lr | 50 ------------------- PyBay/content/code-of-conduct/contents.lr | 2 - PyBay/templates/layout.html | 12 ++++- 4 files changed, 23 insertions(+), 57 deletions(-) delete mode 100644 PyBay/content/code-of-conduct/code-of-conduct-reporting/contents.lr diff --git a/PyBay/content/code-of-conduct/code-of-conduct-policy/contents.lr b/PyBay/content/code-of-conduct/code-of-conduct-policy/contents.lr index 33ec7f4..d991052 100644 --- a/PyBay/content/code-of-conduct/code-of-conduct-policy/contents.lr +++ b/PyBay/content/code-of-conduct/code-of-conduct-policy/contents.lr @@ -1,9 +1,17 @@ -_model: redirect ---- -target: /code-of-conduct +_model: page --- _slug: code-of-conduct-policy --- short: Code Of Conduct Policy --- -title: CoC Redirect +title: Code Of Conduct Policy +--- +body: + +

PyBay’s Code of Conduct is maintained on the BAPyA website.

+ +

Please use the link below to view the current version.

+ +

+ Read the full Code of Conduct on BAPyA (external site) +

diff --git a/PyBay/content/code-of-conduct/code-of-conduct-reporting/contents.lr b/PyBay/content/code-of-conduct/code-of-conduct-reporting/contents.lr deleted file mode 100644 index 52397e4..0000000 --- a/PyBay/content/code-of-conduct/code-of-conduct-reporting/contents.lr +++ /dev/null @@ -1,50 +0,0 @@ -_model: page ---- -title: Code of Conduct Reporting Guide ---- -body: - -

Reporting Process

-

In any PyBay space (events or online), if you believe someone is violating the Code of Conduct, we ask that you report it in one of the following ways:

- -
    -
  1. Emailing conduct@pybay.com.
    2. -
  2. If there is a concern about a staff member, please reach out to one of the conference chair, chair@pybay.com .
    3. -
- -

Reports will not be available to all staff, instead, they will be available to a limited subset of staff referred to as the Code of Conduct committee.

- -

All reports will be kept confidential where legally possible. In some cases, we may determine that a public statement will need to be made. If that’s the case, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise. In the event of involvement with law enforcement, we will comply with their requests as legally required.

- -

If you believe anyone is in physical danger, please notify appropriate law enforcement first. In the United States, emergency services can be contacted by dialing 911. If you are unsure which law enforcement agency is appropriate, please include this in your report and we will attempt to notify them.

- -

WHAT TO INCLUDE IN THE REPORT

- -
    -
  1. Your contact information (so we can get in touch with you if we need to follow up)
    2. -
  2. Names of any individuals involved (real names, nicknames, or pseudonyms). If there were other witnesses besides you, please try to include them as well.
    3. -
  3. When and where the incident occurred. Please be as specific as possible.
    4. -
  4. Your account of what occurred. If there is a publicly available record (e.g., a mailing list archive or a public chat logger) please include a link.
    5. -
  5. Any extra context you believe existed for the incident.
    6. -
  6. Whether you believe this incident is ongoing.
    7. -
  7. Any other information you believe we should have.
    8. -
- -

WHAT HAPPENS AFTER YOU FILE A REPORT

- -

The PyBay community team aims to follow the process outlined in the Code of Conduct Response Playbook.

- -

We promise to acknowledge receipt of any reports within 24 hours or sooner, and a resolution (or update in case a resolution is delayed) within 7 days.

- -

Note: If the violation is determined to be an ongoing incident or a threat to physical safety, the staff’s immediate priority will be to protect everyone involved. This means we may delay an "official" response until we believe that the situation has ended and that everyone is physically safe.

- -

Once we determine the final needed action, we’ll contact the original reporter to let them know what action we’ll be taking, if any. Please understand that while we take into account feedback from the reporter on the appropriateness of our response, we cannot guarantee we can or will act on it.

- -

Finally, the staff may choose to make a public report of the incident if it was reported outside one of our conferences.

- -

APPEALING

- -

Only permanent resolutions (such as bans) may be appealed. To appeal a decision, contact the PyBay staff at conduct@pybay.com with your appeal and they will review the case.

- ---- -short: Code of Conduct Reporting Guide diff --git a/PyBay/content/code-of-conduct/contents.lr b/PyBay/content/code-of-conduct/contents.lr index c42c2b9..58c3078 100644 --- a/PyBay/content/code-of-conduct/contents.lr +++ b/PyBay/content/code-of-conduct/contents.lr @@ -78,8 +78,6 @@ Speakers, presenters, and open space organizers

If you believe that someone is violating the Code of Conduct during one of our events, please contact the CoC team immediately by emailing us at conduct@pybay.com.

-

To help us respond in the best way to the situation, please follow the Code of Conduct Reporting. The CoC representatives employ the Code of Conduct Response to handle reports.

-

If you believe a member of staff is violating our Code of Conduct, please reach out to one of the conference chairs, Slava (slavabal@gmail.com) or Hemanti (hemantisd@gmail.com).

All reports will be kept confidential where legally possible. In some cases a public statement might be required (for example in a CoC transparency report following conferences), but these reports are anonymized and do not include any personally identifying information. In the event of involvement with law enforcement, we will comply with their requests as legally required. diff --git a/PyBay/templates/layout.html b/PyBay/templates/layout.html index 7c6206c..3bf8fd4 100644 --- a/PyBay/templates/layout.html +++ b/PyBay/templates/layout.html @@ -295,10 +295,20 @@ color: #ffefb0 !important; } +body.coc-policy-page { + min-height: 100vh; + display: flex; + flex-direction: column; +} + +body.coc-policy-page #main { + flex: 1; +} + - + From fce008d77612455dfad4db773f9242280a09bfab Mon Sep 17 00:00:00 2001 From: Christopher Brousseau Date: Tue, 24 Feb 2026 18:45:18 +0000 Subject: [PATCH 2/2] Fix workshops heading hierarchy for accessibility --- PyBay/content/speaking/workshops/contents.lr | 22 ++++++++++---------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/PyBay/content/speaking/workshops/contents.lr b/PyBay/content/speaking/workshops/contents.lr index ee57632..8ee8b0b 100644 --- a/PyBay/content/speaking/workshops/contents.lr +++ b/PyBay/content/speaking/workshops/contents.lr @@ -13,12 +13,12 @@ Reserve your spot when you buy your ticket. If you have already bought a ticket,
-#####Workshop 1: Azure Database for PostgreSQL workshop##### -######Time: 10:30am - 12:30pm###### -######Title: Build Agentic AI with Semantic Kernel and Graph RAG on PostgreSQL###### -######Abstract###### +## Workshop 1: Azure Database for PostgreSQL workshop +### Time: 10:30am - 12:30pm +### Title: Build Agentic AI with Semantic Kernel and Graph RAG on PostgreSQL +### Abstract In this hands-on lab, you will build an agent-driven Retrieval-Augmented Generation (RAG) application using a U.S. Case Law dataset. You will work with Azure Database for PostgreSQL, Visual Studio Code, and the Semantic Kernel Agent Framework to explore AI-powered text and vector search. The lab also introduces GraphRAG with Apache AGE, enabling enriched querying across structured and graph-based data. By the end, you'll gain practical skills in semantic search, vector indexing, and intelligent data retrieval. -######Topics Covered###### +### Topics Covered Setup your Azure PostgreSQL Database
Launch PSQL Command Line Shell in VS Code
Using AI-driven features in Postgres
@@ -28,12 +28,12 @@ Semantic Agent Configuration and Plugin Assembly

-#####Workshop 2: Azure Cosmos DB workshop##### -######Time: 1:30pm - 3:30pm###### -######Title: Building a Full-Stack FastAPI App with Open Source DocumentDB via Docker###### -######Abstract###### +## Workshop 2: Azure Cosmos DB workshop +### Time: 1:30pm - 3:30pm +### Title: Building a Full-Stack FastAPI App with Open Source DocumentDB via Docker +### Abstract This hands-on lab guides you through the process of building a modern, full-stack web application using FastAPI for the backend and open source DocumentDB as the database, all orchestrated with Docker containers. Attendees will learn how to rapidly prototype and deploy scalable Python APIs, leverage containerization for consistent development and testing, and integrate with DocumentDB for flexible, cloud-ready data storage. -######Topics covered###### +### Topics covered Setting up a FastAPI backend and connecting it to DocumentDB using Docker Compose.
Best practices for local development, testing, and CI/CD integration with Docker.
How open source DocumentDB enables rapid iteration and seamless migration to cloud environments.
@@ -43,7 +43,7 @@ By the end of the lab, you’ll have a working application, a deeper understandi
-####Workshop Sponsor: Microsoft Azure Databases#### +## Workshop Sponsor: Microsoft Azure Databases Azure enriches the database platforms that Python developers rely on to build intelligent apps and agents with less friction. Our fully-managed database services come backed with industry-leading security, compliance and reliability and are equipped with advanced features to support modern workloads. Azure Cosmos DB is a serverless and scalable, low-latency NoSQL database with built-in vector and hybrid search, perfect for powering AI, RAG pipelines, and multi-agent systems. Azure Database for PostgreSQL combines the power of open-source Postgres with enterprise-ready scale and security, is infused with genAI capabilities and natively supports vector data and advanced RAG techniques. And with DocumentDB—our new open-source, MongoDB-compatible engine—you get flexibility and choice backed by the Linux Foundation. All three services integrate seamlessly with Python SDKs and tools, so you can build apps, APIs, and AI workloads faster, without worrying about infrastructure.