| 1 |
On 06/10/2016 10:20 AM, M. J. Everitt wrote: |
| 2 |
> On 10/06/16 17:16, james wrote: |
| 3 |
>> <snip> |
| 4 |
>> And this effort needs a documentation collection to support users, |
| 5 |
>> post installation to their target (ideal stage-4?) collection of |
| 6 |
>> packages; many of which they maintain themselves even if a strong-user |
| 7 |
>> or dev |
| 8 |
>> helps them assimilate those final packages. Then they can use stage-4 |
| 9 |
>> snapshots for periodic backups on complete systems. or for quick |
| 10 |
>> installs of new systems. (that would super-charge my cluster dev work)! |
| 11 |
>> |
| 12 |
>> |
| 13 |
>> It just seems to me that we have all of that now, but it is:: |
| 14 |
>> 1) not organized |
| 15 |
>> 2) needs documentation so folks do not have to use irc to ask the same |
| 16 |
>> questions over and over and over again (gentoo wiki is maturing in |
| 17 |
>> this direction too, imho. |
| 18 |
>> 3) needs (desires) gentoo managed repos, not github |
| 19 |
>> |
| 20 |
>> For now, we can use github for users. A glep or 2 can solved 1 and |
| 21 |
>> (2), well I was politely turned down, so suggestions on documentation |
| 22 |
>> to achieve this? Data-mining of emails and irc could easily provide |
| 23 |
>> the first-draft of the docs for need (2). |
| 24 |
>> |
| 25 |
>> |
| 26 |
>> |
| 27 |
>> James |
| 28 |
>> |
| 29 |
> (2) any user can edit wiki pages not governed by Projects. Even Project |
| 30 |
> pages I'm sure could be updated by means of patches submitted to the |
| 31 |
> appropriate team, with some basic follow-up to ensure action. |
| 32 |
|
| 33 |
Yes, exactly my point on this and similar threads. If the focus was |
| 34 |
placed on item (2), item (1) evaporates and github or /usr/local/portage |
| 35 |
solves (3). Gentoo managed SaaS is not necessary but highly desirable |
| 36 |
after (2) is solved. The 'grandness of these aforementioned musings' are |
| 37 |
irrelevant-noise and not necessary. If (2) is solved (door number 2 you |
| 38 |
are a winner!), the utopia, graciousness and nirvana all arrive, for |
| 39 |
free (or little effort). |
| 40 |
|
| 41 |
DOCUMENTATION |
| 42 |
to lift the masses, is what is truly needed at Project:Gentoo and is a |
| 43 |
red-herring at Gentoo, particularly among many of the devs. It is |
| 44 |
free-will choice, but it is akin to the lowest common denominator of |
| 45 |
public education (gentoo-style). Great resources, well organized allow |
| 46 |
for and encourage 'self-study'. Add incentives, like 'strong-user, |
| 47 |
repos, proxy, and dev, statues to the reward matrix and folks will |
| 48 |
follow the docs. Young kids (HS and college) need and want jobs. |
| 49 |
Providing a pathway to deep linux education (which is what gentoo really |
| 50 |
is) is the the honey to grow our ranks. Old farts (like me) will |
| 51 |
naturally gravitate to Gentoo, if (2) is solved. The better the docs and |
| 52 |
modules, the stronger the magnetism. |
| 53 |
|
| 54 |
For a more introspective survey, ask ordinary gentoo users how they |
| 55 |
use GIT/github in there daily routine. It's a practical-skills desert |
| 56 |
among rodinary-gentoo users, imho. |
| 57 |
|
| 58 |
|
| 59 |
> (3) until some enthusiastic sponsors come forward to host/maintain these |
| 60 |
> systems, I don't think its fair to overburden the already stretched |
| 61 |
> Infra guys (no offence, guys! you're doin a great job). |
| 62 |
|
| 63 |
Agreed. As I stated, solve (2) and all the grandiose schema are totally |
| 64 |
in reach. (3) is a trivial effort and can be multiplicative in pathways, |
| 65 |
*after (2) is solved*. Just look at Arch Linux. We are moving in that |
| 66 |
direction, if not mostly akin to a herd of cats..... |
| 67 |
|
| 68 |
> MJE |
| 69 |
|
| 70 |
|
| 71 |
Thanks for your insight, MJE. |
| 72 |
|
| 73 |
Great appreciation to all the gentoo devs.... past and present. |
| 74 |
James |
Archives