[Haskell] FedCSIS 2019 - CALL FOR EVENTS

[Federated Conference on Computer Science and Information Systems]

Call for Events
Federated Conference on Computer Science and Information Systems

Leipzig, Germany, 1-4 September, 2019
www.fedcsis.org <http://www.fedcsis.org/>

The 2019 Federated Conference on Computer Science and Information 
Systems cordially invites you to consider contributing an Event 
(conference, symposium, workshop, consortium meeting, project 
dissemination meeting, special session, etc.). The FedCSIS 
multi-conference consists of a significant number of recurring Events 
and it welcomes proposals for new Events until November 20, 2018. The 
Events can run over any span of time within the conference dates; from 
half-day to three days. Invitation is extended also to existing events 
that would like to join the vibrant FedCSIS ecosystem.

The FedCSIS Events provide a platform for bringing together researchers, 
practitioners, and academia to present and discuss ideas, challenges, 
and potential solutions on established or emerging topics related to 
research and practice in computer science and information systems.

The Events will be selected based on the scientific/technical interest 
and/or their relevance to practitioners in their topics, the clarity of 
the proposal in addressing the requested information, the innovativeness 
of the Event topics, and the fit with the FedCSIS multi-conference program.

The FedCSIS 2018 – held in Poznań, Poland – attracted 349 papers, of 
which 74 were accepted as regular full papers (acceptance rate of 
approximately 21%). Some events accepted additionally regular short, 
position and communication papers. FedCSIS 2018 regular full and short 
papers are being submitted to the IEEE Xplore Digital Library, while 
position and communication papers have been published in a separate 
volumes of the Annals of Computer Science and Information systems 
series. Regular and short papers are submitted for indexation in 
Clarivate Web of Science (where they have been indexed since 2012), as 
well as to other indexing services, e.g. Scopus, DBLP, etc.


Publications

As in previous years, FedCSIS preprints will be published on a USB 
memory stick given to FedCSIS participants. *Only* papers presented 
during the conference will be submitted to the IEEE Xplore Digital 
Library (or will appear as position papers, published in a separate 
volume, which will not be submitted to the IEEE), and posted at the 
conference WWW site. The IEEE DL proceedings will be published with an 
ISBN, ISSN, IEEE Catalog and DOI numbers, under a nonexclusive 
copyright. Such copyright implies that Events' organizers can and, 
indeed, are strongly encouraged to invite extended and revised papers 
for post-conference publications in high-quality journals, edited 
volumes, etc. Position and Communication Paper volumes (separate as each 
category) will be published with ISBN, ISSN and DOI numbers.



Event Proposals

Event proposals should include the following information (2 pages maximum):

1.The nature of the Event.

2.The title of the Event, and a clear description of the topic, 
including a brief justification.

3.The complete contact information of the Event organizers, including a 
link to their personal websites, and an overview of previous experiences 
with organization of scientific events.

4.Preliminary list of PC members who have agreed to join.

5.Indication of the expected number of papers/attendees to attend the 
Event.

6.Information of expected post-Event publications, of extended and 
revised papers, in high-quality journals, edited volumes, etc.

Event organizers should email their proposals (in a single pdf file) by 
November 20, 2018 to the FedCSIS Secretariat at: secretariat at fedcsis.org 
<mailto:secretariat at fedcsis.org>

More information concerning Event organization can be found at:
http://www.fedcsis.org/cfe

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/haskell/attachments/20181104/abac579a/attachment-0001.html>