Because there's good ideas out there, and the community needs to know about them.
Because there's bad ideas out there, and the community needs to help the pitcher evolve them.
Page that lives at ideas/new. Page has a web form
When it's submitted,
Pitchcommunity-general on gitcoin slack with the title of the idea and a link to itThis page lives at ideas/title-url-encoded and is the 'view' page for the idea. It will display the same information as the form, and it will also give the end user the ability to upvote / comment on the idea. one upvote per ip address.
This page is the index page of all of the ideas, and it lives at `ideas/
https://github.com/gitcoinco/web/issues/198



__This issue now has a funding of 0.22 ETH (193.79 USD) attached to it.__
This could be very interesting... I would like to throw my hat in the ring for working on this tentatively π
@owocki what is your timeframe when you would like to have this done by?
@mkosowsk i just put '1 month' as the expiration for the bounty... so ideally we'd be aiming for a merge into master within the next 3 weeks. i think that having a bounty hunter who is commited to seeing it across the finish line is more important than someone who is gonna start RIGHT NOW
@owocki I will see this through, I bet @vs77bb's life on it π π π
Will post a plan of attack by EOD Saturday, very excited to take this one on!
@PixelantDesign I am very excited to start work on this ticket by tonight π
Please let me know if there's some additional direction you'd like to provide. Thanks!
hey @mkosowsk can you sync with @KennethAshley on the form styles he has been implementing?
Will do! π
Yea ive been working on the forms. let me know what you need.
@PixelantDesign these designs are bomb. Would of loved to be the one working on this ahaha.
@KennethAshley I actually didn't design these! Seth did!
I've blocked out a lot of my weekend to work on this, so hope to deliver on these great designs!
@KennethAshley does https://github.com/gitcoinco/web/pull/514 have the latest and greatest on forms for Gitcoin?
@KennethAshley I am forking from your repo to do work on this guy for forms. As I will be building extensively off your work, it's only right I send over part of the bounty if/when my PR is accepted.
Does .1 ETH sound like a fair amount to you considering this bounty is .22 ETH? Thanks! π
@mkosowsk Dude yea! Whatever you want to send over! Thanks!
@mkosowsk also yes, #514 has the latest and greatest!
@KennethAshley I walked through your commits and learned a thing or two... including status code 204 which I had never used before!
Just sent over that .1 ETH because talk is cheap π thanks for your help! ππ»
First pass on the idea-modal.png design!

This image is from a 1336x768 resolution, will work on making it responsive for tablet and mobile at a later time ππ»
@sethmcleod and @PixelantDesign, here are some thoughts I had as I was building this out.
I think it would be more internally consistent to not use a modal here as well, especially considering that it doesn't seem to me that Gitcoin is using modals much elsewhere.
I personally am more of a fan of using "Full name" instead of splitting it as "First name" and "Last name" can be a bit confusing to the international crowd... sometimes you see these fields written out as "First/Given name" and "Last/Family name" but then at that point I think you're better off using the cleaner "Full name" and being done with it
Which fields are required for this form? All of them? π€
In the original design, radio buttons are used for the "What are you looking for?" and "What do you have already?" fields but I think checkboxes are more suited for these options. Checkboxes allow easy selection/deselection and I feel are better suited when selecting none/one/many options. Radio buttons are a better fit for when selecting one option, like how we do in Explorer for Status of "Open", "Work Started", "Work Submitted", etc. I'm happy to discuss this further and am definitely open to feedback ππ»
Last but not least, I opted for a button styling for the "Submit" also from submit_bounty.html from https://github.com/gitcoinco/web/pull/514 which is a blue block instead of a red one with rounded corners. I'm fine with either but think it would be best to standardize ππ»
Once these are squared away, here is my plan of attack:
so excited for this to get into PR stage :)
@owocki great! Will have another update by end of this Sunday (3/11) where I will have some major damage done.
I will have PR out before the following Sunday (3/18) come hell or high water πͺπ»would like to have PR out before the 18th but been getting slammed at work π€
This is looking great @mkosowsk! So much fun to see these designs come to life :)
To answer some of your comments:
I agree with this. Perhaps we can do some refactoring later and utilize modals throughout the app.
This makes sense. I had those split up because sometimes it's nice to have a reference for the first name, for example: Hi Seth, welcome back to Gitcoin! just doesn't feel the same level of personality if my last name was included.
As far as I know all fields are required.
I completely overlooked that. You're right, we should have used checkboxes there instead of radios!
Looks good to me! Perhaps we can update this once we finish defining UI guidelines and consistent form/button styles cc @PixelantDesign
@sethmcleod thanks for the feedback and also for providing the excellent designs, really a pleasure to work with! π
To point #1, I'm not married to having Full Name vs. First Name and Last Name but if we do decided to keep Full Name I think we could split the full name on the first space to have a bit of personality.
So 'Mitch Kosowski' would become 'Hi Mitch, welcome back to Gitcoin!'
Names like 'Anne Marie Smith' don't work as good tho -> 'Hi Anne, welcome back to Gitcoin!' doesn't work if she's used to be calling Anne Marie...
Anywhoo, I think the most important thing is to be consistent across the platform so as #514 is merged into default now I will roll with Full Name for the time being. Happy to discuss further at a later date like when this PR's π thanks!
@mkosowsk ππ
@PixelantDesign, @sethmcleod, @owocki, et al.,
The idea-view.png view uses Disqus for commenting which I am on board with but wanted to confirm that jived with the vision for Gitcoin π
If we use Disqus, looks like there's an npm package at https://github.com/rcurrier666/node-disqus but it seems to more popular route is just using a Universal Embed Code via https://help.disqus.com/customer/portal/articles/472097-universal-embed-code
I haven't used Disqus before but it looks fairly intuitive... definitely open to feedback on the approach :)
Quick update, was working on list view over the weekend but don't quite have this at a ready state to show off with a screen shot. I am following the design but also using a bit of inspiration from the Explorer page π
I am taking Friday off to do some errands but also to take this to a PR (or at least WIP PR) :)
@mkosowsk @PixelantDesign Are we sticking to disqus ? It kinda looks out of place
( I'm talking on long run )
@thelostone-mc I think Disqus looks somewhat out of place but I'm not sure of a better alternative π€
I've heard decent things about https://posativ.org/isso/
It's lightweight and got a shitty UI -> cause they expect you to customize it for your own site (that's exactly how it was pitched to me :P
( let's stick to Disqus to avoid any confusion, but yeah just wanted to check )
Keep up the good work @mkosowsk!
thanks for the update @mkosowsk
First pass on ideas-list:

Some thoughts to follow tomorrow morning, my brain is leaking out my ears at the moment so I need to take a breather π
Edited in comments on some chocies:
@mkosowsk Do you have a PR open ?
I could pull it in and help with the review whenever you need me to ^_^
@thelostone-mc Sure, I always appreciate your help! ππ»ππ»ππ» I will have a WIP PR open within the next 16 hours... want to spend a bit more time on it today :)
Some things I'd like to cover in that time in order of priority:
My goal for today is to accomplish items 0-2, the following is future work:
I'd have liked to have a lot more done at this time but I've been a bit time-constrained with personal things and work as well as building out fresh views taking a lot more time than I expected... I'm used to tweaking established designs and didn't budget enough time for starting greenfield!
I am editing my previous comment now to explain the rationale for some decisions and then will start cracking π
Haha looks like you've got it all planned out ! Sounds good to me ^_^
excited for the PR -- looks like this is really coming together
@owocki WIP PR is here if you've got some cycles :D
commenting on PR now
Quick update, will address WIP PR feedback (thanks @owocki and @thelostone-mc π ) this weekend and open the legit PR by end-of-day Sunday. Thanks!
@owocki and @thelostone-mc et al, thanks for your guidance but I'm stopping work on this issue. Unfortunately my work has super ramped up recently and I just don't have the dev cycles to see this ticket through to fruition in the coming weeks. In hindsight I should have picked up something easier to digest for my first ticket on the Gitcoin project! My apologies on the bait-and-switch :(
To whomever picks this up, feel free to use any or all parts of https://github.com/gitcoinco/web/pull/647 as a base if need be. Good luck!
I can take it :raised_hand:
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
__Work has been started__.
has committed to working on this project to be completed 1Β month ago.
Does the counter next to heart icon in top right corner reflect recommends count in disqus thread?
Does the counter next to heart icon in top right corner reflect recommends count in disqus thread?
yes!
@kziemianek are you still working on this issue?
@kziemianek are you still working on this issue?
@kziemianek you mind leaving a comment here for the bot π
cc @mbeacom The inactivity period check -> as of now we check only if a comment has been posted by the hunter as a sign of activity right? (and not a referenced PR )
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
@kziemianek has been removed for inactivity and the issue has been returned to an βOpenβ Status. Let us know if you believe this has been done in error!
@owocki sorry, i cannot submit my work as described in #883
ahh its bc the issue is expired. ill cancel the issue now and tip ya out when the PR is merged
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
__The funding of 0.22 ETH (148.67 USD @ $675.77/ETH) attached to this issue has been approved & issued.__
Most helpful comment
@owocki I will see this through, I bet @vs77bb's life on it π π π