Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Saicharan Reddy
@mrsaicharan1
@codedsun
Mario Behling
@mariobehling
The FOSSASIA Python, Flask, EmberJS job is now also listed on Indeed: https://www.indeedjobs.com/fossasia/jobs/d1c0dba8cf18dba1dd33
Shubham Pathak
@tronku
how to assign a issue to yourself? is there any command for the chat bot?
Shreyansh Dwivedi
@shreyanshdwivedi
@tronku there is no such way to assign yourself. Just comment that u want to work, one of the mentors will respond
Shubham Pathak
@tronku
Okay, I have commented. I'll wait for the mentors.
Mayank Soni
@may55
Hello all, I am trying to install "open-event-frontend", I am done with all the installation steps in https://github.com/fossasia/open-event-frontend/blob/development/docs/installation/local.md
but I am confused, Do I need to run open-event-server before doing ember server? If yes, please tell me the steps I need to follow!
Shubham Pathak
@tronku
Any updates on Issue #6461(fossasia/open-event-server#6461) in Open Event server?
smrutiranjan0
@smrutiranjan0
I am a newbie and I want to start contributing to this project, could anyone suggest me how to start my work?
Areeb Jamal
@iamareebjamal
README is a great place to start. Read it
Sai Rithwik
@DaKeiser
@may55 once you are done with the installation type ember serve
And then visit http://localhost:4200/
Harshit Khandelwal
@liveHarshit
Dear Codeheat participants, it is great to see how many of you have contributed substantial code and involve more and more in FOSSASIA projects. Let's move to the next steps now and document your scrums and blog posts as well. We have created a spreadsheet to collect this information. Please add your name, Github and project you involve in on the left in each sheet. Then add a link to your scrums on the sheet labeled "Scrum" and add blog posts and other information into the sheet labeled "Deliverables". Here is the link to the document: https://docs.google.com/spreadsheets/d/1uGlQ4Ijou0QmuGHNyGV_rbEhCo5Ljb-UlLRLqENPiXs/edit?usp=sharing Keep up the good work!
https://codeheat.org
Shubhika Bhardwaj
@ShubhikaBhardwaj
Hi everyone!
I am new to the fossasia community. I would like to make contribution and became a GCI mentor.From where should I start?
Nitin Kumar
@snitin315
@ShubhikaBhardwaj Please sign up here: https://fossasia.org/gci-mentor
@jmsingh6871 People who have made substantial work in a FOSSASIA project during a program or developers who are regularly active in FOSSASIA projects and contribute actual code can be mentors in GCI. So, now is a good time to contribute code and solve issues, if you want to get on board.
@ShubhikaBhardwaj **
Shubhika Bhardwaj
@ShubhikaBhardwaj
@snitin315 Thank you for the information. I am excited to get started on this
Kshitij Kotasthane
@kshitij86
I want to start contributing to this project, where can I start?
Dhruv Gupta
@imdhruvgupta
Hi, everyone! I am Dhruv. I am developing web applications for the past few years now. I have experience in Javascript frameworks like React, Ember. While in a backend, i have worked with Express, Spring boot. I am also an Instructor for Full Stack Web Development at Coding blocks, a programming institute in Delhi region.
Dhruv Gupta
@imdhruvgupta
So, I was going through the open-event project and I was wondering why are not we using the pods layout over the classical layout? With the project as complex as open-event, pods layout would be incredibly useful and not to mention damn easy to mention.
It would take a few hours, but I can do the refactoring. What are your views @mariobehling @iamareebjamal ?
Areeb Jamal
@iamareebjamal
Go ahead, generally with refactoring, people leave in between and work stalls. So, if the work is done in one go, I have no problem
Dhruv Gupta
@imdhruvgupta
Okay, then. I'll look into it.
Kush Trivedi
@kushthedude
The pod structure doesnt give the Quality handling in case of add ons, as there are several components which may not be associa
Dhruv Gupta
@imdhruvgupta
As far as the components are concerned, there is one folder where all the components are placed. The pods layout will combine route, controller, template into buckets based on the route.
@kushthedude I don't get your concern, could you please explain it in a little more detail?
Kush Trivedi
@kushthedude
Pod Structure is not recommended for the projects with quite an add-ons, Also I dont see the advantage of pod layout over the classical layout. Also, Currently refactoring of directories is also not affordable, we have some high priority issues and enhancements to make. Following refactoring would make more sense when each and every aspect of app is well tested and the web app is well coveraged
Areeb Jamal
@iamareebjamal

when each and every aspect of app is well tested and the web app is well coveraged

That will never happen. Facebook is 15 years old and it's still not true for them

Pod Structure is not recommended for the projects with quite an add-ons

Source?

I dont see the advantage of pod layout over the classical layout

Read about package by feature and package by layer. Package by feature is always better. If I want to see code related to admin route, I have to navigate components, routes, helpers, the dark dimension and what not. In package by feature, every related component, route, and helper is in one folder.

Areeb Jamal
@iamareebjamal

refactoring of directories is also not affordable, we have some high priority issues and enhancements to make

It's a voluntary project, if someone contributes to make the project better, it's not costing our time, so it's not the issue of affordability at all. And again, stop worrying about the breakage. If the code is not production ready, it will not be merged

chamodperera
@chamodperera
hi
Dhruv Gupta
@imdhruvgupta

Read about package by feature and package by layer. Package by feature is always better. If I want to see code related to admin route, I have to navigate components, routes, helpers, the dark dimension and what not. In package by feature, every related component, route, and helper is in one folder.

That's exactly what I wanted to say!

chamodperera
@chamodperera

@mentors I submitted this task about 10h ago
https://codein.withgoogle.com/dashboard/task-instances/5565774555512832/

still not approved

Suneet Srivastava
@codedsun
@kushthedude @prateekj117 @iamareebjamal I am able to create a ticket with validity more than that of the event end date, it shall be implemented for both server and frontend side.
Also I have enabled stripe payment in the admin payment gateway module, but the frontend doesn't shows this. Someone can help me here?
image.png
Screenshot 2019-12-08 at 6.56.42 PM.png
Prateek Jain
@prateekj117

@kushthedude @prateekj117 @iamareebjamal I am able to create a ticket with validity more than that of the event end date, it shall be implemented for both server and frontend side.

Go ahead. Open an issue regarding this.

Suneet Srivastava
@codedsun
Thanks. Also please guide me regarding the stripe payment.
Rehaan Khan
@rehaankhan1
Can anyone tell me how to use external ES6 JS file in emberJS that too in body ,not in head.
My solution only works in the head part of route , which is of no use to me because I have to query DOM elements
Areeb Jamal
@iamareebjamal
Wait for onload event, also, querying DOM elements is not recommended for data driven frameworks like react, vue or ember
Kush Trivedi
@kushthedude

Also I have enabled stripe payment in the admin payment gateway module, but the frontend doesn't shows this. Someone can help me here?

Use on production mode for now.

It should work
Areeb Jamal
@iamareebjamal
GCI participants, please understand the project and its scope before creating issues. Most issues created by GCI participants in open event android app repos have been invalid. By not understanding the project and its scope, you are not helping the project move forward, but instead hurting it, as maintainers have to redirect their attention from important issues to moderating an influx of invalid issues. Please understand the open event ecosystem and start by exploring eventyay.com, and then understand what is the use and scope of organizer and attendee app respectively. Read the documentation, and then report bugs. Reporting something that is not meant to be in the app is not helpful. Thank You
Mario Behling
@mariobehling
:thumbsup:
Ayush Shrivastava
@s-ayush2903
This message was deleted