Boosting the development effort
Hello trisquel community,
Luis here, I'll like to start thanking all of you who have commented, shared a fix, valuable info and/or donated to the project.
Recently I'll like to thank anyone reporting issues on the new bug tracker at the GitLab instance, they keep growing.
As you might know there is an ongoing work to increase the development, the support for new architectures on the latest Aramo release and a overhaul in general of the whole project, as a result the project is continuously growing in the amount of work to be done, while the development team not so much.
Rubén and I have shared some thoughts and we see the need to point out the steps on how to contribute on development, rework the documentation, and ease the participation of new developers or contributors.
In that train of thought, I've like invite the community in general, and users in particular that would like to learn the trisquel development tools and workflow to start contributing on the maintenance for the project, some kind of "mentorship" if you will, as you might know the development meetings are Wednesdays at 12hrs ET, but you might find me online most of the week, as I'll be mainly involved on this effort.
Please note that this will be an ongoing process to learn how to find, identify, test and resolve issues within the trisquel workflow, not designed as coding classes.
Anyone interested please join us at the #trisquel-dev channel on IRC at the libera.chat network, you can post your doubts here or at the development mailing list.
Thank you for your attention, and keep enjoying this great project and community around it.
Cheers!
Hi,
About the Git Lab instance, it's inaccessible without JavaScript, I use among others, NoScript for privacy reasons, so, as is, I cannot help with the bug tracker.
I found a Git that works without JavaScript: SourceHut, you might take a look to see if it would suite your needs by gaining trust amongst those that like me prefer to avoid JavaScript for privacy reasons.
Also, imposing JavaScript is an accessibility issue, for example, people with visual deficiencies might not have a screen reader that deals with JavaScript.
Thanks for taking this in consideration.
Greetings.
> About the Git Lab instance, it's inaccessible without JavaScript, I use among others, NoScript for privacy reasons, so, as is, I cannot help with the bug tracker.
No problem, anyone that would not accept any javascript on their browser can use the devel mailing, personally I am willing to go the extra mile to meet someone there if there is a real intention to contribute.
> Also, imposing JavaScript is an accessibility issue, for example, people with visual deficiencies might not have a screen reader that deals with JavaScript.
On an ideal world we would already have all the tools already accesible for anyone and not only that, they would meet all our requirements.
That's not the case yet, there has been a lot of pondering on what we can do and we can accept in order to continue improving, as result we got the current state of Trisquel's Gitlab instance.
I agree that it's not the perfect solution, but is good enough to keep work moving forward, maybe with a more robust dev team eventually we'll be able to migrate to something better when possible.
My point is that gitlab should not be seen as a wall to stop new willing contributors to join.