docs: Updated Roadmap document

[Golodhros]

Summary of Changes

Updates our roadmap document to remove already done items
Updates planned features and focus (biased by Lyft's roadmap)

Documentation

Updates the doc

CheckList

Make sure you have checked all steps below to ensure a timely review.

• PR title addresses the issue accurately and concisely, including a title prefix.
• PR includes a summary of changes.
• My commits follow the guidelines from "How to write a good git commit message"

[feng-tao]

@Golodhros I will take a look later today as well, but I think we should include some of the ongoing RFCs in https://github.com/amundsen-io/rfcs.

[feng-tao]

if we are only targeting table level lineage in short term, we may want to make it explicit.

[Golodhros]

I think we want both, and we have designs for both

[allisonsuarez]

thanks!

[feng-tao]

@Golodhros @allisonsuarez I don't think we include the one from @amundsen-io/rfcs ?

[Golodhros]

@Golodhros @allisonsuarez I don't think we include the one from @amundsen-io/rfcs ?

Which one? This https://github.com/amundsen-io/rfcs/blob/master/rfcs/002-databuilder-record-abstraction.md ?

[feng-tao]

amundsen-io/rfcs#10 and amundsen-io/rfcs#13, but let me create a sperate PR to include. Thanks @Golodhros !

[markgrover]

Thanks! While we are at it, should we include a minor update to the push API?
Say, something like:

Possible through [Kafka extractor](https://github.com/amundsen-io/amundsendatabuilder/blob/master/databuilder/extractor/kafka_source_extractor.py), though message format is not well defined. More work not planned.

Flexible here, thoughts?

[Golodhros]

amundsen-io/rfcs#10 and amundsen-io/rfcs#13, but let me create a sperate PR to include. Thanks @Golodhros !

Makes sense!

[Golodhros]

Thanks! While we are at it, should we include a minor update to the push API?
Say, something like:

Possible through [Kafka extractor](https://github.com/amundsen-io/amundsendatabuilder/blob/master/databuilder/extractor/kafka_source_extractor.py), though message format is not well defined. More work not planned.

Flexible here, thoughts?

Could you include this in your PR @feng-tao ?

[feng-tao]

sure