public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Arnaud Hubaux <ahu@info.fundp.ac.be>
To: ecos-devel@ecos.sourceware.org, ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Study on conflict resolution with configtool
Date: Sat, 13 Aug 2011 15:09:00 -0000	[thread overview]
Message-ID: <E8B62E65-9F74-49BA-80F8-046040C1E4F7@info.fundp.ac.be> (raw)
In-Reply-To: <5B9868D5-EFDD-416B-B8F4-1118EE9BFB66@info.fundp.ac.be>

Dear eCos users,

several of you asked us whether the study is limited to configtool (GUI). The answer is no: it also includes ecosconfig (command-line). If you have experience with either of them, your input is most welcome: https://docs.google.com/spreadsheet/viewform?formkey=dDhrRmNVZ3NQMmMyNTU0RjBQOHg4eEE6MQ

Thank you.

On 11 Aug 2011, at 10:03, Arnaud Hubaux wrote:

> Dear eCos user, 
> 
> we are a team of researchers from the GSD Lab of the University of Waterloo (ON, Canada). We do research on configuration methods and algorithms and are conducting a study on the problems faced by users during conflict resolution with configtool. We would greatly appreciate it if you could answer the 17 questions in the following questionnaire: https://spreadsheets.google.com/spreadsheet/viewform?formkey=dDhrRmNVZ3NQMmMyNTU0RjBQOHg4eEE6MQ
> 
> The whole questionnaire should not take you more than 15 minutes to complete. 
> 
> Thank you very much for your contribution. 
> 
> Arnaud Hubaux, University of Namur/University of Waterloo
> Yingfei Xiong, University of Waterloo 
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      reply	other threads:[~2011-08-13 15:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 14:03 Arnaud Hubaux
2011-08-13 15:09 ` Arnaud Hubaux [this message]

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=E8B62E65-9F74-49BA-80F8-046040C1E4F7@info.fundp.ac.be \
    --to=ahu@info.fundp.ac.be \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).