Le 15/03/2014 17:31, Info SHS-AV a écrit :
Agree.
UE team should ask regional teams about domestic structure in order to
build functional software.
In example, for address, UE team shold require these info:
Address format: Italy -> %(zip) %(city)s %(state_id)s
ZIP format: Italy -> 5 digits
ZIP
Le 14/03/2014 10:42, Lionel Sausin a écrit :
Unfortunately the tagged releases run red on runbot
I base this assumption on the status of the *.*-release branches I
pushed here, using the tagged revisions:
http://runbot.openerp.com/numerigraphe-team.html#
__
Dear Olivier,
Thanks for your care, the changes you made are fine by me. They're red
on runbot at the moment but it seems to be a simple reference problem in
the test.
If you merge them into the trunk, I'm confident I can port it all back
to OCB v7.
Now, you're not proposing everyone with a s
We're quite interrested in testing this early branch, but we'll only be
able to give feedback next week and the week after. Is that OK?
Lionel.
Le 13/01/2014 10:27, Jos Colpaert a écrit :
Dear community members,
You may be aware of it: we presented, on the last community days, our
analyze on
Le 13/01/2014 17:12, Wouter Tebbens a écrit :
Hi,
I had exactly the same experience as Alexandre describes. Only by going
the partial delivery route could I ship the order.
Allow me an additional comment: for the lot numbers to be assigned on a
*FIFO* basis, one (or at least: I) would expect th
Le 16/12/2013 11:09, Joël Grand-Guillaume a écrit :
(...)
3) Too few people invest time to make reviews and test the work of
other without being part of the reviewer. May I remind here that
EVERYBODY CAN REVIEW each others work and give his opinion. The
community reviewer team only gives the c
Le 29/10/2013 10:09, Joël Grand-Guillaume a écrit :
(...) So, at the end, the question will be : How OpenERP SA can
benefit from us ;) ?!
Being an end user, I could just as well ask how you can all benefit from
us ?
Joking of course - well, half joking at least. But let's not forget the
communi
Le 29/10/2013 02:50, Olivier Dony a écrit :
If this problem occurs again with a high frequency we should make sure
the following MP is verified to be working safely and apply it - all
feedback welcome:
- original MP for 6.1:
https://code.launchpad.net/~openerp-dev/openobject-server/6.1-fix-po
Hi,
to put this discussion in perspective, let me give an overview of
which schema changes have been put through in ocb-addons/7.0 so far:
- An 'active' field was added to account.journal
- A sequence field was added to account.tax
- A link was created from crm.phonecall.report to crm.lead
J
Le 25/10/2013 16:44, Stefan a écrit :
My personal gripe is with [3]. I think having an 'unstable' series
that does allow the occasional new field to percolate through is a
major attraction to OCB. It must be the reason that I remember our
conversation at the community days slightly differently
Yes this is still a problem with legacy code: you filing a bug report
was the right thing to do.
Maybe you can push a merge proposal too ?
Lionel.
Le 25/10/2013 09:10, ? a écrit :
Hello everyone who cares about improving OpenERP.
We faced the problem with context and I want to pay
Le 16/09/2013 14:35, Olivier Dony a écrit :
One thing that's easily overlooked is that OpenERP is a very complex
piece of software, and the R&D team spent *a lot* of efforts during
the last few years in order to simplify it for new users.
I can imagine how much work that is and I'm grateful for
skip v6.1, and I'm not sure
whether we can ever migrate to v7 (we'd skip from v6.0 to v8).
So I'd be happy to co-maintain shared modules if that can make it less
time consuming for us.
Lionel.
Le 16/09/2013 12:15, Lorenzo Battistini a écrit :
Il giorno 16/set/2013 09:26
Hi,
Personnally, I would most appreciate if you made merge proposals to the
trunk when applicable.
I known OpenERP SA is not reactive to this type of MP's (I have made
quite a few myself that not been reviewed for months/years). Even
though, I remain convinced that most of this this belongs t
Thanks for that needed work.
IMHO you should leave the "comming soon" parts out, or make sure they
are not rendered in the final docs. Those words usually bring
frustration to the reader.
Lionel Sausin.
Le 14/09/2013 18:54, Maxime Chambreuil a écrit :
Hello everyone,
Thank you very much for
Sorry to reply so late (I was off for weeks), but...
I remember last year Ana said of the community days: "if they'd given me
the money it costs to do it here, in Spain I would organize the biggest
fiesta you've ever seen!" :)
Joke aside, the best would be to seize the opportunities of real-wo
Title: Eric CAUDAL
Dear Fabien,
One more question please?
We're just developed modules to help us manage our annual physical
inventory (6 levels of nested locations, 4000 product refs +
prodlots). Those improvements are generic and useful for
medium/complex
Excellent!
I'm looking forward to work with this when you merge it into the trunk.
Lionel.
Le 03/07/2013 00:05, Fabien Pinckaers a écrit :
Did you check the new branch (same name but with -fp) It has 3000 lines of code
removed and costing is more isolated allowing an easy inheritancy
Sent from
Hi,
Thanks for the pointer, that looks great!
And a bit complex too.
Would you care to explain where I should start ? Maybe a demo screencast
or a documentation?
In particular, how do I add the EBP specific parts (CSV file in a
specified format + needs to be pushed to a windows share)
Lionel Sa
Fabien,
I've had a quick look at the dev branch : impressive stuff !
I have just one additional request right now: would you please split the
costing code to separate modules?
We're going to deeply audit/review the average costing code but doing
this right now is insanely hard.
Thanks in advanc
nt-seduce>
I can't do more than that, hope it helps.
Regards,
Joël
On Wed, Jun 26, 2013 at 5:42 PM, "Lionel Sausin, de la part de
l'équipe informatique Numérigraphe" <mailto:informati...@numerigraphe.com>> wrote:
Thanks Joël,
We're quite willin
object-addons/trunk-wmsimplement-seduce>
I can't do more than that, hope it helps.
Regards,
Joël
On Wed, Jun 26, 2013 at 5:42 PM, "Lionel Sausin, de la part de
l'équipe informatique Numérigraphe" <mailto:informati...@numerigraphe.com>> wrote:
Tha
Thanks Joël,
We're quite willing to adapt what we've done so far to the new system.
We now have a full time developer for our logistics projects.
So, we would appreciate as much detail as possible while the
implementation is going on. A blog would be really great.
Otherwise we'll have to wait un
As a reminder, I'd also like to point to this extensive blueprint we
wrote last year about the picking GUI.
https://blueprints.launchpad.net/openobject-addons/+spec/new-partial-picking-wizard
Demo implementation here:
http://fr.slideshare.net/openobject/openerp-new-procedure-for-partial-deli
Dear Eric and others,
Thank you all for this big and needed push forward.
We're in the process of restructuring our logistics using OpenERP, and
mostly we agree with Eric's view.
My remarks so far are inlined bellow.
I am well aware that some of what we expose here is not supposed to be
in the
Hi,
I hate to be a trouble maker, but I'll just give you an outsider's view
on this process: forcing a timing on reviews means only shallow problems
will be identified, and not deep functionnal issues.
Many issues that need improvements in the area of warehouse management,
financial management
Dear Olivier,
Just to keep you and others from spending time on this: I finally
figured out that I can avoid the trouble by putting the values I want to
commit in the demo dataset, and let OpenERP roll back the tests.
Lionel.
Le 24/05/2013 15:33, Lionel Sausin a écrit :
Dear Olivier Dony,
We'
Hi,
You should make a merge proposal if you haven't already (Launchpad
doesn't show one on the branch you quote).
I believe OpenERP SA is always looking for l10n improvements.
Lionel
Le 22/05/2013 10:45, Geert Janssens a écrit :
Hi all,
I have been working on making the l10n_be translatable.
Hi,
You can count me in, I'll be happy to take part in a shared generic module.
There was a "city" module in v5.0/6.0 extras, which I had optimized a
goog bit and made more generic. Unfortunately our changes were
ruthlessly overwritten and the merge proposal [1] I made remained
unreviewed, and
Dear Christian and community,
Ovnicraft wrote:
Hello, i am interested to work with you in this for 6.1 we are working
with stock modules and has that requirements.
I've converted my patch into a module, which I suppose will be easier to
work with.
It is available here :
https://code.launchpad.
Dear community,
If I'm not mistaken, no solution has yet been found to make the products
and the stock locations searchable in the official OpenERP addons.
Yet, all it takes is to implement search functions for a few fields - in
Product : qty_available, virtual_available ; in Location : stock_r
Le 14/02/2013 11:59, Normunds Vilcans a écrit :
(...) Selling AGPL module puts barrier for "leechers/forkers", who
want "invest" by changing name of module and some menus and advertise
as their sole work.
You will say that those leechers will get "source" anyway, yes they
will, but it will be "
Dear Greg Moss, please let me sum it up again.
You're preaching for an obsolete business model that others have already
tried and failed at.
There are no customers for this here.
You are in a market where programming is the investment, community
contribution is the advertising, and consulting i
Le 06/02/2013 12:17, Christophe Hanon a écrit :
I agree with Arun.
Not saying I am against Bertrand opinion. If you find a published
module and get benefits using it, it is fair to work with and pay the
publisher.
However it seems, there are some difficulties in OpenERP community to
admit
Oh well.
Partners, you really are but a fraction of the OpenERP ecosystem.
Spend your time&money on a private wiki if you like. Be aware that
previous OpenERP wikis have failed however.
The "knowledge base" already exists outside the partners - it's the
documentation, and it desperately needs lo
Bonjour,
Le mieux est d'en discuter avec les relecteurs qui gèrent le lexique et
valident les traductions : openerp-i18n-fre...@lists.launchpad.net ; je
les met en copie.
Lionel Sausin.
Le 04/02/2013 09:36, doddo a écrit :
Bonjour,
Ok, je comprends l’argument. Néanmoins, vous appelez donc
Hi,
You could try bzr checkout --lightweight - that won't let you commit
local changes I believe, but maybe it's OK for you?
Lionel.
Le 01/02/2013 04:24, indra kurniawan a écrit :
Hi , I was trying to checkout the source from launchpad as written in doc.
What is the download size (checkout siz
Le 30/01/2013 12:02, Stefan Rijnhart a écrit :
On 01/30/2013 11:51 AM, Nabil Majoul wrote:
(...)My understanding is that this will lead to a one to one
negociation between A and B...But is there practices established ? is
there an interest to establish some rules or a framework for this
kind o
Dear community,
Can you please point an up-to-date description of the new "official"
community-maintained projects ?
I'd particularly like to know how they relate to the existing experts
team, and to the main addons maintained by OpenERP SA : when I file a
bug report or make a merge proposal, I
Le 09/01/2013 16:09, Michael Telahun Makonnen a écrit :
Ideally, I would like to see these changes integrated in to the
official point_of_sale module. In that case a separate module would
not be needed.
Yes, I suggest you start making merge proposals to have the new features
adopted by OpenERP,
Yep, I mostly branch my bug-fixes from a stable "x.y.0" tag, which has 2
more advantages :
* it makes uploading the branch to LP much faster
* it often allows the same branch to be merged in several stable
versions AND in trunk.
However there are cases where this is not possible because of con
Here's what I do when I build a patched debian client package for 6.0.4,
I hope it helps you :
* dch -v 6.0.4-something to add a debian changelog entry and bump version
* modify the version number in setup.nsi bin/release.py to 6.0.4-something
* to keep dpkg-buildpackage from complaining that the
Le 11/12/2012 11:25, Joël Grand-Guillaume a écrit :
I started creating the 7.0 series on some of the community projects as
we start migrate some modules. I did it without branching the 6.1
serie and I associated a brand new branch on them. The goal is here to
start including in the 7.0 serie on
I doubt the developers can improve that much on this issue, but what
everybody can do is watch the merge proposed into the trunk, and
politely demand good wording and mark them "fix needed"
As for the existing strings, making lots and lots of merge proposal will
probably flood the core team.
H
Dear community,
For now the urgency is v7, but beyond that I really encourage the native
English speakers in the community to gather as a team and tackle the
task of reviewing *all* the strings.
This *is* a lot of work, but only a bit harder than reviewing a whole
translation.
I'm sure Olivi
Le 22/11/2012 10:31, Pieter J. Kersten a écrit :
I agree with Joël. I see your points, but this is not a matter of
"best possible code", but of "decent manners".
Hmm... manners are such a cultural thing, sometimes it's hard not to
offend others...
In a culturally neutral way, I too suggest that
Dear community,
I'm glad to see the new projects take shape and start moving. I'd like
to make 2 more suggestions:
First, I'd love the projects to make their announcements through
Launchpad (https://launchpad.net//+announce). That
integrates into the news feed of "OpenERP Project Group" whic
Dear Gilles Major and community,
We won't be able to come to the sprint, but here are two topics where we
have been asked to write tests and have not yet succeeded.
First, testing the correctness of the stock report would allow us to
optimize the SQL code with confidence. This is blocking our
Le 03/08/2012 15:35, Fabien Pinckaers a écrit :
the fastest to develop, easier to package and distribute is to do a web client
module.
starting from v7.0, the wen client api should not change too much.
you can use the pos as an example, or the point of delivery that has been
announced recently
Maybe with product variants?
Lionel.
___
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
I definitely encourage the creation of active experts group and
coordinated community developments.
Numérigraphe can't really get actively involved for the moment (there's
still plenty of things to fix/improve in the main addons for our needs),
but we will encourage and contribute to the extend
Le 08/05/2012 09:21, Amin Oruji a écrit :
I have problem with one2many fields in wizards
when I want to save a wizard with one2many field I have Error
I can't put many2one field for it in other class because this work is
forbidden
can anybody help for this problem?
What version of OpenERP?
Fro
Le 20/03/2012 15:11, Alexandre Fayolle a écrit :
Hello,
I have accidentally pushed an openerp-doc changeset to
lp:openerp-doc/6.1
(http://bazaar.launchpad.net/~openerp-community/openobject-doc/6.1/revision/1722).
Sorry if this is not the expected process. However, I would gladly read
any documen
the technical side and
maybe present it as a workshop.
Looking forward to your feedback
Thanks, Nicoleta
On 02/21/2012 02:43 PM, "Lionel Sausin, de la part de l'équipe
informatique Numérigraphe" wrote:
D
Le 22/02/2012 16:12, Raphael Valyi a écrit :
(...)
the money and effort is already spent doing something sub-optimal.
That's more or less off-topic, but I'll add that's not only OpenERP SA's
money. Partners and a few independent users like Numérigraphe also spend
money on real R&D (ad hock solu
Dear Nicoleta,
Thanks for your reply.
15 minutes is fine for a demo, but too short for a constructive
discussion. For example we've spent the last 10 days analyzing the issue
of partial deliveries, so I don't expect decision to be made in less
than an hour.
I'm surprised nobody else proposed
Dear OpenERP community,
We are currently very frustrated with the way OpenERP implements partial
deliveries (in, internal and out).
We're committed to provide an alternative procedure with a simpler, more
consistent interface and cleaner code, and propose it for merging into
the trunk.
Our f
Dear Nicoleta Gherlea,
Will there be work sessions where members of the community and the
core team could discuss complex functional issues? I don't see any
on the agenda.
There have improvements proposed by the community that need to be
discussed extensivly, and the
Le 16/02/2012 15:22, Simone Orsi a écrit :
(...) you just update other packages dep according to the new name of
the package.
Won't that be a problem in itself? We have not communication channels
and no central authority, so how will I even know when a name changes?
Or do we make transitional p
So, we can use "openerp.*" for core packages (like "openerp.res") and
"openerpcommunity.*" for community addons.
That's not so good, because the name changes when a community module
gets "adopted" by the core team (localization modules for example).
Lionel Sausin.
_
I agree that apps site needs to improve.
I also think the extra-addons still have a reason to exist for modules
that can be interesting to every user, but can not be accepted in the
main addons.
On the other hand, it really really needs a cleanup, because everyone
has been dumping their module
Dear Olivier,
When v6.0 was released, the core team marked lots of bugs "invalid" or
"won't fix" because they didn't intend to address them in v6.0, so that
they don't "get in the way" before the release.
I understand the need for a clean view of what bugs are blocking a release.
But the way i
Le 17/10/2011 14:24, Viktor Nagy a écrit :
> I know these two solutions, but I would like to inherit base_calendar
> using normal python class inheritance.
In v6 that's not how it works. I read there is work in progress in the
trunk towards this goal but for now this unreleased.
Do you need somethi
Hi,
You have to reference it in your module's __openerp__.py, in the
"depends" section.
I think you should not import it, rather call the pooler's get() method.
Lionel Sausin
Le 17/10/2011 13:43, Viktor Nagy a écrit :
> hi,
>
> in my server config file I've specified the addons_path as a list
>
>
64 matches
Mail list logo
