Add a mock project #3 to accomplish Microtask 1 for GSoD

[xiaoya-yaya]

This Pull Request is to add a mock project #3 to accomplish Microtask 1 for GSoD

---

name: Project Submission
about: Submit a project to be badged
title: 'Project Submission: {Mock Project #3}'
labels: project
assignees: ''

---

Project Submission

Communication Channels

Metric Question: How welcoming, responsive, respectful are interactions even on hot topics of debate? What is the diversity of voices speaking/being heard?

Q Are the communication channels of the project used to help create a diverse and inclusive project environment?

A Yes

Q If the previous answer is yes, how does the project create a diverse and inclusive environment in its communication channels?

A The project runs a mailing list for anyone who is interested and wants to communicate, official accounts on Facebook, Twitter and other social media to post lastest news and we have managers ready for any possible questions in the comments. We claim to welcome any participants and do not discriminate regards of race, sex, age or country.

Issue Tracker

Metric Question: How well does the project issue tracker setup to invite new contributors, skilled contributors, non-technical contributors?

Q Is the issue tracker used to invite new contributors, skilled contributors, and non-technical contributors?

A Yes

Q If the previous answer is yes, how does the project use an issue tracker?

A We use labels like "good first issue" to motivate newcomers.

Response Times & Quality

Metric Question: How quickly and well does the project respond to suggestions, PR'S, and questions?
Q
Q Is the response time of the project's administration, developers, or collaborators measured?

A No

Q If the previous answer is yes, what is the process for collecting and disseminating this data?

A At present we have not yet figure out a good solution to measure the time of response, but we will promote this aspect in the future.

Sentiment

Metric Question: What is the sentiment within external communication channels regarding our own press releases and within our internal communication channels?

Q Is the sentiment of the project's communication channels measured?

A Yes

Q If the previous answer is yes, what is the process for the sentiment of the communication channels?

A On our most important communication platform -- the project mailing list, each manager is required to make sure that every mail is to be answered, whether it's from a newcomer or a familiar member, whether the content of the mail requires an answer or just to say hi. The sentiment should be friendly, polite, and delightfully.

Documentation

Metric Question: What is the thoroughness, and accessibility of documentation according to a set of criteria?

Q (Screen Readers) Is the documentation accessible for screen readers?

A Yes

Q (Awareness) Is the documentation findable?

A Yes

Q (Clarity) Is the documentation easy to follow and structured intuitively?

A Yes

Q (Relevance) Is the documentation regularly updated?

A Yes

Q (Relevance) Are the environment builds up to date?

A Yes

Q (Non-Technical Accessibility) Does the documentation limit the use of unnecessary technical jargon?

A Yes

Q (Inclusion) Does the documentation avoid non-inclusive language? (this could be ‘brogrammer’ language or exclusionary/derogatory language)

A Yes

Q (FOSS standards) Do the README & CONTRIBUTING files provide intended information?

A Yes

Q Please provide a statement on the project's commitment to the promotion of Diversity and Inclusion through documentation.

A The project commits to the promotion of Diversity and Inclusion through documention.

Q Add more relevant information here.

A

[JackieBinya]

Hello @xiaoya-Esther
My name is Jacqueline Binya. I am a core contributor to the YY-Search.

These are some of my recommendations after going through your application:
To address
How welcoming, responsive, respectful are interactions even on hot topics of debate? What is the diversity of voices speaking/being heard? and How well does the project issue tracker setup to invite new contributors, skilled contributors, non-technical contributors?

• At YY-Search we have a contributing guide which includes a link to a Code of Conduct. The Contributing Guide is quite useful in on-boarding contributors of different levels of expertise to the project. Consequently we are then able to attract a more diverse pool of contributors. The Contributing Guide is written in an easy to understand manner and we made an effort to avoid use of unnecessary technical jargon. Its contents includes a general overview of the project, installation and set up guides as well as as basic contributing instructions.
• In the Contributing Guide the participants are explicitly advised to read the Code of Conduct and make sure they understand it before contributing. This has to some extent sanitized our communication channels, as in the Code of Conduct consequences in failing to comply are stipulated.

...