I'll add my comments to Ed's below:
1. Slides 9 and 10 are duplicate slides
2. Slide 15, I might clarify that the /efs/dev namespace is local
("regionalized"?), and is the development sandbox. Without explanation,
"development data" might imply tools/compilers/environments. Might be
moot, but mentioning that /efs/dev is not replicated might help.
3. Slide 16, Release: typically a single, versionized release of a
single software product
4. Minor nit, and maybe nobody cares at YAPC, but I've always seen
"Perl" used when referring to the language, and "perl" when referring to
the interpreter itself (see Slide 34 and 35 for example).
Other than that, looks good. The voiceover is key to making this all
make sense to those at the talk.
----
David A. Desrosiers | Bank of America | VP/Global Technology | EFS
<http://efs.worldnet.ml.com/> Engineering Team Lead | NY
* ddesrosi <mailto:[email protected]> | mobile: (860)
271-1642 | google: (860) 367-8456 | bberry pin: 21BE16BC
P Please consider the environment before printing this email!
From: [email protected]
[mailto:[email protected]] On Behalf Of Inderrieden,
Edward B
Sent: Thursday, June 17, 2010 9:38 AM
To: EFS core development list; Moore, W Phillip; Gay, Gerard
Subject: Re: [EFS-dev] YAPC::NA 2010 EFS Talk Draft
Comments and questions by slide as I go over it.
* Slide 9: despite your use of it, there is no word "noone". It
should be "no one".
* Slide 12: Not really important, but I am not seeing how you
get to these goals from your previous slides, especially "access
multiple releases simultaneous". I know that is the goal of EFS, but I
am unclear how your previous slides are addressed by these bullets.
Perhaps go back and make sure each point is addressed as an issue? I may
have just missed it.
* Slide 13: Worth mentioning that EFS 3 is alpha? Is that later?
Is that fact counter-productive?
* Slide 15: nice! I like that /efs/home is there.
* Slide 20: Is this too deep for your audience. Probably not,
but something to consider.
* Slide 23: Do you want to mention Kerberos here? Is GSSAPI
Kerberos?
* Slide 30: Doesn't the access have to be delegated? You can
"can"; should it be "must"? Is there a parameter you can set where this
is turned off?
* Slide 32: are these items (Moose, DBIx::Class) still
"bleeding" edge? I thought it was pretty standard at this point.
* Slide 33: Do you want to mention the difficulty of getting
Perl into EFS during installation? Any fun stories?
Anything about EFS Deploy? Worth mentioning?
Otherwise, good flow; sounds good!
From: [email protected]
[mailto:[email protected]] On Behalf Of Phillip Moore
Sent: Wednesday, June 16, 2010 2:35 PM
To: EFS core development list
Subject: [EFS-dev] YAPC::NA 2010 EFS Talk Draft
Here's the draft of the talk for next week. As usual, compressing
everything EFS is and does into a 40 minute talk isn't easy.
I'm going to spend some more time on this on Friday, and probably do
some last minute tweaking next week.
I think that rather than more detail about how EFS works, a couple of
real world use cases would be helpful. I'm thinking about a couple of
slides about how gcc is integrated will be interesting, as well as a
couple that show how EFS itself is managed out of /efs/dist, in
particular how we use releasealiases to manage upgrades.
Anyway, feedback (even typos :-P) most welcome.
_______________________________________________
EFS-dev mailing list
[email protected]
http://mailman.openefs.org/mailman/listinfo/efs-dev
