Is this still maintained?

[rockstar]

This library seems to be the only one providing ecal support, but it looks like the original authors are no longer using ecal. What's the status of this library? Is it looking for a new maintainer? Is it active enough that if I put patches up, I could get merges and releases on a regular cadence? I'd rather not fork the library, if I can get away with it; the ecal name in crates.io is really helpful.

I definitely do need ecal support in rust, and if I can contribute to a public good, I'm interested in that. I just don't want to invest effort into making this library better if the patches will just sit in the pull requests. Is there active maintenance on this crate?

[KerstinKeller]

Hi, I'm one of the eCAL devs.
From the eCAL point of view, we're definately interested in the existance of a maintained Rust extension.
None of our team members is actively using Rust, which is why the language port was added by Kopernikus Automotive.

@denzp how would you / the team feel about moving this repository to the eclipse-ecal organization?
We'd still need an active maintainer, but we could support to the best of our knowledge from the eCAL team.

[rockstar]

I'm still working out the details internally, but there is a high likelihood that I can become an active maintainer of this library. Having it be part of the eCAL organization proper would be super appealing as well–we've been hesitant to use this library because, while eCAL claims the integration, it didn't look like it was actively participating in it, so it was hard to know whether we can bet the future of our product on it.

[alknemeyer]

Hey, sorry for the delay in getting back to you!

We will transfer the repo to the eclipse organisation. I believe I need to be given the ability to create repositories there? Or would you do the transfer in a different way?

[rex-schilasky]

Thank you for supporting this. We need to align with Eclipse Foundation how to organize the transfer now.

[rockstar]

@KerstinKeller is there a way you could connect with @alknemeyer about this ownership transfer? This is blocking some potential moves I can make internally that will set us up for long-term success.

[rex-schilasky]

@rockstar the transfer process is started with Eclipse, they do some checks currently for this repo (ecal-rs). I expect we will get some green light from their side soon. Please @alknemeyer contact me by mail (f i r s t n a m e . l a s t n a m e @ c o n t i n e n t a l . c o m) and we can organize the transfer together.

[rockstar]

I'm sure there are things going on behind the scenes, but an update would be nice. If this takes much longer, I think we'll have to re-visit our ecal decision. If we can move this along and get to a place where we can submit and have patches merged, etc, that would be helpful.

[FlorianReimold]

Hi @rockstar,

Not sure if you noticed, but the ecal-rs repository has been transferred since 2024-03-26 12:00 CET. You can find the Eclipse helpdesk issue here: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4417

The repo transfer should not hinder you in any major way from using it or contributing to it. The repository content did not change at all, so if you have a local clone, you should be able to just modify your origin URL. If you have a fork, that fork should now automatically be a fork of this repository without you having to do anything. Already existing pull requests now point to this repo.

The repository will stay here in the foreseeable future and the URL will not change anymore. If you would like to contribute to it, please be aware that it is now an Eclipse project using the Eclipse process, so you will have to sign the Eclipse Contributor Agreement before we can merge your PRs. To do that, please create an Eclipse account, add your GitHub account name in the "Social Media Accounts" Section and sign the CLA.

[rummanwaqar]

@FlorianReimold

I've recently started working with ecal-rs and would like to contribute improvements to the project. I've already created an Eclipse account and signed the Eclipse Contributor Agreement (ECA). Before I begin submitting contributions, I wanted to check if there are any additional steps I should complete or project guidelines I should follow. I'm also interested in knowing if there are any undocumented priorities that need attention.

My planned contributions include:

• Updating the Prost and Protobuf library dependencies
• Implementing ECal logging functionality
• Developing reflection support for Prost messages in the ECal monitor
• Adding Service implementations

Please let me know if any of these areas align with the project's current priorities or if there are other areas where contributions would be more valuable.

[FlorianReimold]

Hi @rummanwaqar

Awesome, feel free to make contributions, here!

Before investing too much effort please be aware that we are currently working on the eCAL 6.0 release. eCAL 6.0 has a slightly different API, so if you are flexible enough I would recommend directly starting with the current eCAL master HEAD. Note, that in the eCAL repository we currently selected the 5.13 support branch as default branch, but development obviously does not happen on that branch.

• Updating the Prost and Protobuf library dependencies

👍

• Implementing ECal logging functionality

👍

• Developing reflection support for Prost messages in the ECal monitor

I think that would rather be a contribution for the main eCAL repository. This ecal-rs only holds the Rust binding.

• Adding Service implementations

👍

Please let me know if any of these areas align with the project's current priorities or if there are other areas where contributions would be more valuable.

The current priorities are releasing eCAL 6.0, so getting the rust binding eCAL 6.0 ready would be a great thing.