Create Developer Contributor Board

[TiffanyGYJ]

What?

Create a BOS Developer Contributor Board that acknowledges the invaluable contributions of community developers.

👉 UX Design

Why?

Developer contributor pages significantly enhance the collaborative and inclusive atmosphere of open-source projects.

They offer transparency and acknowledge the varied contributions of numerous individuals. These pages motivate contributors and foster community building, allowing individuals to establish their reputations and build trust and credibility. They offer a sense of belonging and encourage new contributors to get involved.

These boards also make the experience more engaging and fun by gamifying the contribution process and transforming contributions into a rewarding challenge where participants can gain recognition as top contributors. 💪

Additionally, contributions boards act as a historical record, charting the project's development, and assist in collaboration by clearly showcasing each participant's specific role and contributions. 📝

How?

The Data Platform and Near.org Core Experience teams will work together to complete this joint effort. 🤝

👉 Core Exp will build the front-end landing page.
👉 Data Platform will provide the backend data pipelines.

• UX - @xuan-ytr
• BE - @Oksanusha (@pkudinov EM)
• FE - @shelegdmitriy (@charleslavon EM)
• PM - @thisisjoshford

Completion Requirements ✅

• Stand-alone page created w/ link in near.org header nav
• Shows three data range views (all time, last 30 days, last 7 days)
• Returns all contributors and paginates results
• Default ranking is based on the number of components created
• Allows users to sort tables by a selected column
• Follows UX Figma design that includes:

Column	Details
Name	User's display name with a link to their profile page
Components	Total number of created components (during selected timeframe)
Stars	Total number of stars their components received (during selected timeframe)
Forks	Total number of forks their components had (during selected timeframe)
Commits	Total number of published code events (during selected timeframe)
Lines of Code	Total lines of code shipped (during selected timeframe)
Start Date	The date a user shipped their first line of BOS code
Actions	Ability to follow someone or display following if they already are

Related Data Issues:

Beta Give feedback

1. https://github.com/near/data-analytics/issues/17
2. Developer Contributions Stats Pipeline #24
   Near.org +1
   
3. Add number of star to component stats pipeline #47
   Stale +1
4. Add number of forks to component stats pipeline #48
   Stale +1

[xuan-ytr]

Hi @thisisjoshford, we're not quite ready to hand-off the designs for shipment yet, given:

• We haven't yet established a clear outcome that would drive the success of this feature,
• Which influences the column headers, the order in which they appear, and the data needed to populate the leaderboard

Could we take a look at this worksheet together once you get back?

As a point of process, designs are reviewed and validated by @sarahmills and team before hand-off to PM / engineering. Github status for design will move as follows:
In Design --> In Review --> Validating --> Design Complete

cc @TiffanyGYJ for related ticket #134

[thisisjoshford]

Hi @thisisjoshford, we're not quite ready to hand-off the designs for shipment yet, given:
We haven't yet established a clear outcome that would drive the success of this feature,
Which influences the column headers, the order in which they appear, and the data needed to populate the leaderboard
Could we take a look at this worksheet together once you get back?

Ah there seems to be some confusion here, hopefully I can try to clear this up with some background & context for everyone.

• @TiffanyGYJ, @pkudinov, and I have been discussing these dev contribution / leaderboards for some time as both Tiffany and I had this feature on our respective roadmaps.

• She worked with you and @pkudinov on the creation of this and they shared the completed designs on 10/5 for feedback. I gave the same adjustment requests then that I did with you during our call this week.

• @TiffanyGYJ and I decided that this feature made sense for me to own as a DevX feature and to include it in my Developer Reputation Initiative. Also, they were short on frontend dev resources and unsure of when they would be able to create it in a timely manner.

• My Dev Reputation kick off w/ the Core Exp team was delayed until this week and the leaderboard was prioritized as the last ticket to execute on once certain dependencies are complete (such as forks, favorites, and data pipeline).

• I then reached out to you to inquire about the design that you created and to make these column & description adjustments in preparation for this.

As a point of process, designs are reviewed and validated by @sarahmills and team before hand-off to PM / engineering. Github status for design will move as follows:
In Design --> In Review --> Validating --> Design Complete

My apologies if my recent adjustment request was perceived as circumventing the design process. I was just executing something that I was informed was ready to go but just wanted to see if some minor adjustments could be made before handing it off to engineering.

Also, this release of the Developer Contributor board is an MVP and not necessarily its final version. I am trying to execute a more Agile methodology for feature releases and not get too caught up on the perfect solution for a first iteration. The details
outlined in the Completion Requirements more than satisfy this as a "MVP / first release" IMO but happy to discuss dissenting opinions here.

I'll reach out to you and @sarahmills on Slack and see if we can schedule a call to iron this out before I head out of office next week.

[xuan-ytr]

@thisisjoshford thanks for explaining! We didn't think you were trying to circumvent process, it's just that we haven't had a lot of opportunities to align on the continuous improvements being made on the team since so much as been changing. Looking forward to our sync with @sarahmills, which should clear up any misunderstandings.

[xuan-ytr]

@heycorwin item 1 in the completion requirements / acceptance criteria implicates an IA change on the top level. I know we're headed towards not having the top nav, so this might be soon obsoleted even if we shipped it. Could we explore with @joshuajbouw impact and alternative solutions to discoverability of this page?