Add Documentation for Open-Source Leaderboard Component so it can be easily used by community builders.

Work with all of the auth implementer to determine the best platform for maintaining a super profile associated with each user.

Implement React component for Gluu Authentication.

Start with simple auth as POC.

Starting thinking about extending to maintaining a super profile assiciated with each user record.

Work with other auth implementers to make sure the component's intterfaces are compatible.

Like a youtube viewer. Shows thumbnail of video . Upon clicking starts to play video.

Enable "standard" playback controls of the underlying libray.

Make sure it can efficiently support multiple instances on one page.

The community logo in the home page does not appear after loading the page.

The attached URL points to a resource that does not exist.

Browser version:
Google Chrome - Version 99.0.4844.51 (Official Build) (64-bit)

Duplicate the community builder's experience of the Github component kit -- for a self-hosted Gitlab instance,

Create a React based Hacker News "top list" or "current list" component based on configurable criterion.

Model this one close to the existing Discourse component.

Create menu hierachy to support our GSoC and GSoD Communities:

Community
    Google Summer of Code 2022
         Program information   --->  https://docs.rocket.chat/contributors/google-summer-of-code/google-summer-of-code-2021
         Introductions  --->  https://open.rocket.chat/channel/gsoc2022
         Team -->  https://open.rocket.chat/channel/google-summer-of-code
         Leaderboard ->  https://gsoc.rocket.chat
         Virtual Conference -> https://rocket.chat
         Office Hours ->  https://rocket.chat
         Projects Ideas ->  https://docs.rocket.chat/contributors/google-summer-of-code/google-summer-of-code-2021#project-ideas
         Results -> https://docs.rocket.chat/contributors/google-summer-of-code/google-summer-of-code-2021#update-may-20th-2021
    Google Season of Doc 2022
       Program information   --->  https://docs.rocket.chat/contributors/google-season-of-docs/google-season-of-docs-2021
       Introductions  --->  https://open.rocket.chat/channel/gsod2022

Create a React based Stack Overflow "top upvoted list" or "current list" component based on configurable criterion.

Model this one close to the existing Discourse component.

Description :

Footer Logo is not working

Current Discourse module will keep populating the top ranking list to 10s or 100s of entries.

Re-implement the logic to select the TOP N entries - with N anywhere from 3 to 15 ONLY.

Define a "module structure" that makes sense for these sort of "full stack reactjs components", beware it will always be executing on nextJS (keep to JAMStack ideals).

Keep this work on ONE SINGLE PR.

Description :

Typography, responsiveness, and UI of the mainstage page along with animation.

Create a full-stack React component that displays the top 3 to 15 issues from Github. - ranked based on a set of pre-defined filters (most voted up, for example).

This component should be very similar to the existing Discourse component.

Description

I found a bug in the header part in https://community.rocket.chat/ , source of img is not valid

Create a React component that surfaces the features of browser integrated crypto wallets for community members, such as via MetaMask extension or via built-in wallet of the Brave browser.

link #87

Create a React based Stack Overflow "top list" or "current list" component based on configurable criterion.

Model this one close to the existing Discourse component.

Add a nodeJS server at our deployment site, behind nginx , and run nextJS as production there.

Create a React component encapsulating the UI of Forem.

Test the resulting component with dev.to.

Check community.rocket.chat for styling. Restyle the existing components to the standard of community.rocket.chat

BE CAREFUL:

• keeping ALL current reactJS components responsive, when shrunk to mobile format - ti should still be highly usable
• do not add any global styling - do each components' styling in its own CSS module
• maintain static generation, do not write components that forces SSR (with 1 exception - the client-side countup counter)
• do restyling of ALL current component in ONE LONG PR, do not create separate PR for components

Implement React component for Keycloak Authentication.

Start with simple auth as POC.

Starting thinking about extending to maintaining a super profile associated with each user record.

Work with other auth implementers to make sure the component's interfaces are compatible.

Description :

The Jisti logs are visible to the client

Expected Behavior :

Hide Jitsi Logs from Client

Adapt existing Poll + Rocket.Chat app as a React components for polling of community members.

Investigate into the possibility of creating a component that takes datasource (strapi, URL to JSON, URL to CSV) and populate its children components iteratively with that data. Without:

1. touching or modifying the styling of its children
2. having any major assumption about its childrren (except perhaps an exported data population method)

Create a React component that adds NFT marketplace integration for community members.

Investigate possibilities with OpenSea and other trending marketplaces.

I wonder if we can move these down to the componenet level -- making each one of our components an indepdendently installable npm module (optionally).

Originally posted by @Sing-Li in #78 (comment)

Create a reactJS component for Big Blue Button - you may need to work closely with the Big Blue Button team.

This component should enable community members to video conference with one another in:

scheduled meetings
scheduled virtual events
scheduled virtual classes

Description :

The Current Github Component Kit has the following issues :

• The current kit has multiple components which are used using different tags ,this makes it more complicated to use
• The database design for the component is not suitable for multiple repositories
• The current kit does not have a pull request component

Proposed Changes

• Create a single <Github ... /> tag which can display different components .
• Improve database design for scalability

• Create Pull Request Component

Description :

SQL Lite is throwing a duplicate column error due to duplicate column error in github-repositories due to ID field

Including subs such as r/etherum

Description :

Make a Re-Usable Announcement Component which can display relevant announcements on top of any page .

Creaete a React component for conducting virtual conferences between community members.

Re-use the Jitsi or Big Blue Button component if it makes sense.

Create a reactJS component from the Jitsi web SDK.

This component should enable community members to video conference with one another in:

• 1 to 1 calls
• scheduled meetings
• scheduled virtual events

Implement React authentication components for:

1.  Firebase
   

2. Auth0
   

Take the simple and direct route first as POC. Then start thinking of adding a "super profile" associated with the user account.

Description:

Whenever the app is loaded we see some console warnings/errors. These are there due to the following reasons :

1. JSX Typing errors.
2. Not passing key props to components.
3. Nesting Button inside another component which represent buttons.
4. Not Passing id props to Menus/Forms.

Steps to reproduce:

1. Run the CDN and APP.
2. Open browser.
3. Checkout the Console.

Expected behavior:

1. Console warnings should be minimized.

Actual behavior:

1. We see and error in console.

• announce and manage the signup , and operations of the virtual conference at community.rocket.chat

Add back the "Click to Chat" button as it is on community.rocket.chat

We will want to create a new user entry into our Super Profile - when an existing user with a Rocket.Chat account first access the site.

Please remove all count down and local time hacks on mainstage page.

Put static time with Brazilian time zone in all events.

We've learnt the hard way this time around why this just doesn't work. Thanks.

Description :

The favicon has not been updated and still shows the vercel logo

Create a React component using the matrix Javascript SDK npm module.

Allows community members to collaborate via embedded federated channels.

Also enabling matrix for federated subscriptions on data channels. (such as real time distirbuted score updates)

Create a React component for BoardX - enabling visual collaboration between community members.

Create a component that manages an interactive form to be filled.

Form data should be pushed to our persistence implementation data lake.

An indication if that form has been filled already, should be part of the Superprofile.

Make sure multiple instances on a page is easily handled.

Description :

Add emoji animations to live chat component and responsive video and chat component

Description :

Build errors due to accidentally omitted MdPreview Component

Restyle the first page to make it more friendly to community builders.

Create a React component to integrate Discord.

Use the existing Rocket.Chat integration as a template and expand into Discord specific featureas.

Description :

Refactor Leaderboard into two components :

• Main leaderboard.js which can be accessed via the dynamic route at -> root/gsoc/gsoc2022/orgname
• Reusable `leaderboardcompact.js' which can be used any where by communities.

Based this React component's interface on the existing GSoC Leadeboard.

Keep the interface flexible for repurposing as Game players' Leaderboard.

Add pre-commit hooks for:

• gitlint.
• code lint and formatting.

Add

• CHANGELOG.md
• Contributing-Guidelines.md

Description

• Currently the speaker speaker schema does not have a date_time field to specify the time and date of the speaker session / talk.
• The speaker schema does not have a duration field to specify the estimated duration of a speakers talk on the main stage.
• The live and ended fields of the speaker schema have to be manually updated to specify if a speakers session is currently live or if it has ended.

Expected Behavior

• Speaker Schema should have a date_time field to specify time and date of the speakers event on the mainstage.
• Auto Updation of Live and Ended fields according to date_time and estimated time_duration of the talk