- This topic has 177 replies, 24 voices, and was last updated May 23-4:44 pm by Brian Masinick.
-
Posts
-
Xecure
If there is an organization chart specifying what each member of the developer team does, in addition to the work to be performed, it may be that the members of the forum can identify work that can collaborate.
All those you see with the Forum Admin tag, I consider are the main developers.
Also, the “About” MX page has a table of developers, and most (if not all) of them also participate in antiX development.
The rest of us, mortals (members and Moderators), are well intended antiX users, helping if/when we can.
Probably someone else can expand on this.antiX Live system enthusiast.
General Live Boot Parameters for antiX.SamK
@marcelocripe
You do an excellent job of communicating in a non-native language.
Welcome Screen
The decision has already been reached. A welcome screen will not be adopted by antiX.Next Release
Earlier in this topic, anticapitalista outlined some of the the work that needs to be done. I am not aware of anyone stepping forward to help with it. This gives the appearance the work of the “new generation” as you describe them, now has two conditions attached:
• They stipulate the work that should be done,
• There is no point in doing the work unless a guarantee is given it will be adopted.
These will ultimately lead to disappointment.How can the participants of this forum collaborate in any way with the work teams?
This also has been covered previously in this topic. The most recent version is
The usual process is:
• Produce the work because it has local value,
• Make the finished result available,
• Wait to see if it gets picked up.Alternative
If the above do not coincide with expectations or preconceptions of how antiX works there is another route available. Creating a re-spin using tools provided in antiX specifically for that purpose. The advantage of doing so is that everything included in it is entirely under the control of the re-spin producer. Any idea, script or guide can be included and that re-spin made available today. Previously in this topic multiple participants have made multiple suggestions to create a re-spin but there appears to be a lack of willingness to do so. It would be the acid test of whether there are large numbers of Windows refugees waiting for it.How can I collaborate with what little I know?
Continue to promote antiX in your own country, perhaps ensure all documentation (current and future) is available in your language, perhaps consider making antiX videos in your language, etc.
- This reply was modified 2 years, 5 months ago by SamK.
- This reply was modified 2 years, 5 months ago by SamK.
- This reply was modified 2 years, 5 months ago by SamK.
Brian Masinick
I’ve already suggested that new user usability be a priority for a future release, at least in the Full implementation.
Please add your ideas and suggestions for future releases. There is no guarantee that every idea will be included (including mine), but if we document our ideas, we can discuss them and then the developers can make the decisions on which features are actually included, taking into account what’s important to them and which community suggestions are feasible to implement while maintaining the character and features of this distribution.
As I stated in this original note, “There is no guarantee that every idea will be included (including mine)”
I would also like to stress once again that though there are many good ideas expressed here, that does not guarantee their inclusion either in the repository or one of the release versions. This doesn’t prevent people from sharing ideas, scripts, etc. People can create tools and freely share them for those who are able to use them (and in some cases) create custom solutions for others.
It’s possible that someone may want to build their own derived distribution, either for private or public use. As long as proper credit (and
licensing) are provided, it is legal to create another shared work. I’m happy to see that a few people have already shared their derived builds. It may be better to do this occasionally rather than expect to see them as a standard component of this distribution. With no changes other than updated software, I still find antiX to be one of my preferred platforms on which I customize and build for myself whatever I need without having to impose my personal preferences on anyone at any time.--
Brian MasinickXecure
Due to many upstream changes in Debian, python2 and a lot of gtk2 will go.
That includes a few apps that have been ‘standard’ on antiX eg disk-manager, lxkeymap, lxappearance(?), gtkdialog and others.Our in-house apps also have to be ported from python2/gtk2 as well.
Dave has already started porting them (in testing/sid branch). Most seem to work ok, but there are bugs – testing will be needed.The live-system (including frugal, remaster, snapshot etc) seems to be working ok. However, the UEFI side probably needs to be improved to cater for more and more frugal/live users booting via UEFI since they have newer hardware.
Documentation certainly needs updating.
So, is there a list of things that need to be done and who is already working on it, and what has nobody assigned? We need to avoid duplication of work.
If possible, can a list be compiled for:
— In house Apps that need to be ported (new libraries for both inside working and graphical interface: Programming language required)
— Apps used in antiX that need a replacement (we can start searching for them and test them before suggesting them, comparing them with the previous tool and listing size and dependency requirements, under the devs criteria).
— What parts of the documentation need to be updated. The structure? The categories? Are certain parts more urgent/important?
— Can we have a contact (as in person in charge of this specific section) to send revisions for approval or simply make merge requests to the gitlab project?
— What is already being worked and how can we help test it? What should our feedback look like? Are specific tests needed? Special hardware requirements?If there is no guidance, it is difficult for us to know what and how we can help. It is like expecting a child to do something after the adult tells them to, without explaining how, what and where. Children cannot know or guess what the adult is thinking if things are not explained properly. They will go around in circles (our current state), trying to guess things, but the adult is only telling them “no, not that”. Children get frustrated easily.
I will put other projects on hold, and try to help as best I can, under the limitations of knowledge and time I have. Let me know how I can help out.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Brian Masinick
Regarding these items:
Have you tried to identify the different levels of computer users that still exist in the 21st century?
1- Learner user – is learning to use a computer.
2- Beginner user – already learned to turn on the computer and identifies the internet browser and some programs.
3- Basic user – has already gone through the previous steps and already knows how to use the internet browser, Office package and already knows how to use the File Manager, but presents several difficulties in using these basic programs.
4- Ordinary user – learned to install and uninstall programs, it is curious, eventually destroys the operating system. You already know how to install an operating system. I believe that you still have to use the ISO of antiX full.
5- Average user – knows exactly what he wants, already knows how to do and does not destroy the operating system. You can probably use the base antiX ISO and have some kind of CLI skills.
6- Intermediate user – can use the base ISO, net and core and probably solve almost everything via CLI. The base antiX ISO should be considered by these users as “very easy” or “full” of menus.
7- Advanced user, developer, programmer, remasterizer and etc. – they do not need a GUI, I believe they should solve everything via CLI and sometimes they end up forgetting about “normal” users.
I would comment that antiX is not intended to specifically cater to any of these categories, though groups 4-7 are likely to be able to create, use and manage an antiX distribution effectively.
Groups 1, 2, and 3 may be able to use antiX with guidance, or by patiently reading and learning. These groups may also benefit from individuals in their community who have the time to acquire the necessary skills or already have learned them. There are quite a few things that can be found and learned either by searching and reading through forums or by visiting sites with a collection of information. Our forum does offer a lot of information, but it may not be specifically organized to satisfy the beginner, unless that beginner is determined to learn by searching, reading, experimenting and learning. That’s how a lot of us became familiar with Linux.
In my case, I had a university education that taught me basic hardware and software skills, but I finished that education long before the arrival of Linux. I used my experience with other systems to learn new systems, but it took thousands of hours of reading, experimentation, failure and success to gain my current knowledge; to expect groups 1, 2 and 3 to have that knowledge without effort is not taking into account what is necessary and it is not the responsibility of a distribution to provide all of it; what we can do is answer questions and point people to useful resources. This forum has many tips, the Wiki and the main page have more, and the Internet is full of things people can use, along with their own time and effort to learn; it takes time and effort to learn it well.
--
Brian Masinick
christophe
I’ve been thinking about this thread. And I keep coming back to this thought: what brought each of us to antiX? antiX should always keep whatever that special something is. It surely isn’t something that it doesn’t have already, by definition. anticapitalista has executed his vision from the beginning, and it has produced exactly what antiX is. It’s nice that he has been welcoming in receiving our suggestions. But it’s always got to be that: we can make suggestions, and he takes from that (or doesn’t). Any of us users can go elsewhere. But, since we really like what antiX is, we stay.
antiX isn’t too hard. We all (that is, every single one of us who are using it) have figured it out. Where we couldn’t figure something out, we found help through documentation, the web, or this forum. In the beginning, we may have had old hardware that no one else was supporting, then we may have had to learn something new to get used to antiX. Some of us may have had a harder time than others, but a friendly forum may have been a great help in getting us sorted. I know it was for me.
Necessity sometimes pushes us to learn new things. And learning something good (by definition, again), isn’t a bad thing.
confirmed antiX frugaler, since 2019
Brian Masinick
Dave
If possible, can a list be compiled for:
— In house Apps that need to be ported (new libraries for both inside working and graphical interface: Programming language required)
— Apps used in antiX that need a replacement (we can start searching for them and test them before suggesting them, comparing them with the previous tool and listing size and dependency requirements, under the devs criteria).
— What parts of the documentation need to be updated. The structure? The categories? Are certain parts more urgent/important?
— Can we have a contact (as in person in charge of this specific section) to send revisions for approval or simply make merge requests to the gitlab project?
— What is already being worked and how can we help test it? What should our feedback look like? Are specific tests needed? Special hardware requirements?If there is no guidance, it is difficult for us to know what and how we can help. It is like expecting a child to do something after the adult tells them to, without explaining how, what and where. Children cannot know or guess what the adult is thinking if things are not explained properly. They will go around in circles (our current state), trying to guess things, but the adult is only telling them “no, not that”. Children get frustrated easily.
I will put other projects on hold, and try to help as best I can, under the limitations of knowledge and time I have. Let me know how I can help out.
I cannot say exactly, only my opinion / view on the matter. Anyone is free to correct me. There has been a few email discussions with similar questions. I recently expressed that I find it difficulty to build, maintain, and follow a list as most items in my list become outdated by the time one task is completed. I am currently working on the wallpaper app and porting it to python3/gtk3. Most others (That I wrote/modified) should be ported over but I am certain they are bug ridden. One example is the menu building script (desktop-menu). It relies on python-xdg which itself has been ported / updated to python3 and has bugs. Skidoo has helped quite a bit with testing / research / repairs in some thread on the forum. (I do not have my notes and cannot find the thread at the moment)
1,2,5. This requires making an install and upgrading the install to use testing or later repositories (antiX and debian); performing regular updates and testing. At the moment, basically anything gtk2 based and python2 based ( which is pretty much everything that is not command line 😉 ) need updating. The antiX “packages” are at https://gitlab.com/users/antiX-Linux/projects. The others I am not certain about. Trying to purge gtk2/python2 libs should show that I suppose; there is probably a better way using apt/dpkg. Beyond that just trying what is in the menu / control centre in a testing or newer environment.
3. This I am unsure about. I it think through transifex? https://www.transifex.com/anticapitalista/antix-development/ Some of the strings may be changed slightly in and update / rewrite.
4,5. A person to keep detailed issues up to date on gitlab would be nice from my point of view. It should make it easier for myself to view and address any problems without searching up the details in the forum. I believe once there is an issue reported the author(s) of the apps can handle priority and assignments. Though if the issue is obviously large it can be prioritized straight away. Right now as far as I know, everyone monitors the particular project and a bit around what they have worked on. Updates the project in their own gitlab and submits a pull request to the main antiX-Linux gitlab. At least that is how I have been doing it. What should issues/reports look like…? A forum thread to link to for details, then a summary on gitlab with the description of the problem seen, the way to replicate the problem, any other details from the thread that pertain to replicating the issue. Specific tests and hardware depends on the problem I suppose. If the problem is easy to replicate the issue then probably not. The gitlab summary should be enough. If there is something more complex and needs further testing that can be sorted in the forum thread.
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
manyroads
FWIW… I think all too many people get stuck in their heads trying to jam square pegs into round holes. I recommend everyone take that path that makes them most comfortable. In computing, Linux offers many, many options. Choose what makes you comfortable and suits your fancy/ needs. Tweak and adjust to your heart’s (and skills) content. The bottom line is that if antiX suits your needs- wonderful. If not, then don’t redefine antiX, find the right answer for yourself (it is almost certainly out there).
- This reply was modified 2 years, 5 months ago by manyroads.
Pax vobiscum,
Mark Rabideau - http://many-roads.com
"For every complex problem there is an answer that is clear, simple, and wrong." H. L. Mencken
dwm & i3wm ~Reg. Linux User #449130
20 Jan 2021 ~ "End of an Error"Brian Masinick
@manyroads:
Thank you, I agree. For me, antiX fits right “as is” and also allows me to create multiple versions to suit multiple interests.
Others may have to explore to find what suits them the best or modify the software and setup until satisfied.
--
Brian MasinickModdIt
regarding next debian release and hoops to jump through.
Debian is the only remaining major distribution which is not owned and ruled by a private company.
Red Hat is IBM. SUSE owned by a US Investment company Ubuntu Canonical, majority
ownership a South African Billionar ?. Microsoft is arguably following an Embrace and destroy path.
Google is involved at many levels, directly and indirectly.
linux as we know it is a very endangered species. Penguins unfortunately too.
Part of that path seems to be the make systemD removal near impossible. Concentrate and weaken an
ecosystem. Contributors are deliberatly ignoring a resolution to support init freedom.to the discussion regarding what we can do as individuals for a future release, I have been digging in to
translation for German. Much is controlled/contributed upstream and Suse is dominant. I have not given up
but my conclusion is pretty much rather than fight a private enterprise either an internal approach is needed
or I concentrate on helping new users. Education, Promotion, Expanding and winning users is also a very big
priority.I also want to discuss what we can contribute together with some old and new users but now is still critical
exam time and a total mess. Pandemic driven by goverment incompetence, arrogance or hidden agenda.
Get rid of ballast, as many aged persons as possible. Covid also kills more People of colour, Racism is rife
in hospitals.Governments and general public. Part of the blame game..My contacts in China and Vietnam are incredulous at what is happening outside of asia.
Xecure
@Dave
Thanks, Dave. I will do as you suggest and upgrade a clean antiX 19.3 base edition to testing. I will investigate and compile a list of applications gtk2/python2/qt4 dependent and ask one of the mods to publish it so that there is a thread for feedback, collaboration and testing. I will also check the gitlab page to see what projects have already been ported and need testing.I tend to get distracted easily and require myself to build lists, so I understand how frustrating it gets to keep them in order.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Anonymous
I have been digging in to translation for German.
Much is controlled/contributed upstream and Suse is dominant.^— This is not true.
Even to claim “…some is controlled…” or “…a tiny bit is controlled…” would be untrue.You are installing packaged software.
Suse developers do not package your software.
The (Debian, antiX, MX, et al) package maintainers may, and often do, create or patch any translation files associated with a package.Even for a particular program authored by Suse (or other corporate) developers, the most expedient route for submitting translations or other proposed changes is through the (your) package maintainer. That way, your proposed changes can be incorporated into a new pkg version which may become available to you and your peers within a matter of days. In contrast, changes submitted to and accepted by “upstream” authors/developers might not be incorporated into packages distributed via {Debian,antiX} stable repositories for months or even (literally) years.
manyroads
FWIW…When asserting anything about an industry, Linux included, facts always seem, to me, to be more interesting than any of my initial assumptions might be.
The links below indicate who the more likely significant contributors contributors are (most notably to the kernel). But, beware this ecosphere is blindingly diverse…
— https://www.omgubuntu.co.uk/2018/08/interesting-facts-about-linux
— https://thenewstack.io/contributes-linux-kernel/
— https://www.linuxfoundation.org/wp-content/uploads/2020/08/2020_kernel_history_report_082620v2.pdfEDIT: This article provides a great overview of the “Linux Universe”…. https://en.wikipedia.org/wiki/Linux
- This reply was modified 2 years, 5 months ago by manyroads.
Pax vobiscum,
Mark Rabideau - http://many-roads.com
"For every complex problem there is an answer that is clear, simple, and wrong." H. L. Mencken
dwm & i3wm ~Reg. Linux User #449130
20 Jan 2021 ~ "End of an Error"skidoo wrote:
> antix-viewer
it employs QTWebEngine,
correction:
FWIW, I noticed today that the current version of antix-viewer depends “libqt5webkit5”
(not the “QTWebEngine” component which had repeatedly experienced longstanding vulnerabilities)
- You must be logged in to reply to this topic.
