SQO-OSS meeting 2007-04-18 - Revision history

Dimitro at 16:49, 18 April 2007

2007-04-18T16:49:37Z

← Older revision		Revision as of 18:49, 18 April 2007
Line 20:		Line 20:
	**Access to version control systems (and possibly other data sources) (circular)		**Access to version control systems (and possibly other data sources) (circular)

	*dmitro will work on finding ~~[[OSGi/Equinox]\|~~references] and information on OSGi and giving a presentation to all of us		*dmitro will work on finding references and information on OSGi and giving a presentation to all of us

Dimitro at 16:49, 18 April 2007

2007-04-18T16:49:18Z

← Older revision		Revision as of 18:49, 18 April 2007
Line 20:		Line 20:
	**Access to version control systems (and possibly other data sources) (circular)		**Access to version control systems (and possibly other data sources) (circular)

	*dmitro will work on finding references and information on OSGi and giving a presentation to all of us		*dmitro will work on finding [[OSGi/Equinox]\|references] and information on OSGi and giving a presentation to all of us

195.251.249.155: add dimitro contribution

2007-04-18T15:28:04Z

add dimitro contribution

← Older revision		Revision as of 17:28, 18 April 2007
Line 19:		Line 19:
	**Presentation layer (gousiosg)		**Presentation layer (gousiosg)
	**Access to version control systems (and possibly other data sources) (circular)		**Access to version control systems (and possibly other data sources) (circular)

			*dmitro will work on finding references and information on OSGi and giving a presentation to all of us

195.251.249.155: Finished my contribution

2007-04-18T14:53:01Z

Finished my contribution

← Older revision		Revision as of 16:53, 18 April 2007
Line 1:		Line 1:
	Some random notes I 've kept:		Some random notes I 've kept and also some things that I 've though of while writing:

	*We should work in 2 week iterations, after which we are going to integrate and sync our work		*We should work in 2 week iterations, after which we are going to integrate and sync our work
Line 6:		Line 6:
	*We will need a lightweight job submission/work queue implementation, ie an asynchronous work model will be used		*We will need a lightweight job submission/work queue implementation, ie an asynchronous work model will be used
	*The presentation layer will use web services as a mechanism to retrieve results.		*The presentation layer will use web services as a mechanism to retrieve results.
	**What about job submission? Should we only use local (ie cmd-line) job submission ~~only~~?		**What about job submission? Should we only use local (ie cmd-line) job submission?
	**What about security and authentication?		**What about security and authentication?
			*What are the requirements for data sources such as mailing lists and bug management databases?

	<h2>Work on D5</h2>		<h2>Work on D5</h2>

			The work on D5 will be carried out in a distributed manner. Each person that has been assigned a piece of D5 is responsible for all phases of designing, from implementing prototypes to asking and managing partners' contribution. Panos will have the final word in all cases.

	*Sections in D5 and work assignments		*Sections in D5 and work assignments
	**Plugin description and infrastructure, sync with equinox (~~vbill~~)		**Plugin description and infrastructure, sync with equinox (bkarak)
	**Database access		**Database access and DB schema (panos)
			**Presentation layer (gousiosg)
	**
			**Access to version control systems (and possibly other data sources) (circular)

195.251.249.155: Initial content

2007-04-18T14:42:06Z

Initial content

New page

Some random notes I 've kept:

*We should work in 2 week iterations, after which we are going to integrate and sync our work
*We will use UMLGraph for classes and possibly for activity/sequence diagrams
*Metrics that do not output a single value but things such as diagrams or plots are going to be stored on the hard disk and a the file path will be stored in their value field.
*We will need a lightweight job submission/work queue implementation, ie an asynchronous work model will be used
*The presentation layer will use web services as a mechanism to retrieve results.
**What about job submission? Should we only use local (ie cmd-line) job submission only?
**What about security and authentication?

<h2>Work on D5</h2>

*Sections in D5 and work assignments
**Plugin description and infrastructure, sync with equinox (vbill)
**Database access
**