A question for the distribution developers. If I edit the build instructions so that 0 A.D. has version 0.0.26 - can I expect this version to appear in the official repository? My efforts with the kernel update have only benefited a limited number of people. Will I be able to help with updating this game?

For example, I just finished building the game via package.yml from the official solus repository.

tomscharbach My screenshot key combination does not work in flatpak. And it seems to me that you should still update these packages.

    Moreover, I have already completed the build, and provided the developers with their build instructions) Perhaps by the way I indicated the release field a little wrong there.

      algent Dear Sir, I have already assembled more than one package. Before that I built linux-6.0-current and linux-6.0-zen for solus. So now I am just waiting for the developers to accept the update. The only mistake I made was 1 instead of 40 (like in 0.0.25 release).

          So I'm not a member of the development team, the help center says that I can only send a proposal for an update via a task force.

            Just out of curiosity, why isn't this discussion being handled internally through dev/maintainer communications channels rather than on this forum, which is public and intended for user support? @ketronixdev lists three team members as contributors on his linux-current and linux-zen Gitbubs, so I gather that he is in contact with those team members.

              tomscharbach I don't keep in touch with them, and I'm not on the list of developers. They were just imported from the original repository. If I kept in touch with them individually - there would be 6 kernels in solus by now)))

                  ketronixdev From my experience you can usually submit an update to any package except system tools like Kernel, Mesa, glibc etc. It will not appear right away in the software repos someone from the core team will have to check and approve your submission.

                    ketronixdev I don't keep in touch with them, and I'm not on the list of developers.

                    Perhaps you should consider offering to become part of the team as a global maintainer, working with the team rather than around it, making a multi-year commitment to Solus rather than just freelancing.

                    ketronixdev If I kept in touch with them individually - there would be 6 kernels in solus by now)))

                    ... or not. Solus has dodged some real bullets by not mindlessly adopting every kernel update as it came along.

                          tomscharbach Or not, but at this point I have already built a sixth kernel for myself and also published eopkg packages on github, but I was told that my help was not needed, so I decided to build 0 A.D.)

                          As for joining the team - I don't think I have enough knowledge. Or time. Since I'm currently studying at university. Although I was able to build and update kernels and the game)

                            ketronixdev You don't have to be a member of development team to submit a differential to update a package. Everyone can do it.
                            You already built it for yourself an it is working. Just share it with other Solus users by submitting a differentail in our phabricator.
                            There are some rules, like you have to use your real name in packager file. You can't submit package update for packages that already have a maintainer. You don't submit the eopkg file via diff, because they are built in build server, after the differential is accepted.

                              @ketronixdev So just to be perfectly clear, as there seems to be some confusion, the process to submit a package update is as follows:

                              1. Check that the package doesn't have a MAINTAINERS.md file on dev.getsol.us (if it has, the process becomes a bit more involved, as we have to first check with the maintainer, or find out if they are still active). In this case there is no MAINTAINERS.md file, so we can ignore that for now.
                              2. Check that no patch/diff to update the package has already been submitted to https://dev.getsol.us (in this case you're a-okay in this regard as well, as you're the first to submit one)
                              3. Follow the "Building a Package", "Updating an Existing Package", and "Submitting the Package" guides to send a package update "diffusion" (i.e. basically a patch) to our dev tracker https://dev.getsol.us
                              4. Wait for someone to take a look at the diff, and if they request changes follow their instructions

                              After this process has completed the update will finally be merged (usually, unless there are insurmountable problems), and the build server creates the package for the unstable repository, where it can be tested until the next sync to the stable repository, where all our users can access the updated package.

                              tomscharbach Perhaps you should consider offering to become part of the team as a global maintainer, working with the team rather than around it, making a multi-year commitment to Solus rather than just freelancing.

                              A note here: Usually the team will be looking at a history of contributions to Solus before an inclusion into the team is considered. I guess there could be exceptions of "OMG, we absolutely need to have this person on the team!", but usually we're looking at a process that starts by the person simply submitting patches of consistent quality to the dev tracker, or contributing in some other way to Solus, for an extended period of time, before a question like inclusion into the team even arises.

                                  Staudey I know this info is publicly available with a close reading of the website, but this explanation of the Solus Packaging workflow deserves its own page on the Help Center in my opinion.

                                  When I first started contributing, the process wasn't very clear to me, and I had to get help from several of you kind folks. I get it now, but hindsight is much clearer.

                                      infinitymdm yeah, I require(d) help getting started also. Honestly, I don't know that I would have got there without help and the old youtube video Josh has about building a package. I think it was Budgie task switcher applet?