Hi,

I have come across T2 only a few weeks ago and have been playing around with it in my free time. So I can share my perspective as a newcomer. I have been using Slackware for the last few years and I like T2 so far as it seems to take a similar approach, but with the added benefit, that it supports a lot more architectures. I also like the approach that T2 takes in regards to system configuration and packaging. However, there are some things that make the on-boarding a little bit tedious for me and some things I wish that would be added.

Documentation and Usability:
Comprehensive Documentation: Enhance documentation to make it more accessible for new users. Clear, detailed guides and tutorials can help users understand how to configure and use T2 SDE effectively.

I think documentation is the one big thing T2 needs more of. The handbook, even though old, is the best introduction at the moment. Alas it is unfinished and leaves some things out. As far as I can tell, it is the only good resource for getting information about the package system and network configuration. Of course one can always look at the scripts in the repository, but without watching some of your videos and watching
you do some packaging work, I would have a much harder time.
For example I still don't quite know where built packages are stored after building them with Build-Pkg or how mine factors into the package management. I don't need it for installing packages, as I usually do this with Emerge-Pkg but removing software is done via mine. I understand that mine is to be replaced some time into the future according to the Github issues, but until it happens a little bit more info would be nice
and save time.

Package Management:
Dependency Resolution: Improve automatic dependency resolution to make it easier for users to select and compile packages without running into issues. Repository Management: Maintain and expand repositories with up-to-date packages and ensure easy access to popular and essential software.

The package and build systems seems really nice once you get to know it. I am not there yet ;). Nonetheless the dependency resolution doesn't quite work that well yet. After installing T2 24.6 x86_64 wayland desktop iso and doing the post install recompilation steps (python, perl, etc.), the system is not able to do an Emerge-Pkg -system without some of the builds failing. The mesa package is one example due to not finding the xcb header files (in my case at least). Nothing a symlink can't fix, but as a newcomer to T2 and trying to install, configure and update the default system, it is a little bit of a road block to immediately dive head first into the package scripts and trying to fix missing dependencies or missing includes for package building. I would at least expect the default distributed images to update cleanly.

Community and Support:
Active Community Engagement: Foster a more active and supportive community to share knowledge, troubleshoot issues, and contribute to the project.

It was a bit hard to find sites to get into touch with the community. Of course there is the reddit thread, but other information seemed outdated on the T2 website. For example the discord channel is mentioned several times but no valid invitation link is given. I found a link on your Patreon page, but to see it I need to create an account and set up a donation. There is nothing wrong with that and support is important, but if the discord is meant to be an exclusive community channel, then it has to be communicated as such in my opinion. Similar with the mailing list. The gmane links are outdated and I could only find archives which mention a t2-project.org mailing list, but not a t2sde.org mailing list as referenced on the T2 website. Which one should be used? There seem to be also more than one mailing list, like the one for commits and developers, but I could not find any archive of them. A little more clarification would be appreciated.

Furthermore I would really like a wiki for sharing knowledge about T2. In my opinion T2 shines with its hardware and cross compiling support. A place where the community can create pages and share the knowledge about configuring and running T2 on different hardware would be really nice. It might even be a way to share some target configurations for older hardware like the Wifi access point you configured in one of your streams. Of course normal articles about the build system and configuration or guides from setting up a simple desktop system with graphical login up to creating a virtualization environment with T2 will also find a good place there.

Ok, that was a lot and I hope you stuck with me :) These were my main points so far. All in all I really like T2 so far and will try to get more and more into it. I already have some ideas of my own and some packages I want to add, given I find the time. Thank you and everyone else, that is already contributing, for your work!


Keep up the great work and thank you for this distro!

  n1to



----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
li...@t2-project.org with a subject of: unsubscribe t2

Reply via email to