https://istlab.dmst.aueb.gr/wiki/api.php?action=feedcontributions&feedformat=atom&user=195.251.249.155 2026-11-15T06:47:38Z User contributions MediaWiki 1.43.9 https://istlab.dmst.aueb.gr/wiki/index.php?title=SQO-OSS_meeting_2007-04-18&diff=1943 2007-04-18T15:28:04Z

<p>195.251.249.155: add dimitro contribution</p> <hr /> <div>Some random notes I 've kept and also some things that I 've though of while writing:<br /> <br /> *We should work in 2 week iterations, after which we are going to integrate and sync our work<br /> *We will use UMLGraph for classes and possibly for activity/sequence diagrams<br /> *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. <br /> *We will need a lightweight job submission/work queue implementation, ie an asynchronous work model will be used<br /> *The presentation layer will use web services as a mechanism to retrieve results. <br /> **What about job submission? Should we only use local (ie cmd-line) job submission?<br /> **What about security and authentication?<br /> *What are the requirements for data sources such as mailing lists and bug management databases?<br /> <br /> &lt;h2&gt;Work on D5&lt;/h2&gt;<br /> <br /> 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. <br /> <br /> *Sections in D5 and work assignments<br /> **Plugin description and infrastructure, sync with equinox (bkarak)<br /> **Database access and DB schema (panos)<br /> **Presentation layer (gousiosg)<br /> **Access to version control systems (and possibly other data sources) (circular)<br /> <br /> *dmitro will work on finding references and information on OSGi and giving a presentation to all of us</div>

195.251.249.155 https://istlab.dmst.aueb.gr/wiki/index.php?title=SENSE&diff=1942 2007-04-18T14:59:27Z

<p>195.251.249.155: Re organised stuffed a bit</p> <hr /> <div>== Goodies ==<br /> * [[:Category:Book SENSE|SENSE book library]]; [[SENSE book wishlist]]<br /> * [[:Category:Equipment SENSE|SENSE equipment]]; [[SENSE equipment wishlist]]<br /> <br /> == Progress ==<br /> * [[SENSE publication plans]]<br /> * [[SENSE research plans]]<br /> * [[SENSE personal plans]]<br /> <br /> == Other ==<br /> * [[Akademy '08 proposal]]<br /> * [[SQO-OSS sprints]]<br /> <br /> [[Category:SENSE]]</div>

195.251.249.155 https://istlab.dmst.aueb.gr/wiki/index.php?title=SQO-OSS_meeting_2007-04-18&diff=1941 2007-04-18T14:53:01Z

<p>195.251.249.155: Finished my contribution</p> <hr /> <div>Some random notes I 've kept and also some things that I 've though of while writing:<br /> <br /> *We should work in 2 week iterations, after which we are going to integrate and sync our work<br /> *We will use UMLGraph for classes and possibly for activity/sequence diagrams<br /> *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. <br /> *We will need a lightweight job submission/work queue implementation, ie an asynchronous work model will be used<br /> *The presentation layer will use web services as a mechanism to retrieve results. <br /> **What about job submission? Should we only use local (ie cmd-line) job submission?<br /> **What about security and authentication?<br /> *What are the requirements for data sources such as mailing lists and bug management databases?<br /> <br /> &lt;h2&gt;Work on D5&lt;/h2&gt;<br /> <br /> 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. <br /> <br /> *Sections in D5 and work assignments<br /> **Plugin description and infrastructure, sync with equinox (bkarak)<br /> **Database access and DB schema (panos)<br /> **Presentation layer (gousiosg)<br /> **Access to version control systems (and possibly other data sources) (circular)</div>

195.251.249.155 https://istlab.dmst.aueb.gr/wiki/index.php?title=SQO-OSS_meeting_2007-04-18&diff=1940 2007-04-18T14:42:06Z

<p>195.251.249.155: Initial content</p> <hr /> <div>Some random notes I 've kept:<br /> <br /> *We should work in 2 week iterations, after which we are going to integrate and sync our work<br /> *We will use UMLGraph for classes and possibly for activity/sequence diagrams<br /> *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. <br /> *We will need a lightweight job submission/work queue implementation, ie an asynchronous work model will be used<br /> *The presentation layer will use web services as a mechanism to retrieve results. <br /> **What about job submission? Should we only use local (ie cmd-line) job submission only?<br /> **What about security and authentication?<br /> <br /> &lt;h2&gt;Work on D5&lt;/h2&gt;<br /> <br /> *Sections in D5 and work assignments<br /> **Plugin description and infrastructure, sync with equinox (vbill)<br /> **Database access <br /> **</div>

195.251.249.155 https://istlab.dmst.aueb.gr/wiki/index.php?title=SQO-OSS_sprints&diff=1939 2007-04-18T14:29:38Z

<p>195.251.249.155: add 18-04-2007 minutes</p> <hr /> <div>*[[SQO-OSS sprint 2007-03-07]]<br /> *[[SQO-OSS sprint 2007-03-21]]<br /> *[[SQO-OSS meeting 2007-04-18]]</div>

195.251.249.155