1. 11 Jan, 2020 2 commits
  2. 09 Jan, 2020 1 commit
  3. 31 Dec, 2019 15 commits
  4. 18 Dec, 2019 2 commits
    • Christelle Zouein's avatar
      Network function for use with any data source · 9a4afcee
      Christelle Zouein authored
      Network function added with a case check for wether or not that
      dataframe comes from issues or repos/mail, since they differ widely in
      how the edges of the network are calculated.
      Corresponding tests and adjustments to parsing.
    • Christelle Zouein's avatar
      Actitvity function for all data sources · bc8e426b
      Christelle Zouein authored
      comdaan module created to group the analyses of the same type for
      different data sources with the activity and parsing functions.
      Parsing files adjusted.
      Testing of the activity function.
      The repo repository was added as a submodule.
  5. 26 Nov, 2019 9 commits
  6. 08 Nov, 2019 6 commits
    • Christelle Zouein's avatar
      Issue response time analysis · 1e45b9ab
      Christelle Zouein authored
      In the response time analysis, response time variations over time are
      Rolling window of 50 for smoothing.
      Displaying a bar chart in the response analysis that shows the rates of
      unanswered issues at each creation date.
    • Christelle Zouein's avatar
      Centrality analysis for git issues · dd6dbcb6
      Christelle Zouein authored
      The centrality analysis's network is built according to the network
      analysis' network. It is heavily inspired by the git repositories'
      centrality analysis.
    • Christelle Zouein's avatar
      Network Analysis for issue discussions · 32cea33b
      Christelle Zouein authored
      The network analysis, when it comes to issues is based on the
      discussions that happen on the issue themselves.
      And so, we build a graph that connects the author of an issue to all
      those that commented on said issue.
      Not removing edges with a weight of 0 because simply, there
      aren't any, at least not with the way the edge_list is currently built.
    • Christelle Zouein's avatar
      Issues teamsize analysis · a6ef1150
      Christelle Zouein authored
      Teamsize anaylsis based on the number of authors (per date) for teamsize
      and the number of issues (per date) for activity.
      Including commenter data in teamsize analysis
    • Christelle Zouein's avatar
      Activity analysis for issues · b597436d
      Christelle Zouein authored
      Analysing commenter as well as reporter activity
    • Christelle Zouein's avatar
      Parsing issues · dd5e4ba0
      Christelle Zouein authored
      Parsing issues either from a path to a directory with JSON files
      containing issues or a path to a JSON file containing issues.
      Ruleset finding, is_entry_acceptable and postprocessing available as
      well as preprocessing.
  7. 07 Nov, 2019 1 commit
    • Christelle Zouein's avatar
      Script for fetching git issues · 023389b6
      Christelle Zouein authored
      Using python-gitlab to fetch the issues of a project with a given
      project id.
      Adding a discussion field to the issue dictionary that stores the
      discussion around said issue. And thus it stores a list or threads,
      which are a list of comments... so a list of lists of dictionaries.
      Adding private access token as mandatory cli argument for gitlab
      instance authentication.
      Shifting to Pipfile, Requirements.txt removed
  8. 31 Oct, 2019 2 commits
  9. 07 Oct, 2019 2 commits
    • Christelle Zouein's avatar
      Centrality analysis for mailing lists · 4bfaae40
      Christelle Zouein authored
      Centrality analysis for mailing lists mimicking the git repositories'
      centrality analysis.
      But, I'm not skipping the first two values or size_df in this one.
      size and centrality also stop before activity.
    • Christelle Zouein's avatar
      Network analysis for mailing lists · c937e048
      Christelle Zouein authored
      Heavily inspired from the git repositories' netwrok analysis, it
      expresses how much a sender's message was referenced and how much they
      reference other messages.
      Instead of the intersection of the references lists of each user like in
      the git version, this version's edge list weights is the
      intersection of the list of message ids of all of the source's message
      and the references list of the target. It thus focuses on the sender
      being referenced instead of just the sender referencing.
      And thus we consider the phenomenon of being referenced since the former is
      be more meaningful as to the sender/person's value inside the mailing
      community should increase with the amount of time they are referenced.
      Moreover in the process of sending and receiving emails some people are
      mentioned and replied to and some others mention and reply, and since
      being mentioned many times is a more important indicator to someone's
      centrality than barely mentioning (because, really, anyone can mention
      others), I'm switching to a firected graph to represent the data.