Buenas Tardes desde Allemania,

muy bien escuchar kastilliano aka;)

I'm interested in this module and will give it a try soon. I wrote a
little extension to the project-module, which associates projects to
sales and some other presale activities. The employee checks in
time.lines to the project - so its interesting to extend the employee
with informations of his weekly worktime to validate this in
project_plan. so cedk comment is reasonable: your modul should extend
the employee. if I know the salary of a employee, i can calculate the
costs of a project or something else.

Mal ingles;)
Jan



Am 18.01.2011 22:28, schrieb Cédric Krier:
On 18/01/11 04:42 -0800, oscar_andres_col wrote:
Hi, Developers

I want to present you a new external tryton module Staff, :
     - Define employees (name, salary, category, ...), sales
performance (for to pay commissions), It don't integrate with sales or
account module yet.

TODO:
         -  To create shifts register (in/out employees of the company)
for payroll
         -  To generate automatic settlement of shifts for timework
and  time extra work
         -  To generate Paper Pay Document of salary including bonus
and discountsaccording to payroll action notice
         - To create Curriculum of each employee that notice payroll
action report (for example vacations, licences, absenteeism,
permissions)
        - To connect to Account and Sales Module
       -  To generate Chart Reports

Payroll action notice: It is a periodical report about different
administrative situations that affects payroll liquidation and
payment.

Download here: http://mercurial.intuxication.org/hg/tryton_staff/
Just some remarks:

- why don't you reuse the company.employee model?
- I think you should split the module in many sub-modules with simplier
   concept like:

     - sale_performance
     - payroll
     - sale_commission
     etc.

- You should not put trytond_staff.egg-info in the repository (it generated on
   the fly by setup.py)

Otherwise the guide lines seem to be well respected ;-)

PS: You should fix the COPYRIGHT file (I did not do any dev on this module :-)

Waiting for next...

--
[email protected] mailing list

Reply via email to