What's the future direction of TC?

[bassbum]

Tiny core is a nice distro, I wish there was a root password.

[tinypoodle]

Tiny core is a nice distro, I wish there was a root password.

Search the forum how to set one, this has been addressed.

[bassbum]

Thanks, I would like to see a GUI install option at some point for newer users. Otherwise, keep getting the word out, keep making improvements and I'm sure this distro will be around a while.

I'd like to see it replace DSL on the top ten.

[tinypoodle]

Umm, which top ten?

[gerald_clark]

Yeh, The website and download area have not been updated for 2 years.

[Guy]

On Distrowatch, DSL was classified as Dormant, quite some time ago. At that time it was removed from the ranking.

[dentonlt]

Since documentation is always a challenge ...

Perhaps TC needs 'documentation checkpoints'. Agreeing upon 'officially documented versions' might tie down the documentation challenge, keeping it from being an infinitely large and moving target.

If 3.3 is the next major release, perhaps plan on making a really thorough 3.3 manual/wiki, then plan to -not- thoroughly document 3.4/3.5 (instead, highlight 3.4/3.5 changes in the 3.3 docs). Start a new 'official' set of docs when 3.6rc1 comes out.

Or pick/plan what versions will be documentation checkpoints. Every major release? Or something.

This may help fill some of the documentation gap, clean up the wiki, archive/highlight some of the high-traffic forum content, etc. Having a "Tiny Manual" may also help better describe features, give good press, and attract more TC newbies.

[dentonlt]

EDIT: I have now been pointed to SvOlli's tcbuild frontend. See http://forum.tinycorelinux.net/index.php?topic=2056.0

Extension building is changing with each version. More options, etc. Documentation can help, but ...

Why not make a "Tiny Extension Builder" extension? Basically, a tool to either make or use a configuration file + support files to create extensions. The script/wrapper can help automate the creation/use of:

* a list of required dependencies/extensions for building the target
* a target extension type (pkg, pkg-dev, pkg-doc, etc)
* icons & desktop files are placed
* the listed source files

Then future extension builds can start with exactly where the last builder left off.

Start with bmarkus's old build script, and wrap it. An extension config file would just need to mention all that stuff above plus where to get binaries.

[Guy]

documentation is always a challenge

The Tiny Core team are doing a great job, and are busy doing it. You can't expect them to do more.

Anyone can contribute to wiki / documentation.

Instead of saying "It is not good enough," say: "What can I do do improve it."

I encourage everyone who has a good understanding of Tiny Core to contribute to the documentation. It will be appreciated.

As the number of people using Tiny Core increases, the number of people contributing to the documentation should also increase.


People who would like to contribute, but don't have a really good understanding of Tiny Core, could write about the applications they use, and include them in this section: http://wiki.tinycorelinux.com/Applications

[dentonlt]

Instead of saying "It is not good enough," say: "What can I do do improve it."

I'm not pointing at inadequacy, mind. Thread was to identify goals, so I came up with a target. Sorry if I stepped on fingers. I'm certainly willing to chip in on docs where I can.

[Guy]

Sorry if I stepped on fingers

Everyone is happy.

If you say, this is a goal that should be achieved. I say, who will do it?

Then encourage more people to get involved.

[bmarkus]

People who would like to contribute, but don't have a really good understanding of Tiny Core, could write about the applications they use, and include them in this section: http://wiki.tinycorelinux.com/Applications

I do not see reason to open WIKI articles for generic applications, like ImageMagick at TC WIKI where nothing is TC specific and the Internet is full with great manuals, introductions, etc, including upstream vendors site

[Guy]

I believe there are benefits to having pages for individual applications.

1. These can provide any information specific to running particular applications.
For example, look at this: http://wiki.tinycorelinux.com/mplayer-nodeps
Without that information, people would have a difficult time running the application.

2. Most of us know about the common, widely used applications. But have not heard about some of the rarer applications. If there was a description about each application, we could decide if that was an application we wanted to install. Without that information, it is sometimes a matter of installing an application to see what it does. If it is not what we want, we then need to remove it.

You can search the internet, and sometimes find the information you want. However, I think it would be a good idea to have information about Tiny Core applications, on the Tiny Core web site.

When there is information about more applications, we can introduce more features, such as the ability to search by category.

[tinypoodle]

For example, look at this: http://wiki.tinycorelinux.com/mplayer-nodeps
Without that information, people would have a difficult time running the application.

I can frankly say I was not aware of that page until I saw it mentioned now and I did not have any difficult time at all running mplayer-nodeps basic tasks.

Code: [Select]

mplayer --help
provided me with all info needed, and it also contains this reference:

* * * SEE THE MAN PAGE FOR DETAILS, FURTHER (ADVANCED) OPTIONS AND KEYS * * *

And if one could spare some resources, smplayer is a very handy GUI frontend   

[Guy]

I believe everything should be made as easy as possible for new users.

It amazes me that some people with a good understanding, don't seem to care about new users learning this for the first time. Some new users struggle. There are some people who try Tiny Core you don't hear from. They give up, and use another operating system.

I have been using Linux for many years now. But I remember when I first started, it took some time to learn the basic concepts. These things are easy for me now. But I think of others who are where I was.

Even now I try new things, and keep learning.

I also do many things with my time other than Tiny Core. If I had unlimited time, I could figure out anything I wanted to know. But I would like the information to be easily available, so I can find it quickly and easily. I am sure there are many other people who are busy, who want to find out things quickly and easily.


Tiny Core should also finish up with a professional wiki, where the information is correct, up to date, easy to understand, and covers a broad range of subjects. It can't be done immediately, but it should be the long term aim. Why should we be happy with the Tiny Core web site being less professional than the web sites of other distros?

and we can all contribute.