I'll have some down time at the airport this afternoon and see about
dealing with this
On Friday, October 7, 2016, Carter Schonwald
wrote:
> Sounds good to me unless anyone objects or has an alternative?
>
> On Friday, October 7, 2016, Takenobu Tani > wrote:
>
>> GHC proposal process is active
Sounds good to me unless anyone objects or has an alternative?
On Friday, October 7, 2016, Takenobu Tani wrote:
> GHC proposal process is active at same time.
> To avoid confusion about starting process, it's good that pre-starting
> process is written somewhere.
>
> What about directly writing
GHC proposal process is active at same time.
To avoid confusion about starting process, it's good that pre-starting
process is written somewhere.
What about directly writing at README.rst as following?
(It's simpler than PR.)
[README.rst]
While the process is open for everyone to participate, c
Hrmm, I guess I shall have to do my first pr, unless anyone else thinks we
should tweet this clarification slightly? But i suppose that can be on the
pr :)
On Thursday, October 6, 2016, Takenobu Tani wrote:
> Thank you for your kind explanation.
>
> I understood that accountability of a proposal
Thank you for your kind explanation.
I understood that accountability of a proposal (github PR) is very
important.
If it doesn't exist, the github proposal repo may become a collection of
"throw-out" PRs.
It's reasonable for me that only committee members can create PRs.
In my understanding from
I guess the question is what is the definition of issue in that context?
Whatever the specifics, I think if you either
a) privately talk with a memeber of the committee about what you intend to
do and they are willing to "co own" / "sponsor it", and this is indicated
in the pr summary or the like
Dear Iavor,
Members of non prime-commitiee could send pull-request?
README.rst [1] is written as follows:
> While the process is open for everyone to participate, contributing
entirely new issues is currently limited to the members of the Core
Language Committee.
[1]: https://github.com/haske
OK, I put a section at the top saying that, and then summarizing the
process for people who are familiar with the tools. I also updated the
last list to say that you should add a link to the rendered version and how
to do it.
On Tue, Oct 4, 2016 at 8:40 AM, David Luposchainsky via Haskell-pr
On 04.10.2016 01:27, Iavor Diatchki wrote:
> During our Haskell Prime lunch meeting at ICFP, I promised to create a
> detailed
> step-by-step guide for creating Haskell Prime proposals on GitHub. The
> instructions are now available here:
>
> https://github.com/yav/rfcs/blob/instructions/step-b
Hello,
During our Haskell Prime lunch meeting at ICFP, I promised to create a
detailed step-by-step guide for creating Haskell Prime proposals on
GitHub. The instructions are now available here:
https://github.com/yav/rfcs/blob/instructions/step-by-step-instructions.md
Please have a look and l
10 matches
Mail list logo