Move Log Analytics import_logs.py in its own repository #7163
Assignees
Labels
Task
Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Milestone
Comments
mattab
added
Task
mattab
pushed a commit
that referenced
this issue
Feb 10, 2015
|
Ok to use a submodule? |
|
sure, and add it to https://github.com/piwik/piwik-package/blob/master/scripts/build-package.sh#L19-L20 so it's there in the packaged release |
|
Moved to 2.12.0 as it's hopefully a quick improvement 👍 |
|
note: It's kind of obvious but we must keep the Git history for this file when moving to another repo |
|
(FYI: asked github support to move |
This was referenced Mar 8, 2015
This was referenced Mar 12, 2015
|
Update: Log Analytics issues were moved to the new repository for Piwik Log Analytics: https://github.com/piwik/piwik-log-analytics/issues |
diosmosis
added a commit
that referenced
this issue
Mar 17, 2015
Fixes #7163, removing misc/log-analytics directory and replace w/ submodule.
mattab
pushed a commit
to matomo-org/matomo-package
that referenced
this issue
Mar 17, 2015
mattab
added a commit
that referenced
this issue
Mar 19, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The goal of this issue is to move the Log Analytics folder to its own repository under
piwik/log-analytics. This was discussed a few times by the team.Having the project under a separate repository makes sense because it is independent from the main source code, it is written in a different technology python, we think it will make contributions easier to have a separate repo. also we want to add CI for log analytics in #7062 - maybe we could also split the big python file in several smaller files as suggested by @diosmosis to make maintenance easier.
This would be done while keeping BC of course. we could ask github support to move the issues with label "Log Analytics" to the new repo (I think they can do this).
The text was updated successfully, but these errors were encountered: