trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: September 2012

Re: [trinity-devel] Press

From: Darrell Anderson <humanreadable@...>
Date: Tue, 11 Sep 2012 15:13:55 -0700 (PDT)
> Regarding the original topic of this thread, I ran across
> this today: http://jehurst.wordpress.com/2012/02/23/my-last-kde-rant
> 
> I wonder how many other people just gave up after a while
> and don't know that TDE exists or is viable.

My view is few people know about Trinity. My perception is based upon reading an above average volume of daily free/libre software RSS news feeds. With consistency, KDE, GNOME, Xfce, LXDE, and Enlightenment are mentioned regularly but Trinity is not.

The complaint about KDE/GNOME developers not responding as desired can be narrowed in many ways to the introduction of features and designs that many traditional desktop users do not want. Trinity could fill that void, but only if users know that Trinity exists. Get Trinity in the news.

A similar common complaint with software development is developers introducing "cool" new features rather than focusing on bug quashing. Both are important but bug quashing should prevail. Any time a new feature is added, serious design thought must include how users can disable the new feature when not wanted. New features must not be shoved down any proverbial throats.

Trinity does not have a regular "maintenance point release" schedule to publicly prove that bugs are being seriously quashed or to keep Trinity in the news. Bug quashing (maintenance point releases) are a huge public relations benefit and are, for the most part, painless. For a small project like Trinity, a dozen or two bug fixes could constitute a maintenance bug release and keep Trinity in the news every two months.

The only way to get Trinity in the news is to get Trinity in the news. Release 3.5.13.1 as soon as practical. Coordinate and submit a realistic R14 schedule --- including tentative subsequent point releases. Get Trinity in the news.

Darrell