|

»

1st Atalaya meeting minutes

View: New views

5 Messages — Rating Filter: Alert me

	1st Atalaya meeting minutes by Francesco Vivoli :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Hi everybody as promised here go the minutes of what we said between on tinto and the other:) (and btw, I think there should be shifts for whom does the note keeping) List of high level features (+'s for priorities) 1- reporting(-): agreed to remove the current impl and to rethink the whole thing. 2- UI(++): - make it smoother (cut rough edges, clutchy actions and the like) - fix bugs - improve charts (flash?) 3-plugins(+): - how to develop, i.e the API and also providing some basic declarative configuration mean (many plugins only differ for a regex...) - lifecycle: how to configure/deconfigure and load/unload them 4- error handling and reporting(++): be more descrptive when some updates fail 5- configuration management(+): - initial setup (user side) - for developers (what they need to import to develop plugins - see the API stuff) - for the project (setup TRAC and migrate from SF bug tracker) 6-issues repository(++): this means re-activating corration between security elements) 7-policies(++): finish this first impl across the appliance set 8-false positives(++): finish this first impl across the appliance set 9-XML API(+) : draft design 10-MSBA(++): implement 11-testing(): evaluate what makes sense to be tested with Selenium Now, speaking of assignments, I think that Giacomo can easily carry on what he was doing, that is 7,8 and 10. Then I can get on 4, 6 and part of 2. Roman, as you see you've got plenty of speculative work ahead (:)) but IMO 2.3 and 5.3 should be given priority. Then the rest of 5 would be great to have, since it also eases our daily work. Once these things are done I'm eager to see how we can tackle the plugin matter:) well, friday - 19:47...I think this's enough, I'm offff! ciao F ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Atalaya-developer mailing list Atalaya-developer@... https://lists.sourceforge.net/lists/listinfo/atalaya-developer
	Re: 1st Atalaya meeting minutes by Robert Kielty :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. Hi, I have spent the last three months working with JasperReports and iReports. I have worked on designining reports, and have implemented a web app that runs reports asynchronously; (user requests a report via web app, servlet launches report fill asynchronously, a listener is notified when the report has been filled and the listener then exports the report to a file (PDF OpenOffice HTML whatever) and sets the report status as having been complete. Then the next time the web page is reload/refreshed or revisited the presence of the exported report is not and a link is displayed to a download servlet. I've glossed over one or two of the details but that's the guts of it. I am away on vacation for the next two weeks with limited access to email but if you can roughly spec out some requirements and issues that you are face with reporting I could probably provide some input. Kind regards, Robert Date: Fri, 1 Aug 2008 19:48:02 +0200 From: f.vivoli@... To: atalaya-developer@... CC: pablocelada@... Subject: [Atalaya-developer] 1st Atalaya meeting minutes Hi everybody as promised here go the minutes of what we said between on tinto and the other:) (and btw, I think there should be shifts for whom does the note keeping) List of high level features (+'s for priorities) 1- reporting(-): agreed to remove the current impl and to rethink the whole thing. 2- UI(++): - make it smoother (cut rough edges, clutchy actions and the like) - fix bugs - improve charts (flash?) 3-plugins(+): - how to develop, i.e the API and also providing some basic declarative configuration mean (many plugins only differ for a regex...) - lifecycle: how to configure/deconfigure and load/unload them 4- error handling and reporting(++): be more descrptive when some updates fail 5- configuration management(+): - initial setup (user side) - for developers (what they need to import to develop plugins - see the API stuff) - for the project (setup TRAC and migrate from SF bug tracker) 6-issues repository(++): this means re-activating corration between security elements) 7-policies(++): finish this first impl across the appliance set 8-false positives(++): finish this first impl across the appliance set 9-XML API(+) : draft design 10-MSBA(++): implement 11-testing(): evaluate what makes sense to be tested with Selenium Now, speaking of assignments, I think that Giacomo can easily carry on what he was doing, that is 7,8 and 10. Then I can get on 4, 6 and part of 2. Roman, as you see you've got plenty of speculative work ahead (:)) but IMO 2.3 and 5.3 should be given priority. Then the rest of 5 would be great to have, since it also eases our daily work. Once these things are done I'm eager to see how we can tackle the plugin matter:) well, friday - 19:47...I think this's enough, I'm offff! ciao F It’s time to join the family - Get the next generation of Free Windows Live Services now! Click here! ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Atalaya-developer mailing list Atalaya-developer@... https://lists.sourceforge.net/lists/listinfo/atalaya-developer
	Re: 1st Atalaya meeting minutes by Francesco Vivoli :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Hi Robert always a pleasure to meet new people:) wow, what you say it's actually good news, one of the main reasons for us to rethink reporting was that our current implementation sucks... It would be real cool to draft new specs with someone with a better understanding of Jasper. Beside that, we were speculating about moving to Eclipse BIRT, would you have any opinion about such a move. One of the problems with Jasper that Giacomo had was the difficulty of producing good looking reports when datasets have an high degree of variability from one invocation to another (short/long text areas and the like...). I'm also going on vacations next week so I'll be mostly offline, but it'd be cool to retake this topic at the end of the month. Thanks a lot for your inputs and willingness, talk to you soon. cheers Francesco On Fri, Aug 1, 2008 at 11:18 PM, Robert Kielty <r_kielty@...> wrote: Hi, I have spent the last three months working with JasperReports and iReports. I have worked on designining reports, and have implemented a web app that runs reports asynchronously; (user requests a report via web app, servlet launches report fill asynchronously, a listener is notified when the report has been filled and the listener then exports the report to a file (PDF OpenOffice HTML whatever) and sets the report status as having been complete. Then the next time the web page is reload/refreshed or revisited the presence of the exported report is not and a link is displayed to a download servlet. I've glossed over one or two of the details but that's the guts of it. I am away on vacation for the next two weeks with limited access to email but if you can roughly spec out some requirements and issues that you are face with reporting I could probably provide some input. Kind regards, Robert Date: Fri, 1 Aug 2008 19:48:02 +0200 From: f.vivoli@... To: atalaya-developer@... CC: pablocelada@... Subject: [Atalaya-developer] 1st Atalaya meeting minutes Hi everybody as promised here go the minutes of what we said between on tinto and the other:) (and btw, I think there should be shifts for whom does the note keeping) List of high level features (+'s for priorities) 1- reporting(-): agreed to remove the current impl and to rethink the whole thing. 2- UI(++): - make it smoother (cut rough edges, clutchy actions and the like) - fix bugs - improve charts (flash?) 3-plugins(+): - how to develop, i.e the API and also providing some basic declarative configuration mean (many plugins only differ for a regex...) - lifecycle: how to configure/deconfigure and load/unload them 4- error handling and reporting(++): be more descrptive when some updates fail 5- configuration management(+): - initial setup (user side) - for developers (what they need to import to develop plugins - see the API stuff) - for the project (setup TRAC and migrate from SF bug tracker) 6-issues repository(++): this means re-activating corration between security elements) 7-policies(++): finish this first impl across the appliance set 8-false positives(++): finish this first impl across the appliance set 9-XML API(+) : draft design 10-MSBA(++): implement 11-testing(): evaluate what makes sense to be tested with Selenium Now, speaking of assignments, I think that Giacomo can easily carry on what he was doing, that is 7,8 and 10. Then I can get on 4, 6 and part of 2. Roman, as you see you've got plenty of speculative work ahead (:)) but IMO 2.3 and 5.3 should be given priority. Then the rest of 5 would be great to have, since it also eases our daily work. Once these things are done I'm eager to see how we can tackle the plugin matter:) well, friday - 19:47...I think this's enough, I'm offff! ciao F It's time to join the family - Get the next generation of Free Windows Live Services now! Click here! ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Atalaya-developer mailing list Atalaya-developer@... https://lists.sourceforge.net/lists/listinfo/atalaya-developer
	Re: 1st Atalaya meeting minutes by Francesco Vivoli :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Hi after some discussion about some of the tasks listed below, it might be time to see whether the priorities are really what we first agreed on. In particular I think that we agree that while a nice-to-have, migrating the tracker from SF doesn't make the project move ahead a lot. Flash charts do instead, as they improve the look and feel a lot. Another piece that we have overlooked so far is SCM. With this I mean at least to make so that someone can develop an appliance without having to rebuild the whole codebase. Same goes for implementations of bindings of new ticketing systems. Well, ok this might go on another thread, I was just trying to make a point here:) cheers F On Fri, Aug 1, 2008 at 7:48 PM, Francesco Vivoli <f.vivoli@...> wrote: Hi everybody as promised here go the minutes of what we said between on tinto and the other:) (and btw, I think there should be shifts for whom does the note keeping) List of high level features (+'s for priorities) 1- reporting(-): agreed to remove the current impl and to rethink the whole thing. 2- UI(++): - make it smoother (cut rough edges, clutchy actions and the like) - fix bugs - improve charts (flash?) 3-plugins(+): - how to develop, i.e the API and also providing some basic declarative configuration mean (many plugins only differ for a regex...) - lifecycle: how to configure/deconfigure and load/unload them 4- error handling and reporting(++): be more descrptive when some updates fail 5- configuration management(+): - initial setup (user side) - for developers (what they need to import to develop plugins - see the API stuff) - for the project (setup TRAC and migrate from SF bug tracker) 6-issues repository(++): this means re-activating corration between security elements) 7-policies(++): finish this first impl across the appliance set 8-false positives(++): finish this first impl across the appliance set 9-XML API(+) : draft design 10-MSBA(++): implement 11-testing(): evaluate what makes sense to be tested with Selenium Now, speaking of assignments, I think that Giacomo can easily carry on what he was doing, that is 7,8 and 10. Then I can get on 4, 6 and part of 2. Roman, as you see you've got plenty of speculative work ahead (:)) but IMO 2.3 and 5.3 should be given priority. Then the rest of 5 would be great to have, since it also eases our daily work. Once these things are done I'm eager to see how we can tackle the plugin matter:) well, friday - 19:47...I think this's enough, I'm offff! ciao F ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Atalaya-developer mailing list Atalaya-developer@... https://lists.sourceforge.net/lists/listinfo/atalaya-developer
	Re: 1st Atalaya meeting minutes by Roman Kalyakin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Hi, I agree with Francesco that we can postpone with migration until we reach a consensus or get tired of SF tracker. Meanwhile, I started working on Flash charts, according to the defined priorities. -Roman On Wed, Sep 3, 2008 at 11:25 PM, Francesco Vivoli <f.vivoli@...> wrote: Hi after some discussion about some of the tasks listed below, it might be time to see whether the priorities are really what we first agreed on. In particular I think that we agree that while a nice-to-have, migrating the tracker from SF doesn't make the project move ahead a lot. Flash charts do instead, as they improve the look and feel a lot. Another piece that we have overlooked so far is SCM. With this I mean at least to make so that someone can develop an appliance without having to rebuild the whole codebase. Same goes for implementations of bindings of new ticketing systems. Well, ok this might go on another thread, I was just trying to make a point here:) cheers F On Fri, Aug 1, 2008 at 7:48 PM, Francesco Vivoli <f.vivoli@...> wrote: Hi everybody as promised here go the minutes of what we said between on tinto and the other:) (and btw, I think there should be shifts for whom does the note keeping) List of high level features (+'s for priorities) 1- reporting(-): agreed to remove the current impl and to rethink the whole thing. 2- UI(++): - make it smoother (cut rough edges, clutchy actions and the like) - fix bugs - improve charts (flash?) 3-plugins(+): - how to develop, i.e the API and also providing some basic declarative configuration mean (many plugins only differ for a regex...) - lifecycle: how to configure/deconfigure and load/unload them 4- error handling and reporting(++): be more descrptive when some updates fail 5- configuration management(+): - initial setup (user side) - for developers (what they need to import to develop plugins - see the API stuff) - for the project (setup TRAC and migrate from SF bug tracker) 6-issues repository(++): this means re-activating corration between security elements) 7-policies(++): finish this first impl across the appliance set 8-false positives(++): finish this first impl across the appliance set 9-XML API(+) : draft design 10-MSBA(++): implement 11-testing(): evaluate what makes sense to be tested with Selenium Now, speaking of assignments, I think that Giacomo can easily carry on what he was doing, that is 7,8 and 10. Then I can get on 4, 6 and part of 2. Roman, as you see you've got plenty of speculative work ahead (:)) but IMO 2.3 and 5.3 should be given priority. Then the rest of 5 would be great to have, since it also eases our daily work. Once these things are done I'm eager to see how we can tackle the plugin matter:) well, friday - 19:47...I think this's enough, I'm offff! ciao F ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Atalaya-developer mailing list Atalaya-developer@... https://lists.sourceforge.net/lists/listinfo/atalaya-developer ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Atalaya-developer mailing list Atalaya-developer@... https://lists.sourceforge.net/lists/listinfo/atalaya-developer