> On Mar 23, 2019, at 6:26 AM, Arjun Salyan via macports-dev
> <[email protected]> wrote:
>
> On Sat, Mar 23, 2019 at 3:15 PM Mojca Miklavec <[email protected]
> <mailto:[email protected]>> wrote:
> I would use the first definition: number of users currently having the
> port installed. It might be pretty common to have to reinstall the
> same port multiple times (maybe just for debugging / development
> reasons) and we don't want to count the port developer 20 times. If
> the user uninstalled the port, it's equivalent to me as never having
> it installed in the first place.
>
> Thanks. But in that case what would be considered as number of installations
> in a particular month? Suppose, the first weekly submission contains port P
> in active_ports, but during second submission(in the same month), the port is
> uninstalled.
>
> One way would be to have it consider the number of users having it in active
> ports on the last day of the month or on 15th.
Actually, the current mpstats job submits data weekly. The following is a
portion of the ‘/Library/LaunchDaemons/org.macports.mpstats.plist’ on my system:
<key>StartCalendarInterval</key>
<dict>
<key>Weekday</key>
<integer>2</integer>
<key>Hour</key>
<integer>06</integer>
<key>Minute</key>
<integer>52</integer>
</dict>
I read somewhere (lost now) that during a month, earlier submissions are
discarded when another submission is received for the same UUID.
As a maintainer, I am interested to know how the characteristics of the users
of my ports change over time. For example, if I make a new version available,
how quickly do users upgrade? How quickly do the users of this port migrate to
newer versions of the Mac operating system? Etc. As mentioned earlier, I have
no interest in inactive versions of ports.
As a project, I think we’d like to know how quickly our user base adopts new
versions of the OS, Xcode and new versions of MacPorts base.
I don’t think we need a tremendous amount of detail. I would propose that we
only need (or need to report on) snapshots as of:
a) week ago (i.e. current information)
b) month ago (4 weeks ago)
c) 3 months ago (13 weeks ago)
d) 6 months ago (26 weeks ago)
e) year ago (52 weeks ago)
This way, submissions over a year old could be purged while allowing fairly
straightforward and understandable reporting criteria.
Craig
