PMC Functional Meeting 20100325
Date: 2010-03-25
Time: 9PM GMT
Venue: irc #adempiere-team
Support Spreadsheet: Adempiere PMC Functional
Chat times in GMT-5
(16:00:08) trifon: OP CarlosRuiz
(16:00:20) CarlosRuiz: Hi
(16:00:23) trifon: hi
(16:00:32) trifon: i was trying to make you operator of the channel :)
(16:00:40) trifon: not sure why command did not worked...
(16:00:47) CarlosRuiz: :-)
(16:01:19) ar_howard: Hello :-)
(16:02:13) CarlosRuiz: Hi Allan
(16:03:05) ar_howard: I don't think Steven will be here today as he is on leave. Not sure if anyone else from Adaxa will attend in his place. I will be a little disjointed today as I'm getting our girls ready for school
(16:04:39) CarlosRuiz: ok - let's wait a little for Joel
(16:06:22) ar_howard: What is of interest to me are 3 things. 1) What is most effective in getting some of developments with Adaxa in front of the community, and 2) How to get those integrated if deemed desirable, or 3) if not desirable the best way to keep other integrations in the public eye in case someone else wants to adopt in the future
(16:09:16) CarlosRuiz: yep - good themes to discuss here
(16:13:11) ar_howard: My initial thought was to make the full environment with source (de-identified data) to be available for people to view and understand. Then discussions from that point could ensue as to the appropriateness, etc of those changes
(16:15:45) ar_howard: I would hope that we could develop a model whereby other customers/integrators could do the same and so the project can "cherry pick" the best ideas
(16:18:10) CarlosRuiz: today we have one example of this - metas published an add-on and it's close to arrive to trunk now
(16:21:39) ar_howard: I think the trick thing is we don't want Adaxa wasting effort of creating an add-on for every change just in case it might be accepted - but others would need to comment on effort/reward and if it's that big a deal. Everything delivered to us so far has been in customization.jar
(16:21:40) JoelS_ [~4b64bbbd@gateway/web/freenode/x-wuhxtxseupneppdu] entered the channel.
(16:22:54) JoelS_: hello gentlemen, i thought it wasnt for another hour
(16:23:13) ar_howard: Hi Joel - the challenges of timezones ;-)
(16:23:45) CarlosRuiz: Hi Joel - we were waiting for you
(16:23:52) JoelS_: how are you allan- long time with no chat
(16:24:14) ar_howard: Good thanks Joel .. finally starting to see more light after our implementation
(16:24:39) JoelS_: it's starting to click for you?
(16:24:55) CarlosRuiz: ___________________
(16:24:55) CarlosRuiz: Allan wrote previously:
(16:24:55) CarlosRuiz: What is of interest to me are 3 things. 1) What is most effective in getting some of developments with Adaxa in front of the community, and 2) How to get those integrated if deemed desirable, or 3) if not desirable the best way to keep other integrations in the public eye in case someone else wants to adopt in the future
(16:24:55) CarlosRuiz: My initial thought was to make the full environment with source (de-identified data) to be available for people to view and understand. Then discussions from that point could ensue as to the appropriateness, etc of those changes
(16:24:55) CarlosRuiz: I would hope that we could develop a model whereby other customers/integrators could do the same and so the project can "cherry pick" the best ideas
(16:24:55) CarlosRuiz: ___________________
(16:26:06) JoelS_: that seems like a high hurdle to ask of some contributors
(16:26:32) JoelS_: maybe with large things like this, we could get it into a branch and build it
(16:26:45) JoelS_: then people might go and look
(16:27:23) JoelS_: this thing with Adaxa work, is I am certain it is quality, so in their specific case, it could be loaded to a branch and we could do peer review and integration
(16:27:50) JoelS_: I'd even get a developer to help with this
(16:27:54) ar_howard_: Yes, we need to find a way to reduce the hurdle - even for Adaxa
(16:28:53) JoelS_: so we could try your idea carlos, for this case, and see how it works
(16:29:14) JoelS_: but even cleaning data for presentation can be some work
(16:29:47) ar_howard_: We also have a Drupal webshop integration that may bring it's own challenges to demonstrate
(16:30:16) CarlosRuiz: which was my idea :-?
(16:31:07) JoelS_: CR: make the full environment with source (de-identified data) to be available
(16:31:22) CarlosRuiz: ah - I was copying what Allan said before
(16:32:02) CarlosRuiz: the part enclosed with ___________________ is from Allan :-)
(16:32:20) JoelS_: ah I see, Allan, we could provide you a hosted server if you would be willing to put a scrubbed database there
(16:32:22) JoelS_: then we could review
(16:33:07) CarlosRuiz: I guess the first step is people to state what they have
(16:33:12) ar_howard_: Our issue is we have exhausted funds for Adaxa's time to do this - typical of most implementation projects
(16:33:19) JoelS_: maybe we could facilitate that- if a contributor makes a branch and gives a scrubbed db, we could put up an instance
(16:33:30) CarlosRuiz: norbert tried to start an inventory of that in wiki ....
(16:34:22) JoelS_: well, for you allan, I would give resources :)
(16:34:59) ar_howard: Thanks Joel, I was hoping that some people would see merit in some of the things done and be able to help out. Thanks
(16:35:06) CarlosRuiz: this is the link
(16:35:06) CarlosRuiz: http://www.adempiere.com/index.php/Feature_Development_Collaboration
(16:35:06) CarlosRuiz: that could be a first step
(16:35:23) CarlosRuiz: although maintaining a wiki page is hard - maybe a spreadsheet will be easier for everybody
(16:36:08) CarlosRuiz: and publish the sources - then we can make a "voting" round - or poll to see what is worthy to work on to integrate in release
(16:36:32) JoelS_: as a project-wide approach, I agree that is good
(16:36:58) CarlosRuiz: thinking on publish data at this stage - is too much work for the implementor or developer
(16:37:22) JoelS_: how about a 'project of the month' where we pick one of the feature sets, advertise it and the contributor, and put up a test instance?
(16:37:39) JoelS_: of course, the contributor must apply for that
(16:38:38) JoelS_: on publishing data, we need a script that can be run to scramble all the names and numbers
(16:38:53) CarlosRuiz: then we need a column to identify the size - there are things there that are just a few lines of code - and there are modules
(16:39:24) JoelS_: well, anything small we should just move in
(16:39:38) JoelS_: this is only needed for big stuff
(16:41:31) CarlosRuiz: something I'm really interested to work on with functional PMC group is a template for those big specifications - to take into account all the edges of the project that commonly in an implementation project are not seen
(16:42:11) CarlosRuiz: i.e.
(16:42:11) CarlosRuiz: qa tests
(16:42:11) CarlosRuiz: test data
(16:42:11) CarlosRuiz: documentation
(16:42:11) CarlosRuiz: impact on other modules - i.e. impact on accounting
(16:42:11) CarlosRuiz: impact on interfaces (i.e. webservices)
(16:42:11) CarlosRuiz: ... etc
(16:42:25) CarlosRuiz: not necessarily to stop things - but to know the status when going into trunk
(16:42:57) JoelS_: yes, i agree. It is my task to draft that template, but still not finished
(16:43:12) JoelS_: did you still want to take that from me?
(16:43:18) CarlosRuiz: sure
(16:43:32) ar_howard: The best time to capture those things are during an implementation - this would minimise rework afterwards - if this were an ideal world the implementation documentation could contribute to such a document
(16:43:52) JoelS_: ok. I will review it promptly once you post a start
(16:44:28) CarlosRuiz: yep - having an adempiere template will help implementors to do that also
(16:44:53) JoelS_: part of my hope is that implementors will post the concept before it is written
(16:45:02) CarlosRuiz: I'll prepare the template and share it with you on maillist and google docs
(16:45:07) JoelS_: so that it gets input, or find out if others have done similar
(16:45:10) CarlosRuiz: and we can review and discuss on next meeting
(16:45:21) JoelS_: and then that document could evolve during the project
(16:45:39) CarlosRuiz: BTW - Allan - do you want to be part of PMC Functional Group? to include you on the mail list and google docs?
(16:45:46) JoelS_: and at the end be a decent representation (docs are never totally up to date)
(16:46:01) ar_howard: Yes, happy to contibute whatever "little" things I can
(16:46:29) CarlosRuiz: ok - will add you to the group and all the stuff
(16:47:58) JoelS_: ok, so it sounds like the Functional Group is hinged at the moment on the specification template
(16:48:20) JoelS_: for the next week, I think I will put a 'functional review' type item on the agenda
(16:48:42) JoelS_: maybe with a specific funtionality to discuss, we will generate some interest
(16:49:41) CarlosRuiz: next week is full of holidays here - can we meet again in two weeks?
(16:50:15) JoelS_: sure
(16:50:25) JoelS_: what holidays?
(16:50:30) ar_howard_: Yes, same here with holidays (going mobile - fingers crossed)
(16:51:18) CarlosRuiz: something called "holy week" :-)
(16:52:22) CarlosRuiz: so - is it ok if we set up next meeting to be april 8 same time?
(16:53:04) McBoss [~ca59367a@gateway/web/freenode/x-hfzcshbrcdikqhwq] entered the channel.
(16:53:44) CarlosRuiz: and in the agenda for next meeting will be
(16:53:44) CarlosRuiz: discuss spec document
(16:53:44) CarlosRuiz: discuss how to evolve the page "Feature_Development_Collaboration"
(16:53:44) ar_howard__ [~ar_howard@58.108.111.101] entered the channel.
(16:53:53) CarlosRuiz: Hi Peter
(16:53:54) ar_howard__ has left the channel (quit: Client Quit).
(16:54:11) ar_howard__ [~ar_howard@58.108.111.101] entered the channel.
(16:54:32) McBoss: Hello Carlos - please excuse the bungled attempt to join you - thanks for the email
(16:55:02) CarlosRuiz: :-) the important is you're here
(16:55:07) JoelS_: hi carlos, sounds good
(16:55:53) McBoss: I'll just watch for the moment and see where I can contribute
(16:56:19) CarlosRuiz: Peter - before you arrived I asked Allan if he wants to be official member of PMC Functional Group
(16:56:19) CarlosRuiz: now asking the same to you :-)
(16:57:09) McBoss: Well - you'd want to be sure I've got something to say and contribute....
(16:57:31) CarlosRuiz: I'm sure you have :-)
(16:57:47) CarlosRuiz: you were the top contributor on triage day
(16:58:00) ar_howard_ has left the channel (quit: Ping timeout: 276 seconds).
(16:58:09) McBoss: Alan's a bloke with real skill and balls (if you'll excuse the expression) what he's done at Intouch is nothing short of revolutionary
(17:00:04) ar_howard__: My wife is trying to talk me about writing a freelance IT article about it - I'm perhaps a bit too much of a perfectionist to know when to do such a thing :-)
(17:01:38) JoelS_: Allan, do you still have contact with anyone at NPSGlobal?
(17:02:09) JoelS_: > too much of a perfectionist to know when to do such a thing -- release early release often!
(17:03:58) ar_howard__: I thin NPS global founders were probably retrenched - last communication I had was they were expecting a big restructure and thought they would be ok - I now guess not :-( for them
(17:06:21) ar_howard__: Joel - release early/often is too radical to demonstrate at CIO level which is where I would target
(17:08:38) ar_howard__: On train now so I will probably lose connectiion - thanks to all for our discussion
(17:08:59) CarlosRuiz: ok guys - I guess we can finish this meeting - not very productive today - but it's a good start to work with Australian PMC members
(17:09:05) CarlosRuiz: I sent the invitation for next meeting
(17:09:18) CarlosRuiz: and I'll subscribe Allan and Peter to the maillist and docs
(17:09:20) CarlosRuiz: thanks for attending
