Bhack
June 14, 2021, 6:18pm
#1
Can we ask authors to announce new RFC PRs in the announcements section using the rfcs
tag?
2 Likes
lgusm
June 15, 2021, 9:39pm
#2
what do you think @Joana and @Marcus ?
1 Like
thea
July 13, 2021, 6:42pm
#4
Ditto, but one thing that’s important (for licensing and process reasons) is to direct specific design suggestions to the RFC itself in GitHub. This way all substantive comments are properly licensed and consolidated in a central place.
I’ll chat with the team to make sure if we implement this, we do so consistently (as was the case when announcing to developers@tensorflow.org ), and update the RFC process documentation in GitHub accordingly.
Bhack
July 13, 2021, 6:43pm
#5
If it is a “read-only” announcement post it is ok for me.
1 Like
Bhack
August 16, 2021, 1:00pm
#7
Could we start with this?
tensorflow:master
← iislucas:iislucas
opened 02:14PM - 31 Jul 21 UTC
This RFC will be open for comment until Friday, Sep 13, 2021.
cc @iislucas @p… yu10055
| Status | Proposed |
:-------------- |:---------------------------------------------------- |
| **RFC #** | [395](https://github.com/tensorflow/community/pull/395) |
| **Author(s)** | Lucas Dixon (ldixon@google.com) |
| **Sponsor** | Ping Yu (piyu@google.com) |
| **Updated** | 2021-08-12 |
## Objective
Support the naming of dimensions in TensorFlow JS to provide an abstraction that
makes it easier for developers and researchers to write and read ML algorithms
(and support some automated optimisation):
* Make it harder to make subtle mistakes (have type-checking get intelligible
type-error messages).
* Leveraging TypeScript IDE support to get better auto-completion.
* Make it easier to support writing an algorithm and then generalise it to
support batches.
* Have code more closely resemble the pseudocode and algorithms in papers.
* Allow machine optimization of the ordering of indexes, transpositions and
permutations.