thorin-schiffer/freeturn

Freelance mission control

freeturn's Issues

Acceptance tests need their own env

Acceptance tests have very specific and heavy dependencies, which makes building the python env slow and also interferes with unit tests from the project.

Acceptance tests should get their own pipfile and python env, freeturn deps will be placed in the source code directory [#30] and they both result from the splitting the current pipfile.

Improve message inspection

Currently the project listing

And inspection

look quite basic and don't represent the conversation flow.
The messages will be organized corresponding to their threads structure and also link to the thread's Gmail page.

The inspect page would show the previous conversation history, showing the folding grade, subjects and timestamps. The messages would look similar to the timeline from #27 or #28 and also may include the project events this message is related to.

Project timeline

The project inspect page will become a full log of actions happened to it.

This is particularly useful when maintaining a long term leads with corporate clients.
Probably logging events in the CRM is a bigger thing, so this one would require a generalistic and convenient way of logging.

The log entries will be marked with icons and form a timeline in a visually appealing way.

Python social auth is a deprecated dep

Describe the bug

Deprecation notice - 2016-12-03
As for Dec 03 2016, this library is now deprecated, the codebase was split and migrated into the python-social-auth organization, where a more organized development process is expected to take place.

Details about moving towards the new setup is documented in the migrating to social document.

Expected behavior
Using https://github.com/omab/python-social-auth/blob/master/MIGRATING_TO_SOCIAL.md migrate to the social

Portfolio project technologies block is missing

If the project page has no logo.

• The block must be visible
• Technologies must be listed
• The default logo must be used

CV skills layout optimization

The front page of the CV+portfolio can max only have three recent project links because the skills are taking up significant space. The content is flipping to the next page, but it can be a significant conversion obstacle if the whole CV is not fitting into one page.

The "skills" block will be moved to the right panel, utilizing the remaining space and freeing space up for more recent projects to link.

Custom dashboard

Using the data from the log entries (see #27), the default wagtail dashboard will be extended and represent the overall activity in the project, including the page edits, which are now available on the dashboard.

Project.name must be neither blankable nor nullable

For some mysterious reason, project.name can be left empty, which is definitely not assumed in project name generation

    def save(self, *args, **kwargs):
        if not self.daily_rate and self.company:
            self.daily_rate = self.company.default_daily_rate
        if not self.name:
            self.name = str(self.company)
        super().save(*args, **kwargs)

This must be fixed and project.name must become neither nullable nor blankable.

Add project description to CV edition page

In the CV editing/creation page

while picking the projects and technologies and to highlight in the cv, it would be very useful to see the project description from the corresponding project. This would help to validate the automatic picking and polish the selection.

Project state machine needs simplication

The current project state machine is too big and messy.
The number of states must be reduced.
Archived and dropped projects must have an option of unarchiving and undropping.
The new state machine will be thoroughly explained and described in the documentation, including the transitions, describing in detail when and where those transitions will be happening.

Project leads expiration

After a certain time, the inactivity on the project means it's not gonna happen.
The projects will expire after the certain number of days of inactivity, leading to their archiving.

WIll be done after #33, and archived will be a new state.

The listing page will get a new button leading to the full list of projects:

Portfolio projects highlighting

Currently, the project in the project portfolio don't correspond the highlighted project in the front page,
which can be quite misleading.

The highlighted projects will be following first.
Besides that and optional: figure out how to inner document link the projects from the front page aka CV to the project pages in the portfolio.

Move source code to a separate directory

Currently, the source code is placed on the same level as the rest of the files. This can be a big impediment in splitting the things from each other and also makes the root of to be looking quite messy.

There is future plan of splitting the acceptance tests deps from the rest of the repo, as they are completely different and quite heavy, this is the first step in that direction.

While splitting check if the following functionality is not broken:

• docker support, docker image is building and running
• unit tests are running
• acceptance tests are running
• circle ci pipelines are working
• heroku Procfile is correct
• invoke routines are working correctly (check inv bootstrap for example)