You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Create a specification/ for .md documents with what we agreed upon #302
I would like to propose that we create a directory specification/ where we drop .md files that result from the discussions we have over google docs, so that they are given the proper visibility in this repository.
We would continue to use google docs to iterate on them. Once ready, I propose to PR them to this repo.
Reasons:
Licensing: the work on them imo should remain ASF-licensed
visibility: we have a simple place where we can refer to
easier to contribute: it is easy propose changes to those documents
audit: changes to those documents are properly versioned, specially after we "agreed" on them
Reacted by QP Hou, Daniël Heres and Sathis Kumar Muthusamy
I think it is a great idea. I vaguely remember that Fernando suggested a more full featured version of a process to create the documents as well, but perhaps starting with recording the docs we do make is a good step towards formalizing the process more
Activity
jorgecarleitao commentedon May 10, 2021
Any thoughts @alamb @andygrove @houqp @Dandandan @nevi-me ?
houqp commentedon May 10, 2021
+1000, could we also serve them as part of datafusion's user/developer documentation?
Dandandan commentedon May 10, 2021
I think it is a good idea. What about using the term RFC?
alamb commentedon May 10, 2021
I think it is a great idea. I vaguely remember that Fernando suggested a more full featured version of a process to create the documents as well, but perhaps starting with recording the docs we do make is a good step towards formalizing the process more
In other words, 👍
fix: Iceberg scan transition should be in front of other data source …