Skip to content

[IMP] Employees: Update new employees #13050

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: 18.0
Choose a base branch
from

Conversation

larm-odoo
Copy link
Contributor

Updating to new standards, and new fields. Lots of small changes to the UI requiring a new format to the sections and doc.

@larm-odoo larm-odoo self-assigned this Apr 24, 2025
@robodoo
Copy link
Collaborator

robodoo commented Apr 24, 2025

Pull request status dashboard

@larm-odoo larm-odoo added the 3 label Apr 24, 2025
@larm-odoo larm-odoo requested a review from slinkous April 24, 2025 19:54
@C3POdoo C3POdoo requested a review from a team April 24, 2025 19:55
@larm-odoo larm-odoo force-pushed the 18.0-employees-new-employee-larm branch from 018c92e to d0d629a Compare April 24, 2025 20:31
@larm-odoo
Copy link
Contributor Author

Hi @slinkous - this is ready for a peer review!

Copy link
Contributor

@slinkous slinkous left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Holy cow that is a beast of a doc! I feel like I should have an "HR Professional" certification added to my resume tab just for having read it!

All this info looks crucial. I flagged a few places that were confusing for me as a newcomer to the topic, which may or may not be useful to you.

One thing to flag is that you have a lot of content in the format of:

- :guilabel: Field: do these instructions with this field

And technically, imperative form sentences are complete sentences, so those should all start with a capital letter and end with a period according to our style guide. I see inconsistency in our docs about what we do after a colon in a list, so I think it's worth discussing.

@larm-odoo larm-odoo force-pushed the 18.0-employees-new-employee-larm branch from d0d629a to b363cc5 Compare April 24, 2025 23:10
@larm-odoo
Copy link
Contributor Author

Thank you for the super thorough review, @slinkous! My docs ALL used to be huge beasts! I made ONE doc for each app, then decided to chop them up and migrate them to their own docs. I used to make the craziest, longest docs =D

@larm-odoo larm-odoo requested a review from a team April 24, 2025 23:12
@larm-odoo
Copy link
Contributor Author

Hi @Felicious - this is ready for a final review!

@larm-odoo larm-odoo added 5 and removed 3 labels Apr 25, 2025
Copy link
Contributor

@Felicious Felicious left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for all the hard work you put into updating this massive doc, @larm-odoo! 😊

We usually base points on the percentage of the doc that's been redone (this one was around 60%), but given the volume of lines changed and the improved structure and organization throughout, this deserves to be bumped up to a 5-point doc 💪 Great job!

@larm-odoo larm-odoo force-pushed the 18.0-employees-new-employee-larm branch from b363cc5 to f617dd8 Compare April 25, 2025 20:41
@larm-odoo larm-odoo requested a review from a team April 25, 2025 20:41
@larm-odoo
Copy link
Contributor Author

Hi @samueljlieber - this is ready for a tech review!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants