Process question

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Process question

Iavor Diatchki
Hello,

Now that we've started with a few proposal, I am realizing that I have no idea how to proceed from here.  In particular:

1. How would I request I proposal to be rejected
2. How would I request that a proposal be accepted

Ideas?

-Iavor

_______________________________________________
Haskell-prime mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-prime
Reply | Threaded
Open this post in threaded view
|

Re: Process question

Mario Blazevic-2
On 2016-10-04 01:09 PM, Iavor Diatchki wrote:
> Hello,
>
> Now that we've started with a few proposal, I am realizing that I have
> no idea how to proceed from here.  In particular:
>
> 1. How would I request I proposal to be rejected
> 2. How would I request that a proposal be accepted

        I don't know if we need to fix the acceptance/rejection process so
early on. Once a new proposal is merged in, it need not be immediately
accepted or rejected. It could just collect comments and adjustments. I
see no point in voting for acceptance or rejection until the time comes
to prepare Haskell 2020.

        If my understanding of the process is correct, this raises two more
groups of questions.

1. I assume we'd use GitHub issues to discuss and/or point flaws in a
particular proposal?

1a. If so, it would be nice to group together all issues related to a
paricular proposal, but GitHub issues don't come with much metadata. Do
we prescribe some keyword that has to be specified in the subject of
each proposal-related issue?

1b. There could be a special "Accept me" issue for each proposal used
for tracking its status. GitHub issues can be assigned to milestones,
such as "Accepted for Haskell2020", "Last Call for Votes", "Awaiting
Comments", or "Work In Progress".

2. How do we prepare the actual Haskell 2020 language report? The report
is more than a collection of disparate proposals. The Haskell 2010
report also contains errors whose fixing shouldn't require writing up a
whole language proposal.

2a. Would the current text of the Haskell' language report be stored in
the same GitHub repository with the RFCs? If not, where else?

2b. Would we merge each proposal into the language report as soon as
it's accepted? Whose responsibility would this (largely mechanical)
process be?

_______________________________________________
Haskell-prime mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-prime
Reply | Threaded
Open this post in threaded view
|

Re: Process question

Richard Eisenberg-4
Does this GitHub feature help: https://github.com/haskell/rfcs/projects/1

After a proposal is accepted, then an individual (or small group) needs to write up the changes to the Report, which should then also go back through the larger committee.

And I’ll amplify some of Mario’s questions:

>
> 2. How do we prepare the actual Haskell 2020 language report? The report is more than a collection of disparate proposals. The Haskell 2010 report also contains errors whose fixing shouldn't require writing up a whole language proposal.
>
> 2a. Would the current text of the Haskell' language report be stored in the same GitHub repository with the RFCs? If not, where else?
>
> 2b. Would we merge each proposal into the language report as soon as it's accepted? Whose responsibility would this (largely mechanical) process be?

I think we should put the Report text in this separate repo. An accepted proposal is merged into the rfcs repo -- that is, the PR is accepted. Then a new PR can eventually be made to amend the text in the report repo.

Richard

> On Oct 5, 2016, at 10:50 AM, Mario Blažević <[hidden email]> wrote:
>
> On 2016-10-04 01:09 PM, Iavor Diatchki wrote:
>> Hello,
>>
>> Now that we've started with a few proposal, I am realizing that I have
>> no idea how to proceed from here.  In particular:
>>
>> 1. How would I request I proposal to be rejected
>> 2. How would I request that a proposal be accepted
>
> I don't know if we need to fix the acceptance/rejection process so early on. Once a new proposal is merged in, it need not be immediately accepted or rejected. It could just collect comments and adjustments. I see no point in voting for acceptance or rejection until the time comes to prepare Haskell 2020.
>
> If my understanding of the process is correct, this raises two more groups of questions.
>
> 1. I assume we'd use GitHub issues to discuss and/or point flaws in a particular proposal?
>
> 1a. If so, it would be nice to group together all issues related to a paricular proposal, but GitHub issues don't come with much metadata. Do we prescribe some keyword that has to be specified in the subject of each proposal-related issue?
>
> 1b. There could be a special "Accept me" issue for each proposal used for tracking its status. GitHub issues can be assigned to milestones, such as "Accepted for Haskell2020", "Last Call for Votes", "Awaiting Comments", or "Work In Progress".
>
> _______________________________________________
> Haskell-prime mailing list
> [hidden email]
> http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-prime

_______________________________________________
Haskell-prime mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-prime
Reply | Threaded
Open this post in threaded view
|

Re: Process question

Haskell - Haskell-prime mailing list
In reply to this post by Iavor Diatchki
On 04.10.2016 19:09, Iavor Diatchki wrote:
> Now that we've started with a few proposal, I am realizing that I have no idea
> how to proceed from here.

> 1. How would I request I proposal to be rejected

I think we should be discussing things, rather than inventing too many processes.
The number of people participating is still rather small, so verbally stating
that you’re strongly opposed to a feature (in principle or just in its current
form) is fairly visible.

> 2. How would I request that a proposal be accepted

Make yourself the shepherd of the proposal (assign yourself to it), make sure all
questions and concerns have been discussed, then send a “last call” style email
to the mailing lists or other public places you think should give it a final
thought? I think that sounds sensible.

David


--
My GPG keys: https://keybase.io/quchen
_______________________________________________
Haskell-prime mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-prime