collecting data for a specific head branch ~

[CodeDotJS]

Based on the discussion and what we intend to do, the collection of the specific amount of data matters. The whole idea is to limit the extra fields so that things can stay on one road for the sake of development.

I think, for now, instead of creating a more diverse list of parent topics, let's choose one topic as a base and create a prototype of the idea.

If we spend some time and find at least 2-5 mentors (even one) for each topic mentioned below, we'll have a base (~45-90 mentors) to start the development of the project. (What you think?)

Computer Science

Mathematical foundations

• Coding theory
• Game theory
• Graph theory
• Mathematical logic methods
• Number theory

Algorithms and data structures

• Algorithms
• Data structures

Artificial intelligence

• Artificial intelligence
• Automated reasoning
• Computer vision
• Machine learning
• Evolutionary computing
• Natural language processing
• Robotics

Communication and security

• Networking
• Computer security
• Cryptography

Computer architecture

• Computer architecture
• Operating systems

Computer graphics

• Computer graphics
• Image processing
• Information visualization

Concurrent, parallel, and distributed systems

• Parallel computing
• Concurrency (computer science)
• Distributed computing

Databases

• Relational databases – the set-theoretic and algorithmic foundation of databases.
• Structured Storage - non-relational databases such as NoSQL databases.
• Data mining – Study of algorithms for searching and processing information in documents and
• databases; closely related to information retrieval.

Programming languages and compilers

• Compiler theory
• Programming language pragmatics
• Formal semantics
• Type theory

Scientific computing

• Computational science
• Numerical analysis
• Symbolic Computation
• Computational physics
• Computational chemistry
• Bioinformatics and Computational Biology
• Computational neuroscience – Computational modelling of neurophysiology.

Software engineering

• Formal methods
• Software engineering
• Algorithm design
• Computer programming
• Human-computer interaction

[geekodour]

Great work on curating these subtopics.

I think, for now, instead of creating a more diverse list of parent topics, let's chose one topic as a base and create a prototype of the idea.

Correct, We cannot assume the number of subtopics or topics. To make our initial work even easier, I think it will be best to find 5 people each in computer science and add them and then tag them with the topics/subtopics.

Or we can find people by topics ourselves like you mentioned by googling, twitter whatever (this is what this project aims to solve)

This is similar to #2 closing #2.

[geekodour]

MVP and the thought process for a user of this project:

• Be working/studying in ABC domain
• Hey I think X should be added in this directory because he/she knows so much about XYZ in the ABC domain.
• Search if X is already in the reachout directory
• If not, submit info about X in the described format.
  • Sumbit it using PR
  • Sumbit it using email
• Bots verify static information and generates and validates the entry
• Create a pending entry for X to be added in the directory.
• Once verified by mods(humans), X is added to the directory.

Notes:

• I don't think we should be manually creating intial files/directories/entries of the same format for the mentors. Can result in human error, also will be tedious to maintain. I don't think automating the entry process will be a premature optimization.
• Manually creating and editing files/directories using PRs will always be allowed though.

[CodeDotJS]

I've got some questions and points in my mind, but I didn't sleep since yesterday. More updates when I wake up.

[CodeDotJS]

Could be useful? ~ Awesome OSS Mentors