> Gesendet: Samstag, 21. September 2024 um 21:23 > Von: "gene heskett" <ghesk...@shentel.net> > An: emc-developers@lists.sourceforge.net > Betreff: Re: [Emc-developers] Where to inspect the > latestdocumentation->GitHub (was Buildbot(s)) > > <html><head></head><body>On 9/21/24 12:51, Greg C wrote: > > On Fri, Sep 20, 2024 at 1:45 PM andy pugh <bodge...@gmail.com> wrote: > > > >> On Fri, 20 Sept 2024 at 18:24, Greg C <gregory.d.c...@gmail.com> > wrote: > >>> > >>> I am all for moving the ball forward, but the commit without any > warning > >>> was definitely a hard pill to swallow. > >> > >> It does only affect those using buildbot builds and master. Normal > >> users, working with released versions of 2.9 are unaffected. > >> > > > > I am aware. The point was not to speculate on how many users were > > impacted, but rather to point out the unannounced impact to the users. > > Changes of this magnitude could benefit from clearer communication, > > especially since some "normal" (non developer) users rely on the master > > branch, and updates to it, for legitimate reasons. > > > > On Fri, Sep 20, 2024 at 12:26 PM andy pugh <bodge...@gmail.com> wrote: > > > >> On Fri, 20 Sept 2024 at 17:13, Marius Liebenberg > <mar...@mastercut.co.za> > >> wrote: > >> > >>> So please do not drop the ball on the Buster users. At least not > until > >>> there are a new stable Debian release. > >> > >> Buster is out of support, though. > >> > >> However, the reason for dropping support was not that, it was the > >> unavailability of various software packages (a working version of > po4a > >> for example) > > > > > > I know it happened slowly over time, but it seems like this project has > > become the LinuxCNC Document Translation project. That comment is appreciated. Quite some effort goes into that and we yet do not have a reliable readout about how much this is helping our community to attract new users or is indeed a distraction. What indeed shall not happen is that we have documentation-associated dependencies hinder the backport of LinuxCNC to existing users. The answers I see is that - we could help with backports of the LinuxCNC dependencies and consequently also - move LinuxCNC from buster to buster-backports. There is the Debian-independent freexian project to provide such https://wiki.debian.org/LTS/Extended for older releases > > While I appreciate that > > document translations were deemed necessary, it seems to have drawn focus > > away from the main project and had a counterproductive effect. Perhaps > > managing document translations in a separate repository could help us > focus > > more on the core project while still supporting that important work. The > > shear number of commits that have broken things, as well as the the > > increase in size of the project (now hundreds of megabytes) due to > document > > translations is concerning. > > > FWIW (not much) I agree. I have no clue how to shrink the main docs, > there is very little that can be deleted. At the same time 1100+ pages > to be tossed in the bin at new release time is too big. By the time it > has been put on dead tree's its $14+ for decent but recycled paper and > $50 for ink for my old brother tabloid sized printer/scanner. And on > 24lb paper, it doesn't fit comfortably in a binder with 2" D-rings. I > think it can be said that we have a tiger by the tail. How can we tame it? I do not think that the documentation should be printed - online PDF/html should be all you need. Also, I have uploaded all LinuxCNC PDFs to a chatGPT assistant at https://chatgpt.com/g/g-vfeQnX43z-linuxcnc-assistant (yes, I should find a Free alternative) that I guess shall also help with translations, and explains stuff. Best, Steffen _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
[Emc-developers] Extended long-term support for Buster, separating documentation was Re: Where to inspect the latestdocumentation->GitHub (was Buildbot(s))
Steffen Möller via Emc-developers Sun, 22 Sep 2024 04:01:27 -0700
- Re: [Emc-developers] Where to inspect t... andy pugh
- Re: [Emc-developers] Where to inspect t... gene heskett
- Re: [Emc-developers] Where to inspect t... andy pugh
- Re: [Emc-developers] Where to inspect t... Greg C
- Re: [Emc-developers] Where to inspect t... Sebastian Kuzminsky
- Re: [Emc-developers] Where to inspect t... andy pugh
- Re: [Emc-developers] Where to inspect t... Greg C
- Re: [Emc-developers] Where to inspect t... andy pugh
- Re: [Emc-developers] Where to inspect t... Greg C
- Re: [Emc-developers] Where to inspect t... gene heskett
- [Emc-developers] Extended long-term sup... Steffen Möller via Emc-developers
- Re: [Emc-developers] Extended long-term... gene heskett
- Re: [Emc-developers] Extended long-term... andy pugh
- Re: [Emc-developers] Extended long-term... gene heskett
- Re: [Emc-developers] Where to inspect t... andy pugh
- Re: [Emc-developers] Where to inspect t... Marius Liebenberg
- Re: [Emc-developers] Where to inspect t... andy pugh
- Re: [Emc-developers] Where to inspect t... gene heskett
- Re: [Emc-developers] Where to inspect t... gene heskett
- Re: [Emc-developers] Where to inspect t... andy pugh
- Re: [Emc-developers] Where to inspectth... gene heskett