Development

https://img.shields.io/github/issues/fsi-tue/fachschaftsempfaenger.svg https://img.shields.io/github/issues-pr/fsi-tue/fachschaftsempfaenger.svg

Getting Involved

The fachschaftsempfaenger project welcomes help in the following ways:

Adapt it to your own needs

The following workflow also works fine if you are interested in creating your own infoscreen. Except submitting Pull Requests to our own repository, simply reimplement the submodules and views to your own needs.

Workflow

  1. Fork this repository on Github. From here on we assume you successfully forked this repository to https://github.com/yourname/fachschaftsempfaenger.git

  2. Install fachschaftsempfaenger locally in development mode

git clone https://github.com/yourname/fachschaftsempfaenger.git
cd fachschaftsempfaenger
python setup.py develop --user
  1. Create a django project structure on your machine with

django-admin startproject yourproject
  1. Add fachschaftsempfaenger to your INSTALLED_APPS in yourproject/mysite/settings.py:

INSTALLED_APPS = [
    ...,
    'fachschaftsempfaenger'
]
  1. Add code, tests or documentation.

Note

If you are from another student union we recommend to reimplement all submodules to your own needs.

  1. Add and commit your changes.

    git add -u
    git commit -m 'fixes #42 by posing the question in the right way'
    

    You can reference relevant issues in commit messages (like #42) to make GitHub link issues and commits together, and with phrase like “fixes #42” you can even close relevant issues automatically.

  2. Push your local changes to your fork:

git push git@github.com:yourname/fachschaftsempfaenger.git
  1. If the changes you made are relevant for our project, feel free to submit a Pull Request at https://github.com/yourname/fachschaftsempfaenger/pulls and click “New pull request” to submit your Pull Request to https://github.com/fsi-tue/fachschaftsempfaenger.

Building documentation

The projects documentation is stored in the doc/ folder and is created with sphinx. You can rebuild the documentation by executing

make html

in the documentation folder.