I have interest in "Staff Rostering". Right now I'm planning to work on porting to OpenERP a custom developed shift scheduling app.
DR From: juancristo...@gmail.com Date: Sat, 24 Nov 2012 02:22:22 -0300 To: nho...@gmail.com CC: openerp-community@lists.launchpad.net; openerp-community-revie...@lists.launchpad.net Subject: Re: [Openerp-community] Community project Last updates Ok, I booked: https://blueprints.launchpad.net/medical-openerp/+spec/healthcare-building-blocks (will start working next month) On Sat, Nov 24, 2012 at 2:05 AM, Nhomar Hernández <nho...@gmail.com> wrote: Excellent.... 2012/11/24 Juan Cristobal Lopez Arrieta <juancristo...@gmail.com> Nhomar, We will be glad to contribute to the the 'medical' project. Actually we are working on a review that goes beyond the migration. We will create some blue-prints very soon. The place, to avoid misunderstood! https://blueprints.launchpad.net/medical-openerp/+addspec Regards! Also it will be nice to have some inputs from Eckhard Schwarzat, from Valuedecision. We are starting a project for at least one major Hospital next year rgds On Fri, Nov 23, 2012 at 10:59 PM, Nhomar Hernández <nho...@gmail.com> wrote: Hello Friend some comments. 2012/11/23 Joël Grand-Guillaume <joel.grandguilla...@camptocamp.com> Dear all, Some informations about the last (suggested) changes after your feedback, hopes, and fears ;) Project title:--------------I renamed the project title with " OpenERP * " prefix so we can identify them more easily when assigning bugs (this was suggested by some of you). The branches and LP project name are still unchanged. Bug tracker:---------------I don't took the time to activate all bug tracker on every project right know. Anyone from the "OpenERP community reviewer" team can do it easily if needed. For others, I suggest to email us in case you need it. Review and Merge proposal (6.1 and 7.0 series):--------------------------------------------------------------As we committed our own Camptocamp's module in the new community project without review, and to be fair with everyone, I suggest the following about the reviews. On the 6.1 serie of all new community projects, we make more softened review of the modules. This will smoothly bring everybody to a better quality level while still accepting the today's existing and acceptable modules. This means, community modules on version 6.1 will accept module that are not "perfect", but on the other hand will incite the developer to push the quality a step further on every MP. This is mostly due to the fact that we don't have defined quality standard right now and we need to start building our community ecosystem anyway. But... For future serie 7.0, I'll suggest that we really take care of which module we accept on every community project, and with which quality standard. This means, we WON'T BRANCH the 6.1 serie to starts the 7.0 one. We'll rather extract all modules from it, and built a MP to an empty 7.0 branch. Each MP on serie 7.0 will be reviewed more deeply as we will know we'll gonna maintain it over years together. I think this is a fair approach that will both allow existing module with a fair quality to be part of the "adventure" while ensuring strong basis for the future ! Review documentation: ------------------------------ I'll point here the LP documentation about reviewing merge and also added it to the official doc.openerp.com : https://help.launchpad.net/Code/Review I also read this : https://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews and find it very interesting as a starts to build our own rules. Anybody wanting to write a first draft of our own from this ? GTK client:-------------- Apparently no majority will to make a community branch of the GTK client. I let the interested people organize their-self together to starts a common project on LP. New/Future project:------------------------- New project landed: - Medical in OpenERP : https://launchpad.net/medical-openerp Thanks God i made this fork in the right moment jeje, we installed very basic features on some hospitals almost for Free because they are in little countries, as community should be cool mantain this project complaining all community guidelines talked before in __this__ project, Today, we are not planning put code in other place different to this. but if somebody will take care of the migration (we are planning do it but not this year), we can merge them changes at instant [EveryBody knows our compromise with the efective community] and if they ask publically to be a reviewer and community is agreed i open as the other projects where selected for now just openerp-community-reviewer already selected by community are the reviewers. I think if somebody else wants to take control of the project before i can give the rights without any problem, but please show first the code ;-) and ask to community. - Hotel Management System on OpenERP : https://launchpad.net/hotel-management-system We are migrating right now to use the more basic features because we have in Venezuela one demo in a Hotel School, we will be in charge of the migration, if somebody can help us to migrate views (almost all are broken) it can be great we start with hotel and hotel_reservation, hotel is instalable right now. I think the first sprint can be done just to be able to install on v7 if somebody else have othe ideas, welcome. Thanks for the support/. Future suggestions: - GIS for OpenERP Joel. as in private i ask you, We are planning work with you from a commercial PoV in this project, for us should be an honor help you with this, we already are closing deals that need this framework/feature that you in C2C developed already, WE ARE IN ;-) - Community Web addons for OpenERP I think we should have some minimal technical rules before select what a web_addons means, because JS is so easy to brake, but IMHO it is a must to have one time we have the quorum of modules. Though ? Thank you all, have a nice week-end, Cheers, Happy WeekEnd. Joël -- Joël Grand-Guillaume Division Manager Business Solutions Camptocamp SA PSE A, CH-1015 Lausannehttp://openerp.camptocamp.com/ Phone: +41 21 619 10 28 Office: +41 21 619 10 10 Fax: +41 21 619 10 00 Email: joel.grandguilla...@camptocamp.com _______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- -------------------- Saludos Cordiales Nhomar G. Hernandez M. +58-414-4110269 Skype: nhomar00 Web-Blog: http://geronimo.com.ve Servicios IT: http://vauxoo.com Linux-Counter: 467724 Correos: nho...@openerp.com.ve nho...@vauxoo.com twitter @nhomar _______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- Juan Cristobal Lopez Arrieta http://www.openerp.com/node/560 +54376 4437686 Celular: +549376 4376481 skype : jclopezar -- -------------------- Saludos Cordiales Nhomar G. Hernandez M. +58-414-4110269 Skype: nhomar00 Web-Blog: http://geronimo.com.ve Servicios IT: http://vauxoo.com Linux-Counter: 467724 Correos: nho...@openerp.com.ve nho...@vauxoo.com twitter @nhomar -- Juan Cristobal Lopez Arrieta http://www.openerp.com/node/560 +54376 4437686 Celular: +549376 4376481 skype : jclopezar _______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
