[OpenSPP-project] Notes from Team Meeting of 20110609

[Dean W. <dea...@so...>]

Here are my notes from this morning's call. They are being archived (and
revised as needed) on the wiki.

---------------------------

Open SPP Team Call, Thursday June 9, 2011

Attending: Jeremy, Vijay, Jean-Francois, Dean

Notes by Dean


Dicussion: OSS components and software licensing as rferred to CableLabs
legal. A formal decision is still  pending, but Jean-Francois and team are
recommending (to Legal) the approach suggested by the dev team, and the team
is to proceed with the proposed OSS components and the Apache Version 2
license for now.


Discussion: Sprint 1 Backlog

Slipping start date to tomorrow and finish date to 6/18/11

Remove audit from sprint backlog (Action: Dean)

Discussed use of database persistence vs. in-memory. Agreed that we will
attempt to get the database persistence model to work in Sprint 1, using
Spring/JDBC. (Lead: Vijay)

Do we attempt Syed's ENUM-like REST API in Sprint 1: No, but the product
backlog needs to be amended to include it (Action: Dean to edit product
backlog).

How do we incorporate M&S in Sprint 1? Leaning towards asking them to handle
the SOAP service interface stuff.

Jeremy and David will meet with them Monday. (Action: Jeremy to report back
to team.)

How are we going to do exception handling? We'll work out a minimal approach
for Sprin 1, and mature over the development process. (Action: Dean to add
proper exception handling to product backlog)

Do we need a hosted platform for Sprint 1? Probably. We could use an Amazon
virtual server or work on Dean's server at softarmor for now. (Action: Dean
to set something up, communicate to team).


Object/relational mapping schema: Vijay proposed using numeric IDs instead
of object name for mapping. No objections noted.

String size limitations relating database schema need to be resolved with
the protocol specification. (Action: Dean to Add string size
limitation/validation issues into product backlog.)

Internationized Strings: The current geenral direction is to
internationalize all proper names. Easiest approach appears to be to be to
use UTF-8. This does raise questions from a protocol perspective, especially
around string comparison. Further discussion with Ken is probably required.
(Action: Dean to add Internationalization, UTF-8 selection into product
backlog)

Task division:

Data model, Spring JDBC connector, DAO: Vijay to lead.

Service Interface: Mikkael, Samael working with Jeremy on SOAP envelope

Command processing stub: Jeremy

Exception architecture: Jeremy to lead discussion on list.

Component architecture: What goes into each JAR file, etc. To discuss on
team mailing list.



Further items:

Discussion on tools/support. We probably need to get a handle on use of
Tracker.



Action: Dev team to start "Daily Standup" emails on Monday. Each day, we
each report by email to the team list.

Each such report should address

1) What I have done in the past 24 hours.
2) What I plan to do in the next 48 hours.
3) Any problems/obstacles that I am hitting.

-- 
Dean Willis