officelifehq / officelife Goto Github PK

Hopefully one day Covid will be over and people will come back to offices.

In this case, we should be able to indicate on an employee's profile page, where we can find the employee in the company (for instance, Office 17b, 3rd floor).

We should be able to login using brand login

• LDAP
• SAML
• Active Directory

For employees with an external status.

Dependabot creates a lot of noise in the commit logs.

Could we, instead, schedule a github action that would do a composer update and yarn every week, and commit this with a simple commit message, instead of 12 commits? @asbiin what do you think?

TypeError: route.apply(...).url is not a function

We should add the ability to add photos to a hardware.

Companies all around the world have different regulations regarding data, based on where they are located.

Rules in Canada are different than those in France, China or US.

We need to have some kind of processes to allow customers to create instances in

• US
• Canada
• France.

We'll add new markets as we go.

To make it happen, I propose the following:

• when we click on the Signup button on the marketing site, we should show a page asking for which country we'd like to be located in,
• then, when we click on a country, we are redirected on the actual app hosted in the right country, like ca.officelife.io.

We already support the management of hardware. We should also allow the management of licenses.

The scope of the v1 for this:

• ability to add a software with a number of seats,
• info of the project
  • indicate the renewal date of the contract
  • indicate the price of a seat
• ability to assign a license to someone.
• ability to see who has which license.

Employees can be assigned a position (Front end dev).

We should be able to search a position in the Universel search bar in the header. When cliking on a position, we will display the list of employees matching this position.

Linked to #672

Sometimes, employees have names that are not common. We should let employees upload an audio file that let them record how we should pronounce their name.

Reactions are emojis, like thumbs up, love,...

Right now, we can assign new positions to employees. But when we change position, we don't keep the position history of an employee.

We should be able to know past positions of the employee within the app, as well as the exact dates for each position.

Today we support avatars on the employee profile page.

It would be great and fun to use a video instead, so employees can click on it and see the video of the employee.

Uploadcare (what we use to manage uploads) can re-encode the video for us if needed.

Office supplies are necessary for the company operation. Pens, papers, etc...

We should have an easy way to manage office supplies, and especially stock of office supplies.

A contest lets a company (or a team) offer a prize to their employees.

Employees can indicate whether they want to be part of the contest.

A contest has an expiration date - after this date, employees can't enroll in the contest.

After the contest ends, a winner is randomly chosen.

We should be able to browse a list of employees per position.

The idea: everyone should be able to see all the positions that exist in the company. Then, for each position, we should be able to see the list of employees with this position.

We should allow employees to book time off. This is what we call PTO - or Paid Time Off in the official HR world.

Each company has

• a base number of allowed holidays per employee
• a base number of allowed sick days per year (it can be unlimited)
• a base number of extra off days per year

Each company also has a company calendar which indicates the days considered off for everyone.

There are many places in the app where people can post stuff. Employees should be able to add comments to them.

The first feature that should have comments, are project messages.

Employees should be able to indicate important life events, like a birth, or a death in their family, so everyone knows (ability to let the team know, or the entire company).

We should support the entire Recruiting domain. It's about managing job applications, managing potential candidates, etc...

First responders are employees who have the ability to provide basic medical help when something bad happens, while we wait for true medical professionals to arrive.

We should add the ability to indicate who is first responder on an employee profile, and find this information quickly when we are inside the application.

As of now, we don’t manage timezones in the application.

All dates are stored in UTC and displayed as such for all users.

We should change that:

• dates should ALWAYS be stored as UTC, as it’s the case
• users should have a default timezone (set in the instance), but should be able to change it for themselves
• we should have some kind of helpers that convert dates to the right timezone
• this conversion should be done in the ViewHelpers, not in the Vue file. The Vue file shouldn't have to do any conversion of some sort, ever.

A company might have several offices all around the world. For instance, in Paris, Montreal, New-York.

Each office has a set of teams, and therefore employees.

This is the hierarchy of the different levels in OfficeLife:

• company
• office
• teams
• employees

What to do

We should start by the very minimum set of information:

• name of office
• address

An office can have one or more teams.

That's it. We'll add the rest later.

@asbiin the BallPulseLoader doesn't display the three dots anymore. I think this is due to the changes we've made.

Notion lets us sign in with a code.

Basically, there are no passwords, and once you enter your email address, if it exists, you receive a link by email that redirects the user to their logged account.

Polls allow anyone in the company to take the pulse of the company or a specific team.

A poll is

• a title,
• a list of potential answers
• a deadline.

Then, we should have polls report, available for everyone to see. Answers should be anonymous.

We should be able to upload documents on the Employee profile page. This will be useful for onboarding.

Hi @djaiss great project, thanks for your awesome work. trying to give it a try but i got some issues, any idea or i can fix that errors?

ERROR in ./resources/js/app.js
Module not found: Error: Can't resolve '../../public/js/langs/en.json' in '/Users/dukens/Code/officelife/resources/js'

GET https://officelife.test/nprogress/nprogress.css net::ERR_ABORTED 404 (Not Found)

Thanks 🙏

https://github.com/meilisearch/MeiliSearch

https://pociot.dev/35-blazing-fast-search-with-meilisearch-and-laravel-forge

We should log, with a tool like https://www.papertrail.com/, what's happening with our logs.

We should be able to see all employees in a map.

Technically, we should absolutely use the getPartialAddress() of the Place object to make sure no one can see the exact location of employees for privacy issues.

We need to support 2FA.
2FA should be enabled at the user level.

• In an ideal world, there would be a settings in the Adminland (ie reserved for administrators) that would let them require the 2FA for every users in the account.
• Also, we should list on the user list (in Adminland), who has 2FA activated, and who has not, as shown below.

• Blank state for address block on employee profile

A department is composed of teams.

The complete hierarchy would be

Company > Office > Department > Team > Employee.

An employee should be able to select up to 5 team members to ask them for feedback about him/her.

• This process can be triggered anytime.
• For the first iteration, we should only have one question: do you like working with me and what is your opinion about me
• The answers should be anonymous
• Once every member has replied, the poll closes but it will never auto-close itself.
• We should have a section on the employee performance tab, in his profile page, where we list all the previous polls.

Every new employee (added or imported) need to answer

• a set of questions when they arrive,
• upload some documents to comply with the company (NDA, etc...)

HR should be able to add a standard questionnaire that every employee should fill.

This should appear on their dashboard, and employees should be able to see a completion rate.

Everyone in the company should be able to know the ratio of gender, per position.

On our marketing site, we will have a link to a demo account, something like demo.officelife.io.

The demo account has always the latest release of the app.

This account should be automatically populated with fake data provided by the SetupDummyAccount command, so potential customers and users see the potential of the application.

• Demo data should be reset every 5 minutes (so data always look accurate, and people won’t put too much crap in it)
• Demo should be accessible with the [email protected] account

Because the SetupDummyAccount takes a lot of time to run, we should have a SQL dump of the data this script generates, and use this dump to populate the database.

Because this account will be a "special" account, we should have some limitations in it:

• we shoudn't authorize uploading files
• we should not send email at all
• no payment info should be indicated in the app at all.
• we should have a special banner at the top of the account saying "it’s a demo account".

To do this, we should have a new variable in .env that lets us control this.

Pouvoir connaitre les competences des gens: qu’un employé declare savoir être expert dans “les machines Siemens” ou “le pricing d’une cuisine” (savoir qui connait quoi)

https://vue.ant.design/components/date-picker/

The SetupDummyAccount command takes a lot of time. I strongly believe that we should keep testing it to make sure it works, as it will be used by all the developers that want dummy data in their accounts to test and try the product.

Also, we need it ourselves to populate our default test account that we will provide at launch.

However, it’s not efficient to run it alongisde all the other tests.

I propose the following strategy:

• in phpunit.xml, remove the ./tests/Integration from running.
• create another phpunit.xml that will run only the ./tests/Integration files and use it in a separate build.yml file

That will allow us to run it in parallel of all the other tests, so that would help.

What do you think @asbiin ?

Teams always have some kind of recurring events (like monthly meetup, or daily scrum, etc...).
We should be able to indicate what those activities are, and display them on a calendar.

OKR (Objectives and Key Results) are a fancy way of managing goals of employees each year. It was initially used by Google, and now many companies are using it.

We should support this methodology.

• Hiring date on employee page
• Edit of hire date on employee profile
• Hiring date anniversaries on team page
• Hiring date anniversaries on company page
• Hiring date when adding an employee
• New candidates coming this week in team
• New candidates coming this week in company
• Statistics to know how many employees have been hired after you

We shoud support the electronic signature of documents (especially during the onboarding process). Potential candidate for this: https://eversign.com/.

In this tab, employees can see pay days, days considered off, holidays. Managers/HR can add events and important dates.

In real life, hardware/software needs of developers is different from the needs of accountants.

We should be able to create profiles that are team specific (and/or position specific), so when we add a new employee to the company, we can assign a profile to him/her.

That way, we can assign the right hardware and softwares to the employee.