BadgeYAY

badgeyay is a simple badge generator with a simple web UI to add data and generate printable badges in a zip.

The user should be able to:

• Choose size of badges
• Choose background of badges and upload logo and background image
• Upload a CSV file or manually enter CSV data as: name, type of attendee, nick/handle, organization/project

Deploy

One-click Docker, Heroku, Scalingo and Bluemix deployment is also available:

Checkout badgeyay in action:

Our current goal is to provide an interface to generate badges for the FOSSASIA conference.

If you like to join developing,

• you can chat on gitter, mentioning the maintainers.
• you can find/create issues and solve them.
  • When you solve an issue, you do not own it. Share your progress via a Pull-Requst as soon as possible.
  • Discuss with others who work on the issue about the best solution. It is your responsibility, not the maintainer's to choose the best solution.
• If in doubt, let's follow CCCC.

Specification

Technologies Used

Badgeyay uses a number of open source projects:

• Flask - Microframework powered by python
• Bootstrap - Responsive frontend framework
• Shell - Script used for merging badges of different types
• Heroku - Webapp deployed here
• Travis - Continuous Integration of the project
• Github Release - Releases are GitHub's way of packaging and providing software to the users

Testing Methodology Used

• Python Unit tests - for assertion, with the help of Selenium for web browser automation.

The guidelines for setting up and running the tests are mentioned in the testing docs.

Input

• The input is a set of csv files in the same folder, UTF-8.

• The csv file is named after the badge type to take. Example: vip.png.csv uses the picture vip.png.

• The CSV has up to 5 columns for the name and the twitter handle. They will be filled if this number is filled:

  • ___X_

  • ___XX

  • __XXX

  • _XXXX

  • XXXXX

  • badge_wrap: It can be true or false. If set to true then for each entry in the csv file two badges will be generated so that they can be wrapped around the badge card.

  • paper_size_format: As of now it's value can be either "A3" or "A4". The value will decide the size of the page on which the badges (in groups of 8) will be printed. Not required if width and height of parameters are explicitly mentioned.

  • width: Width of the page on which badges (in groups of 8) will be printed. Value should be in mm. For example: "297mm"

  • height: Height of the page on which badges (in groups of 8) will be printed. Value should be in mm. For example: "420mm".

• A set of sample csv files can be found here.

Output

The output file is svg / pdf / multipage pdf of size A3. Each badge has the size A6. The outputs are in a folder derived from the input csv. The outputs can be either of the two types, viz ZIPs or PDFs, or both. User has the choice to choose from either of the two or from both of them.

Customization

You can change the font style, font size, color etc from the .svg file in the folder badges. Inkscape is generally used for editing of such files.

Usage

You need Ubuntu to run the application. We are working on integrating vagrant to make it easier to run on windows. Check out the User Input Guide for more details.

Install Dependencies

Badgeyay requires the following dependencies to be installed

• python3

For Ubuntu/Debian based Package Managers

sudo apt-get update
sudo apt-get install python3

For Fedora/CentOS/RPM based package managers

sudo -i
yum install python3
exit

For Arch based package managers:

sudo pacman -S python-cairosvg
sudo pacman -S python-lxml

Installation

Badgeyay can be easily deployed on a variety of platforms. Currently it can be deployed in following ways.

1. Local Installation using Virtual environment

2. Local Installation using Vagrant environment

3. Deployment on Heroku

4. Deployment with Docker

Contributions, Bug Reports, Feature Requests

This is an Open Source project and we would be happy to see contributors who report bugs and file feature requests by submitting pull requests as well. Please report issues in the GitHub tracker.

Issue and Branch Policy

Before making a pull request, please file an issue. So, other developers have the chance to give feedback or discuss details. Match every pull request with an issue please and add the issue number in description e.g. like "Fixes #123".

We have the following branches

• development
  All development goes on in this branch. If you're making a contribution, you are supposed to make a pull request to development. PRs to master must pass a build check and a unit-test check on Travis.
• master
  This contains shipped code. After significant features/bugfixes are accumulated on development, we make a version update, and make a release.

Also read CONTRIBUTING.md

CLI

Badgeyay project can also be used as a cli application, and can also be imported as a library.

Installation Steps

cd cli\
python setup.py install

When you execute pip freeze you will see badgeyay is installed as a library into your virtualenv.

Verify

badgeyay --help

This will show the information about the parameters to be supplied to the CLI application.

Implementation

generate_badges.py creates svg files from the csv, png and badges/8BadgesOnA3.svg.

merge_badges.py converts them into pdf files and merges them together into one.

Travis creates new releases with the all-badges.pdf file.

License

Badgeyay - A simple badge generator. Its main purpose is to generate badges for events/conferences under the Open Event project of FOSSASIA. The Open Event project aims to make server and client software required for hosting events/conferences easy to build and configure. Copyright (C) 2016, FOSSASIA. This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.

Maintainers

You can reach the maintainers and ping them personally by looking at the Badgeyay team.

You can become a maintainer by following the project and contributing code to it. Please see your role in the CCCC.

The project is maintained by the Badgeyay maintainer's team. To join the team:

1. Contribute
2. You or someone else proposes you in an issue to become a member of the team.
3. A Badgeyay admin adds you.

To stay a maintainer in the team:

1. Follow the rules of CCCC or Badgeyay and do not violate them willingly or in a harmful way.

To be removed from the team:

1. Someone creates an issue to ask for removal, e.g. because of inactivity or a violation.
2. An admin removes you.