Skip to content

Solution (#62): Scribe-Android Outreach 👋🚀#656

Closed
TFGSUMIT wants to merge 1 commit into
scribe-org:mainfrom
TFGSUMIT:fix/issue-62
Closed

Solution (#62): Scribe-Android Outreach 👋🚀#656
TFGSUMIT wants to merge 1 commit into
scribe-org:mainfrom
TFGSUMIT:fix/issue-62

Conversation

@TFGSUMIT

Copy link
Copy Markdown

"PR: Implement Outreach Module for Scribe-Android App

This PR adds an outreach module to the Scribe-Android app, allowing users to post on social media, forums, and language institutions. The module is implemented using a modular approach, with separate classes for each outreach platform.

Changes:

  • Added Constants class for centralized outreach URLs
  • Added OutreachManager class for managing posting logic
  • Added OutreachSocialMedia, OutreachForums, and OutreachLanguageInstitutions classes for specific outreach platforms
  • Added OutreachUtils class for accessing outreach URLs
  • Updated MainActivity to demonstrate usage of outreach module

Testing:

  • Run ./gradlew test to execute JUnit tests
  • Verify that posting on each platform works correctly

Review and merge when ready!"

@github-actions

Copy link
Copy Markdown

Thank you for the pull request! 💙

The Scribe-Android team will do our best to address your contribution as soon as we can. The following are some important points:

  • Those interested in developing their skills and expanding their role in the community should read the mentorship and growth section of the contribution guide
  • If you're not already a member of our public Matrix community, please consider joining!
    • We'd suggest that you use the Element client as well as Element X for a mobile app
    • Join the General and Android rooms once you're in
  • Also consider attending our bi-weekly Saturday developer syncs!
    • Details are shared in the General room on Matrix each Wednesday before the sync
    • It would be great to meet you 😊

Note

Scribe uses Conventional Comments in reviews to make sure that communication is as clear as possible.

@github-actions

Copy link
Copy Markdown

Maintainer Checklist

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 :)

  • Tests for changes have been written and the unit test, linting and formatting workflows within the PR checks do not indicate new errors in the files changed

    • Tests may need to be reran as they're at times not deterministic
  • The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

First PR Commit Check

  • 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 Scribe-Android repo (can be set with git config --global user.email "GITHUB_EMAIL")

@andrewtavis

Copy link
Copy Markdown
Member

Closing as this is doesn't solve the "issue" which is more of a discussion in a convenient place. Appears to be agentic with no reflection on the output.

@TFGSUMIT, please consider the ramifications of how you choose to code. You've wasted the community's time and your own with this. Reading the issue and checking your results before sending them is the least that an open-source project can ask for, and you haven't even done that here.

Coding is fun and you don't need AI to do it for you. Read the docs, do some tutorials, put in the work and solve interesting problems with your own problem solving skills that you develop along the way :)

Cheers 👋

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants