Noob optimized live System - a specs' sheet
Posted: 25 Dec 2015, 18:34
Hey, may you have a sweet digestion ~:-]
Thought I'd begin sharing the specifications sheat I'm doin for a noob optimized live system, possibly with Porteus. With those of you guys that have some interest in this, so you can take, critic and share. It's a work in progress and this post will be updated to reflect further progress, and feedback.
Warning: This thread does contain English mistakes and coloured vocabulary. You should not read it this can hurt your feelings.
As I did it before, a note on doing a live OS for other people. May seem easy, about the same than building one for yourself. Well in my experience it's not (unless they're your twins). E.g. the audience may not want it, understand what it is or what (s)he can do with "that stick". Last winter I previously built a serie of live systems for three different kind of people. Audiences went from young internet techie to the employees at a reception centre for homeless people.
So let's start with the specifications sheat for a live system. Please add your input How would you make Porteus as good or a better solution than an easy-to-use cloud OS for these points?
A - Who
1. Define your Audience
2. Environment
* Hardware
* Human
* Usage (present and wanted)
3. Goal
Like for any project having defined the main goals is a major key to get the live system made, and further improved. "Main" means keep a low details level.
4. Available time and budget
B - What (needs)
Audience's main needs
* Usages and specific formats
* Accessibility
* Language(s)
* Specific hardware, eg. accessories
* Users and ACL
* Security, now and after
Support and Maintenance
* Security updates
* Distant access
C - How
That's were we gather, build, test and compare solutions that address the needs listed above, inside your time and budget.
Device
Software
OS
To be updated.
Thought I'd begin sharing the specifications sheat I'm doin for a noob optimized live system, possibly with Porteus. With those of you guys that have some interest in this, so you can take, critic and share. It's a work in progress and this post will be updated to reflect further progress, and feedback.
Warning: This thread does contain English mistakes and coloured vocabulary. You should not read it this can hurt your feelings.
As I did it before, a note on doing a live OS for other people. May seem easy, about the same than building one for yourself. Well in my experience it's not (unless they're your twins). E.g. the audience may not want it, understand what it is or what (s)he can do with "that stick". Last winter I previously built a serie of live systems for three different kind of people. Audiences went from young internet techie to the employees at a reception centre for homeless people.
So let's start with the specifications sheat for a live system. Please add your input How would you make Porteus as good or a better solution than an easy-to-use cloud OS for these points?
A - Who
1. Define your Audience
2. Environment
* Hardware
* Human
* Usage (present and wanted)
3. Goal
Like for any project having defined the main goals is a major key to get the live system made, and further improved. "Main" means keep a low details level.
4. Available time and budget
B - What (needs)
Audience's main needs
* Usages and specific formats
* Accessibility
* Language(s)
* Specific hardware, eg. accessories
* Users and ACL
* Security, now and after
Support and Maintenance
* Security updates
* Distant access
C - How
That's were we gather, build, test and compare solutions that address the needs listed above, inside your time and budget.
Device
Software
OS
To be updated.