Re: Process question

[David Luposchainsky via Haskell-prime]

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
Haskell-prime@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-prime

Re: GitHub proposal repo permissions

[David Luposchainsky via Haskell-prime]

On 12.10.2016 19:09, Iavor Diatchki wrote:
> could someone with access fix it, maybe David

I’m just a regular Haskell member (I think), Herbert gave me the access rights
and I didn’t run into any problems yet. Now that I’m back from my holidays I
guess I’m a bit late to answering your issue.

Anyway, I looked at the RFCS settings, and it seems like I could have added you.
Is the issue resolved, or should I give you permissions?

Greetings,
David

-- 
My GPG keys: https://keybase.io/quchen
___
Haskell-prime mailing list
Haskell-prime@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-prime

Re: Step-by-step guide for creating a new proposal

[David Luposchainsky via Haskell-prime]

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-by-step-instructions.md
> 
> Please have a look and let me know if something is unclear, or if I 
> misunderstood
> something about the process.

The target audience for this document is someone who is unfamiliar with Git and
Github, which we should make clear at the beginning. As an experienced user, it
left me searching for relevant information among all those sub-lists to find out
that it really just is about opening a pull request containing a template. We
might provide a link to the document in the process section [1] of the current
README if others think this amount of detail helps lowering the barrier of 
entry.

One thing we should also mention somewhere is to please provide a link to the
rendered version of the proposal in the ticket, because Git diffs are in a very
reader-unfriendly format.

Greetings,
David

[1]: https://github.com/yav/rfcs/tree/instructions#proposal-process


-- 
My GPG keys: https://keybase.io/quchen
___
Haskell-prime mailing list
Haskell-prime@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-prime

Re: New Github features and Haskell Prime

[David Luposchainsky via Haskell-prime]

I did not plan this out too much. I would say let's use common sense rather 
than setting up processes. The columns are to give viewers an overview for our 
open process.

Anyway, here's the gist behind the columns when I created them:

Pre-proposed is for things nobody cared enough about to write the proposal. The 
idea is that pull requests/proposals should be created from each. 

Proposed is where things start being tracked as actual proposals with rst files 
and what have you. These are invitations for everyone to participate in the 
discussion. 

In discussion is to single out the tickets with the most traffiic for those who 
want to get am overview of current events. When the discussion stalls the 
ticket might move back a column. 

Last call means that, ideally, every committee member (and whoever else is 
interested) should do a final proof-read of the proposal. Things in this column 
are considered good and final by the participants in the discussion before, and 
if there is no objection, that's what goes into the report. 

The last column is to show what made it into the report pipeline for some time 
for our less frequent readers. 

Greetings, 
David/quchen 


On 22 September 2016 19:43:12 CEST, M Farkas-Dyck  
wrote:
>I see we have a "Last call" column. What are its semantics? What are
>the criteria for moving an RFC into it? Once there, can the RFC be
>moved back out? Has it a time limit when an RFC there must be either
>merged or closed? How shall we choose whether to merge or close?
>
>If no one has an idea yet, i propose this:
>• A Committee member can move to nominate an RFC by making a comment
>to that effect. If no comments have been made on the RFC since,
>another member may then move the RFC to "Last call".
>• Once in "Last call", an RFC remains for 1 week while further
>comments can be made and committee members cast votes for either
>"Merge" or "Close". Open question: shall we vote openly in the
>comments or by some other system TBD?
>• At the end of the voting period, if a majority of the committee (not
>merely of those who voted) votes to merge or close, we do so; else we
>move the RFC back to "In discussion".
>
>I formulated this procedure so no one member could push an agenda
>unilaterally, but to break the stall in progress i have been feeling
>here. Alternative proposals welcome.

-- 
Sent from my cellphone. Please excuse my brevity.
___
Haskell-prime mailing list
Haskell-prime@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-prime

New Github features and Haskell Prime

[David Luposchainsky via Haskell-prime]

Hello prime people,

Github recently added a board-style overview over tickets and small notes. I
think this is a great addition, and converted all current PRs to board items.

There is no shortage of things to be considered for Haskell Prime, and I find it
hard to think of them all. For things I’m somewhat interested in seeing a
proposal for, I created notes that are not yet tickets, but serve as a reminder
to consider them at some point.

I’d like to invite you all to add your language extensions and ideas to the 
board
in the pre-proposal column. Even if you don’t have the time to write a proposal,
someone else might see the note and decide to do so instead.

See you at https://github.com/haskell/rfcs/projects/1

Greetings,
David/quchen



-- 
My GPG keys: https://keybase.io/quchen



signature.asc
Description: OpenPGP digital signature
___
Haskell-prime mailing list
Haskell-prime@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-prime

Re: Merging RFC pull requests

[David Luposchainsky via Haskell-prime]

On 10.08.2016 05:23, M Farkas-Dyck wrote:
> Who has authority to do so? Shall we vote whether to merge each?

The idea is that people talk about the proposals in the comments, and if we come
to an agreement on a proposal, we merge the PR. This isn’t set in stone, but I
felt like someone should get some form of process started, so I took a look at
how Rust is doing it, and here we are. :-)

David/quchen
___
Haskell-prime mailing list
Haskell-prime@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-prime