reactiveui
/
rfcs
зеркало из
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность

Changed Ember to ReactiveUI 

There were a couple that were missed.
This commit is contained in:
Stephen Price 2018-05-12 00:42:55 +08:00 коммит произвёл GitHub
Родитель afd1d96f30
Коммит b34205217f
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4AEE18F83AFDEB23
1 изменённых файлов: 2 добавлений и 2 удалений
Показать статистику Скачать Patch файл Скачать Diff файл Показать все файлы Свернуть все файлы

4
README.md
Просмотреть файл

@ -4,7 +4,7 @@ Many changes, including bug fixes and documentation improvements can be
implemented and reviewed via the normal GitHub pull request workflow. implemented and reviewed via the normal GitHub pull request workflow.
Some changes though are "substantial", and we ask that these be put Some changes though are "substantial", and we ask that these be put
through a bit of a design process and produce a consensus among the Ember through a bit of a design process and produce a consensus among the ReactiveUI
core team. core team.
The "RFC" (request for comments) process is intended to provide a The "RFC" (request for comments) process is intended to provide a
@ -86,7 +86,7 @@ become 'active'.
## The RFC life-cycle ## The RFC life-cycle
Once an RFC becomes active then authors may implement it and submit the Once an RFC becomes active then authors may implement it and submit the
feature as a pull request to the Ember repo. Becoming 'active' is not a rubber feature as a pull request to the ReactiveUI repo. Becoming 'active' is not a rubber
stamp, and in particular still does not mean the feature will ultimately stamp, and in particular still does not mean the feature will ultimately
be merged; it does mean that the core team has agreed to it in principle be merged; it does mean that the core team has agreed to it in principle
and are amenable to merging it. and are amenable to merging it.