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 --------
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
