Web: Clicking on the organization icon in the bounty page throws a 404

[arku]

User Story

As a gitcoiner, I would like to view the gitcoin profile of an organization.

Why Is this Needed?

Summary:

I am not sure if we have profiles for organizations yet. If we don't, we shouldn't link the organization icon to the profile. Currently, clicking on the organization icon in the bounty page displays the 404 page.

My guess is that when someone visits https://gitcoin.co/profile/gitcoinco, the app is looking for a user object with the username gitcoinco. Maybe we need to create a new route /org/:orgname?

Description

Type: Bug

Current Behavior

Visting https://gitcoin.co/profile/gitcoinco throws a 404

Expected Behavior

Visting https://gitcoin.co/profile/gitcoinco should render the profile of gitcoinco instead.

Reproduction

1. Go to https://gitcoin.co/issue/gitcoinco/web/1013/320
2. Click on the Gitcoin icon to the left of the bounty title

[mbeacom]

@arun1595 Thanks for reporting this.

It's due to the ProfileHiddenException being raised because gitcoinco's hide_profile=True in dashboard/views.py@profile_helper - I am uncertain if setting this to True was intentional. @owocki ?

I can set it to False for the time being to resolve the loading issue. I think it might be helpful to have a discussion about the UX benefits of displaying a template specific to hidden profiles versus a 404 .

[arku]

@mbeacom I also tried visiting the profiles of a few other organizations, they all threw a 404 FYI.

How about linking the icon to the github profile if their gitcoin profile is hidden?

Or we could simply not render the link if the gitcoin profile is hidden.

[thelostone-mc]

Has this been fixed ? 😅

[mbeacom]

@thelostone-mc I went in and changed the gitcoinco Profile.hide_profile to False.
One possible solution would be to prompt users hitting an organization profile page that is actively hidden or missing to notify the organization owner/members to approve the profile public listing.

Moving forward, it might be beneficial for us to introduce an organization management section to settings.

[owocki]

@mbeacom I also tried visiting the profiles of a few other organizations, they all threw a 404 FYI.

we're trying to figure out the best way to balance privacy / ux here. itd be nice to be able to see each organization, but without a specific opt-in, we might run afoul of privacy best practices..

[mbeacom]

@owocki My initial idea to solve this is to:

• Add an Organization model (subclass of django.Group to handle profiles that are an organization.
• Add Profile objects to Organization.members if they exist on gitcoin.
• Add an organization settings view where org owners can update members, perms, and general org details (description, website url, svn/gh profile url, avatar, keywords/tags, integration/notification settings, i.e. Slack, and view following members list, featured bounties, what to display, start/submit work hunter preferences/scheme settings, etc)
• Notify the organization owner (email/web?) about the pending authorization to list their org on GC with a link to approve/deny the org if the org doesn't already exist on GC or still needs approval.
• Add a view to display org specific "profile" pages.
• Add a CTA on the associated template to request approval from the owner/members if the org doesn't already exist OR approve the listing, if org owner/member. If the org exists, display related card details defined above.