Reflowed events.
This commit is contained in:
parent
0b8a2ce783
commit
a655c7f5fb
274
events.xml
274
events.xml
|
@ -1,175 +1,135 @@
|
||||||
<eventdefs>
|
<eventdefs>
|
||||||
|
|
||||||
|
|
||||||
<!--spring 2007-->
|
<!--spring 2007-->
|
||||||
|
|
||||||
|
|
||||||
<eventitem date="2007-07-17" time="7:00 PM" room="AL 116" title="C++0x - An Overview">
|
<eventitem date="2007-07-17" time="7:00 PM" room="AL 116" title="C++0x - An Overview">
|
||||||
<short>Bjarne Stroustrup</short>
|
<short>Bjarne Stroustrup</short>
|
||||||
<abstract><p>
|
<abstract><p>
|
||||||
A good programming language is far more than a simple collection of
|
A good programming language is far more than a simple collection of
|
||||||
features. My ideal is to provide a set of facilities that smoothly work
|
features. My ideal is to provide a set of facilities that smoothly work
|
||||||
together to support design and programming styles of a generality beyond
|
together to support design and programming styles of a generality beyond
|
||||||
my imagination. Here, I briefly outline rules of thumb (guidelines,
|
my imagination. Here, I briefly outline rules of thumb (guidelines,
|
||||||
principles) that are being applied in the design of C++0x. Then, I
|
principles) that are being applied in the design of C++0x. Then, I
|
||||||
present the state of the standards process (we are aiming for C++09) and
|
present the state of the standards process (we are aiming for C++09) and
|
||||||
give examples of a few of the proposals such as concepts, generalized
|
give examples of a few of the proposals such as concepts, generalized
|
||||||
initialization, being considered in the ISO C++ standards committee.
|
initialization, being considered in the ISO C++ standards committee.
|
||||||
Since there are far more proposals than could be presented in an hour,
|
Since there are far more proposals than could be presented in an hour,
|
||||||
I'll take questions.
|
I'll take questions.
|
||||||
</p></abstract>
|
</p></abstract>
|
||||||
</eventitem>
|
</eventitem>
|
||||||
|
|
||||||
<eventitem date="2007-07-06" time="4:30 PM"
|
<eventitem date="2007-07-06" time="4:30 PM" room="AL 116" title="Copyright vs Community in the Age of Computer Networks">
|
||||||
room="AL 116" title="Copyright vs Community in the Age of Computer Networks">
|
<short>Richard Stallman</short>
|
||||||
<short>Richard Stallman</short>
|
<abstract><p>
|
||||||
<abstract>
|
Copyright developed in the age of the printing press, and was designed
|
||||||
<p>Copyright developed in the age of the printing press, and was designed to fit with
|
to fit with the system of centralized copying imposed by the printing
|
||||||
the system of centralized copying imposed by the printing press. But the copyright
|
press. But the copyright system does not fit well with computer
|
||||||
system does not fit well with computer networks, and only draconian punishments can
|
networks, and only draconian punishments can enforce it.
|
||||||
enforce it.</p>
|
</p><p>
|
||||||
<p>
|
The global corporations that profit from copyright are lobbying for
|
||||||
The global corporations that profit from copyright are lobbying for draconian punishments,
|
draconian punishments, and to increase their copyright powers, while
|
||||||
and to increase their copyright powers, while suppressing public access to technology. But
|
suppressing public access to technology. But if we seriously hope to
|
||||||
if we seriously hope to serve the only legitimate purpose of copyright--to promote progress,
|
serve the only legitimate purpose of copyright--to promote progress, for
|
||||||
for the benefit of the public--then we must make changes in the other direction.</p>
|
the benefit of the public--then we must make changes in the other
|
||||||
<p>
|
direction.
|
||||||
Ths CSC would like to thank MEF and Mathsoc for funding this talk.
|
</p><p>
|
||||||
</p>
|
Ths CSC would like to thank MEF and Mathsoc for funding this talk.
|
||||||
<p>
|
</p><p>
|
||||||
<a href="http://www.fsf.org/events/waterloo20070706">The
|
<a href="http://www.fsf.org/events/waterloo20070706">The Freedom Software Foundation's description</a><br />
|
||||||
Freedom Software Foundation's description</a><br />
|
<a href="http://www.defectivebydesign.org">FSF's anti-DRM campaign</a><br />
|
||||||
<a href="http://www.defectivebydesign.org">FSF's anti-DRM
|
<a href="http://www.badvista.org">Why you shouldn't use Microsoft Vista</a><br />
|
||||||
campaign</a><br />
|
<a href="http://www.gnu.org">The GNU's Not Unix Project</a><br />
|
||||||
<a href="http://www.badvista.org">Why you shouldn't use
|
</p></abstract>
|
||||||
Microsoft Vista</a><br />
|
</eventitem>
|
||||||
<a href="http://www.gnu.org">The GNU's Not Unix
|
|
||||||
Project</a><br />
|
|
||||||
</p>
|
|
||||||
</abstract>
|
|
||||||
</eventitem>
|
|
||||||
|
|
||||||
<eventitem date="2007-06-27" time="4:30 PM"
|
<eventitem date="2007-06-27" time="4:30 PM" room="MC 4042" title="Usability in the wild">
|
||||||
room="MC 4042" title="Usability in the wild">
|
<short>A talk by Michael Terry</short>
|
||||||
<short>A talk by Michael Terry</short>
|
<abstract><p>
|
||||||
<abstract>
|
What is the typical monitor resolution of a GIMP user? How many monitors
|
||||||
<p>What is the typical monitor resolution of
|
do they have? What size images do they work on? How many layers are in
|
||||||
a GIMP user? How many monitors do they
|
their images? The answers to these questions are generally unknown: No
|
||||||
have? What size images do they work on? How
|
means currently exist for open source applications to collect usage
|
||||||
many layers are in their images? Th
|
data. In this talk, I will present ingimp, a version of GIMP that has
|
||||||
e answers to these questions are generally
|
been instrumented to automatically collect usage data from real-world
|
||||||
unknown: No means currently exist for
|
users. I will discuss ingimp's design, the type of data we collect, how
|
||||||
open source applications to collect usage
|
we make the data available on the web, and initial results that begin to
|
||||||
data.
|
answer the motivating questions.
|
||||||
In this talk, I will present
|
</p><p>
|
||||||
ingimp, a version of GIMP that
|
ingimp can be found at http://www.ingimp.org.
|
||||||
has been in
|
</p></abstract>
|
||||||
strumented to automatically collect usage
|
</eventitem>
|
||||||
data from real-world users. I will dis
|
|
||||||
cuss ingimp's design, the type of data we
|
|
||||||
collect, how we make the data availabl
|
|
||||||
e on the web, and initial results that
|
|
||||||
begin to answer the motivating questions.
|
|
||||||
ingimp can be found at
|
|
||||||
http://www.ingimp.org.
|
|
||||||
|
|
||||||
</p>
|
|
||||||
</abstract>
|
|
||||||
</eventitem>
|
|
||||||
|
|
||||||
<eventitem date="2007-06-22" time="4:30 PM"
|
<eventitem date="2007-06-22" time="4:30 PM"
|
||||||
room="MC 4042"
|
room="MC 4042"
|
||||||
title="Email encryption for the masses">
|
title="Email encryption for the masses">
|
||||||
<short>Ken Ho</short>
|
<short>Ken Ho</short>
|
||||||
<abstract>
|
<abstract><p>
|
||||||
<p>E-mail transactions and confirmations have become commonplace
|
E-mail transactions and confirmations have become commonplace and the
|
||||||
and the
|
information therein can often be sensitive. We use email for purposes as
|
||||||
information therein can often be sensitive. We use email for purposes as
|
mundane as inbound marketing, to as sensitive as account passwords and
|
||||||
mundane as inbound marketing, to as sensitive as account passwords and
|
financial transactions. And nearly all our email is sent in clear text;
|
||||||
financial transactions. And nearly all our email is sent in clear text;
|
we trust only that others will not eavesdrop or modify our messages. But
|
||||||
we trust only that others will not eavesdrop or modify our messages. But
|
why rely on the goodness or apathy of your fellow man when you can
|
||||||
why rely on the goodness or apathy of your fellow man when you can
|
ensure your message's confidentiality with encryption so strong not even
|
||||||
ensure your message's confidentiality with encryption so strong not even
|
the NSA can break? Speaker (Kenneth Ho) will discuss email encryption,
|
||||||
the NSA can break? Speaker (Kenneth Ho) will discuss email encryption,
|
and GNU Privacy Guard to ensure that your messages are sent, knowing
|
||||||
and GNU Privacy Guard to ensure that your messages are sent, knowing
|
that only your intended recipient can receive it.
|
||||||
that only your intended recipient can receive it.
|
</p><p>An optional code-signing party will be held immediately
|
||||||
</p>
|
afterwards; if you already have a PGP or GPG key and wish to
|
||||||
<p>An optional code-signing party will be held immediately
|
participate, please submit the public key to
|
||||||
afterwards; if
|
<a href="mailto:gpg-keys@csclub.uwaterloo.ca">
|
||||||
you already have a PGP or GPG key and wish to participate, please submit
|
gpg-keys@csclub.uwaterloo.ca</a>.
|
||||||
the public key to <a
|
</p><p>
|
||||||
href="mailto:gpg-keys@csclub.uwaterloo.ca">gpg-keys@csclub.uwaterloo.ca</a>.
|
Laptop users are invited also to participate in key-pair sharing
|
||||||
Laptop users are
|
on-site, though it is preferable to send keys ahead of time.
|
||||||
invited
|
</p></abstract>
|
||||||
also to participate in key-pair sharing on-site, though it is preferable
|
</eventitem>
|
||||||
to send keys ahead of time.</p>
|
|
||||||
</abstract>
|
|
||||||
</eventitem>
|
|
||||||
|
|
||||||
<eventitem date="2007-06-18" time="4:30 PM"
|
<eventitem date="2007-06-18" time="4:30 PM"
|
||||||
room="DC 4040" title="Fedspulse.ca, Web 3.0, Portals and the Metaverse">
|
room="DC 4040" title="Fedspulse.ca, Web 3.0, Portals and the Metaverse">
|
||||||
<short>Peter Macdonald</short>
|
<short>Peter Macdonald</short>
|
||||||
<abstract>
|
<abstract><p>
|
||||||
<p>The purpose of the talk is to address how students interact
|
The purpose of the talk is to address how students interact with the
|
||||||
with the
|
internet, and possibilities for how they could do so more efficiently.
|
||||||
internet, and possibilities for how they could do so more
|
Information on events and happenings on UW campus is currently hosted
|
||||||
efficiently. Information on events and happenings on UW campus is
|
on a desperate, series of internet applications. Interactions with
|
||||||
currently hosted on a desperate, series of internet
|
WatSFIC is done over a Yahoo! mailing list, GLOW is organized through a
|
||||||
applications. Interactions with WatSFIC is done over a Yahoo! mailing
|
Facebook group, campus information at large comes from
|
||||||
list, GLOW is organized through a Facebook group, campus information
|
<a href="http://imprint.uwaterloo.ca">imprint.uwaterloo.ca</a>. There
|
||||||
at large comes from <a href="http://imprint.uwaterloo.ca">imprint.uwaterloo.ca</a>. There has been
|
has been historical pressures from various bodies, including some
|
||||||
historical pressures from various bodies, including some thinkers in
|
thinkers in feds and the administration, to centralize these issues. To
|
||||||
feds and the administration, to centralize these issues. To create a
|
create a one stop shop for students on campus.
|
||||||
one stop shop for students on campus.
|
</p><p>
|
||||||
</p>
|
It is not through confining data in cages that we will finally link all
|
||||||
<p>It is not through confining data in cages that we will finally link
|
student activities together, instead it is by truly freeing it. When
|
||||||
all
|
data can be anywhere, then it will be everywhere students need it. This
|
||||||
student activities together, instead it is by truly freeing it. When
|
is the underlying concept behind metadata, data that is freed from the
|
||||||
data
|
confines of it's technical imprisonment. Metadata is the extension of
|
||||||
can be anywhere, then it will be everywhere students need it. This is
|
people, organizations, and activities onto the internet in a way that is
|
||||||
the
|
above the traditional understanding of how people interact with their
|
||||||
underlying concept behind metadata, data that is freed from the confines
|
networks. The talk will explore how Metadata can exist freely on the
|
||||||
of
|
internet, how this affects concepts like Web 3.0, and how the university
|
||||||
it's technical imprisonment. Metadata is the extension of people,
|
and the federation are poised to take advantage of this burgeoning new
|
||||||
organizations, and activities onto the internet in a way that is above
|
technology through adoptions of portals which will allow students to
|
||||||
the
|
interact with a metaverse of data.
|
||||||
traditional understanding of how people interact with their networks.
|
</p></abstract>
|
||||||
The
|
</eventitem>
|
||||||
talk will explore how Metadata can exist freely on the internet, how
|
|
||||||
this
|
|
||||||
affects concepts like Web 3.0, and how the university and the federation
|
|
||||||
are
|
|
||||||
poised to take advantage of this burgeoning new technology through
|
|
||||||
adoptions
|
|
||||||
of portals which will allow students to interact with a metaverse of
|
|
||||||
data.
|
|
||||||
</p>
|
|
||||||
</abstract>
|
|
||||||
</eventitem>
|
|
||||||
|
|
||||||
|
|
||||||
<!-- Winter 2007 -->
|
<!-- Winter 2007 -->
|
||||||
|
|
||||||
<eventitem date="2007-04-11" time="3:30 PM"
|
<eventitem date="2007-04-11" time="3:30 PM" room="Hagey Hall" title="The Free Software Movement and the GNU/Linux Operating System">
|
||||||
room="Hagey Hall" title="The Free Software Movement and the GNU/Linux Operating System">
|
<short>A talk by Richard M. Stallman (RMS) <b>[CANCELLED]</b></short>
|
||||||
<short>A talk by Richard M. Stallman (RMS) <b>[CANCELLED]</b></short>
|
<abstract><p>
|
||||||
<abstract>
|
Richard Stallman has cancelled his trip to Canada.
|
||||||
<p>
|
</p></abstract>
|
||||||
<!-- Richard Stallman will speak about the goals and philosophy of the Free Software Movement, and the status and history the GNU operating
|
|
||||||
system, which in combination with the kernel Linux is now used by tens of millions of users world-wide.
|
|
||||||
-->
|
|
||||||
Richard Stallman has cancelled his trip to Canada.
|
|
||||||
</p>
|
|
||||||
</abstract>
|
|
||||||
</eventitem>
|
</eventitem>
|
||||||
|
|
||||||
|
<eventitem date="2007-04-08" time="4:30pm" room="MC 4041" title="Loop Optimizations">
|
||||||
<eventitem date="2007-04-08" time="4:30pm"
|
<short>A talk by Simina Branzei</short>
|
||||||
room="MC 4041" title="Loop Optimizations">
|
<abstract><p>
|
||||||
<short>A talk by Simina Branzei</short>
|
Abstract coming soon!
|
||||||
<abstract>
|
</p></abstract>
|
||||||
<p>
|
|
||||||
Abstract coming soon!
|
|
||||||
</p>
|
|
||||||
</abstract>
|
|
||||||
</eventitem>
|
</eventitem>
|
||||||
|
|
||||||
<eventitem date="2007-04-01" time="4:30 PM" room="MC 3036" title="Surprise
|
<eventitem date="2007-04-01" time="4:30 PM" room="MC 3036" title="Surprise
|
||||||
|
@ -251,21 +211,21 @@ The ReactOS operating system has been in development for over eight years and ai
|
||||||
with a fully functional and Windows-compatible distribution under the GPL license. ReactOS comes with
|
with a fully functional and Windows-compatible distribution under the GPL license. ReactOS comes with
|
||||||
its own Windows 2003-based kernel and system utilities and applications, resulting in an environment
|
its own Windows 2003-based kernel and system utilities and applications, resulting in an environment
|
||||||
identical to Windows, both visually and internally.
|
identical to Windows, both visually and internally.
|
||||||
<br/><br/>
|
</p><p>
|
||||||
More than just an alternative to Windows, ReactOS is a powerful platform for academia, allowing
|
More than just an alternative to Windows, ReactOS is a powerful platform for academia, allowing
|
||||||
students to learn a variety of skills useful to software testing, development and management, as well as
|
students to learn a variety of skills useful to software testing, development and management, as well as
|
||||||
providing a rich and clean implementation of Windows NT, with a kernel compatible to published
|
providing a rich and clean implementation of Windows NT, with a kernel compatible to published
|
||||||
internals book on the subject.
|
internals book on the subject.
|
||||||
<br/><br/>
|
</p><p>
|
||||||
This talk will introduce the ReactOS project, as well as the various software engineering challenges
|
This talk will introduce the ReactOS project, as well as the various software engineering challenges
|
||||||
behind it. The building platform and development philosophies and utilities will be shown, and
|
behind it. The building platform and development philosophies and utilities will be shown, and
|
||||||
attendees will grasp the vast amount of effort and organization that needs to go into building an
|
attendees will grasp the vast amount of effort and organization that needs to go into building an
|
||||||
operating system or any other similarly large project. The speaker will gladly answer questions related to
|
operating system or any other similarly large project. The speaker will gladly answer questions related to
|
||||||
his background, experience and interests and information on joining the project, as well as any other
|
his background, experience and interests and information on joining the project, as well as any other
|
||||||
related information.
|
related information.
|
||||||
<br/><br/>
|
</p><p>
|
||||||
<strong>Speaker Bio</strong>
|
<strong>Speaker Bio</strong>
|
||||||
<br/><br/>
|
</p><p>
|
||||||
Alex Ionescu is currently studying in Software Engineering at Concordia University in Montreal, Quebec
|
Alex Ionescu is currently studying in Software Engineering at Concordia University in Montreal, Quebec
|
||||||
and is a Microsoft Technical Student Ambassador. He is the lead kernel developer of the ReactOS Project
|
and is a Microsoft Technical Student Ambassador. He is the lead kernel developer of the ReactOS Project
|
||||||
and project leader of TinyKRNL. He regularly speaks at Linux and Open Source conferences around the
|
and project leader of TinyKRNL. He regularly speaks at Linux and Open Source conferences around the
|
||||||
|
@ -317,7 +277,7 @@ writing world class software. These techniques are universal to all
|
||||||
programming languages, platforms and deployed technologies but are often times
|
programming languages, platforms and deployed technologies but are often times
|
||||||
viewed as being so obvious that they are ignored by the typical developer. The
|
viewed as being so obvious that they are ignored by the typical developer. The
|
||||||
topics covered in this lecture will include:
|
topics covered in this lecture will include:
|
||||||
<br/><br/>
|
</p><p>
|
||||||
- Writing bug-free to extremely low bug count software in real-time<br/>
|
- Writing bug-free to extremely low bug count software in real-time<br/>
|
||||||
- The concept of single-source, universal platform software<br/>
|
- The concept of single-source, universal platform software<br/>
|
||||||
- Programming language interoperability<br/>
|
- Programming language interoperability<br/>
|
||||||
|
@ -391,7 +351,7 @@ promise multi-core holds.
|
||||||
This informal presentation will look behind the scenes to show the
|
This informal presentation will look behind the scenes to show the
|
||||||
strategies and technologies used and to show the problem magnitude. We
|
strategies and technologies used and to show the problem magnitude. We
|
||||||
will review the IST Security web site with an emphasis on these pages
|
will review the IST Security web site with an emphasis on these pages
|
||||||
<br/><br/>
|
</p><p>
|
||||||
<a href="http://ist.uwaterloo.ca/security/vulnerable/">http://ist.uwaterloo.ca/security/vulnerable/</a><br/>
|
<a href="http://ist.uwaterloo.ca/security/vulnerable/">http://ist.uwaterloo.ca/security/vulnerable/</a><br/>
|
||||||
<a href="http://ist.uwaterloo.ca/security/security-wg/reports/20061101.html">http://ist.uwaterloo.ca/security/security-wg/reports/20061101.html</a><br/>
|
<a href="http://ist.uwaterloo.ca/security/security-wg/reports/20061101.html">http://ist.uwaterloo.ca/security/security-wg/reports/20061101.html</a><br/>
|
||||||
<a href="http://ist.uwaterloo.ca/security/position/20050524/">http://ist.uwaterloo.ca/security/position/20050524/</a><br/>
|
<a href="http://ist.uwaterloo.ca/security/position/20050524/">http://ist.uwaterloo.ca/security/position/20050524/</a><br/>
|
||||||
|
|
Loading…
Reference in New Issue