changed 4 years ago  
Published Linked with GitHub

Hello fellow Striders,

November 29th we had another community meeting. This blogpost summarizes the topics we talked about.

Sponsors

  • Started off with a thank you to all those who donated on the new sponsor platform: Open collective. In particular a big thanks to:

A month of Open collective

After a month using the new sponsor platform, the Stride collective has reached a balance of $1,984.31 USD.
We started discussing how and where the money should be distributed. We want to do this with the help of Open collective 'Projects'. These projects are listed on Stride's Open collective page, and have their own tiers, targets and description. Users can sponsor projects directly instead of the main Stride collective if they want to.

We have come up with several projects that need to be written out in more detail before we will add them to the Open collective page. All tickets below have a Github discussion for more details.

  • OC project: Bug bounties project

    • Before starting on an issue, make it known on Github and Discord that your are willing to tackle the issue. It would be a shame if multiple people try to solve the same issue.
    • Any PR to the Stride repo must be reviewed by a contributor and discussed if needed.
    • Once a PR is reviewed and merged to the Stride repo, the submitter 60% of the bounty.
    • The submitter receives the remaining 40% when stride release happens.
    • https://github.com/stride3d/stride/discussions/1204

  • OC project: .NET 6 platforms support

  • OC project: Shader system

  • OC project: Linux/macOS support'

    • A rather large topic that requires a lot of work is the support for Linux and/or macOs. When worked out in more detail, it can be used in the plan for requesting an Epic grant. Subtopics to resolve:
      • Runtime/3d
      • Build tools (able to msbuild a Stride project and have the asset compiler work on it) requirement: FBX/Assimp
      • Editor
    • https://github.com/stride3d/stride/discussions/1202

Preparing request Epic grant

For a while now we have been wanting to pursue the option of requesting an Epig grant. In order to do so however, we need to come up with a proper plan. The end goal is to have a proper document explaining what we want to do, and how we plan to spend any given budget.

AggrorJorn starts a github ticket where we gather info on the request to Epic. He will contact others for proofread and further info. https://github.com/stride3d/stride/discussions/1207

Some of the topics mentioned:

  • Shader system
  • Editor rewrite
  • Megascan Integration
  • ECS rewrite/Run Update() and Render() in parallel

Other action items

  • We close the forum in December as there is almost no activity there. We want to utilize Discord and Github discussion for this. The forum will be read only but we will no longer refer to it from the website and Github.
  • Use a Github project for remaining tasks: https://github.com/orgs/stride3d/projects/3/views/1
  • Github ticket on a simple free community marketplace
    • https://github.com/stride3d/stride/issues/1197
    • A lot of people have made useful components/utilities/art and other useful assets for Stride projects. Right now we don't have a quick and easy way to import such assets in to an existing (editor) project.
    • What we can do is utilise the existing Nuget (tagging) system so that users can quickly add a component to their ongoing project in the editor.
  • Documentation on the stride source/new comers tutorial

Ongoing development

  • Manio143: finishing touches/documentation for Physics constraints
  • AggrorJorn: Splines
    • Trying to finish the base splines which could be integrated in to the Stride source. Other Spline based components should be added later, so that we can have a milestone finished.
    • Some tricky stuff with custom translation gizmo's for controlling tangents in the editor are currently holding me back. If this isn't resolved quickly I will make a PR without this (nice to have) feature
  • Release of 4.1 only held back by final .NET 6 related fixes. After that Xen2 will prepare for release. AggrorJorn will aid in blogpost release notes.
Select a repo