Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (athena.apache.org: domain of sealytics@gmail.com
 designates 209.85.220.53 as permitted sender)
MIME-Version: 1.0
Sender: sealytics@gmail.com
Date: Wed, 28 May 2014 13:08:20 +0200
Message-ID: 
 <CADXZZfsf5DrRS_SKNToirupd5aEVvsB3du0oN3BFafdi46fhgA@mail.gmail.com>
Subject: Survey on Project Conventions
From: Martin Brandtner <brandtner@ifi.uzh.ch>
To: dev@cloudstack.apache.org
Content-Type: multipart/alternative; boundary=047d7b15a6938c1f2a04fa73d40b

--047d7b15a6938c1f2a04fa73d40b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello

My name is Martin Brandtner [1] and I=E2=80=99m a software engineering rese=
archer
at the University of Zurich, Switzerland.
Together with Philipp Leitner [2], I currently work on an approach to
detect violations of project conventions based on data from the source code
repository, the issue tracker (e.g. Jira), and the build system (e.g.
Jenkins).

One example for such a project convention is: =E2=80=9CYou need to make sur=
e that
the commit message contains at least the name of the contributor and
ideally a reference to the Bugzilla or JIRA issue where the patch was
submitted.=E2=80=9D [3]

The idea is that our approach can detect violation of such a convention
automatically and therefore support the development process.

First of all we need conventions and that=E2=80=99s why we ask you to take =
part in
our survey. In the survey, we present five conventions and want you to rate
their relevance in your Apache project. Everybody contributing to your
Apache project can take part in this survey because we also want to see if
different roles may have different opinions about a convention.
The survey is totally anonymous and it will take about 15 minutes to answer
it.

We would be happy if you could fill out our survey under:
http://ww3.unipark.de/uc/SEAL_Research/1abe/ before June 13, 2014.

With the data collected in this survey we will implement a convention
violation detection in our tool called SQA-Timeline [4]. If your are
interested in our work, contact us via email or provide your email address
in the survey.

Best regards,
Martin and Philipp

[1] http://www.ifi.uzh.ch/seal/people/brandtner.html
[2] http://www.ifi.uzh.ch/seal/people/leitner.html
[3] http://www.apache.org/dev/committers.html#applying-patches
[4] https://www.youtube.com/watch?v=3DZIsOODUapAE

--047d7b15a6938c1f2a04fa73d40b--