chicagopython / buddy_mentorship Goto Github PK

Django Model implementations should look to the data model for the appropriate fields/types/linkages.

Emails needed:

• Received a request
• Request accepted
• Received an offer
• Offer requested

Email copy should explain process.

Pending completion of #4

Will assume all profiles are visible to all logged in users, until/if we implement permissions.

Create a model for storing user profile information. See https://wireframe.cc/bC2Pcw for a wireframe and notes about the fields.

Should include at least:

• Bio
• Want help
• Can help

See #7 for exact tables/fields

Since github is the main login, let's emphasize it more

To be used for sending e-mail notifications. Probably one of:

• mailgun
• fastmail
• sendgrid

Contents TBD. Can have a welcome message/description of the app's purpose for now.

A way to keep track of requests for mentors/mentees

See #7 for details

Relates to #1

When a mentor accepts a request they should both get each other's email

Add md files to keep track of how to contribute to the project, and any changes between versions. These files will need to be kept up-to-date over time by folks contributing PRs

Allow users to authenticate with GitHub (in addition to through a user/pass specific to our site).

Query Profiles

If ability to request or offer is not available, explain why in text.

See https://wireframe.cc/bC2Pcw

Builds on #25 and #26 so that request list view and request detail view can show live data.

Request list view will show a) list of requests that user has sent, and b) list of requests that user has received. Buddy requests model currently does not track whether requests have been accepted; if/when we implement this, might make sense to distinguish between accepted and unaccepted requests.

Request detail view shows the contents of a single buddy request.

See: http://buddy-mentorship.herokuapp.com/profile/.
@rifferreinert, can you take a look at this?

Set up a basic Django app with sensible defaults.

Related tutorial: https://developer.mozilla.org/en-US/docs/Learn/Server-side/Django/skeleton_website

Some features such as sending a request don't work unless you have skills, let's add a banner to the top of their profile to tell them

Related tutorial: https://developer.mozilla.org/en-US/docs/Learn/Server-side/Django/Authentication

Don't forget CSRF

Users can sign up for accounts now but they need to be able to edit their details

Can help/want help should be mutually exclusive
Remove can help/want help checkboxes from add skill form (make hidden)
Change delete message.

There should be a way for folks to contact us with any website bugs or for general inquiries. If we don't want to recreate the wheel, we can wire up a link in the nav to direct people to this page: https://www.chipy.org/contact/

Depends on #12

See #10

• automatically link profile to Github
• pull profile pictures & show on profile
• suggest skills?

On rejection, do not send email notification and remove rejected requests from request list view.

Right now CI uses a hard-coded download path for chromedriver, which changes based on the version. The Chrome install pulls down the latest version of Chrome, and the Chromedriver version needs to match the Chrome version to work. This is not a sustainable setup!

Official Docs: https://docs.djangoproject.com/en/2.1/topics/auth/customizing/#substituting-a-custom-user-model
Unofficial Tutorial: https://wsvincent.com/django-tips-custom-user-model/

See #7 for tables/fields

Filter search results by minimum/maximum levels of specific skills.

With link to all views and a logout/login button (depending on status)

Right now, only appears directly after account creation.

This is mostly uncommenting html.