<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Mar 23, 2019, at 6:26 AM, Arjun Salyan via macports-dev <<a href="mailto:macports-dev@lists.macports.org" class="">macports-dev@lists.macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class="">On Sat, Mar 23, 2019 at 3:15 PM Mojca Miklavec <<a href="mailto:mojca@macports.org" target="_blank" class="">mojca@macports.org</a>> wrote:<br class=""></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">I would use the first definition: number of users currently having the<br class="">
port installed. It might be pretty common to have to reinstall the<br class="">
same port multiple times (maybe just for debugging / development<br class="">
reasons) and we don't want to count the port developer 20 times. If<br class="">
the user uninstalled the port, it's equivalent to me as never having<br class="">
it installed in the first place.<br class=""></blockquote><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">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.</div></div></div></div></blockquote><br class=""></div><div>Actually, the current mpstats job submits data weekly. The following is a portion of the ‘/Library/LaunchDaemons/org.macports.mpstats.plist’ on my system:</div><div><br class=""></div><div><div><span class="Apple-tab-span" style="white-space:pre"> </span><key>StartCalendarInterval</key></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><dict></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><key>Weekday</key></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><integer>2</integer></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><key>Hour</key></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><integer>06</integer></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><key>Minute</key></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><integer>52</integer></div><div><span class="Apple-tab-span" style="white-space:pre"> </span></dict></div><div class=""><br class=""></div></div>I read somewhere (lost now) that during a month, earlier submissions are discarded when another submission is received for the same UUID. <div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">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. </div><div class=""><br class=""></div><div class="">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:</div><div class="">a) week ago (i.e. current information)</div><div class="">b) month ago (4 weeks ago)</div><div class="">c) 3 months ago (13 weeks ago)</div><div class="">d) 6 months ago (26 weeks ago)</div><div class="">e) year ago (52 weeks ago)</div><div class=""><br class=""></div><div class="">This way, submissions over a year old could be purged while allowing fairly straightforward and understandable reporting criteria.</div><div class=""><br class=""></div><div class="">Craig</div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>