Good news,

Scott gave me complete admin rights on the linuxcnc-ethercat organization
https://github.com/linuxcnc-ethercat
did new pre-releases if anyone has hardware to test will be welcome, I also added an ethercat-master 1.6.9 under the same organization, heavily modified with quick parallel OP, and more features coming.
@automata
I share your sentiment about go, ripped it out, rewrote in python3 some scripts, and in C some of the stuff where performance matters, no go dependency, no other added dependency.

Glad to share access with anyone who would like to have it just in case, or has hardware and wants to help maintain/test.

Best Regards,
Luca

On 4/11/2026 10:42 AM, Luca Toniolo wrote:
linuxcnc-ethercat user on GitHub should be the place to take over, I'll try to 
reach out to Scott, see what's his plan.

On April 11, 2026 6:43:25 AM GMT+08:00, rodw <[email protected]> wrote:
I don't think you can use grotius's repo as Scott Laird's current repo at   
https://github.com/linuxcnc-ethercat    includes a lot of enhancements that 
Grotius will not include.
Grotius includes a header file from etherlab's Ethercat master repo   
https://etherlab.org/en_GB/ethercat   Whilst, it is required to compile, it 
should not be just copied into the project.
A better source might be the libethercat-dev package.
Finally, it ignores the project history. Why not use my fork or anybody elses at random? Scott Laird had permission from the original developer Sasha Itnner to take over the project and developed workflows that published his Deb files to the etherlab repositories. Prior to Scott arriving on the scene, etherlab also had Sasha's consent to host his repo and were doing so before Scott started adding enhancements. Sasha has been active in discussions on Scott's repository in 2026. Sasha tells people on his repo to   use Scotts.   There are only two valid sources should linuxcnc take it over:
Scott Laird's   https://github.com/linuxcnc-ethercat
Luca's   https://github.com/grandixximo/linuxcnc-ethercat
I think the preferred course would be work from Scott's and Luca should send his recent and important PR to the new repo. workflows should then publish the deb files to the Linuxcnc repository. Rod Webster

On 2026-04-11 06:31, Amit Goradia <[email protected]> wrote:
On Tue, Apr 7, 2026 at 6:06 PM Bari  <[email protected]>  wrote:

  After 4 months of no replies I'd call that abandoned. How much longer
  should you wait? Fork it publicly and move on with our lives. It's
  trivial to merge later IF the other fork maintainer reappears. People
  get sick or worse, have kids, loose interest, etc etc.


Bari, your sentence phrasing is really hilarious if you do not parse the
comma properly...
People get sick or worse, have kids... LOL...


  On 4/7/26 4:04 AM, Luca Toniolo wrote:
   >  Scott has been out for about 4 months, no answers no merging, does
  anyone else have the administration access to the
  linuxcnc-ethercat/linuxcnc-ethercat repo on GitHub? Users on the forum have
  been pointed to my fork, but I am not sure that is proper, Sascha's work is
  not compatible at the moment, need some guidance from a maintainer for
  direction on the project...
   >  _______________________________________________
   >  Emc-developers mailing list
   >  [email protected]
   >  https://lists.sourceforge.net/lists/listinfo/emc-developers

  Luca, I agree with Bari, 4 months with no response can be construed as
abandoned. Also, the Go dependencies introduced in this project was a bit
of a bother anyways.
I'd much prefer to use grotius' fork available at
https://codeberg.org/skynet/linuxcnc-ethercat where he moved everything to
a CMake file although he lost most of the directory structure.
-automata


  _______________________________________________
  Emc-developers mailing list
  [email protected]
  https://lists.sourceforge.net/lists/listinfo/emc-developers

_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers


_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to