Introduction to the Argus Future Workshop Room: 31/S-023 The Argus Future WS meeting is intended to be a semi-structured collaborative workshop, with lots of interaction and fewer formal presentations. In these first 15 min we will jointly define the specific agenda of the workshop

Phase I: "Why" - painting the Argus Landscape Room: 31/S-023 Everyone present (really! both those local and remote) shall have at most 5 minutes to describe "why am I here?". Which technical issue with Argus do you face in daily life that made you come here? What vision of the future do you have that features Argus in it? Which element(s) of Argus do you use today that you consider of value to you, your work, or your organization(s)? Have you come here to find out if Argus is already dead? Maybe you want it to die, and why? Or not, and why? No problem if you repeat a previous speaker: it may give a different viewpoint on the same issue, or at least reinforces the point!

Phase I: Agenda building - Identifying the Focus Areas of interest for an Argus Future Room: 31/S-023 Post your ideas and share your key words! We group the topics put forward into a number of ‘focus areas’ (say: at most 4), with ideas and notes put forward that are related grouped together. That will give us the agenda for the afternoon. We'll also ask for a volunteer to act as 'rapporteur' for each focus area and come up with a summary ...

Phase II: "What" - what do we see Argus doing to address the issues? Room: 31/S-023 What can we technically do to address the issues raised for each focus area? What does already work? What new features are needed? Is Argus the best place to add those features? ... and if we have to add features, by when are those features no longer relevant to be added to Argus, i.e. what will have missed the boat on that one? Discussing these kind of questions (and you are welcome to think of more!) should give us an idea of where development is needed, and what our strengths and weaknesses are. If there are enough people and many topics, we might split in groups, otherwise we have two consecutive discussions (time-boxed please ;-)

Phase II: "What" - second session Room: 31/S-023 second topic or parallel session

Phase III: Who? Room: 31/S-023 Which skills do we have around the table, or can we attracts from friendly parties? Not everyone is comfortable with every programming language, validation/testing environment, or has the capability to experiment at scale - so can we do what we want to technically achieve? Where do you feel you (or someone close in your organisation) have a good technical skill set? And if you did have infinite time (I know you don't, but that's another question!)? We would like to hear from everybode around the table (and remote): - what kind of technical skills do you have available? - OR: explain briefly why the identified focus areas fall short of meeting your requirements - OR: tell why you think other products are better suited for a particular problem - we do want to conserve effort!

Phase IV: When?! Room: 31/S-023 Getting things sorted: which features do we prioritize, and do we have the skill set to make it happen? More importantly, we invite each participant to express an interest (1 min max each!) in each focus area feature list. E.g. “I really wish this to happen and will push inside my org to get some time allocated to this”, or “I like the feature list, but it will be in my spare time”, or “I have been forbidden by my home organization to contribute”, or “I can spend 4 hours a week on this kind of thing”, or … Can we indeed make all the (hopefully useful and nice) things we thought about today actually happen?

Conclusion Room: 31/S-023 Logistics and next steps! - Logistics: mailing list members - How to broaden the involvement: presentation, minutes or white paper, new user communities or more developers first, … - Feedback on the meeting format - Follow-on meetings? Your feed-back is very welcome.