Skip to content

Commit 4e37776

Browse files
Haircut
1 parent ecdf4ec commit 4e37776

File tree

1 file changed

+4
-60
lines changed

1 file changed

+4
-60
lines changed

website/content/blog/2024-09-11-meeting.md

Lines changed: 4 additions & 60 deletions
Original file line numberDiff line numberDiff line change
@@ -34,93 +34,37 @@ We discussed and decided to allow loading of raw content files (pngs, wav, etc)
3434
- [`Content.Load<Song>("asset name");`](https://github.com/MonoGame/MonoGame/issues/8483)
3535
- [`Content.Load<Video>("asset name");`](https://github.com/MonoGame/MonoGame/issues/8484)
3636

37-
The flow will basically be like this:
38-
39-
1. Try to load the `.xnb` as normal, if the Content.Load<Texture2D> call fails, then:
40-
2. Then search the Content directory (or sub-directory) provided by assetName for files other than .xnb which can be loaded without an importer (i.e. BMP, PNG, JPG, JPEG should be enough and are supported)
41-
3. Try to use (for example) `Texture2D.FromStream(_graphicsDevice, file, DefaultColorProcessors.PremultiplyAlpha);` on that file (assuming premultiplied alpha here because it is MGCB's default)
42-
4. Continue as normal.
43-
4437
::: note For later
4538
At this time, shaders and models will still have to use the Content Pipeline as there are many dependencies involved in handling these kinds of content. We will address them in time, but for now, they will have to wait.
4639
:::
4740

48-
The benefit of this approach is to also ease the burden as projects evolve and developers may want to switch to the content pipeline (or other methods) at a later date, and rather than cause dramatic reworkings of code, instead, the content will simply need to move and the code stays the same.
49-
50-
::: important
51-
If you have a suggestion on how to improve this or add more flexibility at runtime, **NOW** is the time to have your voice heard by commenting or making suggestions in the issues above.
52-
:::
53-
5441
### Release Improvements
5542

5643
Like the Content Pipeline improvements above, the same view has also been turned to the way we release MonoGame today via NuGets. We recognize this might not be a 100% fit for all as NuGet does impose some limitations, especially for offline use.
5744

5845
To this end, we have also kicked off two other streams of work:
5946

6047
- [Update build pipeline to generate a "Complete" Source package for releases](https://github.com/MonoGame/MonoGame/issues/8485)
61-
62-
Currently, the Source package that GitHub automatically generates ONLY contains the MonoGame source, it does not include submodules or dependencies.
63-
This change will generate a zip that includes **ALL** source, including submodules and dependencies so that it can be dropped in a project and referenced.
64-
Source access will allow a project to be completely self-contained and build the framework on demand.
65-
66-
6748
- [Update build pipeline to generate a "Binaries" Source package for releases](https://github.com/MonoGame/MonoGame/issues/8486)
6849

69-
Currently the Binaries package that GitHub automatically generates ONLY contains the MonoGame binaries, it does not include submodules or dependencies.
70-
This change will generate a zip that includes **ALL** binaries and dependencies so that it can be dropped in a project and referenced.
71-
Perfect for automation or offline scenarios where snapshot builds of dependencies are needed without modification. (instead of NuGet)
72-
73-
Hopefully, this will open up new avenues for advanced projects and pipelines.
74-
75-
::: important
76-
If you have a suggestion on how to improve this or add more flexibility at runtime, **NOW** is the time to have your voice heard by commenting or making suggestions in the issues above.
77-
:::
78-
7950
### Bounties, Bounties, Bounties
8051

8152
Work continues on all existing bounties, but these updates were at the top of mind for discussion.
8253

83-
- DX12 / GDK support is a go
84-
The work for the DX12/GDK update is now complete, required dependencies for the "platform" are being merged into the public MonoGame this week. Once in, the private Xbox repo will be published with the new updates, then finally the public MonoGame / GDK updates can be published.
85-
86-
- The final gap in updating the Content Pipeline dependencies is complete
87-
The [Basis Universal](https://github.com/MonoGame/MonoGame/pull/8456) bounty was the final milestone in generating true cross-platform capabilities needed for an updated Content Pipeline backend.
88-
89-
- [Shared native base]](https://github.com/MonoGame/MonoGame/issues/8242) is 99% done!
90-
The shared native base is nearing completion and will be usable in the coming months for implementing platforms on top of.
54+
- DX12 / GDK support is a ready and completing final adoption
55+
- The [Basis Universal](https://github.com/MonoGame/MonoGame/pull/8456) bounty is complete
56+
- [Shared native base]](https://github.com/MonoGame/MonoGame/issues/8242) is nearing completion and will be usable in the coming months.
9157

9258
### Full Time maintainer - full steam ahead
9359

94-
Now that we have had an official meeting and preceded over a vote on the subject, we have given the go-ahead for a full-time member to take on the role of "MonoGame Maintainer" whose duties will include:
95-
96-
- General admin, site maintenance, community engagement
97-
- Socials management - Patreon, LinkedIn, Twitter, Facebook
98-
- PR reviews and clean-up
99-
- Issue fixing, reviews and clean-up
100-
- Bounty posting, review, and chasing bounty holders
101-
- Taking on specific bounties and progress
102-
- Docs reviews and maintenance
103-
104-
::: note
105-
This is not an exhaustive list as we are still grinding out the details, but the main task is to pick up the slack from the part-time, sometimes lacking efforts from the existing board members to dedicate time to these efforts in between their busy work life and precious free time. We do our best, but we have never been able to 100% focus on these tasks.
106-
:::
107-
108-
It was also agreed to appoint none other than `Dominique Louis` will take on the role as he will have the time now to take on the role. We wish Dom all the best in taking on this mammoth challenge (especially if you only look at the issue backlog, shudder).
60+
Now that we have had an official meeting and preceded over a vote on the subject, we have given the go-ahead for a full-time member to take on the role of "MonoGame Maintainer"
10961

11062
The final details to award this role are still being worked out, but the Foundation has to be able to afford this appointment and it likely will not be at "market rates" as this is a non-profit organization after all.
11163

11264
## Updates releases and schedules
11365

11466
One month on from the `3.8.2` release and we are already making plans for next month's release, assuming the recent PR merges warrent it. We were very serious about keeping pace and we are tightly focused on it.
11567

116-
::: Important
117-
We will endevour to keep the 2-monthly schedule for releases, but **ONLY** if there is sufficient change to warrant a release, but we will give due notice and reasons should a release not be forthcoming. If you want releases at this pace, we need your support to keep making changes and moving forward.
118-
119-
Essentially, if you want/need something, then **Get a PR ready and submit it!** (with the appropriate suggestion issue to outline the change of course :D)
120-
:::
121-
122-
Before you know it, MonoGame `4.0` will be on our doorstep ince sufficient large changes are in play, which from this months meeting, you should be able to draw your own conclusions.
123-
12468
## Get Involved
12569

12670
[Contributions are welcome through:](https://monogame.net/donate/)

0 commit comments

Comments
 (0)