Meeting Minutes

General

• Moderator: Mark Ostermann
• Secretary: Mario Calderon
• Participants: Colin Rooney, John Agudelo, Mark Ostermann, Teo Sarca, Paul Aviles, Suman Ravuri, Victor Perez, Mario Calderón, Mike Judd, Tobias Schöneberg, Enrique Ruibal
• Date / Time: June 10th, 2013 / 12:00 PM - 2:00 PM GMT

Agenda

1. Decision about which functionality will be included
2. Setting of a deadline (Release Date 3.8)
3. Next meeting

Discussion

• The decision about which functionality will be included in the release was discussed. Some functional descriptions of contributions were still missing in http://www.adempiere.com/Release_380LTS. Teams were urged to meet ASAP to analyze contributions, and contributors will not review their own contributions technically or functionally.
• Volunteers for functional analysis were determined: Colin Rooney, Mario Calderon, Mike Judd, Mark Ostermann, John Agudelo, Enrique Ruibal, Victor Perez, and Karsten Thiemann (to be asked).
• Volunteers for technical analysis were identified: Tobias Schöneberg, Teo Sarca, Victor Perez, and Trifon (to be asked).
• The setting of a deadline for the release was discussed. It was decided to allocate 3 months for reviews and integration, followed by 1 month of stabilization before the release.
• The suggested release date was October 14th, 2013.
• The next meeting was scheduled for Monday, June 17th, 12:00 GMT.

Next Meeting

• Monday, June 17th, 12:00 GMT.

Log

Following is the meeting log

Monday, 10th June 2013

Monday, 10 June 2013
[06:21:54] * Mario Calderón invited colin.rooney enrique.ruibal jdaison jens.pfeiffer_evenos.de karsten-thiemann metas.mark.ostermann metas_ts metas_tsa michael_judd mike.mckay_christine.hodge paul.aviles plavania ravurisuman trifonnt vpj-cd
[06:21:56] Conference call, duration 00:00.
[06:22:04] Mario Calderón: hi
[06:22:22] Michael Judd: hi mario - how are you ?
[06:22:56] Victor Perez Juarez: hi
[06:23:21] Michael Judd: Hi Victor - Hi all
[06:23:42] Colin Rooney: hi all
[06:24:17] suman ravuri: Hi
[06:24:18] Mario Calderón: if there is somebody missing, please add him to the meeting
[06:25:17] Mario Calderón: anybody else present?
[06:25:22] Mark Ostermann: hi all
[06:26:18] Mario Calderón: Steven wrote he wouldn't attend, because of a business flight
[06:27:12] Schöneberg, Tobias (metas.de): hi
[06:27:35] Mario Calderón: do we wait a couple of minutes for people or do we start right now?

I mean, we are almost 30 mins. delayed
[06:27:49] suman ravuri: Let us start
[06:27:54] suman ravuri: +1 to start
[06:28:32] Mark Ostermann: +1 to start
[06:28:46] Schöneberg, Tobias (metas.de): +1
[06:28:49] Mario Calderón: +1 to start
[06:28:58] Mario Calderón: ok then let's start
[06:29:10] Mario Calderón: moderator + secretary
[06:29:18] Mario Calderón: I can be the secretary
[06:31:48] suman ravuri: May I request Mark to be Moderator?
[06:33:36] Mark Ostermann: back, sry was on phone
[06:33:55] Teodor Sarca: hi all, sorry for delay
[06:34:33] Mark Ostermann: ok, i'll take part of moderator - for today - if nobody rejects ;-)
[06:34:41] Mario Calderón: ok
[06:35:20] Mark Ostermann: so let's define the agenda:
[06:35:25] Mark Ostermann: * http://www.adempiere.com/Release_380LTS (Status of filling in contributions)
[06:36:25] Mark Ostermann: * here's the MM from last week (thanks Mario) http://www.adempiere.com/FT/TT_meeting_minutes_June_3rd_2013
[06:38:30] Mark Ostermann: * Decisions to be taken today: 

** Decision about which functionality will be included and release date will be taken on next meeting.
[06:39:13] Mark Ostermann: ** Setting of a deadline (Release Date 3.8)
[06:39:16] Mark Ostermann: ...
[06:39:38] Mark Ostermann: ... any other topics?
[06:40:31] suman ravuri: we need to dicuss at least few features and decide whthere they are part of 3.8
[06:40:45] Mario Calderón: that is it Mark
[06:40:58] Mario Calderón: @suman: agree
[06:41:49] Mark Ostermann: ok, then lets start with discussion about "features for 3.8"
[06:43:52] Mark Ostermann: we at metas have startet with filling the pages of  http://www.adempiere.com/Release_380LTS. Besides that we have started integration work for cour contribs, so that we can build them in an adempiere test version for others to test/ decide.
[06:43:58] Mario Calderón: I see that some pages are documented, some others not
[06:44:24] Mario Calderón: do we go from top to bottom?
[06:44:40] Mark Ostermann: yepp
[06:45:38] Victor Perez Juarez: Mario i have an question is necessary create multiples pages
[06:46:08] Victor Perez Juarez: in my example i can see
[06:46:10] Victor Perez Juarez: http://www.adempiere.com/FR3426137_Smart_Browser
[06:46:16] Victor Perez Juarez: http://www.adempiere.com/Sponsored_Development:_Libero_Smart_Browser
[06:47:03] Victor Perez Juarez: http://www.adempiere.com/Smart_Browser
[06:47:47] Mark Ostermann: but first question: what do we want to decide going through this list of contributions http://www.adempiere.com/Release_380LTS ?
[06:48:04] Mark Ostermann: probably we can discuss this on one entry in that list
[06:48:37] Mark Ostermann: http://www.adempiere.com/Sales_Management_%28CRM%29
[06:48:42] Mario Calderón: I would suggest: go over the the list, and decide if it will be included
[06:49:20] Mark Ostermann: @mario: thats the problem i see. we cannot decide here and now.
[06:49:33] Mark Ostermann: because in the lists we don't see any code
[06:49:46] Mark Ostermann: and haven't got any community tests
[06:49:49] Schöneberg, Tobias (metas.de): [14:49:22] Mario Calderón: I would suggest: go over the the list, and decide if it will be included



<<< maybe instead we can decide about a relative prio, compared to the other contribs
[06:50:18] Schöneberg, Tobias (metas.de): ..so that we can direct our efforts to the contribs with the highest prios first
[06:51:30] Mark Ostermann: but why decide? why don't let the contributors do their work in integrating and asking community for help?
[06:51:42] Teodor Sarca: why not starting with those that have documentation + code completed
[06:51:59] Mark Ostermann: for review?
[06:52:03] Teodor Sarca: exactly
[06:52:06] Mark Ostermann: ok
[06:52:43] Teodor Sarca: because at this moment i don't see which is the list that needs to be prioritized. e.g. what shall be the next package that RM can integrate?
[06:53:31] Mario Calderón: ok
[06:53:50] Mark Ostermann: yes, and i believe we don't need to priotize before review
[06:54:17] Mark Ostermann: and for release we should take what we get and what is finished at a given date (finished = reviewed and agreed)
[06:54:48] Mark Ostermann: wdyt?
[06:55:00] Teodor Sarca: agree
[06:55:23] Mario Calderón: so, do we go through the documented contribs and "decide" to integrate

Suman would start integrating them?
[06:55:55] suman ravuri: but this team has to decide what need to be integrated
[06:56:03] Mark Ostermann: yes
[06:56:07] Mark Ostermann: FT/ TT
[06:56:07] Mario Calderón: yes Suman
[06:56:43] Teodor Sarca: true. but because i am not up2date, i am asking what is ready to be integrated?
[06:57:01] Mark Ostermann: @teo: agree
[06:57:22] Mark Ostermann: that's the question we should answer
[06:57:53] Mario Calderón: I now some of the Adaxa and eEvolution contribs, because I have them working on clients
[06:58:14] Mario Calderón: when we go over them, I can give my comments
[06:58:24] Mario Calderón: Victor, too
[06:58:25] Mark Ostermann: and the features are included in ADempiere Test Version yet?
[06:58:38] Mark Ostermann: so that FT/ TT can review?
[06:58:39] Mario Calderón: Steven also, but he is unluckily on a plane now
[06:59:14] Mario Calderón: I would say so
[06:59:21] Mario Calderón: do we start?
[07:00:17] Mark Ostermann: lets start with first entry
[07:00:17] Mark Ostermann: [14:49:19] Mark Ostermann: http://www.adempiere.com/Sales_Management_%28CRM%29



<<< 
[07:00:54] Mario Calderón: I use this contribution and works well
[07:00:54] Victor Perez Juarez: i propouse here the procedure
[07:01:04] Victor Perez Juarez: but never get some comment
[07:01:17] Victor Perez Juarez: exept by Mike Mckay
[07:01:25] Victor Perez Juarez: https://adempiere.atlassian.net/browse/ADEMPIERE-56
[07:01:34] Victor Perez Juarez: https://adempiere.atlassian.net/browse/ADEMPIERE-57
[07:01:45] Victor Perez Juarez: https://adempiere.atlassian.net/secure/attachment/10211/ADempiere%20Workflow%20Bugfix.pdf
[07:02:52] Victor Perez Juarez: https://adempiere.atlassian.net/secure/attachment/10210/ADempiere%20Workflow%20Feature.pdf
[07:03:18] Teodor Sarca: wow, nice
[07:03:28] Mark Ostermann: about Sales_Management_CRM. so Mario u could do the FT review?
[07:03:43] Mark Ostermann: who can do the TT review for that?
[07:04:27] suman ravuri: I don't have acceess to these links
[07:04:40] Mario Calderón: I would say that the review must be done by the teams; here we just decide to include it or not
[07:04:51] Victor Perez Juarez: do you need link into jiara
[07:04:53] Victor Perez Juarez: jira
[07:05:06] Victor Perez Juarez: https://adempiere.atlassian.net
[07:05:12] suman ravuri: I need access for it
[07:05:18] suman ravuri: username/password
[07:05:27] suman ravuri: sorry
[07:05:35] suman ravuri: I will take this offiline
[07:05:50] suman ravuri: @Mark, continue
[07:07:45] Mark Ostermann: [15:05:21] Mario Calderón: I would say that the review must be done by the teams; here we just decide to include it or not



<<< hmm, i would prefer FT/ TT to distibute review work among their members and discuss the results for integration in release or not
[07:08:08] Mark Ostermann: because the reviewing will take endless time if has to be done during our meetings
[07:10:16] Mark Ostermann: and i would like to prefer having at least one opinion of member of FT and TT - which did the review. and these two can suggest it to FT/ TT Meeting for decision
[07:10:36] Teodor Sarca: @mark, agree... reviews can be done out of the meeting and use mail/skype for communication
[07:11:57] Mark Ostermann: FT/ TT reviews is about doing work and taking over reponsibility for quality and functionality of ADempiere release
[07:13:02] Mark Ostermann: and i would suggest that the FT/ TT member that does the review should not be in the same company of the contributor
[07:13:45] Mark Ostermann: ... we even seperate this in out development work at metas. the developer never tests his own coding.
[07:13:53] Mario Calderón: @Mark: this would mean, the RM does the integration for all contribs and then we decide?
[07:13:54] Mark Ostermann: code review same
[07:15:08] Victor Perez Juarez: if the FT ad TT need review I have some question
[07:15:12] Victor Perez Juarez: How?
[07:15:17] Victor Perez Juarez: Who?
[07:15:21] Victor Perez Juarez: When?
[07:15:38] Victor Perez Juarez: Where?
[07:18:02] Mario Calderón: the other way would be to include all this functionality in a branch, and we start testing

the contrib that fails either by functionality, bugs or whatever, is dismissed
[07:18:28] Mario Calderón: then the analysis can be done as Mark suggests: FT and TT separatedly
[07:18:41] Mark Ostermann: [15:15:50] Victor Perez Juarez: if the FT ad TT need review I have some question

How?

Who?

When?

Where?



<<< yes victor, that's what we are deciding at the moment
[07:19:27] Schöneberg, Tobias (metas.de): [15:14:34] Mario Calderón: @Mark: this would mean, the RM does the integration for all contribs and then we decide?



<<< i think there should be a review ( -> TT/TF) prior to integration into development-branch (-> RM) and then testing
[07:20:14] Schöneberg, Tobias (metas.de): but if the reviews were ok and it was integrated, the decision was more or less made to fix all problems that come up during testing (1 month stabilization phase)
[07:20:31] Schöneberg, Tobias (metas.de): at least that'S how i understood it
[07:20:50] Mark Ostermann: @tobi: agree
[07:22:43] Mark Ostermann: * contributor integrates from his own development into a feature branch an adempiere repo

* FT/ TT member gets the documentation and does the review and suggets to team

* FT/ TT Team decides to integrate or not

* RM integrates into dev branch
[07:23:15] Mark Ostermann: then from given date ther is a one month stabilisation phase (integration testing)
[07:23:19] Mark Ostermann: --> release
[07:23:21] Victor Perez Juarez: I think that we can go
[07:25:00] Victor Perez Juarez: 1.- Each contributor explant the contribution , code , documentation , etc based on http://www.adempiere.com/Release_380LTS
[07:25:07] Mario Calderón: @Mark: most contribs have a branch  

the documentation has to be completed

so the point would be now that FT and TT meet ASAP



but I thought we would do it here
[07:25:52] Mark Ostermann: [15:25:49] Mario Calderón: so the point would be now that FT and TT meet ASAP



<<< ... thats what i suggested. let's distibute the work to members to do the review ;-)
[07:26:09] Victor Perez Juarez: 2.- Suman make a first revision , if all are good then we can call the TT and FT to review and aprobe based in an schedule
[07:26:14] Mark Ostermann: because this cannot be done in 1,5 hours of a weekly meeting
[07:26:25] Mario Calderón: I don't mind calling a FT meeting again, but we must do it in these days; otherwise we will be delayed -again
[07:26:51] Victor Perez Juarez: because now all is an disorder
[07:27:04] Victor Perez Juarez: some code are into repository
[07:27:14] Victor Perez Juarez: on other repositories
[07:27:45] Mario Calderón: so, what do we do?
[07:27:49] Schöneberg, Tobias (metas.de): [15:26:50] Victor Perez Juarez: 2.- Suman make a first revision



<<< suman as TT member?
[07:27:53] Mark Ostermann: [15:26:50] Victor Perez Juarez: 2.- Suman make a first revision , if all are good then we can call the TT and FT to review and aprobe based in an schedule



<<< ?!?
[07:28:01] Mark Ostermann: i thought suman is rm?
[07:28:43] Mario Calderón: we must find a simple and effective way so the RM starts working
[07:28:56] Mario Calderón: now we don't have any
[07:29:12] Victor Perez Juarez: yes because the FT and TT never could work :-)
[07:29:28] Victor Perez Juarez: I see that can happen the same now
[07:29:30] Mario Calderón: he's waiting for three weeks now, and we simply cannot tell him what he has to do
[07:29:37] Victor Perez Juarez: if we try the same fourmula
[07:30:30] Mark Ostermann: [15:28:26] Mario Calderón: so, what do we do?



<<< distribute work among FT/ TT members and let those pairings provide decision material for FT/ TT Meeting -> then vote (FT/ TT) -> then integrate (RM)
[07:30:43] Mario Calderón: so this is a suggestion
[07:30:57] Victor Perez Juarez: So I would like to work with the RM and prepare everything for FT or TT waiting for this approach to work
[07:31:03] Mario Calderón: we should vote on Mark's suggestion
[07:31:53] Victor Perez Juarez: if this works it should not be a problem, if not then we can go ahead and that the RM did effective work
[07:33:46] Mark Ostermann: @victor: effectiveness depends on the FT/ TT Member doing the review. don't blame the RM ;)
[07:35:03] Mario Calderón: so???
[07:35:08] suman ravuri: can we decide dates?
[07:35:22] Mario Calderón: Mark has made a suggestion
[07:35:34] suman ravuri: 3.8 release date and decide dates for all other dates based on that
[07:35:44] Schöneberg, Tobias (metas.de): [15:31:44] Mario Calderón: we should vote on Mark's suggestion



<<< the suggestion is barely TT/TF's self appointed job..do we really want to vote on whether we should do it?
[07:36:19] Victor Perez Juarez: the follwing some workflow
[07:36:21] Mario Calderón: @Tobi: the reason of the meeting was to decide which contribs are included
[07:36:23] Victor Perez Juarez: for example https://adempiere.atlassian.net/secure/attachment/10210/ADempiere%20Workflow%20Feature.pdf
[07:36:41] Victor Perez Juarez: so we can know the what is the stage for each contribution
[07:37:00] Victor Perez Juarez: and if the in some step we are stop
[07:37:25] Victor Perez Juarez: if the FT or TT is slow we can measure
[07:38:45] Mark Ostermann: @all: so let us start with the list again. http://www.adempiere.com/Release_380LTS let's find volunteers to review FT/ TT. I would suggest one member from each side and not members of same company of contributor. wdyt?
[07:39:05] Mark Ostermann: 1. http://www.adempiere.com/Sales_Management_%28CRM%29
[07:39:09] Mark Ostermann: FT? TT?
[07:39:11] suman ravuri: +1
[07:39:25] suman ravuri: Can you propose to complete this review?
[07:39:28] suman ravuri: date
[07:40:23] Mark Ostermann: [15:40:06] suman ravuri: Can you propose to complete this review?



<<< nope, i would propose a date and subtract one month for stabilisation
[07:40:30] Schöneberg, Tobias (metas.de): [15:39:46] Mark Ostermann: 1. http://www.adempiere.com/Sales_Management_%28CRM%29

FT? TT?



<<< i would volunteer to do technical review
[07:40:37] Mark Ostermann: thx tobi
[07:40:49] Mark Ostermann: any FT Member for functional review?
[07:41:36] Mario Calderón: I've done the functional, so I can do it

I will call a FT meeting to go over all cantribs: it is better.
[07:42:40] suman ravuri: But still one guy should be resposible for it
[07:42:52] Mark Ostermann: [15:42:18] Mario Calderón: I will call a FT meeting to go over all cantribs: it is better.



<<< sry, i don't understand
[07:43:00] suman ravuri: So sales management FT mario is primary and responsible for it
[07:43:11] Schöneberg, Tobias (metas.de): [15:43:21] suman ravuri: But still one guy should be resposible for it



<<< yes, ihmo that's an important point (guy or girl ;-) )
[07:43:22] suman ravuri: :)
[07:43:59] suman ravuri: next item mark?
[07:44:28] Mario Calderón: may I say something
[07:44:30] Mario Calderón: ??
[07:44:52] suman ravuri: yes please
[07:44:53] Mark Ostermann: @mario: sure
[07:45:51] Mario Calderón: the FT and TT do not meet regularly

we see that we are 4 people discussing

if we split the work to FT and TT , it can happen taht they don't meet, or don't do their work

that is why a joint FT -TT meeting is done
[07:46:46] Mario Calderón: I would pledge to pospone this discussion, talk over and think over it

and via email we come to a procedure
[07:46:58] Mario Calderón: because we don't seem to agree
[07:47:41] Mark Ostermann: @mario: but we have a procedure
[07:47:45] Mark Ostermann: voted by community
[07:48:03] Mark Ostermann: so we cannot just change it ... decided by us
[07:48:12] Mario Calderón: I know Mark, only it has to be filled with life
[07:48:24] Mario Calderón: and that is my doubt
[07:48:27] Mark Ostermann: thats what we are trying to do here i thought
[07:48:58] Enrique Ruibal: Hi I am here watching the discussion... lets make things simple
[07:50:17] Michael Judd: I am also watching (and thinking) and I'm happy to share some of the functional review with Mario
[07:50:25] Victor Perez Juarez: MArk if we need follwing the procedure then need follwing the workflow and are sure that are work
[07:50:27] Victor Perez Juarez: https://docs.google.com/file/d/0B9QL5-PW36eqNEttdVhsRzN6SDA/edit?usp=sharing
[07:50:41] Mario Calderón: @Mike: thanks
[07:50:44] Mark Ostermann: [15:51:07] Victor Perez Juarez: MArk if we need follwing the procedure then need follwing the workflow and are sure that are work



<<< agree victor
[07:50:49] Mario Calderón: so
[07:51:28] Mark Ostermann: that's why we should find pairings FT/ TT that commit themselves to do certain review and propose to FT/ TT Meeting
[07:51:59] Mark Ostermann: because it did not work in the past just to say FT/ TT will do the review ... and nobody did
[07:52:06] Mark Ostermann: so we need names
[07:53:15] Mario Calderón: @Mark: I would prefer then that the FT and TT meet separately and every team discusses all contribs
[07:53:20] Mark Ostermann: so lets find out who will do some work (until next week) for FT:

* Mario

* Mike

* Mark
[07:53:22] Mario Calderón: then we do a merge
[07:53:34] Mark Ostermann: any other FT member as volunteer?
[07:53:39] suman ravuri: Sorry to repeat to again
[07:53:46] Mario Calderón: I can ask John Agudelo
[07:53:53] suman ravuri: we need tangible goals
[07:53:54] suman ravuri: dates
[07:53:55] Mario Calderón: include John Agudelo
[07:54:08] Mark Ostermann: [15:54:02] Mark Ostermann: * Mario

* Mike

* Mark



<<< * John
[07:54:22] Victor Perez Juarez: are very few people require help from those who are interested in this project
[07:55:07] Victor Perez Juarez: I canare include to Sales_Management CRM
[07:55:11] Mark Ostermann: now the same for TT.  lets find out who will do some work (until next week).

* Tobi
[07:55:20] Victor Perez Juarez: but my question is how reivew
[07:55:32] Victor Perez Juarez: we need first instance an demo
[07:55:45] Mark Ostermann: [15:56:14] Victor Perez Juarez: we need first instance an demo



<<< +1
[07:56:20] Mark Ostermann: [15:55:52] Mark Ostermann: now the same for TT.  lets find out who will do some work (until next week).

* Tobi



<<< any other TT volunteer?
[07:56:21] Victor Perez Juarez: to comprobate the fuctionality , for this we need create the branch , include this some place and ask for technical revision and functional
[07:56:39] Victor Perez Juarez: the revision can not starting only in paper
[07:56:41] Colin Rooney: As “quasi” outsider can I make observation?    these meetings should (need to be) be a rubber stamping exercise for things discussed and agreed outside – perhaps with the rest of the community in the forums or as was effective in the early days in IRC… chatting and working at the same time.  You have to try and rebuild and use the community to get them to do the real heavy work done!  The FT/TT meetings should really be a tick box affair in most cases
[07:57:06] Mario Calderón: @Colin : agree
[07:57:19] Mark Ostermann: @Colin: yepp!
[07:58:32] Mario Calderón: @all: I must leave

I will make a call for a FT meeting ASAP to dscuss the contribs

deadline: next week



the TT must do the same
[07:58:44] Mark Ostermann: [15:57:01] Mark Ostermann: any other TT volunteer?



<<< 
[07:58:51] Mark Ostermann: * Teo will volunteer too
[07:59:05] Schöneberg, Tobias (metas.de): welcome on board, teo :-)
[07:59:05] Mark Ostermann: [15:59:14] Mario Calderón: I will make a call for a FT meeting ASAP to dscuss the contribs

deadline: next week



<<< thanks mario
[07:59:06] Enrique Ruibal: I volunteer
[07:59:25] Enrique Ruibal: for functional reviews
[07:59:30] Mark Ostermann: [15:59:47] Enrique Ruibal: I volunteer



<<< thanks enrique. for TT or FT?
[07:59:34] Enrique Ruibal: FT
[07:59:34] Mark Ostermann: ok, thanks
[07:59:58] Victor Perez Juarez: so we need volunteer committed
[08:00:11] Teodor Sarca: yes, i am in :)
[08:00:34] Enrique Ruibal: I want to suggest
[08:00:35] Mark Ostermann: so FT has now these svolunteers for work until next week:

* Mario

* Mike

* Mark

* John

* Enrique
[08:00:37] Victor Perez Juarez: then take inventory of this now to know who we
[08:00:52] Victor Perez Juarez: I can are in functional team too
[08:00:53] Enrique Ruibal: Is it possible to include fleet management module into the release?
[08:01:12] Enrique Ruibal: since it is something very useful and I understand it has been tested
[08:01:28] Mario Calderón: @Enrique: of coure; just include it on http://www.adempiere.com/Release_380LTS
[08:01:50] Enrique Ruibal: @Mario.
[08:01:53] Enrique Ruibal: got it ..
[08:01:57] Victor Perez Juarez: How many volunteers we have here to do technical reviews?
[08:02:13] Mario Calderón: Tobi and You by now
[08:02:17] Victor Perez Juarez: I can review as technical people
[08:02:20] Victor Perez Juarez: some more
[08:02:21] Victor Perez Juarez: ?
[08:02:31] Mario Calderón: I will ask Karsten if he joins us
[08:02:34] Victor Perez Juarez: Teo, Tobi, Trifon?
[08:02:57] Teodor Sarca: yep
[08:03:02] Mark Ostermann: so TT has these volunteers for work until next week:

* Tobi

* Teo

* Victor
[08:03:16] Victor Perez Juarez: How many volunteers we have here to do functional review?
[08:03:27] Mark Ostermann: * (Karsten to be asked)

* (Trifon to be asked)
[08:03:35] Mark Ostermann: who will ask them?
[08:03:44] Mark Ostermann: somebody from TT?
[08:03:55] Colin Rooney: I have no adempiere isntalltion of development environment setup - it will take me awhile to get organised
[08:04:09] Michael Judd: Colin - perhaps we could use the nightly build demo ?
[08:04:13] Victor Perez Juarez: but the ide that the people that I like include , remembe again committed volunteers
[08:04:18] Mark Ostermann: [16:03:58] Victor Perez Juarez: How many volunteers we have here to do functional review?



<<< [16:01:17] Mark Ostermann: so FT has now these svolunteers for work until next week:

* Mario

* Mike

* Mark

* John

* Enrique



<<< 
[08:04:33] Michael Judd: Colin - if not - you can work off my build....
[08:05:11] Colin Rooney: ok - if you do the development siode and apply the work I will help with the functional testing
[08:05:25] Mark Ostermann: great. thanks colin. ;-)
[08:05:48] Mark Ostermann: FT: 

[16:04:59] Mark Ostermann: * Mario

* Mike

* Mark

* John

* Enrique



<<< * Colin

* Victor
[08:05:59] Victor Perez Juarez: Include me in functional
[08:06:18] Victor Perez Juarez: I implemented some contribution of Adaxa , and I know
[08:06:30] Victor Perez Juarez: but I like that other review my contribution
[08:06:52] Mark Ostermann: thx victor. ;-)
[08:07:04] Mark Ostermann: so u will volunteer in FT and TT?
[08:07:47] Victor Perez Juarez: I think these people only have
[08:07:50] Victor Perez Juarez: :-)
[08:08:25] Victor Perez Juarez: now we  need distribute the work create an schedule or agenda and starting with the meeting ASAP
[08:08:58] Mark Ostermann: yepp. FT meeting will be called by Mario (as i understood) asap. i would suggest to do this in TT too.
[08:09:08] Mark Ostermann: who will call TT Meeting?
[08:09:46] Enrique Ruibal: I like the idea of a weekly mettings like these with FT and TT
[08:09:47] Victor Perez Juarez: I can convocate the TT
[08:10:04] Schöneberg, Tobias (metas.de): This message has been removed.
[08:10:05] Enrique Ruibal: not good to isolate FT and TT
[08:10:09] Mark Ostermann: ok, thanks
[08:10:39] Mark Ostermann: [16:10:47] Enrique Ruibal: not good to isolate FT and TT



<<< its just to organise the work until next FT/TT Meeting next monday
[08:10:44] Mark Ostermann: and to have results
[08:10:49] Enrique Ruibal: I get it..
[08:10:57] Mark Ostermann: the decisions will be take together by FT/TT meeting
[08:11:03] Enrique Ruibal: @Mark
[08:11:06] Enrique Ruibal: perfect
[08:11:23] Mark Ostermann: great ;-)
[08:11:41] Mark Ostermann: so can we go to next topic?
[08:12:15] Mark Ostermann: * date for release?
[08:12:58] Mark Ostermann: release date - 1 month for stabilisation phase - integration time
[08:13:17] Victor Perez Juarez: I think that can make a open window of 3 months
[08:13:25] Mark Ostermann: so i believe we have to decide how long we will give us for  integration time
[08:13:57] Victor Perez Juarez: but can created pre-releases , because we need that the FT have demo version for testing or reviews
[08:14:36] Mark Ostermann: @victor: would not call this pre-release, lets call it integration testing environment
[08:14:39] Schöneberg, Tobias (metas.de): [16:14:38] Victor Perez Juarez: but can created pre-releases , because we need that the FT have demo version for testing or reviews



<<< we can roll out the development-branch to the ADeV servers, e.g. once in 24hrs
[08:14:40] Mark Ostermann: or something like that#
[08:15:06] Mark Ostermann: @tobi: agree
[08:15:48] Victor Perez Juarez: yes the name is not important
[08:16:02] Mark Ostermann: [16:13:58] Victor Perez Juarez: I think that can make a open window of 3 months



<<< so shall we say

* 3 months from now for reviews/ integrating

* 1 month stabilisation

*  release
[08:16:03] Mark Ostermann: ?
[08:16:12] Victor Perez Juarez: can set any name , but we need , ie how the fuctional team can review the sales management CRM
[08:16:19] Victor Perez Juarez: how will test, or review
[08:16:46] Victor Perez Juarez: deployment the branch
[08:17:10] Victor Perez Juarez: if this is ok then it is include into of development
[08:17:53] Victor Perez Juarez: and the addon in development cumulative contributions
[08:18:29] Colin Rooney: does the defined process call for a technical review first?  So once it passes that couldn't it be deploy to the test env for functional testing?
[08:19:01] Colin Rooney: that would make it easy for those with no technical expertise to help
[08:19:10] Colin Rooney: does=doesn't?
[08:19:16] Colin Rooney: a retorical question!
[08:19:20] Colin Rooney: :)
[08:19:42] Michael Judd: does the nightly build update the demo site ?
[08:20:01] Victor Perez Juarez: after completing our process development branch the branch should be release
[08:20:41] Mark Ostermann: yepp. the development branch is for integration testing 1 month stabilisation
[08:20:47] Mark Ostermann: and release candidate
[08:21:23] Mark Ostermann: for FT/ TT review i believe we need the feature banch environments for the reviewers
[08:21:47] Mark Ostermann: and this could be built/ created privatly in own IDE or testing environment
[08:21:58] Victor Perez Juarez: now the issue is that some contributions are depending the others
[08:22:24] Schöneberg, Tobias (metas.de): [16:20:24] Michael Judd: does the nightly build update the demo site ?



<<< yes, there are two ADeV servers for that (one for postgres, one for oracle), it might not be functional currently, but i will check and fix if necesary
[08:22:33] Mark Ostermann: [16:22:40] Victor Perez Juarez: now the issue is that some contributions are depending the others



<<< must just be documented by contributor
[08:22:52] Mark Ostermann: so that reviewers are aware
[08:22:57] Victor Perez Juarez: it complicate this review by each branch
[08:23:53] Victor Perez Juarez: then in this case , I think that contributor should work with RM to create an functional branch to deployment and create demo
[08:23:54] Victor Perez Juarez: ?
[08:24:32] Victor Perez Juarez: whe I say functional  branch , I try say that can be deplyment as demo
[08:24:50] Schöneberg, Tobias (metas.de): [16:24:35] Victor Perez Juarez: then in this case , I think that contributor should work with RM to create an functional branch to deployment and create demo

?



<<< yes, i think those contribs need either be ordered, or bundled.
[08:24:58] Colin Rooney: opr woth those assigned to review (both TT & FT) but then I would hope that happens always
[08:25:06] Michael Judd: if the tt pass the module - can we just build it in to the nightly and then functionally test the nightly ?
[08:25:40] Enrique Ruibal: Hi Guys . I have to leave will read the thread later..good day/night to all
[08:26:40] Mark Ostermann: thanks alot enrique. bye
[08:27:11] Victor Perez Juarez: Adios Enrique
[08:27:27] Victor Perez Juarez: I starting with this work
[08:27:57] Victor Perez Juarez: some contribution was include in development becasuse are necessary for mayor of contribution
[08:28:03] Victor Perez Juarez: for example java 7
[08:28:07] Schöneberg, Tobias (metas.de): [16:25:47] Michael Judd: if the tt pass the module - can we just build it in to the nightly and then functionally test the nightly ?



<<< basically yes, but: imho, after they have been added to the nightly build, it might be hard to remove them again..so it would be good to have a *detailed* review, maybe also (documentation) from FT before deciding to integrate it into the development branch
[08:28:14] Colin Rooney: @Mike, that's what I was thinking but I never really got my head acround Mercurial .. mayhbe it doesn't work that way
[08:28:22] Victor Perez Juarez: and migration management from adaxa
[08:28:29] Victor Perez Juarez: smart browser
[08:28:38] Colin Rooney: bye Enrique
[08:28:56] Colin Rooney: @Tobis - I was thinking somethingt like that ok
[08:29:01] Victor Perez Juarez: this contribution now are into the development branch and can be testing and the reviewion for Teams
[08:29:07] Colin Rooney: Tobis=Tobias
[08:32:23] Mark Ostermann: @all. i would like to close the official part of this meeting. last topic about release date: suggestion: 14th oct 2013
[08:32:25] Mark Ostermann: wdyt?
[08:32:50] Mark Ostermann: today + 3 months review/ integration + 1 month stabilisation = release
[08:33:34] Mark Ostermann: and what is integrated/ reviewed/ agreed until 14th sept. 2013 gets in
[08:33:48] Mark Ostermann: if not has to wait 4 months longer
[08:35:47] Victor Perez Juarez: I think would be good date
[08:36:09] Victor Perez Juarez: I like go more fast , but it depend of TT and FT
[08:36:29] Michael Judd: likewise...
[08:37:48] Schöneberg, Tobias (metas.de): [16:36:51] Victor Perez Juarez: I like go more fast , but it depend of TT and FT



<<< i thinks go really great, we still can announce a pre-release or something similar :-)
[08:38:23] Schöneberg, Tobias (metas.de): early-bird-access (i'm not a marketing guy ;-)  )
[08:38:37] Mark Ostermann: :D
[08:40:29] Mark Ostermann: ok, everybody. thanks alot to all of u. have to go now. see u next week same time for next FT/ TT Meeting ... or in FT Meeting called by Mario for one of the next days.
[08:40:31] Mark Ostermann: bye.
[08:40:42] Paul Aviles: hello all.
[08:41:26] Victor Perez Juarez: Tobias, Teo said me that you like scala language
[08:42:06] Victor Perez Juarez: I will like chat with you about to make some things with ADempiere and Scala
[08:42:20] Victor Perez Juarez: Hello Paul
[08:42:37] Schöneberg, Tobias (metas.de): [16:42:08] Victor Perez Juarez: Tobias, Teo said me that you like scala language



<<< yes, i do (but i never got beyond some tutorials)
[08:43:01] Victor Perez Juarez: haaaa
[08:46:32] Victor Perez Juarez: I will like some path migration , bu is only a personal dream
[08:47:16] Schöneberg, Tobias (metas.de): [16:43:42] Victor Perez Juarez: haaaa

I will like some path migration , bu is only a personal dream



<<< yes, mine too :-)
[08:49:17] Victor Perez Juarez: I want add an the layer to Adempiere based on JSON ,using scala
[08:49:52] Victor Perez Juarez: with Akka and Spray , and using this for connect an UI for adempiere
[08:50:11] Victor Perez Juarez: When I have some more concrent I will invite
[08:50:27] Schöneberg, Tobias (metas.de): thanks, that would be great
[08:52:01] Teodor Sarca: guys, i got to leave, cu
[08:52:06] Schöneberg, Tobias (metas.de): cu
[08:52:16] Victor Perez Juarez: cu
[08:52:38] Paul Aviles: Victor have you seen the amount of issues with scala regarding performance?
[08:53:48] Victor Perez Juarez: mmm, in compile or runtime
[08:54:10] Victor Perez Juarez: becasue in complie is more slow that java
[08:54:28] Victor Perez Juarez: but in run time is the same that java, because work in the same JVM
[08:54:46] Paul Aviles: the architecture itself is the issue, everything requires round trips to the server has nothing to do with java
[08:55:14] Victor Perez Juarez: SO is as fast or slow as java ;-)
[08:56:01] Paul Aviles: it is worse than ZK in perfomance unless you reqrite the entire thing considering how they need to do client side validations
[08:56:07] Paul Aviles: it is on ther documentation
[08:56:09] Victor Perez Juarez: what server ?
[08:56:54] Victor Perez Juarez: Scala only is programing language Paul
[08:57:17] Victor Perez Juarez: but exist some framkeworks as akka or play
[08:57:39] Victor Perez Juarez: So I not understan when said the architecture itself is the issue, everything requires round trips to the server has nothing to do with java
[08:57:46] Paul Aviles: Victor I know what it is and have read the documentation, I guess you have not
[08:59:03] Victor Perez Juarez: but Scala implement a paradigm that -java no implement
[08:59:15] Schöneberg, Tobias (metas.de): paul, maybe you mean seaside/smalltalk ?
[08:59:19] Victor Perez Juarez: they use inmutable datas and actors patters
[09:00:11] Victor Perez Juarez: vs lock and threads of java that is very inefficient to handle concurrency
[09:01:32] Victor Perez Juarez: Current Twtter and Linkedin use scala to solve your peroformace and concurrency
[09:02:53] Victor Perez Juarez: in the case the twiter worked with ruby and failed, but they resolved their issues with Scala
[09:16:28] Colin Rooney: there was a discussion recently on an irish tech forum re scala and someone metioned that twitter went to scala for performance
[09:17:13] Colin Rooney: but someone said that they moved just the message queue to scala but more recemtly have moved their search engine to java
[09:17:28] Victor Perez Juarez: @Colin , I think that was for change the approachs
[09:17:45] Colin Rooney: I thoght because twitter havethe Eur HQ in Dublin someone might have had some inside info
[09:17:46] Victor Perez Juarez: the now use actors to management the high concurrency
[09:18:12] Colin Rooney: https://blog.twitter.com/2011/twitter-search-now-3x-faster
[09:18:35] Colin Rooney: is their tech blkog might be of interest!?
[09:20:35] Colin Rooney: re: Squeak/seaside ... BAhman has recently blogged about Pharo
[09:20:50] Colin Rooney: which is a squeak fork that apparently seaside is developed
[09:20:52] Colin Rooney: in
[09:20:55] Colin Rooney: which was news to me
[09:21:14] Victor Perez Juarez: haaa
[09:21:16] Colin Rooney: seems Pharo want to move squeak out ofthe academic into the real world
[09:24:26] Victor Perez Juarez: they explant here your issues and business case
[09:25:51] Victor Perez Juarez: http://www.artima.com/scalazine/articles/twitter_on_scala.html
[09:28:36] Colin Rooney: thx -  I looked at scalka in 2008 looks like some tasks were well suited but I don't think I'd like to build an ERP, for example, with it! :)
[09:29:25] Michael McKay: Hi guys.  Just reading the thread and can help but I have limited time.
[09:29:45] Victor Perez Juarez: @Colin Why?
[09:30:21] Victor Perez Juarez: Is  as build in java but in scala , with all your adventages
[09:30:34] Victor Perez Juarez: Adempiere now have issue to scale
[09:30:36] Victor Perez Juarez: :-(
[09:31:37] Victor Perez Juarez: out adempiere is design with approach client /server
[09:31:40] Colin Rooney: it's scaling issues is architecture tough?
[09:31:47] Colin Rooney: yes agreed
[09:31:49] Victor Perez Juarez: with a lot the codign hith compling
[09:31:54] Colin Rooney: but that's not java's fault
[09:32:13] Victor Perez Juarez: highly coupled
[09:32:39] Victor Perez Juarez: yes but if I need buid again I prefered try with scala ;-)
[09:34:14] John Agudelo: Hi all, I had problems with the internet I am out of town, I finished reading all the meeting, I am sad because I feel like ls today things are slower and do not know what is then the role of RM
[09:35:50] Victor Perez Juarez: So I had 2 option rewrite bason in JEE or Spring frameworkor in java  or some scala frameworks as (Akka)
[09:36:04] Victor Perez Juarez: so we need units test  for all system
[09:37:42] Colin Rooney: my pref is still java/spring - but that there are some tasks that might be more suite dto a functional language and then scala might be a better fit - and luckily it'ds all in teh JVM so we should be able to mix all in thje JVM
[09:37:55] Colin Rooney: @John - I was thinking that too
[09:38:18] Victor Perez Juarez: the problem is not java Colin, Scala just preference and how others have solved the problem of concurrency and scalabilidad using Scala and explain why they were not with java, which is very interesting
[09:41:02] Colin Rooney: yes it is always intersting - but they are solving a very specific problem but j2ee is a whole architecture not just a language so I would think java/spring is better to implement the core of the enterprise system
[09:41:05] Colin Rooney: that might use scala
[09:41:39] Victor Perez Juarez: is curious to know that Rob Johnson the creator of Spring VMware to leave the company , and now he join typesafe the company creator of scala
[09:42:19] Colin Rooney: that is interesting ok - Rob is my hero! :)
[09:42:27] John Agudelo: @colin:  I will wait and see what happens

see you guys
[09:42:58] Victor Perez Juarez: mee too
[09:43:12] Colin Rooney: :)
[09:43:15] Colin Rooney: I have to run too
[09:43:19] Victor Perez Juarez: but if he move to typesafe and leave VMware
[09:43:27] Colin Rooney: I had a great chat with Rob back in 2006
[09:43:37] Victor Perez Juarez: I think is becasue he will make big things for scala
[09:43:42] Colin Rooney: we drank some guiness - ate some food and ha da nice chat
[09:44:05] Colin Rooney: it certainly has a lot of people interested
[09:44:13] Colin Rooney: and he really dislikes j2ee
[09:44:41] Colin Rooney: more the slowness that is developes I think
[09:44:47] Colin Rooney: he hated EJBs
[09:45:02] Colin Rooney: anyweay I have to leave before the traffic
[09:45:29] Colin Rooney: that he is on board certainly makes me pause and look again!
[09:45:41] Victor Perez Juarez: theoretical implementation to solve a practical problem
[09:45:55] Colin Rooney: he probably make a whole lot of money selling springsource to VMware though
[09:46:00] Colin Rooney: so can do things just for fun
[09:46:39] Colin Rooney: by eall
[09:46:53] Colin Rooney: godo to chat Victor - as always!
[09:49:33] Victor Perez Juarez: yes , I think that people as Rob Johshon or Martin Odersky want to create the next development platform for the next decades
[09:50:07] Victor Perez Juarez: are restless minds, who are not satisfied with what they have
[09:50:21] Victor Perez Juarez: it happen with Rob and EJB
[09:50:49] Victor Perez Juarez: and with Martin Odersky  when create the main core for Java  1.5 and generics
[09:51:43] Victor Perez Juarez: see you Colin goo caht with you
[09:51:50] Victor Perez Juarez: see you later
[11:29:06] Paul Aviles: Victor de scalabilty issues with adempiere has nothing to do with the GUI, it has everything to do with poor design in a flat client
[11:33:58] Victor Perez Juarez: yes Paul it was of conclution
[11:34:09] Victor Perez Juarez: Colin said same , the issue not is java
[11:34:25] Victor Perez Juarez: the issue is the disaign architecture