I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

Current behavior:

Expected behavior:

Steps to reproduce:

Right now if a user uploads a CSV - we are making SVGs, PDFs and ZIP - and then giving the user the option to download one. This will waste time for large number of badges.

Maybe ask the user before-hand what all formats they want the badges in,

Add travis and other code-checks to repo.

I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

Right now the website has crashed due to importerror of urllib module. What i have proposed is to avoid this issue in future i have created a virtual environment so that whenever someone uses a new module, they can pip freeze > requirements.txt it for dependency management.

@niccokunzmann @jajodiaraghav @gabru-md Please give your opinion

I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

Current behavior:
Entering anything generates badges

Expected behavior:
If we know the type of data to be entered,then we can validate it as per the needs

Steps to reproduce:

I'm submitting a ... (check one with "x")

• [x ] bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

Current behavior:
On uploading any sample data and clicking upload, the site displays 500 Internal Server Error.

Expected behavior:
Should create the required badges.

The following paper sizes should be supported:

• A3 (this is currently supported but A4 is more important)
• A4 - this is used in Germany
• ?? - this is used in Singapore

This issue requires some research about:

• where do the next conferences of fossasia take place, which paper format do they use
• what are the dimension of the badges used there? name cards, A6, ???

Please share your research here as it is much appreciated to direct the development flow.
You can implement paper-and badge-sizesfor the different use-cases.

The merge_badges.py file currently performs:

1. Converting SVG to PDF
2. Merging badges together in a single PDF

If it really necessary to perform these operations using shell? Can we convert the shell script to equivalent python script?

Ping @mariobehling @niccokunzmann

I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

While submitting a PR, now we don't have a way to review the PR.
Ways to review a PR, in increasing order of quality check

The person who made PR should give a Heroku deployment link to that branch to test the changes
or app.json file should make a temporary automatic deployment of that PR on pushing each and every commit every time.

I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

Current behavior:

Expected behavior:

@gabru-md has proven commitment by commits, see here I add him as a miantainer. If you have any concerns, please state them here.
Otehrwise, we can close this after some time and if somthing comes up, we can have a discussion.

@gabru-md please read the CCCC guide and the README file if you like to take on this responsibility.

I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

Current behavior:
merge_badges.py contains linux commands being executed from python code, this makes the app dependent on os.

Expected behavior:
Remove the linux commands and use corresponding python code

I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

Expected behavior:
Linting purposes for python.

Are you working on this issue?
Yes

I'm submitting a ... (check one with "x")

• feature request

Current behavior:

I would like to see an automated build of the web app running in a docker container. I have a server so I could host the web app.
There is something similar, #3 but docker is also an option.

Expected behavior:

Please

• Create a docker file which runs the web app
• deploy this file to a web server (I can do this)

I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

This is regarding optimizing the web app

The CSV has four fields:

• Name
• Type (e.g. Speaker)
• Handle or Nick
• Organization/Project

Check the installation steps on the docs folder and report any changes to be made .

Autodeploy project to Heroku on each new merged commit.

I'm submitting a ... (check one with "x")

• feature request

Current behavior:

Currently, we have a deployment to heroku.

Expected behavior:

To make it motivating for others to contribute, we can tell them how long it takes for their changes to become live.

• Document how the automatic deployment works, where to find the deployed version
• Document what to do to get your changes live
• Document, how long it takes after merge to see your changes inline.

Currently UI of App Generator is lacking Menu item in header and Version deployment info in footer.

Expected behaviour:
Add menu like Google/Susper on the top right corner (http://susper.com/)
Add Version deployment info to the bottom like http://staging.loklak.org

Refer: fossasia/open-event-wsgen#1465

I'm submitting a ... (check one with "x")

• bug report

Current behavior:

I do not know how to use to file.

Expected behavior:

I would like to read in the REAME file about the meaning of the file and the project guidelines which seem to be mainfested in the file.

Related code:

#32

I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

Current behavior:
The page is not responsive, gets distorted for smaller screen sizes.

Expected behavior:
The page should be responsive.

Steps to reproduce:

I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

Current behavior:

Expected behavior:

Steps to reproduce:

As an alternative to uploading a CSV file, the user should also be able to enter CSV data in a textarea field and generated badges.

I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

The best way to fix this is to make it a required field, so that one should be selected.

I'm submitting a ... (check one with "x")

• feature request

Current behavior:

As shown in #73, the app is currently deployed in production mode.

Expected behavior:

In order to understand errors in production and even report seldom errors, we could use a debug mode displaying the traceback.

Steps to reproduce:

See #73

What is the workflow of website,when i uploaded png and csv files it says badge is ready download as pdf but it shows download fail NO FILE.

However the uploaded files are downloaded in uploads folder but there is no badge so how are we returning user it's badge as pdf.

I'm submitting a ... (check one with "x")

• [x ] feature request
  Current behavior:
  Uploads folder contains code files and created badges folder, which should not happen .

Expected behavior:
Uploads should only contain uploaded files and code files should be present in app/

Context: I would like to add @meets2tarun to the people who have write access as he is a maintainer.
I would like to add @jajodiaraghav to the people with write access because he has proven to be productive for the project and can merge and review other people's work.

Problem: I do not know who to contact for this.

Two solutions exist:

1. pass admin permissions to me so I can do this.
2. find an other admin to do it, which is also required for 1.

Roadmap

1. Discuss on gitter
2. ping fossasia administrators
3. ping different teams, open-event team first, then others.

I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

Current behavior:

Expected behavior:

There should be guidelines for user as well for the requested format of json or csv that user uploads.
Steps to reproduce:

Creating a route -> /guidlines with proper documentation should do.

Presently duplicate badges are being generated, is this intentional? If not then I would like to fix this.

To follow the principles of contributing to FOSSAsia projects, templates for issues as well as pull requests need to be added

Are you working on this issue?
Yes

https://www.youtube.com/channel/UCQprMsG-raCIMlBudm20iLQ

Badgeyay doesn't have a demo video on Fossasia Youtube channel. Creating a demo and uploading in to the Fossasia channel would help us attract new contributors.

I would like to know what other people think about it :)

I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

A web app made up of flask deployed on Heroku which will trigger Travis with the required configuration to get required badges as a Github Release and provide it to the users.
@niccokunzmann

I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

Current behavior:

Expected behavior:

Steps to reproduce:

Right now to close the Menu (Dropbox?) one needs to click on the link again.
Clicking anywhere outside it, should close it.

Add option to upload a zip file containing the corresponding csv+png files, and return the badges to download

The images like this have the following properties:

1. They have a fix color
2. They have a marker like "EXHIBITOR" written on them.

I would like to have my own text on thie beautiful background but with my own color.

Possible Solution:

Create an SVG file without the exhibitor text.
The triangles all have one color e.g. #33ee66, so that I can replace the color with find and replace in this SVG file. To change the brightness, you can add a grey triange above them. You can make it totally black and just change the transparency value.
You can use Inkscape to create the file.

I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

Current behavior:

Raises a 500 error on /upload

^^
This is the error log.

Expected behavior:

should not throw an error.
/app/static/badges folder is missing and must be added.

Steps to reproduce:

create a folder named badges inside ../app/static.
or

import os
os.chdir('../app/static')
os.mkdir('badges')

this line would also do! :D

I would like to work on this.
Thanks

Allow downloading of badges in multiple formats:

• ZIP file containing all SVGs and PDFs
• SVG
• PDF of individual set

changes in error message due to small typo

Are you working on this issue?
Yes

Provide an option to choose from a set of default images (in /uploads folder) so that user can create badges without the need to upload images themselves. The user should be able to select one (multiple?) image from the set of images and upload a CSV to generate badges.

Current UI only accepts a CSV file and uses certain predefined images. We should allow users to upload an image themselves

I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

I'm submitting a ... (check one with "x")

• feature request

Current behavior:

Currently, as shown in #73, nothing is really displayed on an error page.

Expected behavior:

I would like to have the following displayed, all with as much explanation as possible:

• (1) traceback #74
• (2) installation information
  • (2.1) git commit/version number
  • (2.2) Python version number
  • (2.3) If required packages are installed and which are installed
• (3) some explanatory text that this is unexpected and what it means: the service can not be performed as expected
• (4) a link to the issues page, inviting to pose the problem
  • (4.1) A started description which can be copied and pasted into the issue
• (5) a link to gitter with an inviting text to get started and contribute

I believe, once people come from eventyay, this will help them get to report the error.

If you like to work on the issue, please create a separate PR for each point with the point number e.g. 4.1 mentioned in the heading and referring to this issue with #75 in the description, so it turns up in the discussion.

I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

The files generated from the previous upload might result in unwanted results. Best would be to check and delete the previous files before uploading new ones.

@S2606 is one of the largest contributors in terms of commits and requests to join the maintainer team.
I will add him.

Read about becoming a maintainer

I'm submitting a ... (check one with "x")

• bug report
• feature request
• support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/badgeyay

Current behavior:

Footer overlaps the form whenever '/upload' is successful.
Expected behavior:

The footer must not overlap with the form.
It should stay either fixed on bottom or should be placed below the form everytime.

Steps to reproduce:

Changing some CSS would definitely do.
:D

This service should create badges for evetnyay. This is why it is called badgeyay.
Please allow a flow where I, as an eventyay-user can

1. Export the data from the event for a category of participants (speakers, VIP, orga, ...)
2. import this to the badgeyay frontend
3. choose the background image
4. generate the badges

Hints:

• There is a python file which generates the CSV file from the JSON file: https://github.com/fossasia/badgeyay/blob/ots-eventyay/generate-speaker-csv.py
• This can be tested on actual eventyay Open-Tech-Summit data

We want this app to work for a long time. Versions of modules change, please pin the version of the used python packages in the requirements.txt file. (Reasoning)

You can use pip-tools for this: pip install pip-tools.

I'm submitting a ... (check one with "x")

• bug report

Current behavior:

Please see the comment #46 (comment) for a description and context.
A generic error is caught and not printed out.

Expected behavior:

Errors should not pass silently.

Steps to reproduce:

Please see the comment #46 (comment)

There are two merge_badges.sh files. Which one is the right one?
Please delete the one wich is not used.