Oolite Bulletins

Interesting. We are trying to sort all OXPs into one linear sequence. That I can already do: - by title - by author - by publishing date - by ... You can browse the catalog and experiment which ordering suits you best - and I believe it depends on what you are after. An additional thing I had in min...

What could help is to have a classification system for the expansions. It partly exists in the wiki where on many OXP pages you find a rating if the game becomes easier or more difficult etc. We could add maturity level (bugs, graphics, sound), fix what might need to be fixed and add it to the catal...

I have to say that your OXZ database has proved invaluable to my wiki work. Having read so many dozens of posts on this forum wishing for multi-player Oolite, I also have to say that I'm astounded that your Nexus project never got much attention. Thank you. I guess it is all bad timing. Those wishi...

And I am also wondering whether it is just the two of us who would be active. Hiran... I'm very impressed with your relentless optimism that there is anybody else on the surface of our planet who understands any of this!! :-D Vice versa: When I was more pessimistic it was you who brought me back ag...

Three replies. None of them relate to my initial post. Maybe I should take that as an answer. :roll: Happy for you to set up GitHub Projects. It is not something I have time to look into given the long list in the backlog I already shared, but I would add my items to the project once you set it up ...

Three replies. None of them relate to my initial post.
Maybe I should take that as an answer.

Here's my stab at the backlog:
viewtopic.php?t=22072

Again something for the backlog.

viewtopic.php?t=22072

I'd like to suggest we capture work that needs to be done such that we do not forget and everybody can see what is pending. Hopefully that would encourage more people to actively contribute. Github already has a ticket system that seems to be looked at sporadically only but which at the same time ca...

The dummy edit will run the CI again. But...

hiran wrote:

If I simply rerun the build in my fork, our prerelease is pulled which still provides no metadata.

I am ok with all but that final PR from your fork to oolite master.

Why would have it go to that branch? Pick/create a new one so it is in the oolite repo and visible to everyone and gets processed by the CI/CD chain. If good we can still run a PR to merge into master. Or cherry pick. Or ....

We need to start managing a backlog. One item is to get rid of the python 2 dependencies. Another one could be the javascript version. As far as I understand we have some Oolite custom JavaScript engine that noone outside the project would know. The problem with the engine is more its age. It is we...

How about creating a new branch from master and merging the release branch? We can have a look at the result before merging into master.

We need to start managing a backlog. One item is to get rid of the python 2 dependencies.

Another one could be the javascript version. As far as I understand we have some Oolite custom JavaScript engine that noone outside the project would know.

Since 1.92.1.0 has been released, did the AppImageHub build update to use it? https://github.com/OoliteProject/oolite/releases/tag/1.92.1.0 I neither see progress on the PR nor on the issue I raised: https://github.com/AppImage/appimage.github.io/issues/3718 If I simply rerun the build in my fork, ...