luksan47 / mars Goto Github PK

Implement a printing module.
Users should have printing account, representing the amount of money they have.
There should be an option to print, to remove and add money to the account (by exact amount and by difference) and also a getter.

Frontend and functionality on the server is another issue, should be migrated easily from Urán 1.1.

The users can have free pages for a limited time (add deadline). Add backend and frontend functionality.
Relies on issue #4.

Currently the printing module expects valid data. Add a validator function (see Laravel docs) and handle the other possible edge cases.

Add a printing, an internet and an admin tab. Only the admin tab should be drop-down, with the "accept regiszrations", and "user handlig" tab.

Can be migrated from Urán 1.1.

Follow the same logic with modify_free_pages.
Also, we should agree in the naming convention. For PHP, it's as we use it, but for Laravel, it's camelCase.

Give students the possibility to book a 1-hour slot in a calendar when they wish to wash.

For easier setup and dependency management it would be valuable to use some Docker functionalities.

Goal: after cloning this repository the developer could get the mars site working on his/her local machine using only one command, like docker-compose up -d.

Add documentation: write a developer guide.

Might useful:

• docker compose
• blog
• youtube video
• github example

Currently should only include username, password and email address.

Change the default coding style from

fun
{
}

like braces to

fun {
}

We need a dummy collegist without any permissions to have a non-admin test user.

Issue #19 left a TODO, which is blocked by #27 .
Create a readonly page when the blocker is solved.

The users should be able to store their MAC addresses (max 1 by default, but can be extendable). Also should have a property how long are they allowed to use the internet.

Add an easy to use script that migrates the Student Committee's Google Calender to the users'.

Add a page for requesting MAC slot number extension. The request should come with a MAC address and a reason.

Would be a nice feature to generate automatically the documents required by house rule and other things.

From the Laravel documentation:

The @lang directive does not escape any output. You are fully responsible for escaping your own output when using this directive.

We should move to the newer __ helper function.

It is not too user-friendly to select users by id like here:

Make a reusable user selector with search functionality. (No ajax needed, the full list can be in the output.) Something like bootstrap-select live-search.

Use Laravel's Localization.

User, filename, datetime, cost, status.

There should be a language selector with english/hungarian flags somewhere, setting the language of the page.

There are some issues with the current homestead setup, please fix it.

Can be migrated from Urán 1.1.

Add documentation how to set up the environment to help other contributors. Preferably for different platforms (Linux, OS X, Windows).
Also describe how to write pull requests, and use branches, etc.

Laravel's seeding can be used.

There should be an option (with a fix link, link generation, or something clever, not sure) to get a link which through the users should be accepted automatically.

Change the links and the words at the main page.
Please keep it funny.

Implement a function which modifies a users's free page settings in the PrintController class.

Should only be done at the release. Urán 1.1 solution can be migrated.

Add documentation and example config for the homestead development environment and PHPStrom IDE

Should be added to resources/lang/hu, based on the english one.

Create a page where we can store and admins can edit which room the students live.
Let's discuss

• how to show the data?
• how (long) shall we store it?
• how should we load the data?

Change Radius passwords to the hashed Urán passwords.

We have to think about what permissions do we need.
If an admin/non-admin is enough first, then it can be easily added with simple gates.
If we need more complex (like for the secretariat/committee later), we might have to think about migrating some already written module, e.g. https://github.com/spatie/laravel-permission

Only what's important.

Hi,
we are developing our dormitory's information system, which for now will include printing, user management and internet handling.
Our issues might not be too well-defined because of our background knowledge, but if you are interested in something, just comment under the issue and ask for clarification (if needed).
One important notice: we require quality code.
Thanks for the help,
Norbert

Migrate the template from the Urán 1.1.
Note that the LayoutData structure used there must be avoided.

It should be possible to send emails (to confirm registration, send important notifications, password change requests, etc.). For that, we need to come up with some solution. See config.mail.

A (currently optional) page where users can fill out personal information (like in Uran 1.1), for later use. Should not be a requirement at registration.

Workaround until Issue #15 is fixed.
Add an option to set a 8-character long Radius server username and password with alphanumeric characters only.

Create an issue when done or migrate it to the server.

Only the years between 2005-2018 can be chosen.

Add a page where users can view the students' committe's recordings. (Uploading should be only done by admins, for now.)
Can be migrated from Urán 1.1.

Only basic functionality, can be migrated from Urán 1.1.

Configure and add Laravel's logging services.

Tenants should be able to print and have access to the internet module.
We should not require information about their studies at the registration.

There might be some scenarios where it would be comfortable for the users that we use cookies there (e.g. login). We should analyse the possibilities and add it where it makes sense.

Registration should only be complete when an admin accepts it. Add backend and frontend functionality.

Add option for accepting and rejecting MAC slot requests for admins.

Migrate the template from the Urán 1.1.
Note that the LayoutData structure used there must be avoided.

There should be a page where admins can view and edit users.
DO NOT Migrate the template from the Urán 1.1. Come up with a more comfortable UI.