-
Notifications
You must be signed in to change notification settings - Fork 43
Add a blog post the new event management system and Champion program #103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 6 commits
606b189
6c139ba
067bb8c
60a8334
54dc0ca
8327fe4
ffaa031
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| --- | ||
| title: "Your blog post title" | ||
| description: | | ||
| This is short description about my blog. | ||
| author: | ||
| - name: YOUR NAME | ||
| url: https://github.com/kozo2 | ||
| date: 2022-10-26 | ||
| categories: | ||
| - SOME_TAG | ||
| preview: "cover.png" | ||
| --- | ||
|
|
||
| SOME MARKDOWN HERE. | ||
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,184 @@ | ||||||||||||||||||||||||||||||||||||||
| --- | ||||||||||||||||||||||||||||||||||||||
| title: "Introducing Bioconductor's New Event Management System and Champion Program" | ||||||||||||||||||||||||||||||||||||||
| description: | | ||||||||||||||||||||||||||||||||||||||
| Learn about the transition from GitHub Issue Forms to an automated event management system using Google Forms and Google Apps Script, and how the Bioconductor Champion Program supports event organizers. | ||||||||||||||||||||||||||||||||||||||
| author: | ||||||||||||||||||||||||||||||||||||||
| - name: Kozo Nishida | ||||||||||||||||||||||||||||||||||||||
| url: https://github.com/kozo2 | ||||||||||||||||||||||||||||||||||||||
| date: 2026-02-20 | ||||||||||||||||||||||||||||||||||||||
| categories: | ||||||||||||||||||||||||||||||||||||||
| - community | ||||||||||||||||||||||||||||||||||||||
| - events | ||||||||||||||||||||||||||||||||||||||
| - automation | ||||||||||||||||||||||||||||||||||||||
| format: | ||||||||||||||||||||||||||||||||||||||
| html: | ||||||||||||||||||||||||||||||||||||||
| toc: true | ||||||||||||||||||||||||||||||||||||||
| --- | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| ## Introduction | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| The Bioconductor community is dedicated to fostering collaboration and knowledge sharing through various community events worldwide. As our community continues to grow, we recognized the need to improve our event management processes to better serve both event organizers and participants. This post introduces our new automated event management system and the exciting opportunities it brings for community members. | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| ## Challenges with the Previous System | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| Previously, Bioconductor used GitHub Issue Forms to manage event applications. While this approach aligned with our development workflow, it presented several significant challenges that limited its effectiveness: | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| ### Requirement for a GitHub Account | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| Event applicants were required to have their own GitHub account to submit a request. This created an unnecessary barrier to entry, particularly for: | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| - Community members who are new to open source development | ||||||||||||||||||||||||||||||||||||||
| - Event organizers who primarily focus on teaching and outreach rather than software development | ||||||||||||||||||||||||||||||||||||||
| - Participants from regions where GitHub may not be the primary collaboration platform | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| This requirement essentially excluded potential event organizers who could contribute valuable activities to the Bioconductor community but didn't have or want to create a GitHub account. | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| ### Lack of Privacy | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| Since GitHub Issues do not have a private mode, it was impossible to process event applications that required privacy or confidentiality. This limitation meant that: | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| - All event application details were publicly visible | ||||||||||||||||||||||||||||||||||||||
| - Sensitive information such as budget details, venue negotiations, or personal contact information could not be safely included | ||||||||||||||||||||||||||||||||||||||
| - Some organizers were hesitant to apply due to concerns about public disclosure of planning details | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| This lack of privacy was particularly problematic for events in their early planning stages or those involving sensitive institutional relationships. | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| ### Risk of Oversight | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| There was a significant risk of missing new event applications if GitHub notifications were not monitored consistently. GitHub's notification system, while powerful for development workflows, is not optimized for managing event applications: | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| - Notifications could get lost among other repository activities | ||||||||||||||||||||||||||||||||||||||
| - No dedicated workflow for tracking application status | ||||||||||||||||||||||||||||||||||||||
| - Difficult to ensure timely responses to applicants | ||||||||||||||||||||||||||||||||||||||
| - No automated reminders or follow-up mechanisms | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| These challenges highlighted the need for a more streamlined, accessible, and privacy-conscious solution. | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| To visualize the manual steps and potential bottlenecks, the diagram below summarizes the current workflow we are replacing. | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
|  | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| ## Transition to an Automated System | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| To address these limitations, we have developed a new automated event management system using Google Forms and Google Apps Script. This solution is available in the [@kozo2/bioc-event-workflow](https://github.com/kozo2/bioc-event-workflow) repository. | ||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||
| To address these limitations, we have developed a new automated event management system using Google Forms and Google Apps Script. This solution is available in the [@kozo2/bioc-event-workflow](https://github.com/kozo2/bioc-event-workflow) repository. | |
| To address these limitations, we have developed a new automated event management system using Google Forms and Google Apps Script. This solution is available in the [kozo2/bioc-event-workflow](https://github.com/kozo2/bioc-event-workflow) repository. |
Copilot
AI
Feb 12, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section uses https://www.bioconductor.org/help/events/ here, but later links to https://bioconductor.org/help/events/. Consider standardizing on a single canonical URL format to avoid redirects and keep links consistent.
| 3. **Submit and Confirm**: After submission, you'll receive an automated acknowledgment email confirming that your application has been received. | |
| 4. **Review Process**: The Bioconductor community team will review your application and typically respond within two weeks with: | |
| - Approval and posting of the event information at https://www.bioconductor.org/help/events/ | |
| - Requests for additional information | |
| - Suggestions for event improvement | |
| - Information about available support resources | |
| 5. **Event Planning Support**: Once approved, you'll receive guidance on: | |
| 3. **Submit and Confirm**: After submission, you'll receive an automated acknowledgment email confirming that your application has been received. | |
| 4. **Review Process**: The Bioconductor community team will review your application and typically respond within two weeks with: | |
| - Approval and posting of the event information at https://bioconductor.org/help/events/ | |
| - Requests for additional information | |
| - Suggestions for event improvement | |
| - Information about available support resources | |
| 5. **Event Planning Support**: Once approved, you'll receive guidance on: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file appears to be a placeholder/template post (e.g., "Your blog post title", "YOUR NAME", "SOME MARKDOWN HERE"). Publishing this would add incomplete content to the blog, and it also doesn’t align with the PR’s stated purpose. Please remove this file from the PR or replace it with the finalized Hacktoberfest post content.