Added Open Discussions section; included hyperlink references.

[darrensapalo]

In response to #11

Change 1: Open Discussions section

Proposing to include a new section under the call notes called "Open Discussions" which are items which are discussed in the community calls, but do not result into a resolution/decision.

Having this section will allow core team members to not miss out on topics that were left unresolved.

Change 2: Including hyperlinks

For dApp developers who are unfamiliar with the web 3.0 scene, certain terminologies, and who the different actors are (Jito, Mango, etc.) providing hyperlinks that point to reference materials that introduces them would be helpful.

Additionally, I think creating an ELI5 wiki that include the terminologies and concepts would make understanding the topics discussed in the core community call more accessible.

I think that is inline with what Dan Albert mentions:

Dan Albert: There's been a lot of calls for action from inside of the community of what I see is more people wanting, I'll say read access and then write access for the Solana protocol. Read access being there's a lot of teams core devs and non-core devs that want better visibility into what's coming down the line, how is this going to impact me, particularly like RPC operators, or Dapp developers that are going to be impacted by any breaking changes. [...] it's something that as the core developer Community, I think we can do a better job of communicating.

---

Please let me know if you guys have suggestions. I'm improving the readability of the notes as I go through and listen to the community calls because that's what I'm able to do (for now) as I study Rust, Anchor, and general web 3.0 things.