Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding social links and redirects to About section content #328

Merged
merged 3 commits into from
Jun 18, 2023

Conversation

SaurabhJamadagni
Copy link
Collaborator

Contributor checklist


Description

PR adds interactivity to cells in the About section table view that redirect to a link or call for action.

  • Section that redirect to a link are:
    • GitHub, Matrix, Bug report
  • Sections that call for action:
    • Share Scribe, Rate Scribe, Email redirect

Related issue

@github-actions
Copy link

github-actions bot commented Jun 14, 2023

Thank you for the pull request!

The Scribe team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes well. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

Maintainer Checklist

  • The commit messages for the remote branch should be checked to make sure the contributor's email is set up correctly so that they receive credit for their contribution (name and icon should be the same in remote commits)

  • The CHANGELOG has been updated with a description of the changes for the upcoming release (if necessary)

@SaurabhJamadagni
Copy link
Collaborator Author

Hey @andrewtavis, just wanted to make sure you saw this PR 😅

@andrewtavis
Copy link
Member

I did, @SaurabhJamadagni! Sorry :( I’ll get to it tomorrow morning at the latest :) Call for the activist backend is tomorrow at 13:00 UTC :) You can see the details in the dev channel on Matrix 🙃

@SaurabhJamadagni
Copy link
Collaborator Author

Oh cool no problem 👍

Sorry @andrewtavis, I don't think I will be able to make it to the call tomorrow. I have a family dinner. I'll join the meeting directly in case of any cancellations on the dinner front.

@andrewtavis
Copy link
Member

Sounds good, @SaurabhJamadagni! Have a nice dinner!

if MFMailComposeViewController.canSendMail() {
let mailComposeViewController = MFMailComposeViewController()
mailComposeViewController.mailComposeDelegate = self
mailComposeViewController.setToRecipients(["scribe.language@gmail.com"])
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey! 👋

I noticed that it's possible to set the subject line and the message body as well like the recipients here. I'm thinking that the message body is likely fine staying blank, but would it make sense perhaps to have some default set for the subject line? Just more so thinking in terms of what would be easier or expected from the user perspective.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey Will!

I did consider that. But we have separate sections for almost all the reasons a user might want to approach us. For example, to report a bug there is a section and to rate and share feedback there's the rating section. So writing an email seemed like a very ambiguous use case. That's why I didn't add a subject line in case the user wished to write an email for a completely different reason. Could be a complaint but could also be an email of appreciation 😅

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree that the use case for emails is going to ambiguous 🤔 I just checked and we're still at a grand total of 0 emails 😄 With that being said, maybe something inviting to the user? Hey Scribe!, for instance?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good @andrewtavis! We can do that. Just a tiny problem. I kind of committed my changes for the privacy policy issue (#317) to the branch already. So if I push it now that'll be added to the PR too. So would it be okay if I made this change in the next PR? I am so sorry! 🙈

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

100% ok, @SaurabhJamadagni 😊 No need to apologize :)

Copy link
Member

@andrewtavis andrewtavis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry again for the wait, @SaurabhJamadagni! Really well done :) This here menu really is taking shape! I'll get those designs for the info tooltip up shortly so they're ready for the work that's coming up 😊

@andrewtavis andrewtavis merged commit 0014c0c into scribe-org:main Jun 18, 2023
@andrewtavis andrewtavis mentioned this pull request Jun 18, 2023
2 tasks
@SaurabhJamadagni
Copy link
Collaborator Author

No problem on the wait @andrewtavis. Thank you so much! 😄

@andrewtavis andrewtavis mentioned this pull request Jun 19, 2023
2 tasks
@andrewtavis andrewtavis added the GSoC Available for Google Summer of Code participants label Aug 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GSoC Available for Google Summer of Code participants
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants