Adding Licenses and Wikimedia & Scribe screens

[SaurabhJamadagni]

Contributor checklist

• This pull request is on a separate branch and not the main branch

---

Description

This PR adds the following:

• EN text files for Third-party licenses and Wikimedia & Scribe
• Adds required text formatting functions to retrieve correctly attributed strings with links and images wherever necessary.
• Pushes a new screen when the user selects the above menu items in the About section.
• Changes Z axis of text view and corner image so that text doesn't overlap with the image.
• Adds newline before first line of app texts to fix overlap.

Related issue

• Third-party licenses menu tab in about section #319
• Wikimedia and Scribe menu tab in about section #318

[github-actions]

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 as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

If you're not already a member of our public Matrix community, please consider joining! It'd be great to have you!

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

  • The contributor's name and icon in remote commits should be the same as what appears in the PR
  • If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for git config user.email in their local activist repo

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

[SaurabhJamadagni]

How often does this date get refreshed @andrewtavis? Should we update it?

Scribe-iOS/Scribe/AppTexts/English/ENPrivacyPolicy.swift

Line 68 in 6c15249

This POLICY is effective as of the 24th of May, 2022.

[andrewtavis]

@SaurabhJamadagni, if the text of the privacy policy hasn't been updated, then we're good to keep it as is 😊

[andrewtavis]

Will get to this in the coming days, @SaurabhJamadagni :) Am at a work retreat today and tomorrow 😊

[SaurabhJamadagni]

No problem @andrewtavis. Have a nice time at the retreat! 😄

[wkyoshida]

More my curiosity - I assume that yes, but we've checked the legal stuff for using Wikimedia logos/marks (question more for @andrewtavis perhaps)? My understanding is that this would fall under this section? I haven't read the entire document, but was curious on what Scribe has thought through as far as properly including Wikimedia logos/marks.

[andrewtavis]

This was something that was discussed as early as Data Reuse Days 2022 (my first Wikimedia event). It is strongly recommended that "reusers" of Wikidata and other Wikimedia projects directly cite where they get their information from. Wikidata is CC0, so you technically don't have to, but in conversations with Wikidata employees, editors and the general community they very much like to get recognition where possible. This is also why we have the "With data from Wikimedia" along with the Wikidata logo and Wikipedia logo on the screens for the App Store.

Legally speaking we'd fall within the section that you pointed out, @wkyoshida, but beyond that is a strong suggestion that we include the icon. There are "Powered by Wikidata" logos on the data access page, but then I'm not a big fan of those and chose to just go with the logos instead 🙃

[wkyoshida]

Awesome! 🚀 I was quite certain there must have been some prior conversation/recommendation from the community and was more just curious on how that had played out. Thanks for the comment! Exactly what I was wondering 👍

[andrewtavis]

All looks good to me, @SaurabhJamadagni! I made some minor comments and added some questions for next week's weekly, but it's all just spacing and coloration things that we can discuss as a team 😊 Nothing that would require changes and I want to make sure you can preserve your work flow.

Thanks for all this! Really is coming along nicely 🤩

[SaurabhJamadagni]

I made some minor comments and added some questions for next week's weekly, but it's all just spacing and coloration things that we can discuss as a team

Sounds good @andrewtavis! Looking forward to the discussion! Thanks for the review 😊

[andrewtavis]

Thanks for the codes, @SaurabhJamadagni! 😊