- Joined
- Oct 11, 2009
- Messages
- 3,481
- Reaction score
- 398
- Points
- 123
- Location
- Utrecht
- Website
- www.spaceflightnewsapi.net
Hi everyone,
We thought it might be nice to do a “state of Orbiter Forum” post to talk about where we stand and what we’re working on
Orbiter Forum
Some 2 years ago we migrated to XenForo. This step made our live a lot easier and we’re running up-to-date forum software.
This comes at a cost (but what doesn’t these days). Every year we evaluate the renewal of the license and so far we don’t see any reasons to not renew it.
The forum is currently running (well updated) on a CentOS 7 machine. @Xyon and I (but mainly she) are working on migrating it to either a Rocky 8 installation or the app-service that Digital Ocean is offering and we're pushing on the latter. We’ll keep you informed.
Orbit Hangar Mods
The current version of OHM is… less than ideal. @Xyon developed a new API, I’ve been working on a React-based frontend and we progressed nicely. Eventually, life caught up and development slowed down. We regularly talked about things that needed to be done, but both myself an her are busy with our personal lives as well.
With Orbiter being open sourced (more on that later) we saw a rise in interest in the project. This means there’s also a rise in interest for add-ons and OHM.
Therefore, we were considering the following options:
There's a lot todo there in terms of migrations and planning but it seems like this is the best option. We're pretty excited about this.
This will also return some of the functionality we used to have on the vBulletin board (post creation, for example).
Orbiter Open Sourced
This one is a bit complicated
Martins open sourced Orbiter about a year ago on GitHub.
A couple of us (both OF admins and none admins) are members of the organization but not an owner or maintainer. This limits us in what we can do in terms of CI/CD, setting up pipelines, creating releases, etc.
Also, the main orbiter site is not maintainable by any us, as far as I’m aware.
With the source code now open, discussions can start on how to continue development (in fact, there’s already a thread for this). There are a lot options here so the discussions are good.
The short-term plan is to get a steady CI/CD pipeline working and then start merging PRs. There also needs to be a roadmap, a discussion on what to add to the releases out-of-the-box, how often a new release is published, etc.
Currently we’re setting up a new website, targeted on a fork called “open orbiter”. However, if we can get the right permissions for the GitHub organization I think we can drop the “open” part and just renew the current Orbiter site with what we’re building.
Like I said, tons of options just need to decide with each other on how to proceed.
If you have any valid input, please join the thread and add it there For those who've already shared their ideas - thank you!
That's it for now. I'll try to do these posts more often.
We thought it might be nice to do a “state of Orbiter Forum” post to talk about where we stand and what we’re working on
Orbiter Forum
Some 2 years ago we migrated to XenForo. This step made our live a lot easier and we’re running up-to-date forum software.
This comes at a cost (but what doesn’t these days). Every year we evaluate the renewal of the license and so far we don’t see any reasons to not renew it.
The forum is currently running (well updated) on a CentOS 7 machine. @Xyon and I (but mainly she) are working on migrating it to either a Rocky 8 installation or the app-service that Digital Ocean is offering and we're pushing on the latter. We’ll keep you informed.
Orbit Hangar Mods
The current version of OHM is… less than ideal. @Xyon developed a new API, I’ve been working on a React-based frontend and we progressed nicely. Eventually, life caught up and development slowed down. We regularly talked about things that needed to be done, but both myself an her are busy with our personal lives as well.
With Orbiter being open sourced (more on that later) we saw a rise in interest in the project. This means there’s also a rise in interest for add-ons and OHM.
Therefore, we were considering the following options:
- Continue development on the API and frontend
- Integrate OHM functionality into OF
There's a lot todo there in terms of migrations and planning but it seems like this is the best option. We're pretty excited about this.
This will also return some of the functionality we used to have on the vBulletin board (post creation, for example).
Orbiter Open Sourced
This one is a bit complicated
Martins open sourced Orbiter about a year ago on GitHub.
A couple of us (both OF admins and none admins) are members of the organization but not an owner or maintainer. This limits us in what we can do in terms of CI/CD, setting up pipelines, creating releases, etc.
Also, the main orbiter site is not maintainable by any us, as far as I’m aware.
With the source code now open, discussions can start on how to continue development (in fact, there’s already a thread for this). There are a lot options here so the discussions are good.
The short-term plan is to get a steady CI/CD pipeline working and then start merging PRs. There also needs to be a roadmap, a discussion on what to add to the releases out-of-the-box, how often a new release is published, etc.
Currently we’re setting up a new website, targeted on a fork called “open orbiter”. However, if we can get the right permissions for the GitHub organization I think we can drop the “open” part and just renew the current Orbiter site with what we’re building.
Like I said, tons of options just need to decide with each other on how to proceed.
If you have any valid input, please join the thread and add it there For those who've already shared their ideas - thank you!
That's it for now. I'll try to do these posts more often.