file:///home/srestha/Pictures/Screenshot%20from%202019-02-21%2020-02-55.png
<!!image>
EDIT: Sorry @srestha. I didn't know you were willing to work on this issue.
Hey @jonatoni , I am an outreachy applicant, I have opened this issue, kindly review and assign it to me if it looks fine.
Or maybe we can have one button in the left side panel, which will be present in all the pages, so that we don't have to browse to the homepage for sending happiness packets, instead we can just send it from the panel
"Send some happiness!" link is present, but it doesn't stand out, we can change the font size/ make it a button to highlight it.
If people click on the right at the menu "Send some happiness!" it does the same as the button that you mentioned, and we have it on every page.
Tbh I like it as it is - because it is visible on every page and easy to find.
Metadata Update from @jonatoni: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
How about highlighting the link and removing the two duplicate buttons?
Or maybe we can have one button in the left side panel, which will be present in all the pages, so that we don't have to browse to the homepage for sending happiness packets, instead we can just send it from the panel If people click on the right at the menu "Send some happiness!" it does the same as the button that you mentioned, and we have it on every page.
Metadata Update from @srestha: - Issue status updated to: Open (was: Closed)
Hi – per the upcoming contributor guidelines, this change also affects the upstream project, mxsasha/happinesspackets. To be a considerate downstream project, we should send this pull request to upstream. If upstream accepts it, we can apply the patch downstream to our project.
I will keep the issue open if someone wants to work on this. The pull request should be sent to mxsasha/happinesspackets. However, there are likely better issues to work on. We don't know for sure if upstream will accept the pull request.
Metadata Update from @jflory7: - Issue priority set to: waiting on assignee (was: awaiting triage) - Issue tagged with: PASSED, difficulty - easy, good first issue, improvement, type - frontend, type - summer coding
Metadata Update from @jflory7: - Issue tagged with: type - upstream
hi @jflory7 i would like to work in this issue, kindly assign it to me
Hi @srestha, are you already working on this ticket or planning to work on it?
First, let's make sure @srestha is not already working on this ticket.
If not, you can work on this ticket. Before writing code, we should discuss how to implement this. There was some additional feedback in previous comments in the ticket.
Also, take a look at these guidelines for submitting a contribution to an open source project. There are helpful tips there about putting together a contribution of any kind. I recommend reading through that first before submitting a pull request too.
hello everyone, is there anyone working on this issue ? if not i would like to work on it
This ticket is not assigned to anybody, so you can start working on it @saidat.
hello everyone, is there anyone working on this issue ? if not i would like to work on it This ticket is not assigned to anybody, so you can start working on it @saidat.
hello @alishapapun, my docker has been running well all along without complaining but now as i was building to see some changes ihave made to the site it gave mean this error, i dont know what could be the cause can you please help me out
You can solve the problem temporarily by adding -k after the -s here till this issue doesn't get resolved.
-k
-s
hello @alishapapun, my docker has been running well all along without complaining but now as i was building to see some changes ihave made to the site it gave mean this error, i dont know what could be the cause can you please help me out You can solve the problem temporarily by adding -k after the -s here till this issue doesn't get resolved.
Thanks @shraddhaag, it worked
Metadata Update from @jflory7: - Issue assigned to saidat - Issue set to the milestone: Summer Coding 2019: community bonding
This was completed in PR #224 from @saidat. I'm closing this as complete! :clapper: Thanks @saidat.
Metadata Update from @jflory7: - Issue close_status updated to: complete - Issue status updated to: Closed (was: Open)