[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Resend: draft programme and actions from Tuesday's meeting]
- To: committee@ossg.bcs.org
- Subject: Resend: draft programme and actions from Tuesday's meeting]
- From: garylloyd
- Date: Thu, 23 Jun 2005 09:18:00 +0000
This lost all of it's formatting by the time I reached me, so I am
resending
-------- Original Message --------
Subject:
draft programme and actions from Tuesday's meeting
Date:
Thu, 23 Jun 2005 09:02:51 +0100
From:
Gary Lloyd <garyjlloyd@btinternet.com>
Reply-To:
garyjlloyd@btinternet.com
To:
ossg comittee <committee@ossg.bcs.org>
Below is the draft schedule that we
agree on Tuesday and actions following on from that meeting.
Topic
Responsibility
Venue â?? Speaker(s)
Comment
Sep
What is Open Source?
An introduction for managers and technicians
Paul
Lincoln/London
Timing to coincide with visit by Simon Fipps
(Phipps?) of Sun
Oct
Open Source and Quality
Joint meeting with Software Quality SG
Mark
Southampton
Needs to be 22 or 27 Oct
Nov
Case Study: Oxfam and Open Source
Graham
Oxford
Can be any month on Weds or Thurs
Dec
Software patents: good or evil?
Andrew/Paul
To be determined
Not fixed to any date
Jan
An overview of Open Source Licensing
Obligations that licenses, do or do not, place on
users, distributors and modifiers of OSS
Gary
London â?? Andrew Katz
Speaker can make Sep/Oct/Jan/Mar
Feb
Collaborative development
...and the lessons that can be learned from
Open Source development
Paul
Lincoln/London/Other
Can be any time
Mar
Is Open Source Secure?
Patrick
To be determined
Speaker not determined
April
Open Source and Agile development
Malcolm
To be determined
Speaker not determined
May
Open Source versus Free Software...a debate
Paul
To be determined
Speaker not determined
Jun
It will greatly help to get these
meetings into crowded diaries if each topic has:
A good title (does what it says on
the tin style) and strap-line that amplifies that. Ideally a speaker
name and credentials for the role will be helpful. The credentials bit
need only be their role or relationship to the topic. E.g. Professor of
Software Quality; Lawyer specialising in IT Law etc.
Actions:
Who
What
By When
All
Finalise: topic title, strap line and speaker (if poss.)...and
preferred location
01/07/05
Andrew / Mark
Organise workshop to brainstorm book content
01/07/05
Patrick
Liaise with Manchester Branch re joint meeting
24/07/05
Gary
Advise other SG's of tentative programme and invite
suggestions for joint meetings and/or speakers
24/07/05
Patrick
Determine topic/speaker/date for Security meeting
01/07/05
Subject: Conference Call 21 June
From: paddy
To: committee@ossg.bcs.org
Date: Wed, 22 Jun 2005 09:03:00 +0000
Dear all,
My apologies for not participating in the second conference call yesterday (21/06/05).
Unfortunately a meeting with a software vendor overran.
Obviously I am content to pick up any actions that may have allocated to me in my absence (in an email conversation thread earlier with Gary Iâ??ve volunteered to pick Linux security meeting I am in the porocess of an approach to a couple of project reps).
Once again my apologies - all the best
Patrick