virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Ming Zhao <zhaom@cis.fiu.edu>
Subject: Call for Workshops: 2nd International Conference on Cloud Computing (CloudComp2010)
Date: Sun, 28 Mar 2010 16:57:22 -0400	[thread overview]
Message-ID: <4BAFC2B2.5080701@cis.fiu.edu> (raw)

[Apologies if you receive multiple copies of this announcement]



Update:
-------

* Workshop proposal submission deadline is extended to March 31





========================================================================
CLOUDCOMP 2010 CALL FOR WORKSHOP PROPOSALS

The 2010 International Conference on Cloud Computing (CloudComp 2010)
will be held in Barcelona, Spain, from Monday 25th to Friday 29th
October 2010. Workshops will be held on Friday 29th October 2010

We invite proposals for workshops and tutorials. Workshops are
intended to provide a platform for presenting novel ideas in a less
formal and possibly more focused way than is possioble in the main
conference. Organisers are free to set the format for workshops in
order to best fit the theme. We will include full- or half-day
workshops in the programme.

Tutorials are intended to be more directed at learning, for graduate
and industrial audiences, of technologies and techniques appropriate
to the conference. We especially welcome tutorial proposals by
practitioners in significant fields, or tutorials that present
cross-disciplinary approaches to cloud computing. We expect tutorials
to be half-day only.

Please submit proposals to the CloudComp 2010 Workshop Chair, Simon
Dobson (cloudcompws2010@icst.org). Proposals should be by email (PDF or 
plain text) with "CloudComp" in the subject header. The deadlines for 
submissions are:

- Workshops: 0700 UTC Wednesday 31st March 2010
- Tutorials: 0700 UTC Wednesday 21st July 2010

Notifications of acceptance will be sent out no more than two weeks
after the submission deadline. Both workshop and tutorial proposals
should include:

  1. The name of the workshop or tutorial.
  2. A statement of goals oals and/or learning outcomes.
  3. The names and affiliations of the organisers.
  4. The names of programme committee members, presenters or keynote 
speakers.
  5. A draft call for participation
  6. The expected number of attendees and the planned length (full- or 
half-day).
  7. A description of the plans for publicity.
  8. An explanation of any plans for proceedings or learning materials.
  9. A description of past versions of the event, including dates,
     organisers, submission and acceptance counts, attendance, sites,
     registration fees and summary budget information, if any.
10. The URL of the workshop or tutorial web site, if available.

Please forward any questions to Simon Dobson at cloudcompws2010@icst.org.






-- 
Ming Zhao, Assistant Professor
School of Computing and Information Sciences
Florida International University
Tel: (305) 348-2034, Fax: (305) 348-3549
Web: http://www.cis.fiu.edu/~zhaom

                 reply	other threads:[~2010-03-28 20:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BAFC2B2.5080701@cis.fiu.edu \
    --to=zhaom@cis.fiu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).