GithubHelp home page GithubHelp logo

icsme16's People

Contributors

ai4se avatar celiache8 avatar grammarware avatar mathew-hall avatar mcmillco avatar monarahimi avatar obaysal avatar timm avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Forkers

leonardpunt

icsme16's Issues

register users

  • gustavopinto
  • grammarware
  • mathew-hall
  • celiache8
  • cmcmil
  • MonaRahimi
  • obaysal
  • timm

Olga check new words for icsme website

As is:

How to Submit

Submissions must be formatted according to the ICSME 2016 Formatting Instructions. Papers must not exceed 2 pages (including all text, references, and figures) plus up to 10 pages that contain ONLY the artifact listing(s). All submissions must be in PDF and must be submitted online by the deadline via the ICSME 2016 Artifacts Track EasyChair conference management system.

Submission is limited to one per author. Submissions are open to all, but we especially encourage ICSME 2016 authors to offer interesting parts of their work as artifacts. Submissions must not be verbatim materials presented at other venues without or within ICSME 2016 (e.g., it is not permitted to submit the same thing to the ICSME 2016 tool demonstrations track and to the artifacts track). That said, it is valid to submit some augmented part of an ICSME 2016 submission (e.g., scripts used to generate results for an ICSME 2016 research track paper).

As discussed in the list of known research artifact types, many research artifacts are shorter than a paper. While we also encourage submissions longer than a paper (e.g., scripts, datasets, executables, virtual images), the track chairs reserve the right to reject without review overly long submissions. If in doubt, email the chairs ([email protected] and [email protected]) prior to submission.


To be:

How to Submit, and the Review Process

Write a pdf submissions using the ICSME 2016 Formatting Instructions. This submission would include two (1+1) pages:

  1. First page: Describe the artifact along the dimensions of the scorecard (i.e., Insightful, Useful, Usable). Refer to the Evaluation criteria (at http://www.cs.ucdavis.edu/fse2016/calls/artifacts/). This page will be used to evaluate your artifact.
  2. Second page: Describe the artifact and how one can use it (mention about any difficulties one might encounter in using the artifact, or its maturity relative to the content of the paper). This page will be used in the proceedings and you will append it to your research paper once the artifact is accepted. The description of the artifact for the proceedings must not exceed 1 page (including all text, references, and figures).

Write a pdf submissions using the ICSME 2016 Formatting Instructions. Papers must not exceed 1 page (including all text, references, and figures). Make the name of that pdf “XXX_YYY.pdf”, where XXX is the last name of the corresponding author and YYY is some short name for the artifact.

Get a GitHub account and email that name to [email protected] with the subject line: “ICSME16 artifacts track, add my account to the repository.”

Our reply to you will point to a GitHub repository and a directory for submissions. Drag and drop your pdf onto that directory.

Create an issue in that repository whose title is the XXX_YYY. Do not add any text to the comment.

Review of the artifacts will be conducted in GitHub where reviewers’ feedback will be public.

olga: please check invite words

olga:

please check i have not cross-pollinated ICSME with any FSE references

note also that our artifacts page has NOT updated yet. so i have sent a hurry up to titus and propose we move our deadline back to june 30.

t


Dear ICMSE'16 Author,

Congratulations on the acceptance of your work to ICSME'16. This email is to invite you to submit to the ICSME'16 Artifacts track. Submissions are due June 30.

Note that at ICSME'16 an "artifact" can be many things.

  • For example, executable code could be presented at the demos track (which works best for something with an impressive first impression) or the artifacts track (if the main value of the code is some more nuanced point).
  • Also one research paper may contain many artifacts (literature review, comments on best statistical methods, etc). So your accepted ICSME'16 paper could actually contain numerous separate artifacts that merit submission to this track.
  • For a full list of artifact types, see our https://github.com/researchart/all/blob/master/ListOfArtifacts.md

WHAT TO SUBMIT:

Your submission must be one pdf file containing the following two pages:

First page: Describe the artifact along the dimensions of the scorecard (i.e., Insightful, Useful, Usable). Refer to the Evaluation criteria "Insightful", "Useful", "Usable" at http://icsme2016.github.io/cfp/artifacts-track.html.

Second page: Describe the artifact and how one can use it (mention about any difficulties one might encounter in using the artifact, or its maturity relative to the content of the paper). This page will be used in the proceedings and you will append it to your research paper once the artifact is accepted. This description of the artifact for the proceedings must not exceed 1 page (including all text, references, and figures).

HOW TO SUBMIT

Write a pdf submissions using the ICSME 2016 Formatting Instructions.
This submission would include two (1+1) pages:

  1. First page: Describe the artifact along the dimensions of the
    scorecard (i.e., Insightful, Useful, Usable). Refer to the Evaluation
    criteria (at http://www.cs.ucdavis.edu/fse2016/calls/artifacts/). This
    page will be used to evaluate your artifact.
  2. Second page: Describe the artifact and how one can use it (mention
    about any difficulties one might encounter in using the artifact, or
    its maturity relative to the content of the paper). This page will be
    used in the proceedings and you will append it to your research paper
    once the artifact is accepted. The description of the artifact for the
    proceedings must not exceed 1 page (including all text, references,
    and figures).

HOW TO SUBMIT

  1. Write the 2 page pdf submissions described above using the ICSME 2016 Formatting Instructions.
  2. Make the name of that pdf “XXX_YYY.pdf”, where XXX is the
    last name of the corresponding author and YYY is some short name for
    the artifact.
  3. Get a GitHub account and email that name to
    [email protected] with the subject line: “ICSME16
    artifacts track, add my account to the repository.”
  4. Our reply to you will point to a GitHub repository and a directory for
    submissions. Drag and drop your pdf onto that directory.
  5. Create an issue in that repository whose title is the XXX_YYY. Do not
    add any text to the comment.
  6. Review of the artifacts will be conducted in GitHub where reviewers’
    feedback will be public.

We look forward to your submission.

Regards,
Olga Baysal,Tim Menzies
(co-chairs, ICSME artifact track).

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.