Add May 2026 status update#788
Merged
Merged
Conversation
mhsmith
approved these changes
May 29, 2026
Member
mhsmith
left a comment
mhsmith
left a comment
There was a problem hiding this comment.
The CI check repeatedly says "https://unital.dev/ is broken", but it works fine for me.
phildini
reviewed
May 29, 2026
|
|
||
| On the technical front, in the coming month, we'll also be looking into options for updating code in a running app; and continuing work on the "big picture" app navigation plan published earlier in the year. If time permits, we'll begin investigations into the use of Conda environments in Briefcase apps. | ||
|
|
||
| We're also planning to step up our efforts to build the BeeWare community. We've developed a reputation at PyCon US for running extremely effective sprints; but we need to do more of that outreach for people who can't make it to PyCon. We've already begun doing an audit of our outstanding issues in the hope of curating a more actionable list of work for contributors; and we're going to start being more active on social media, including reaching out to more social media channels. We're also going to host our first Community Call - a live video event where members of the core team and community members can share what they've been working on. [Join us on Discord on June 11 at 11PM UTC (7PM EDT, 4PM EDT, 9AM AEST)](https://discord.gg/U6RfbGDN?event=1509015071890870443) (and yes - we're planning to add calls at other times more convenient for European and Asian audiences). |
Member
There was a problem hiding this comment.
There's an error in the timing here: should be 4PM PDT
kattni
requested changes
May 30, 2026
|
|
||
| On the technical front, in the coming month, we'll also be looking into options for updating code in a running app; and continuing work on the "big picture" app navigation plan published earlier in the year. If time permits, we'll begin investigations into the use of Conda environments in Briefcase apps. | ||
|
|
||
| We're also planning to step up our efforts to build the BeeWare community. We've developed a reputation at PyCon US for running extremely effective sprints; but we need to do more of that outreach for people who can't make it to PyCon. We've already begun doing an audit of our outstanding issues in the hope of curating a more actionable list of work for contributors; and we're going to start being more active on social media, including reaching out to more social media channels. We're also going to host our first Community Call - a live video event where members of the core team and community members can share what they've been working on. [Join us on Discord on June 11 at 11PM UTC (7PM EDT, 4PM EDT, 9AM AEST)](https://discord.gg/U6RfbGDN?event=1509015071890870443) (and yes - we're planning to add calls at other times more convenient for European and Asian audiences). |
Collaborator
There was a problem hiding this comment.
This doesn't really imply there will be more. Suggested edit inline.
AEST? Not AWST?
Suggested change
| We're also planning to step up our efforts to build the BeeWare community. We've developed a reputation at PyCon US for running extremely effective sprints; but we need to do more of that outreach for people who can't make it to PyCon. We've already begun doing an audit of our outstanding issues in the hope of curating a more actionable list of work for contributors; and we're going to start being more active on social media, including reaching out to more social media channels. We're also going to host our first Community Call - a live video event where members of the core team and community members can share what they've been working on. [Join us on Discord on June 11 at 11PM UTC (7PM EDT, 4PM EDT, 9AM AEST)](https://discord.gg/U6RfbGDN?event=1509015071890870443) (and yes - we're planning to add calls at other times more convenient for European and Asian audiences). | |
| We're also planning to step up our efforts to build the BeeWare community. We've developed a reputation at PyCon US for running extremely effective sprints; but we need to do more of that outreach for people who can't make it to PyCon. We've already begun doing an audit of our outstanding issues in the hope of curating a more actionable list of work for contributors; and we're going to start being more active on social media, including reaching out to more social media channels. We're also going to host our first Community Call - a monthly live video event where members of the core team and community members can share what they've been working on. [Join us on Discord on June 11 at 11PM UTC (7PM EDT, 4PM EDT, 9AM AEST)](https://discord.gg/U6RfbGDN?event=1509015071890870443) (and yes - we're planning to add calls at other times more convenient for European and Asian audiences). |
Member
Author
There was a problem hiding this comment.
AEST was deliberate - that's the time the overwhelming majority of AU viewers will know. It's the timezone that gets called "Australian time" more often than not.
Good call on "monthly" though.
Comment on lines
+49
to
+50
| - If you're interested in the tooling for deploying applications to various platforms, take a look at [Briefcase](https://github.com/beeware/briefcase/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22good%20first%20issue%22). | ||
| - Or, if you're interested in GUI widgets, take a look at [Toga](https://github.com/beeware/toga/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22good%20first%20issue%22). |
Collaborator
There was a problem hiding this comment.
We need to have it on our radar to switch this to the GitHub Project once we have those issues well triaged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Time for a status update blog post.
To aid generating these, I've added an agent skill to generate the first draft. That draft has been heavily manually edited, but collecting the PRs and summarising authors is the hard (and automatable) part.
PR Checklist:
Assisted-by: Claude Opus 4.7