📝 Defined a way to manage EinStack Glide project

[roma-glushko]

This is a proposal on how to manage EinStack projects using Github functionality for maximum visibility around what's going on.

The proposal includes:

• Dynamic roadmap based on GH projects (a new thing):

• Two types of issues: epics (an example of epic: 🔊 Setup OpenTelemetry #19) and tasks (was kind of that but now it's more explicit)
• A new priority:* to manage users expectations
• usage of milestones as release goals (doing that right now)

The new structure will hopefully help to answer the following questions:

• What's on Glide roadmap?
• What's on near term plans?
• What's left to finish some functionality?
• In what release goal (e.g. it's not necessary connected to exact versions, so we can have more granular releases) that functionality is going to land?

The structure helps to include epics from other repositories, comment on the epic or upvote it with emojis.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.98%. Comparing base (cf137da) to head (16435f4).

Additional details and impacted files

@@           Coverage Diff            @@
##           develop     #234   +/-   ##
========================================
  Coverage    66.98%   66.98%           
========================================
  Files           78       78           
  Lines         3577     3577           
========================================
  Hits          2396     2396           
  Misses        1054     1054           
  Partials       127      127           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[roma-glushko]

@gernest curious if you have any opinion on this 👀

[gernest]

LGTM.

[roma-glushko]

Okay, I think @mkrueger12 did not have chance to look at, but see not reason to block it. Will iterate on this idea if there are better options.