codeforpoznan / codeforpoznan.pl_v3 Goto Github PK

Multi-select dropdown widget with save button (disable Enter key on save button).

Dashboard for administrative panel is thought to be the equivalent of homepage for the website. Basically the task is to create the path in router and render empty component that will hold all the other components in the future.

General description

We decided to add a team class, which could inform us which person belongs to which team. This information might be useful to get the colleagues from the project better as well as managing that team (e.g. rendering the latest attendance for the members of the team). This epic will contain any task that have anything to do with this.

We should have some script which allow us to add data (some user, participant, and hacknight) to db in simple way

Integration with the github community.

Attendance list shall consist of: ???

Original description

Right now, when 2 developers makes some schema changes on their branches, and alembic creates 2 revisions for them, merging those branches to master causes conflict. During building backend alembic throws error: "Multiple head revisions are present for given argument 'head'; please specify a specific target revision"
Alembic docks about working with branches:
https://alembic.sqlalchemy.org/en/latest/branches.html

It would be convenient to define our styles in separate files and use SCSS instead of CSS. For example - we could store colors as variables in .scss file.

Delete access token and refresh token in proper sequence so that backend won't render error

@stanislawK discovered that there are some problems with writing tests that are related to the organization of files in backend folder - apparently there is some issue with "circular imports". We need to solve this in order to be able to write tests that work.

Until now there were two voices on the matter:

• Staszek suggested we might have to reorganize the structure of files
• Jacek suggested that we need "factory" - he might have been thinking about this?

Add login component with actions in vuex, and autologin

Create Many-To-Many db relationship between Participant and Hacknight models

We should set up test configuration and write tests for ours models and db

In the future this functionality will allow the user to view lists from previous hacknights

Description
Recently, Magul mentioned that in the future (once PAH is up and working) we should figure out some framework on how to collect ideas and choose the projects we will pursue as a community.

Maybe there could be some kind of form on the website where interested organization could submit ideas along with the information on e.g. how it will improve their operations or local community, what are the resources available, how much time they can commit to work on it et cetera.

These, once saved in DB, then could be accessed from admin panel behind the login. This way we could gather the stack of potential projects and cooperations and (having them all in one place) it could facilitate making a choice on what to do next more collectively and transpraently.

Potential developments
Creating that functionality would require to introduce the new class of objects that is "project". By adding the property to it like status: {pending, in progress, currently developed, maintained, archived} we could serve "Our projects" section on the website, using objects from database instead of hardcoding them as it worked so far.

Up for discussion
Of course we have to make a lot of things before but I just wanted to pick your brains on that, collect some thoughts and trigger imagination so that we all can be sure that admin panel can be more than just a list of attendance :D

We need something that will serve the request to get list of participants for the attendance list

Similar to the old version.

General description

We should be able to search participants by any kind of data to find other details when needed.

Technical description

Ideally, a user should be able to type any kind of data (name, surname, github, slack) in the same field and get the probable result. Given that this function is relevant both for editing details in participants component and displaying details in #103 we could extract it in the separate re-usable component.

Resources

We could use the combobox solution like this but without multiple objects as developed

To-do list

• Extract search function in separate component
• Use it in participants component (create/edit form has it at the top) and replace v-select to unify the use
• Make note to use the same solution in #103

We use built-in Flask-CLI instead of Flask-Script in our project, so Flask-Script should be removed from requirements

Form should contain fields:

• first name
• last name
• email
• phone
• github account

Make readme prettier.

With email server settings and fake email delivery for development and debugging purposes.

General description
Import the existing data from attendence list in Google sheets to the new database so we can continue the list we have started by hand.

Technical description

1. The script, converting xls table is probably needed.
2. Please ensure the migration goes through.

Route /api/hacknights/<id>/

Returns:

• id
• date
• participants (as list)

Suggested package: Flask-JWT

General description
This epic contains all the tasks related to managing participant as the object that holds information about each of us that help our self-organize.

Technical description
Participant is the class of object that we use mainly for the hacknight attendance list.
It is needed in order to list people from whom we choose the ones that are present during particular hacknight.

1. We shall be able to: create, retrive, update, delete; to database.
2. Also we should be able to add and remove participants to hacknight.

docker
vue
database (postgres)
flask

With @magul 14.11.2018

@stanislawK

User

• name
• password

Participant

• first name
• last name
• github login
• email (optional)
• phone number (optional)

Hacknight

• date

Relation many to many between participant and hacknight

Technical notes

Create models in SQL Alchemy and use Alembic to create migrations. Migrations need to be applied in docker-entrypoint.sh.

General description
We need a possbility to edit details of the participant that has been already added to the database.

Technical description
We could probably override the logic of create participant form with condition that if a user already exists the component uses different endpoint to PUT data, rather than POST it.

Nevertheless the form should contain fields:

• first name
• last name
• email
• phone
• github account
• slack nick

General description
This ticket is connecting all the tasks needed to replace the current website with the similar one written in Vue.

We need visual mock up of the intended page.

General description
This epic contains all the tasks related to maintaining attendance list of participants during the hacknights. We collect this information in different practical purposes, yet we do not use it as much as we could. Therefore all the tasks aiming to build upon that will be held in this epic.