These are chat archives for fossasia/open-event-server

11th
Jan 2017
Arpit Nandwani
@arpitn30
Jan 11 2017 07:13
I was thinking of using open event server in my website. Where can I find the documentation for using the open event api
Niranjan Rajendran
@niranjan94
Jan 11 2017 07:30
Arpit Nandwani
@arpitn30
Jan 11 2017 07:36
👍
Arpit Nandwani
@arpitn30
Jan 11 2017 08:02
Are there any issues open which aren't assigned?
pipix51
@pipix51
Jan 11 2017 08:05
@arpitn30 you can try #2802
ashwinpathak20
@ashwinpathak20
Jan 11 2017 10:25
I was following up the steps to run the orga server but while installing bower : command 'npm install bower -g' and 'bower install' shows error. Can someone tell me the possible errors and ways to make it run? Thanks in advance.
Saptak Sengupta
@SaptakS
Jan 11 2017 10:29
What error are you getting??
Can you paste the error log in fpaste and share the link?
ashwinpathak20
@ashwinpathak20
Jan 11 2017 12:38
This is the error i got for 'npm install bower -g' : https://da.gd/XSOG
Parag Jain
@PARAG00991
Jan 11 2017 12:42
@ashwinpathak20 try to use sudo before the command
Arpit Nandwani
@arpitn30
Jan 11 2017 15:15
alt
Where can I add discount codes
??
Arpit Nandwani
@arpitn30
Jan 11 2017 15:20
And where can we suggest a feature to add to the server?
Niranjan Rajendran
@niranjan94
Jan 11 2017 17:20

@arpitn30

Where can I add discount codes

you can add it from the administrative section of the app. /admin/sales/

And where can we suggest a feature to add to the server?

You can open a new issue at https://github.com/fossasia/open-event-orga-server/issues

Arpit Nandwani
@arpitn30
Jan 11 2017 17:33
:+1:
ashwinpathak20
@ashwinpathak20
Jan 11 2017 17:36
@PARAG00991 it shows command not found when sudo is used.
Parag Jain
@PARAG00991
Jan 11 2017 17:38
@ashwinpathak20 what did you use?
ashwinpathak20
@ashwinpathak20
Jan 11 2017 18:00
@PARAG00991 I was following the steps by step procedure to install and run the orga server but I got stuck up here. I typed 'sudo npm install bower -g' but the terminal showed 'sudo: npm: command not found'. Also, I have ubuntu as my os and on the github page , it is written that linux users need not use sudo for this command , yet the above errors are being displayed.
Niranjan Rajendran
@niranjan94
Jan 11 2017 18:04

to @/all the new contributors here :) ... Good job with your contributions in the form of bug reports (or) PRs (or) both ...

Got a few suggestions though

  • Write clear meaningful git commit messages (Do read http://chris.beams.io/posts/git-commit/)
  • Make sure your PR's description contains GitHub's special keyword references that automatically close the related issue when the PR is merged. (More info at https://github.com/blog/1506-closing-issues-via-pull-requests )
  • When you make very very minor changes to a PR of yours (like for example fixing a failing travis build or some small style corrections or minor changes requested by reviewers) make sure you squash your commits afterwards so that you don't have an absurd number of commits for a very small fix. (Learn how to squash at https://davidwalsh.name/squash-commits-git )
  • If you're submitting a bug report, make sure you add steps to reproduce it. Especially if that bug is some weird/rare one.
  • If you're submitting a PR for a UI-related issue, it would be really awesome if you add a screenshot of your change or a link to a deployment where it can be tested out along with your PR. It makes it very easy for the reviewers and you'll also get reviews quicker.
  • If you would like to work on an issue, drop in a comment at the issue. If it is already assigned to someone, but there is no sign of any work being done, please free to drop in a comment so that the issue could be assigned to you if the previous assignee has dropped it entirely.
  • Go through the application completely on your local machine. Press on any link/button you can find and see where it leads to. Explore. (Don't worry ... Nothing will happen to the app or to you due to the exploring ;) Only thing that will happen is, you'll be more familiar with what is where and might even get some cool ideas on how to improve various aspects of the app.)

And also, there seems to be some confusion regarding what code is where.

So, any bug-fixes will not be reflected at eventyay until a new release is made in the master branch.

The tentative release policy for now is, (since there is a lot of activity and a lot of bugs), an alpha release every monday and friday. (since we see more activity on weekends).

Thank you for your patience while reading this long message :D

Saptak Sengupta
@SaptakS
Jan 11 2017 18:07
@niranjan94 makes sense...
@niranjan94 has covered all the points. Just to avoid confusion, I would like to add one thing. A pull request with properly squashed commits doesn't necessarily mean the pull request should have only 1 commit. It is okay to have a pull request with multiple commits if it addresses multiple issues or multiple aspects. But if it's just a small fix then ideally there shouldn't be more than 1 commit. The idea is there should be a commit only after a proper significant amount of work is done. I hope the idea is clear...
Niranjan Rajendran
@niranjan94
Jan 11 2017 18:12
@SaptakS Yep.. you're right
Medo
@magdalenesuo
Jan 11 2017 18:19
@niranjan94 @SaptakS Roger that! :smile: :+1:
Mario Behling
@mariobehling
Jan 11 2017 18:36
@niranjan94 @SaptakS Thanks a lot! I think this is perfect for the Readme.md as well for now. Put it up here: https://github.com/fossasia/open-event-orga-server/blob/development/README.md#contributions-bug-reports-feature-requests
I also added some info about the gh-pages branch, which keeps the documentation for http://dev.eventyay.com
Shubham Padia
@shubham-padia
Jan 11 2017 22:04
@niranjan94 @SaptakS +1 :)
Rishav Sapahia
@Rishav09
Jan 11 2017 22:36
Hi,is it just me or in every local installation ,the server is running super slow,it took me 15 minutes just to open the create event page.Any ideas how to fix this?