You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@jamlung-ri A few considerations to think through so we're able to finalise requirements...
Do we have a good enough understanding of why users pin repositories... are there stories where they are pinning for personal efficiency as well as to ensure their Org members and other users see the repo displayed in a prominent position?
How many pinned repositories should we support? Do we have any data on how they're used today?
1. Do we have a good enough understanding of why users pin repositories... are there stories where they are pinning for personal efficiency as well as to ensure their Org members and other users see the repo displayed in a prominent position?
People have used Pinned Repos in the past as a way to "bookmark" them for later, but I think the new way of doing things in v3 (e.g. Dashboard and Follows) should alleviate that need for personal efficiency. The only intent for Pins after that is to highlight content for anyone who enters the Org to see, I think. Do you agree?
2. How many pinned repositories should we support? Do we have any data on how they're used today?
I don't know if we have hard data, but it's certainly possible that the current 4-pin limit is not enough for users. But because of their purpose of highlighting the most important content, it could defeat the purpose if the limit is increased. I have found the 4-pin limit to be good enough, personally, as long as all four pins can be shown adequately on screen.
As a user, I want to be able to Pin a Repository so that I can ensure its positioned prominently in the Organization page.
Acceptance criteria
Design docs
TBC
The text was updated successfully, but these errors were encountered: