Re: [Flightgear-devel] Suggestion for a 737-family repository in FG GitLab

[Xavier D. C. R. <xa...@di...>]

Hello Israel,

Thanks for the tips. As for Discord, I prefer to avoid proprietary 
messaging platforms whenever possible. That being said, I usually hang 
around on FG's official Matrix at #flightgear:hacklab.fi

Best regards,

Xavi

On 26/11/25 16:03, Israel Emmanuel wrote:
> Hello Xavier,
>
> At the present moment there are about 4 people who have expressed 
> interest in working on a 737, myself included. If you were to do this, 
> I would highly advise connecting with those people, namely:
> Naviat (me), for DUs and liveries
> Josh, for systems and FDE
> Falconbird18 and Captain Jake, for modeling
>
> If you were to work with any of those people, I think it would be a 
> great start for you. If you're alright with Discord, we all use that, 
> otherwise we can work something else out.
>
> What parts of development are you interested in?
>
>
> Get Outlook for Android <https://aka.ms/AAb9ysg>
> ------------------------------------------------------------------------
> *From:* Xavier Del Campo Romero via Flightgear-devel 
> <fli...@li...>
> *Sent:* Wednesday, November 26, 2025 6:42:43 AM
> *To:* fli...@li... 
> <fli...@li...>
> *Cc:* Xavier Del Campo Romero <xa...@di...>
> *Subject:* [Flightgear-devel] Suggestion for a 737-family repository 
> in FG GitLab
> Hello FG-dev list,
>
> Earlier today, I explained the status quo for all 737 variants. [1] To
> sum up, none of the 737 variants have received any development for a
> long time, and there are even multiple implementations of the same
> variant e.g.: 737-800YV [2], 737NG [3] and 737-family [4] all
> implementing the 737-800.
>
> A few months ago, I contributed a few improvements to the CDU in the
> 737-800YV [5] that made it into upstream. However, the repository seems
> abandoned at this point, and unfortunately so the 737 in general.
>
> Then, I was suggested [6] to write to this mailing list so that an
> official repository for the 737 family in GitLab, so at least the
> repository is always governed by the FlightGear community and is
> therefore not abandoned, like happened with the others before it.
>
> I cannot guarantee I can actively work in the 737 (mostly because of
> other projects and IRL stuff), but nonetheless I think the suggestion
> above is a good first step to improve the current situation. From a
> first glance, the 737-800YV looks like the most mature implementation,
> even if I suspect its repository contains a few non-free assets that
> should be reviewed. The intention is to cover all 737 variants within
> this repository, if possible.
>
> Please let me know your feedback.
>
> Best regards,
>
> Xavi
>
> [1]:
> https://forum.flightgear.org/viewtopic.php?p=436579&sid=5b663ef59ece0bedc1f02a4d0fa508d1#p436579 
> <https://forum.flightgear.org/viewtopic.php?p=436579&sid=5b663ef59ece0bedc1f02a4d0fa508d1#p436579>
> [2]: https://github.com/YV3399/737-800YV
> [3]:
> https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/737NG/
> [4]: https://github.com/naviat-dev/737-family (no longer available,
> unfortunately)
> [5]: https://forum.flightgear.org/viewtopic.php?f=4&t=43423 
> <https://forum.flightgear.org/viewtopic.php?f=4&t=43423>
> [6]:
> https://forum.flightgear.org/viewtopic.php?p=436580&sid=5b663ef59ece0bedc1f02a4d0fa508d1#p436580 
> <https://forum.flightgear.org/viewtopic.php?p=436580&sid=5b663ef59ece0bedc1f02a4d0fa508d1#p436580>
>
>
> _______________________________________________
> Flightgear-devel mailing list
> Fli...@li...
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel