[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] Issues and questions related to contribution metrics dashboard for XAPI and Mirage OS



Thomas,
thanks for the info. Instructed Santiago to do this
Lars

On 02/04/2014 14:19, Thomas Sanders wrote:

(Removing mirageos-devel list from recipients list since this is only about xapi.)

Â

Thatâs right, Lars.

Â

I think it probably makes most sense to count vncterm in XenServer metrics but not XAPI metrics.

Â

The final set of five that are forked from unrelated upstream projects should have a sixth added:

xen-unstable-mirror git://github.com/xapi-project/xen-unstable-mirror.git

âand yes, it makes sense to exclude those from the analysis (or perhaps consider only the changes that have been made in the xapi-project clone but not in the upstream, as suggested as an option by Santiago DueÃas).

Â

Thomas

From: Lars Kurth [mailto:lars.kurth.xen@xxxxxxxxx] On Behalf Of Lars Kurth
Sent: 01 April 2014 6:53 PM
To: Thomas Sanders; xen-api@xxxxxxxxxxxxx; mirageos-devel@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-API] Issues and questions related to contribution metrics dashboard for XAPI and Mirage OS

Â

On 01/04/2014 18:37, Thomas Sanders wrote:

Most of the XAPI-projectâs upstream forks were created by people who were doing work on the XAPI project (or precursor XenServer), and were created for use in or with the xapi project (but created outside the xapi-project space on github either due to obvious potential for wider use, or due to their initial status as personal experiments). It probably makes sense to include these ones in the analysis.

Thomas,
just checking whether I understand correctly. The repos below were
* created specifically for XAPI or XenServer
* the reason why they were forked were basically workflow related


Â

These include:

Â

PRDup git://github.com/xapi-project/PRDup.git

blktap-dkms git://github.com/xapi-project/blktap-dkms.git

cdrom git://github.com/xapi-project/cdrom.git

ffs git://github.com/xapi-project/ffs.git

libvhd git://github.com/xapi-project/libvhd.git

nbd git://github.com/xapi-project/nbd.git

netdev git://github.com/xapi-project/netdev.git

ocaml-fd-send-recv git://github.com/xapi-project/ocaml-fd-send-recv.git

ocaml-opasswd git://github.com/xapi-project/ocaml-opasswd.git

ocaml-tar git://github.com/xapi-project/ocaml-tar.git

ocaml-vhd git://github.com/xapi-project/ocaml-vhd.git

ocaml-xenstore-clients git://github.com/xapi-project/ocaml-xenstore-clients.git

ocamltest git://github.com/xapi-project/ocamltest.git

tapctl git://github.com/xapi-project/tapctl.git

vhd-tool git://github.com/xapi-project/vhd-tool.git

wsproxy git://github.com/xapi-project/wsproxy.git

xcp-eliloader git://github.com/xapi-project/xcp-eliloader.git

xcp-guest-templates git://github.com/xapi-project/xcp-guest-templates.git

xcp-idl git://github.com/xapi-project/xcp-idl.git

xcp-storage-managers git://github.com/xapi-project/xcp-storage-managers.git

xen-api-backports git://github.com/xapi-project/xen-api-backports.git

xen-api-client git://github.com/xapi-project/xen-api-client.git

xen-api-libs-specs git://github.com/xapi-project/xen-api-libs-specs.git

xen-api-libs-transitional git://github.com/xapi-project/xen-api-libs-transitional.git

xs-pull-request-build-scripts git://github.com/xapi-project/xs-pull-request-build-scripts.git

Thus, there is no real risk that the numbers will be skewed


Â

Created for XenServer and (currently) categorised under XenServer rather than Xapi:

vncterm git://github.com/xapi-project/vncterm.git

OK, should this one be included under XAPI project?


Â

Repositories forked from unrelated upstream projects:

oclock git://github.com/xapi-project/oclock.git

opam git://github.com/xapi-project/opam.git

opam-repository git://github.com/xapi-project/opam-repository.git

python-github2 git://github.com/xapi-project/python-github2.git

ocaml-sha git://github.com/xapi-project/ocaml-sha.git

The last of those was created by vincenthz, who also worked on XenServer and XAPI, but my understanding is that ocaml-sha was a separate personal project.

From what I read then, these 5 should not be counted as they would skew the stats

Regards
Lars

Â

From: xen-api-bounces@xxxxxxxxxxxxx [mailto:xen-api-bounces@xxxxxxxxxxxxx] On Behalf Of Lars Kurth
Sent: 27 March 2014 4:25 PM
To: xen-api@xxxxxxxxxxxxx; mirageos-devel@xxxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] Issues and questions related to contribution metrics dashboard for XAPI and Mirage OS

Â

Hi all,


a while ago I kicked a conversation related to putting a dashboard for the Xen project sub projects together. As it turns out there is an issue in XAPI and MirageOS repositories on github. Some of them are forks of upstreams, which are hard for the tool to analyze. My proposal would be to *not analyse them* and include them into statistics. If I don't hear any screams, then this will be the default. The list of forks detected are listed below ...

Also, it would be good to let me know of any other repos that you dont want to analyse. The full list is at http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html (note that there is 79 pages of them) which should be aggregated into buckets for XAPI and opam

Regards
Lars

= Detected forks in XAPI Project =
xen-unstable-mirror git://github.com/xapi-project/xen-unstable-mirror.git
PRDup git://github.com/xapi-project/PRDup.git
blktap-dkms git://github.com/xapi-project/blktap-dkms.git
cdrom git://github.com/xapi-project/cdrom.git
ffs git://github.com/xapi-project/ffs.git
libvhd git://github.com/xapi-project/libvhd.git
nbd git://github.com/xapi-project/nbd.git
netdev git://github.com/xapi-project/netdev.git
ocaml-fd-send-recv git://github.com/xapi-project/ocaml-fd-send-recv.git
ocaml-opasswd git://github.com/xapi-project/ocaml-opasswd.git
ocaml-sha git://github.com/xapi-project/ocaml-sha.git
ocaml-tar git://github.com/xapi-project/ocaml-tar.git
ocaml-vhd git://github.com/xapi-project/ocaml-vhd.git
ocaml-xenstore-clients git://github.com/xapi-project/ocaml-xenstore-clients.git
ocamltest git://github.com/xapi-project/ocamltest.git
oclock git://github.com/xapi-project/oclock.git
opam git://github.com/xapi-project/opam.git
opam-repository git://github.com/xapi-project/opam-repository.git
python-github2 git://github.com/xapi-project/python-github2.git
tapctl git://github.com/xapi-project/tapctl.git
vhd-tool git://github.com/xapi-project/vhd-tool.git
vncterm git://github.com/xapi-project/vncterm.git
wsproxy git://github.com/xapi-project/wsproxy.git
xcp-eliloader git://github.com/xapi-project/xcp-eliloader.git
xcp-guest-templates git://github.com/xapi-project/xcp-guest-templates.git
xcp-idl git://github.com/xapi-project/xcp-idl.git
xcp-storage-managers git://github.com/xapi-project/xcp-storage-managers.git
xen-api-backports git://github.com/xapi-project/xen-api-backports.git
xen-api-client git://github.com/xapi-project/xen-api-client.git
xen-api-libs-specs git://github.com/xapi-project/xen-api-libs-specs.git
xen-api-libs-transitional git://github.com/xapi-project/xen-api-libs-transitional.git
xs-pull-request-build-scripts git://github.com/xapi-project/xs-pull-request-build-scripts.git

= Detected forks in Mirage OS =
xen git://github.com/mirage/xen.git
mirari git://github.com/mirage/mirari.git
ocaml-cohttp git://github.com/mirage/ocaml-cohttp.git
ocaml-crypto-keys git://github.com/mirage/ocaml-crypto-keys.git
ocaml-cstruct git://github.com/mirage/ocaml-cstruct.git
ocaml-dns git://github.com/mirage/ocaml-dns.git
ocaml-openflow git://github.com/mirage/ocaml-openflow.git
ocaml-re git://github.com/mirage/ocaml-re.git
ocaml-tuntap git://github.com/mirage/ocaml-tuntap.git
ocaml-uri git://github.com/mirage/ocaml-uri.git
ocaml-xenstore git://github.com/mirage/ocaml-xenstore.git
opam-repository git://github.com/mirage/opam-repository.git




-------- Original Message --------

Subject:

Removing forks from the analysis

Date:

Thu, 27 Mar 2014 14:36:06 +0100

From:

Santiago DueÃas <sduenas@xxxxxxxxxxxx>

To:

Lars Kurth <lars.kurth@xxxxxxx>

CC:

citrix@xxxxxxxxxxxxxxxxxx

Â

Hi again Lars,
Â
during our analysis, we found that some of your git repos are forks from
upstream repositories. I don not know whether you talk to Manrique or
Jesus about that but I prefer to remember you which possibilities we
offer and which one we have follow.
Â
The repositories that we have already analyzed are listed on the
scm-repos page:
Â
http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html
Â
We offer three possibilities for treating these cases:
Â
- Do not analyze forks. This is the default option. We have removed from
the analysis those repositories marked as forks in Github and others
from upstream such as "ocaml" and "opam" series (see the attached file
that includes the full list of forks).
Â
Probably, you will want to remove more. If this is your choice, please
have a look at the repositories page and send me an email with the list
of git repositories you want to remove from the analysis.
Â
- Analyze forks. Take into account that this can affect the whole
numbers and stats, particularly if your team is not really active in
these repos.
Â
- Analyze differences between upstream and local repositories. Due this
functionality is out of the basic dashboard, please talk to Manrique or
Jesus to get more details, if interested.
Â
Santi
-- 
Santiago DueÃas
sduenas@xxxxxxxxxxxx
Bitergia S.L.L
Â
Â

Â

Â

Â


_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.