Hi guys, I'm new to this vibrant open source community. My story with Avro can be found here [1]
While implementing the feature, I got stuck and had various discussions with Dough Cutting, Fokko Driesprong.... You may see here [2] Here my (bias) observations about our current Avro 1.9.x: - Some improvements can't be made due to fear of backward incompatibilities. For example: specifications about named Union. - If `Apache Avro™ is a data serialization system.` then the repository `apache/avro` should solely focus on (de)serialization, right? Currently our repository contains many nice-to-have-but-not-critical things like: File I/O, Network I/O.... IMHO, I think: - We should publicly gather RFCs for Avro 2.x - We should move such nice things out of Avro 2.x (may be to other dedicated repositories) What do you think about my suggestions. Pls kindly let me know. Thank you & be strong. [1] My fork: https://github.com/anhldbk/avro-fork#why-this-fork [2] My opened issue: https://issues.apache.org/jira/browse/AVRO-2808?jql=reporter%3Danhldbk%20AND%20resolution%20is%20EMPTY
