JP Vossen on 6 Nov 2015 22:13:09 -0800

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] Suggestion for covering open source project's history before 8:00

+1 for that idea.

I'd also like to propose that attendee introductions wait until right
before the preso, which is what we do at North, but not West and I dunno
about Central.  But when we do them too early at West latecomers miss them.

It might also be good to include in the intros some clue about
experience and skill-levels for the topic, which may help the presenter
tailor the presentation a bit.  It might not too, odds are good there
will be some utter newbies and some experts for any given topic.  Still...

Finally, OK, I'll bite.  Why *did* RH really acquire CentOS?

On 11/07/2015 12:19 AM, Mike DePaulo wrote:
> Hey guys,
> As we've been discussing in other threads, it is very valuable to talk
> about an open source project's history, or the history of prior
> projects, during a plug talk.
> However, this makes the talk last more than 1 hour.
> Since all 3 locations have people typically arriving at 7:00, but the
> talk starts at 8:00, how about we give the presenter the option of
> covering the history from either 7:30 to 8:00 or 7:45 to 8:00?
> Then at 8:00 there would be a brief refresher on the history for those
> walking in, or eating noms outside the classroom at plug north.
> The recording could begin at 8:00, or earlier if the presenter prefers.
> Personally, I am going to finish preparing my 1-hour long fedora talk
> for 10/10/2015 with only 1 or 2 slides on Fedora's history. (Where
> history == prior to the last ~4 years; when many cool things have
> happened and many challenges have arisen (cough: "why did Red Hat really
> acquire CentOS?")). Then I'll see if I have time to prepare 15-30
> minutes of history.

JP Vossen, CISSP            |:::======|
My Account, My Opinions     |=========|
"Microsoft Tax" = the additional hardware & yearly fees for the add-on
software required to protect Windows from its own poorly designed and
implemented self, while the overhead incidentally flattens Moore's Law.
Philadelphia Linux Users Group         --
Announcements -
General Discussion  --