
participants: Morris, Aleksandr, Balazs, David Wallom, Etienne,Ilya Saverchenko, Johannes, Luigi, Mark Morgan, Oxana, Steve Brewer Agenda: (a) Intensive discussions how we can make progress with the requirements w/o telcons Morris: outcome of workshop at OGF28: huge list of requirements how to refine this list? comments? Balazs: requirement collection open til 1 May Morris: have the requirements ready in May for strawman creation devide requirements to different groups to work in parallel -> more progress Balazs: on a group level? Morris: not agreement refinement and check if in scope but not agreements in small groups Oxana: maybe close the requirements collection before the f2f in Amsterdam Morris: speedup the decision making progress check for similarities and duplicates there must be people looking at this few people look at this - make comments to the list if duplicate Oxana: if done in serial manner: 16 full working days it has to be done in parallel Morris: 208 requirements few people looking at them without changing them comment: might be duplicate: comment next telcon: together confirm thoughts, comments maybe 20% duplicate decrease the number for f2f meeting Balazs: Etienne should go through his to check with the newly added from Munich f2f Etienne: not found much duplicates found some not really understandable ie. JM16 ?? Balazs: postponed Morris: overlaps? some things are wrongly written, duplicate Etienne: different meanings in different services Morris: good to add categories another distingtion? Etienne: very important requirement for one person must not be important for others group togehter most important important check with others Morris: create a wiki page divide the 208 among us of course there are different views Etienne: each one should go through all requirements and mark if not understood or missing information much less discussion on the requirements marked as clear Luigi: we need an extension of the wikipage: column for each participant check one of three options: agree, reject, need more information Morris: not a decision process just to mark if clear maybe have two options: ok, need more info three sentences on the wiki page from the requirement creator if need more info is checked David: one "more info" is enough to need explanation Morris: for document we will need the three sentences Balazs: at OGF28 agreed there will be no document David: final outcome will be document Balazs: no, was agreed Morris: we will not discuss 50% of the list at the workshop Balazs: not needing an extra column sequentional numbering column with category Morris: putting a question Steve Brewer: agree with Balazs, divide functional, non functional Morris: potentionally different experst working on this from UNICORE information service: shiraz job management: shavaz speed up with going parallel through the list Oxana: separate wikipages? Morris: tough to edit Etienne: can do this Morris: we have to agree first Etienne: when separating, need to be able to discuss riquirements concerning the same subject Morris: we need the grouping Balazs: use area column as grouping Etienne: here you need index, this is not a database, you cannot sort by the area field Morris: good statement David: would go with Oxana's idea because usability issues Morris: votings for separate areas on separate wiki page Balazs: worst platform to work collaborately Morris: split Etienne splits in different wikis review it at next telcon Etienne: if using the link at the left to add comments in separate wikipage - no need to all edit the same wiki page think can keep it like that Balazs: please introduce sequentional numbering Morris: why? Balazs: if moving no renumbering Oxana: will renumbered when moved any experience with other groups? Morris: not so much requirements Balazs: in GLUE flat list in the tracker Morris: we have requirements in the wiki Oxana: tracker? Morris: point people to specific sections non functional areas: Etienne information services: Balazs (no - not during next week) Shiraz security: Morris application repository: Etienne accounting, logging and book keeping: Luigi (problem during next week) job management: Mark Morris: support understanding room of decreasing the amount of them Balazs: next iteration will be writing text to explain requirements Oxana: three sentences is not yes or no, we cannot fix it Morris: just for understanding Oxana: explanation should be added by requirement contributor Morris: Etienne? not the only guy needing Balazs: goal to have a common understanding just make the things more clear for somebody not understanding Morris: create the wiki page for those who need more information David: needs clarifications Etienne: put the name and why not understood Morris: have to go should not discuss again about items already agreed continue over email ____ (b) Easter vacation problem mitigation (e.g. Balazs away until 12.4.) (c) Amsterdam workshop planning, registration reminder, agenda setup, etc. (d) Discussions about a new telcon tool (possibly funded via EMI similar like the previous one maybe) (e) AOB -- _ _ _ _ _ _ Johannes Watzl |\/| |\ | |\/| Institut für Informatik / Dept. of CS | | | \| | | Ludwig-Maximilians-Universität München ======= TEAM ======= Oettingenstr. 67, 80538 Munich, Germany Room E 005, Phone +49-89-2180-9162 Munich Network Management Team Email: watzl@nm.ifi.lmu.de Münchner Netz-Management Team http://www.nm.ifi.lmu.de/~watzl
participants (1)
-
Johannes Watzl