Need to design basic wireframes and features

Create a mutation to update the redis server for a temporary post
Generate an email with a magic URL which will, upon visiting, move the user from redis cache to the main mongo DB.(This will be an issue in itself)

Basically the point is to create mutations to make a change in the db/cache and then generate a magic url.

Create a magic link for the user to hit (using redis cache probably/mongodb).
Then shift that to the mongoDB (after making certain checks)

Expectations:

• on creation of user(in the redis cache/mongo db), send an email using a background worker.

...userDetails,
verified : false
}

• When updated using that link, change the verified field to true

Depending on whether we end up using redis or mongo, do the next process

Prerequisites

At the moment, there are no proptypes.

Expected Behavior

Use react-proptypes to make sure that the valid prop conventions are followed

You can find more info here.

Talk to the mentor/admin before starting this.

I will be providing details soon. But anyone who knows how to code a store can go right ahead.

Argument for redux-saga can be made in the comments.

Remove the global css padding and margin that is inherent.

*{
margin : 0;
padding : 0;
}

Also change the Navbar color to #8e44ad(this might change in future)

Decide on which server and DB that should be used. See if AWS can be applied to this.

Create the 3 base schema designs that are required for the basic application.

Right now there are no tests.

But the intention in future is to implement a CI so need some basic tests for that.

You can use https://kolosek.com/testing-graphql-server/ for more information.

Convey in the slack/discord channel if you are willing to work on this ticket.

Expected Behavior

Write NPM scripts for running the production and dev server

At the moment we are to just conduct a small research and see what we can come up with.

Prerequisites

Please answer the following questions for yourself before submitting an issue.

• I am running the latest version
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed

Expected Behavior

The menteeType is to be added to the schema in server-api/schema/index.js

Current Behavior

MenteeType is not added

Steps to Reproduce

A menteeType schema similar to mentorType schema structure needs to be added.

This feature would, in future, show the mentors to the users.

This link would be helpful.
At the moment just any dummy data would be okay. In future, we will pair this with the back-end.

Expected Behavior

The folder should include the hero-image, links to various social media platforms and the logo of the project.

Current Behavior

There is no resources /media folder present until now.

Add eslint, babel and mongoose to the backend API

Expected Behavior

Add the packages and update the .babelrc file.

Current Behavior

No babel/mongoose added

Expectations:

• new updated template merging it with the instructions in the old one.

use this link as a template
Include the current PR style in it.

• Also add an issue creation section which will have the link to this page to get the issue creation markdown.

Add basic registration, sign in/log out with the backend.

It would be really cool to have a UI or a atleast a basic ui design

The typedefs need resolvers to render data. Set up a dummy data file to export data.

Once that is done the Backend design can be implemented.

Saw these two pop up. Anyone wants to see what the deal is here?

Use react router to set up protected routing and basic routing.

Getting a CI error https://circleci.com/gh/WrippleFoss/mentorFix/8
Need to fix it.

The tests are written and failing only for the front end folder.

Will provide the details soon. Those who can implement a basic store can go right ahead.

Prerequisites

Knowledge of node.js cluster module

Expected Behavior

Please describe the behavior you are expecting

Utilization of full core of CPU

Current Behavior

Does not have cluster module

Steps to Reproduce

Will use the node js core cluster module

For more information
https://nodejs.org

Updated(@abhishek71994):
For basic level knowledge of beginners working on issues related to this use this link

Expected Behavior

The ideal expected behavior is that the dev creates a mutation that would trigger a mailer and store a temporary value.

Research : check this link and see if that would help with a temporary storage until the user clicks on the link sent to them.

Current Behavior

None of the changes advised are added

Expected Behavior

Create a logo for mentor fix

Current Behavior

There is no logo at the moment

It's expected for the assignee to push the updated resource into the repo after finishing it up

Update the folder structure based on some universal convention which can be mentioned in the readme and contribution.md

So that everyone else can follow that too.

Update all the packages and then if it breaks the app then fix that too.

If possible add user auth to the process. Sign in using oauth maybe an option(This is an enhancement).

Expected Behavior

Expected to see a basic store setup and the Material UI framework to be implemented in the code.

Current Behavior

No redux or material UI implemented

protected url, only verified people will be allowed to use this

This issue comprises of getting all the details necessary for creating a full blown mentor/mentee profile.

Expectations:

• use mutations to update the features related to the user

{
username(required)
interests: will be an array of strings/enums(required)
photo: optional feature
location: _if that's of any use_
Bio: A short description(required)
username: github(required),twitter,medium
}

https://github.com/typicode/husky

mongoDB server connection working with the backend

The mentor should have a button somewhere in the top right that show's "Schedule a webinar"/any relevant icon.

Expectations:

• Upon clicking the button a pop up will appear.
• Will take up the basic information required to create a webinar.
• Once the webinar is set. (NOTIFY all the followers, doubtful about this feature)
• Create the details required for the webinar for front-end.
  namely - data,title,description,attending number, mentor(id)<-- this will be used to fetch other info

Expectations:

• The landing page should have hero text and hero image.(Should have a modern look to it)
• It should have a navbar with relevant links.
• Upon clicking the login/signup button there should be a pop up, with the respective forms.
• footer with links to the social links

Expected Behavior

Fix ESLINT Warnings.

Expected Behavior

When the user signs up, the user shall be asked for

• email
• username

This should be stored in a cached/temporary storage. You have the freedom to decide what you wannna do.

The links that I thought would help are
https://www.npmjs.com/package/passport-magic-link
https://medium.com/@aleksandrasays/sending-magic-links-with-nodejs-765a8686996

Current Behavior

No feature implemented

The following feature is supposed to let mentee's join in with the webinar

Expectations:

• Map the mentee ID with that of the webinar.
• Increase the attendance count on the webinar data.
• Upon clicking join, the mentee will get a pop up to confirm and then they will receive an email regarding the joining link and the time(With a feature to add it to their google calendar)

Prerequisites

Expected Behavior

Please describe the behavior you are expecting

There is different environments for the projects probably for test production and development

There is no testing of backend api and for the components

Current Behavior

What is the current behavior?

There is no docs for it

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

I will make a Architecture.md for same to resolve the above point mentioning how to resolve it and how to resolve if further issue (if any)

This feature is supposed to help the user(mentor/mentee) to login to the system.

Requirements:

• The request must be of the following type:

      {
           email:{Inserted email}
           username:{inserted email}
           password:{inserted password}
      }
  

• The return should be a token( preferrably JWT ) along with the username/email(this for querying)

Thinking of designing the backend using graphQL.

Expected Behavior

The mentorType is to be added to the schema in server-api/schema/index.js

Current Behavior

MentorType is not added

Instruction

• setup the following object type:

{
    id: ID,
    username: String,
    name: String,
    webinars:[WebinarTypes],
    verified: false/true,
    password : salted,
    bio : String,
    location : String,
    links : {}_public profile links_,
    email : String,
    followers : {menteeTypeID},
    expertise: []_A list of expertise_
}

• upon creating that the compilation should show no error and should have no conflicts with the master branch.

Make all the sketches and the wireframes. Also design the backend.