1 |
Paweł Hajdan, Jr. posted on Mon, 17 Dec 2012 08:48:01 -0800 as excerpted: |
2 |
|
3 |
> On 12/17/12 7:32 AM, Anthony G. Basile wrote: |
4 |
>> So what should I teach? Here's what I've got off the top of my head: |
5 |
>> Please comment. If it gets systematized enough, it can be a guide to |
6 |
>> future devs too. Everything will be creative commons. |
7 |
> |
8 |
> I think it's worth to mention somewhere that although packages take |
9 |
> longer to compile than downloading binaries, people don't have to |
10 |
> _watch_ the compilation, and many things can be done e.g. overnight. |
11 |
|
12 |
++ |
13 |
|
14 |
Two reasons. From a user perspective, I often see people's complaints |
15 |
about how much of a waste of time gentoo is, watching the build output |
16 |
scroll by. People simply don't seem to realize that you can go away and |
17 |
do something else while all that's happening, or on a modern multi-core |
18 |
system with a decent amount of memory, set PORTAGE_NICENESS and MAKEOPTS |
19 |
appropriately, and even just go on using the system as you normally would |
20 |
if you weren't compiling in the background (of course as long as that |
21 |
"normally" isn't something like multi-thread ray-tracing, or using the |
22 |
machine as part of a low-latency sound studio, etc), and that what REALLY |
23 |
takes the time is updating the config files and otherwise adjusting to |
24 |
new versions of whatever packages you just upgraded, which would take the |
25 |
SAME amount of time to go thru, for a similar version update, regardless |
26 |
of whether the distro is binary-based or from-source. |
27 |
|
28 |
From a dev and student-dev perspective, more your focus here, it's an |
29 |
even MORE important lesson, as these guys will likely be doing a lot more |
30 |
package building over their schooling and career than the average user |
31 |
(tho maybe not so much more than the average gentoo user), even if they |
32 |
don't stick around on gentoo, and the earlier they get the message that |
33 |
they can let the computer do what the computer does best and that once |
34 |
it's setup properly they don't have to constantly watch it, only check on |
35 |
it once in awhile and check the final status and summary messages, the |
36 |
more efficient they're going to be as students, devs, and ultimately, |
37 |
employees. |
38 |
|
39 |
> Also, remember that Google's ChromeOS takes a lot of things from Gentoo, |
40 |
> including the package manager and many ebuilds. The idea here is that it |
41 |
> has applications in the industry. |
42 |
|
43 |
Good thought. Anchor the theory in real-world practicality. =:^) |
44 |
|
45 |
|
46 |
And since I replied here, I might as well throw in my own suggestion here |
47 |
as well. |
48 |
|
49 |
I don't see any mention of overlays on that list of covered subjects. |
50 |
Perhaps mention them under point #2, covering gentoo as a metadistro, |
51 |
then cover them in more detail under point #3, delivering the goods. |
52 |
|
53 |
Keep in mind that many gentoo devs begin working with project overlays |
54 |
well before they're official devs, under the supervision of the devs |
55 |
responsible for that project. Depending on an individual student's |
56 |
interest, they could be getting involved with projects and working in the |
57 |
respective project overlays before the end of the course, so introducing |
58 |
them fairly early on and giving them a chance to work with them, first as |
59 |
a user, then as they progress, as a dev, should work out quite well. |
60 |
|
61 |
Overlays should work in quite well with your coverage of git, too, since |
62 |
many of the overlays are git-based. You could either take Maxim K's |
63 |
github idea and do the overlay there, or do something similar using |
64 |
overlays.gentoo.org. |
65 |
|
66 |
Either way you'd presumably work with the hosting provider, github, |
67 |
gentoo, or other. I don't know if you can delete github projects, but if |
68 |
I were github, I'd *JUMP* at the chance to cooperate with someone |
69 |
offering a college level course integrating github, and would likely |
70 |
offer to work with you on integrating anything special you needed, like |
71 |
deletable projects, in ordered to do it. This since once a student's |
72 |
using github, they're going to take that practice with them, and in a few |
73 |
years, many of them will likely be pushing paid github accounts at |
74 |
wherever they end up working. If you pursue the github idea, I'd |
75 |
DEFINITELY recommend contacting github, as they may well be able to |
76 |
suggest or even create other features to fit your class as well, and they |
77 |
should have a pretty high motivation to do so. They /might/ even offer |
78 |
to sponsor some of the course material cost, etc, especially since they |
79 |
can almost certainly write it off as either advertising/PR expense or |
80 |
educational donation. =:^) |
81 |
|
82 |
OTOH if you chose overlays.gentoo.org for your hosting, you should get |
83 |
quite close cooperation as well, likely even closer due to scale and |
84 |
direct focus, and AFAIK gentoo already has some experience there from the |
85 |
Google Summer of Code projects. But the experience isn't as easily or |
86 |
directly useful for students beyond the course and gentoo, as working |
87 |
with github would be. OTOH, working too closely with github might be |
88 |
seen as a commercial endorsement you or your school may not wish to make |
89 |
(except perhaps if they /do/ actually offer sponsorship, most schools |
90 |
know how to make /that/ work), while gentoo as a non-profit that's |
91 |
already directly part of the course shouldn't have that issue, and could |
92 |
be seen as useful in its own right since it parallels the adaption to an |
93 |
existing work environment that an employee (and for that matter, |
94 |
volunteer joining a FLOSS project) generally must make, regardless of |
95 |
whatever github or etc experience they may have already. |
96 |
|
97 |
-- |
98 |
Duncan - List replies preferred. No HTML msgs. |
99 |
"Every nonfree program has a lord, a master -- |
100 |
and if you use the program, he is your master." Richard Stallman |