Use machine learning and natural language processing techniques to analyze the changes made in a project, and classify them in:

  • Small / unimportant fix
  • Big / important fix
  • Small / important feature
  • Big / important feature

For this project I will

  1. Generate a basic corpus of labeled data from a different set of project related with openSUSE
  2. Evaluate the best features to make a proper classification: n-gram, PoS tag, TF-IDF (with and without stemmer)
  3. Evaluate and measure the best classification model: Naive Bayes, Linear SVM, Max Entropy, ...

Looking for mad skills in:

nlp machinelearning git github

This project is part of:

Hack Week 10 Hack Week 11 Hack Week 12

Activity

  • almost 3 years ago: jordimassaguerpla liked Detect type of change in a project analyzing the log history
  • over 3 years ago: nicolasbock liked Detect type of change in a project analyzing the log history
  • over 4 years ago: ZRen disliked Detect type of change in a project analyzing the log history
  • over 4 years ago: ZRen liked Detect type of change in a project analyzing the log history
  • over 4 years ago: bkutil liked Detect type of change in a project analyzing the log history
  • Show History

    Comments

    • aplanas
      about 5 years ago by aplanas | Reply

      Yeah. Hackweek 10 collied with openSUSE 13.1, so I will try to for on this during this new Hackweek instance : )

    • froh
      about 5 years ago by froh | Reply

      Would it be hard to train for regression fix vs new feature, based on the comment? I'd be curious how much energy project have to put into regression fixes vs feature additions.

    • osynge
      over 4 years ago by osynge | Reply

      Have you considered looking at ELK and integrating this work in the ELK stack.

    Similar Projects

    ML and AI for code static analysis by mvarlese

    The idea is to explore the technologies and the...


    Architecting a Machine Learning project with SUSE CaaSP by jordimassaguerpla

    The goal of this project is to get an overview ...


    help clojure upstream with clj-common with some PR and contributions by dmaiocchi

    Rationale:

    There is around in the cloju...


    Extract lead and cycle times from Github by jochenbreuer

    When all of the SUSE Manager squads switched fr...