Language Selection

English French German Italian Portuguese Spanish

Tux Machine's editorial picks are...

too many links

Take a look at this for example. http://i.imgur.com/MQ21f8r.png way too many links and it actually keeps going if I scroll down.
No one is going to read all of that. People should be easily able to recognise new content on the website.

Front page

Is shortened summaries, especially of such posts, were to appear in the front page, would that be an improvement? It would necessitate more clicking (to expand the post) but it would save space.

front page

Yes definitely Smile The short summary can include small headlines "New releases from so and so' and "Learn new tricks to fix this and tips to do that" or "New howtos for...." or "Guides for compiling this and that and migrating from software A to B etc.." then when the readers click 'read more', they see the full set of links.

And again, thank you for your dedication towards making the website more user friendly Smile

Shortening

I will be shortening long posts with many links from now on.

the leftovers

the leftovers thing with many links is way too annoying in my opinion.

Suggestion

Do you suggest that they don't get posted at all or just not in this current form?

Not in it's current form.

Not in it's current form. Perhaps make a separate page for "tutorials", or left overs. call it something like 'back news' or short news. And then keep the major articles on the front page Smile

(and thank you for replying)

Feeds

The problem is, how will people subscribe to those pages or be made aware of their existence? it would basically fragment the flow, wouldn't it? Some sites like FAIR.org do this (splitting to sections) and it complicates syndication.

More in Tux Machines

Brocade Wants to Be Red Hat of OpenDaylight

Brocade wants to have the same relationship with OpenDaylight as Red Hat has with Linux. Read more

Rise of Linux – a hacker’s history

The original code of Linux was written for fun, or in Eric Raymond’s phrase, to ‘scratch the itch’ of Linus Torvalds, and later to satisfy the enthusiasm and programming itch of an assortment of hackers and hobbyists who, for the most part, had grown up in the age of the ZX80 and the BBC Micro, Acorns and Apricots, for which the code was often available – and hackable. For those who spent their childhood or adolescence delving into the home computers of the late Seventies and early Eighties, playing with software was a learning experience, and something to be shared. Linux could be said to have grown out of this ethos as much as it grew out of the free software movement, or the early Nineties culture of Usenet where “if you wrote something neat you posted it to Usenet” and the only proviso that came with the software was that “if the software breaks you get to keep both pieces.” Read more

Lollipop unwrapped: Chromium WebView will update via Google Play

Android 5.0, codenamed Lollipop, has introduced a key change to the WebView component, used by app developers to display HTML 5 content within their apps, making new features more readily available. Read more

Being a Sporadic Overview Of Linux Distribution Release Validation Processes

Our glorious Fedora uses Mediawiki to manage both test cases and test results for manual release validation. This is clearly ludicrous, but works much better than it has any right to. ‘Dress rehearsal’ composes of the entire release media set are built and denoted as Test Composes or Release Candidates, which can be treated interchangably as ‘composes’ for our purposes here. Each compose represents a test event. In the ‘TCMS’ a test event is represented as a set of wiki pages; each wiki page can be referred to as a test type. Each wiki page must contain at least one wiki table with the rows representing a concept I refer to as a unique test or a test instance. There may be multiple tables on a page; usually they will be in separate wiki page sections. Read more