Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roadmap #5

Open
11 tasks
anpolimus opened this issue Mar 3, 2017 · 2 comments
Open
11 tasks

Roadmap #5

anpolimus opened this issue Mar 3, 2017 · 2 comments

Comments

@anpolimus
Copy link
Collaborator

anpolimus commented Mar 3, 2017

During migration to D8 our goal is to fix architecture problems that we had previously.

  1. Implement analytics_job as plugin and write next realisations for this plugin:
  • - country_scan_job - job that taking list of all users in a country and adding them to the queue;
  • - country_scan_job_item - job that is analysing profile one by one
  • - user scan : get commits - job that is scanning all commits for determined user
  • - user comments scan : get count of the comments for defined user
  • - user updates : scan for changes in user info (country, company, info)
  • - user comments statuses switch : scan for the issue status changing in a comment that is done by defined user.
  1. Implement new cronjober component - service that is getting items in queue and try to resolve them one by one.

  2. Implement master-slave status functionality.
    By default, during git pull && vagrant up, we should configure instance as slave instance.
    Slave instance is connecting to dranks.info main server and try to get queue items for himself.

We should have version verification and approve each new master in our network in order to avoid scan problems/bugs.

  1. Implement Country statistics page.
    Reimplement it from old versions - should be quite similar.

  2. CodeSprint analysator component.

  • - New CT that has list of atttenders (d.org users) and list of issues (d.org issues).
  • - Attenders and CS issues should scan each hour at the day of the sprint by jobs, described above.
  • - A dynamic report should be automatically updated after each jobs results.
  • - Display of the CS node could be displayed at the big screen of the CS room, showing who is making progress during CS and what issues are already fixed.
  • - When user added patch, changed status or added comment - system should show it at the newsevent in real time (once system get that info from any of job).
@podarok
Copy link
Member

podarok commented Mar 3, 2017

Use OpenY as a basic initial profile for the site

@podarok
Copy link
Member

podarok commented Mar 3, 2017

Next steps

  • 1 - init repo (OpenY + mapping entity + Syncer) @podarok
  • 2 - Implement Country scanner (fetch from Drupal.org, write to Node (Country CT))
  • 3 - Implement Commits scanner (fetch from Drupal.org, write to mapping entity (Commit bundle + fields), write to Node (User CT))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants