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

[Carter Schonwald]

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 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, contributing
>> entirely
>>   new issues is currently limited to the members of the Core Language
>> Committee.
>> + If you want to create entirely new issue, privately talk with member of
>> the
>> + committee or ask on haskell-prime mailing list.
>>
>> I think that non-member will understand pre-process :)
>>
>> Regards,
>> Takenobu
>>
>>
>> 2016-10-06 23:38 GMT+09:00 Carter Schonwald :
>>
>>> 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 :)
>>>
>>>
___
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

[Carter Schonwald]

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 at README.rst as following?
> (It's simpler than PR.)
>
> [README.rst]
>   While the process is open for everyone to participate, contributing
> entirely
>   new issues is currently limited to the members of the Core Language
> Committee.
> + If you want to create entirely new issue, privately talk with member of
> the
> + committee or ask on haskell-prime mailing list.
>
> I think that non-member will understand pre-process :)
>
> Regards,
> Takenobu
>
>
> 2016-10-06 23:38 GMT+09:00 Carter Schonwald  >:
>
>> 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 :)
>>
>>
___
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

[Takenobu Tani]

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, contributing
entirely
  new issues is currently limited to the members of the Core Language
Committee.
+ If you want to create entirely new issue, privately talk with member of
the
+ committee or ask on haskell-prime mailing list.

I think that non-member will understand pre-process :)

Regards,
Takenobu


2016-10-06 23:38 GMT+09:00 Carter Schonwald :

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

[Haskell] ETAPS 2017 final call for papers

[Tarmo Uustalu]

**

JOINT CALL FOR PAPERS

20th European Joint Conferences on Theory And Practice of Software
 ETAPS 2017

   Uppsala, Sweden, 22-29 April 2017

   http://www.etaps.org/2017

**

-- ABOUT ETAPS --

ETAPS is the primary European forum for academic and industrial
researchers working on topics relating to software science. ETAPS,
established in 1998, is a confederation of five main annual
conferences, accompanied by satellite workshops. ETAPS 2017 is the
twentieth event in the series.


-- MAIN CONFERENCES (24-28 April) --

   * ESOP: European Symposium on Programming
   (PC chair Hongseok Yang, University of Oxford, UK)
   * FASE: Fundamental Approaches to Software Engineering
   (PC chairs Marieke Huisman, Universiteit Twente, The Netherlands,
and Julia Rubin, University of British Columbia, Canada)
   * FoSSaCS: Foundations of Software Science
   and Computation Structures
   (PC chairs Javier Esparza, Technische Universität München, Germany,
Andrzej Murawski, University of Warwick, UK)
   * POST: Principles of Security and Trust
   (PC chairs Matteo Maffei, Universität des Saarlandes, Germany,
Mark D. Ryan, University of Birmingham, UK)
   * TACAS: Tools and Algorithms for
   the Construction and Analysis of Systems
   (PC chairs Axel Legay, INRIA Rennes, France,
and Tiziana Margaria, LERO, Ireland)

TACAS '17 hosts the 6th Competition on Software Verification
(SV-COMP).


-- INVITED SPEAKERS --

   * Unifying speakers:
 Michael Ernst (University of Washington, USA)
 Kim G. Larsen (Aalborg University, DK)

   * FoSSaCS invited speaker:
 Joel Ouaknine (University of Oxford, UK)
   * TACAS invited speaker:
 Dino Distefano (Facebook and Queen Mary University of London, UK)


-- IMPORTANT DATES --

   * Abstracts due (ESOP, FASE, FoSSaCS, TACAS): 14 October 2016
   * Papers due: 21 October 2016
   * Rebuttal (ESOP and FoSSaCS only): 7-9 December 2016
   * Notification: 22 December 2016
   * Camera-ready versions due: 20 January 2017


-- SUBMISSION INSTRUCTIONS --

ETAPS conferences accept two types of contributions: research papers
and tool demonstration papers. Both types will appear in the
proceedings and have presentations during the conference.

ESOP and FoSSaCS accept only research papers.

A condition of submission is that, if the submission is accepted, one
of the authors attends the conference to give the presentation.

Submitted papers must be in English presenting original research. They
must be unpublished and not submitted for publication elsewhere (this
does not apply to abstracts). In particular, simultaneous submission
of the same contribution to multiple ETAPS conferences is
forbidden. The proceedings will be published in the Advanced Research
in Computing and Software Science (ARCoSS) subline of Springer's
Lecture Notes in Computer Science series.

Papers must follow the formatting guidelines specified by Springer at
the URL

   http://www.springer.de/comp/lncs/authors.html

and be submitted electronically in pdf through the EasyChair author
interface of the respective conference.

Submissions not adhering to the specified format and length may be
rejected immediately.

FASE will use a light-weight double-blind review process (see
http://www.etaps.org/2017/fase).


- Research papers

FASE, FoSSaCS and TACAS have a page limit of 15 pp (excluding
bibliography of max 2 pp) for research papers, whereas POST allows at
most 20 pp (excluding bibliography of max 2 pp) and ESOP 25 pp
(excluding bibliography of max 2 pp).

Additional material intended for the referees but not for publication
in the final version - for example, details of proofs - may be placed
in a clearly marked appendix that is not included in the page
limit. ETAPS referees are at liberty to ignore appendices and papers
must be understandable without them.

In addition to regular research papers, TACAS solicits also case study
papers (at most 15 pp, excluding bibliography of max 2 pp).

Both TACAS and FASE solicit also regular tool papers (at most 15 pp,
excluding bibliography of max 2 pp).

The rationale of a separate page limit for the bibliography is to
remove the possibility to win space for the body of a
paper by cutting the bibliography, a practise that has a negative
effect on our competitiveness as a community.


- Tool demonstration papers

Submissions should consist of two parts:

* The first part, at most 4 pages, should describe the tool
   presented. Please include the URL of the tool (if available) and
   provide information that illustrates the maturity and robustness of
   the tool. (This part will be included in the proceedings.)

* The second part, at most 6 pages, should explain how the
   demonstration will be carried out and what it will