Re: GSoC 2019 [Collect build statistics]

2019-05-17 Thread Umesh Singla
Nice. Makes testing a lot easier now. It would be great if you could push the Dockerfile as well. Also, I am not liking conversing on these multiple broken threads very much. I'll try to setup Matrix (have absolutely no idea about it yet) today so that we can compare gitter and matrix and move

Re: GSoC 2019 [Collect build statistics]

2019-05-14 Thread Mojca Miklavec
Dear Arjun, I'm CC-ing the list as that's potentially interesting to others as well. On Tue, 14 May 2019 at 19:45, Arjun Salyan wrote: > Summary of today's discussion: > > 1. *Repository: *The existing repository for the web app would be moved > from the staging area to the official MacPorts

Re: GSoC 2019 [Collect build statistics]

2019-04-16 Thread Mojca Miklavec
On Fri, 12 Apr 2019 at 19:50, Arjun Salyan wrote: > On Fri, Apr 12, 2019 at 3:03 AM Mojca Miklavec wrote: > >> One thing that "urgently" needs to be done is to obfuscate the email >> >> (if written at all). I'm not even sure whether we actually want the >> email being displayed there. We need it

Re: GSoC 2019 [Collect build statistics]

2019-04-15 Thread Arjun Salyan via macports-dev
Hi Mojca, On Mon, Apr 15, 2019 at 9:46 PM Mojca Miklavec wrote: > Given the current state of the app with sufficient complexity, I > believe that it would be wise to introduce some unit tests to be able > to extensively test what happens with data you import, and to prevent > / detect any

Re: GSoC 2019 [Collect build statistics]

2019-04-15 Thread Mojca Miklavec
Dear Arjun, I'll answer individual questions & provide further suggestion separately. Given the current state of the app with sufficient complexity, I believe that it would be wise to introduce some unit tests to be able to extensively test what happens with data you import, and to prevent /

Re: GSoC 2019 [Collect build statistics]

2019-04-12 Thread Arjun Salyan via macports-dev
Hi Mojca, On Fri, Apr 12, 2019 at 3:03 AM Mojca Miklavec wrote: > Awesome! Thank You. One thing that "urgently" needs to be done is to obfuscate the email > (if written at all). I'm not even sure whether we actually want the > email being displayed there. We need it to send automated emails

Re: GSoC 2019 [Collect build statistics]

2019-04-11 Thread Mojca Miklavec
Dear Arjun, Thanks a lot for the update. On Thu, 11 Apr 2019 at 16:15, Arjun Salyan wrote: > > I have added maintainer views and tables to the demo app. > > List of maintainers is clickable on the port-detail page. > A maintainer-detail view that display info and list of maintained ports

Re: GSoC 2019 [Collect build statistics]

2019-04-11 Thread Arjun Salyan via macports-dev
Hi, I have added maintainer views and tables to the demo app. - List of maintainers is clickable on the port-detail page. - A maintainer-detail view that display info and list of maintained ports Examples: maintainer-detail:

Re: GSoC 2019 [Collect build statistics]

2019-04-08 Thread Mojca Miklavec
Dear Arjun, On Mon, 8 Apr 2019 at 20:31, Arjun Salyan wrote: > > Dear MacPorts Community, > > I have submitted my Final Proposal. I do understand that during these last > hours it might not be possible to give feedback on the proposals. But if I am > lucky enough to get more of them, I will try

Re: GSoC 2019 [Collect build statistics]

2019-04-08 Thread Arjun Salyan via macports-dev
Dear MacPorts Community, I have submitted my Final Proposal. I do understand that during these last hours it might not be possible to give feedback on the proposals. But if I am lucky enough to get more of them, I will try to get the job done (around 23 hours still remaining). Google Doc:

Re: GSoC 2019 [Collect build statistics]

2019-04-07 Thread Arjun Salyan via macports-dev
> > Hi, On Fri, Apr 5, 2019 at 8:58 AM Umesh Singla > wrote: > >> It’s always to good to show your work and get feedback. It’s difficult to >> comment on the quality otherwise. Please do not forget to make a PR. >> > I have submitted the PR for adding an option to portindex (which would generate

Re: GSoC 2019 [Collect build statistics]

2019-04-05 Thread Arjun Salyan via macports-dev
On Fri, Apr 5, 2019 at 8:58 AM Umesh Singla wrote: > > It’s okay to share all the project related updates on the list. In fact, > it’s preferred that way. > Thanks, I was just being hesitant to write that on the list. > Does this include additions and/or deletions? > Portindex uses modified

Re: GSoC 2019 [Collect build statistics]

2019-04-02 Thread Arjun Salyan via macports-dev
Hi Mojca, On Tue, Apr 2, 2019 at 3:14 AM Mojca Miklavec wrote: > The drawbacks may include: > - some ports will be skipped on the builder, for various reasons (port > is known not to build on a particular builder, it may not be > distributable, ...) > - the buildbot master may be down or

Re: GSoC 2019 [Collect build statistics]

2019-04-01 Thread Mojca Miklavec
Dear Arjun, On Mon, 1 Apr 2019 at 18:38, Arjun Salyan wrote: > > Hi, > I was working on keeping the PortIndex updated, and was able to achieve this: > > Sync Portindex from > 'rsync://rsync.macports.org/macports//trunk/dports/PortIndex_darwin_16_i386/PortIndex' > Update or Add ports that were

Re: GSoC 2019 [Collect build statistics]

2019-04-01 Thread Arjun Salyan via macports-dev
Hi, I was working on keeping the PortIndex updated, and was able to achieve this: - Sync Portindex from 'rsync:// rsync.macports.org/macports//trunk/dports/PortIndex_darwin_16_i386/PortIndex ' - Update or Add ports that were recently built on 10.14_x86_64 (using time frame 'last 24

Re: GSoC 2019 [Collect build statistics]

2019-03-31 Thread Arjun Salyan via macports-dev
On Sun, Mar 31, 2019 at 2:05 PM Mojca Miklavec wrote: > There seem to be some issues with subports. (For example any p5.28-* > under perl would give an error page.) > Yes, it was happening for the ports that contain '.' in their names. I have solved it using regex now. Just curious: what's the

Re: GSoC 2019 [Collect build statistics]

2019-03-31 Thread Mojca Miklavec
On Sat, 30 Mar 2019 at 21:59, Arjun Salyan wrote: > > Thanks Mojca, I will update the Demo App with the suggested changes very > shortly. > > On Sat, Mar 30, 2019 at 8:30 PM Mojca Miklavec wrote: >> >> Anyway, I'm just curious: what's the current situation with >> django/database hosting,

Re: GSoC 2019 [Collect build statistics]

2019-03-30 Thread Arjun Salyan via macports-dev
Thanks Mojca, I will update the Demo App with the suggested changes very shortly. On Sat, Mar 30, 2019 at 8:30 PM Mojca Miklavec wrote: > Anyway, I'm just curious: what's the current situation with > django/database hosting, network and other limitations etc.? > Now that you have the code which

Re: GSoC 2019 [Collect build statistics]

2019-03-30 Thread Mojca Miklavec
On Sat, 30 Mar 2019 at 12:54, Arjun Salyan wrote: > > Hi, > I have installed an ajax based search box in the demo app: > https://frozen-falls-98471.herokuapp.com Cool, I like it, thanks! The next "feature request" would probably be to allow search through descriptions as well :) Anyway, I'm

Re: GSoC 2019 [Collect build statistics]

2019-03-30 Thread Arjun Salyan via macports-dev
Hi, I have installed an ajax based search box in the demo app: https://frozen-falls-98471.herokuapp.com Also, just wanted to give a polite reminder about my open PR: https://github.com/macports/macports-contrib/pull/3 Thank You >

Re: GSoC 2019 [Collect build statistics]

2019-03-28 Thread Arjun Salyan via macports-dev
On Thu, Mar 28, 2019 at 12:05 PM Mojca Miklavec wrote: > What if there's a server outage? > Then the best way is to use HttpStatusPush to deliver instant updates, and so that any build is not missed due to server failure, we could run our fetching script once per day. The script can easily

Re: GSoC 2019 [Collect build statistics]

2019-03-28 Thread Mojca Miklavec
On Wed, 27 Mar 2019 at 17:13, Arjun Salyan wrote: >> >> - A more elaborate plan about how you plan to handle updates / keep >> the database up-to-date. Sure, we can trigger certain actions from the >> buildbot, but those various "actions" need to be implemented. Keeping >> the app up to date in a

Re: GSoC 2019 [Collect build statistics]

2019-03-27 Thread Arjun Salyan via macports-dev
> > - A more elaborate plan about how you plan to handle updates / keep > the database up-to-date. Sure, we can trigger certain actions from the > buildbot, but those various "actions" need to be implemented. Keeping > the app up to date in a safe and reliable way is a very important part > of the

Re: GSoC 2019 [Collect build statistics]

2019-03-27 Thread Arjun Salyan via macports-dev
Thank You Mojca! I read you inline comments as well, I have already started working over the suggestions. I will include these very shortly! > > Does your new semester already start at end of July? Yes, it does. But it won’t affect the project. I have done projects in a semester as tightly

Re: GSoC 2019 [Collect build statistics]

2019-03-27 Thread Mojca Miklavec
Dear Arjunt On Tue, 26 Mar 2019 at 07:34, Arjun Salyan wrote: > > Dear all, > > Using the valuable information and suggestions by all of you here at > MacPorts, especially the potential mentors, I have come up with the first > draft of my proposal for GSoC 2019. > Link to Google Doc: >

Re: GSoC 2019 [Collect build statistics]

2019-03-27 Thread Arjun Salyan via macports-dev
Dear all, Using the valuable information and suggestions by all of you here at MacPorts, especially the potential mentors, I have come up with the first draft of my proposal for GSoC 2019. Link to Google Doc:

Re: Dependencies on non-default variants (was: GSoC 2019 [Collect build statistics])

2019-03-25 Thread Craig Treleaven
Mojca: I apologize for the length of this and for continuing to hammer on this issue but I think this is important. I support the idea of a modern web app to bring together all the relevant information for a port that potential users of MacPorts need in order to assess if they want to install

Re: GSoC 2019 [Collect build statistics]

2019-03-25 Thread Mojca Miklavec
Dear Fred, (Resending due to the initial post from the wrong email account; sorry for the duplicate.) On Sun, 24 Mar 2019 at 22:57, Fred Wright wrote: > On Sun, 24 Mar 2019, Mojca Miklavec wrote: > > On Sat, 23 Mar 2019 at 17:49, Craig Treleaven wrote: > >> > >> I see no reason to report

Re: Dependencies on non-default variants (was: GSoC 2019 [Collect build statistics])

2019-03-25 Thread Mojca Miklavec
Dear Craig, > As you said, people have looked at this problem and not found a workable > solution. Personally I never did spend any effort into fixing this, partially probably also because it doesn't affect any ports that I use or maintain. > It may be a _long_ time before a “proper” solution

Re: GSoC 2019 [Collect build statistics]

2019-03-24 Thread Craig Treleaven
> On Mar 24, 2019, at 5:57 PM, Fred Wright wrote: > > On Sun, 24 Mar 2019, Mojca Miklavec wrote: >> On Sat, 23 Mar 2019 at 17:49, Craig Treleaven wrote: >>> >>> I see no reason to report inactive ports. >> >> Neither do I. I would remove those as I already mentioned in an earlier >> email. >

Re: Dependencies on non-default variants (was: GSoC 2019 [Collect build statistics])

2019-03-24 Thread Craig Treleaven
> On Mar 24, 2019, at 4:05 PM, Mojca Miklavec wrote: > > On Sun, 24 Mar 2019 at 19:55, Craig Treleaven wrote: >>> On Mar 24, 2019, at 1:09 PM, Mojca Miklavec wrote: >>> On Sun, 24 Mar 2019 at 01:06, Craig Treleaven wrote: There are a number of ports that require a dependency to be

Re: GSoC 2019 [Collect build statistics]

2019-03-24 Thread Fred Wright
On Sun, 24 Mar 2019, Mojca Miklavec wrote: On Sat, 23 Mar 2019 at 17:49, Craig Treleaven wrote: I see no reason to report inactive ports. Neither do I. I would remove those as I already mentioned in an earlier email. But in the spirit of lossless collection, those should be included and

Dependencies on non-default variants (was: GSoC 2019 [Collect build statistics])

2019-03-24 Thread Mojca Miklavec
On Sun, 24 Mar 2019 at 19:55, Craig Treleaven wrote: > > On Mar 24, 2019, at 1:09 PM, Mojca Miklavec wrote: > > On Sun, 24 Mar 2019 at 01:06, Craig Treleaven wrote: >>> >>> There are a number of ports that require a dependency to be installed with >>> a non-default variant in order to build

Re: GSoC 2019 [Collect build statistics]

2019-03-24 Thread Craig Treleaven
> > On Mar 24, 2019, at 1:09 PM, Mojca Miklavec wrote: > > On Sun, 24 Mar 2019 at 01:06, Craig Treleaven wrote: >> >> please note that we can’t expect all ports to build successfully on the >> buildbots. > > Nobody said that, but we cannot blame the student collecting the data > from

Re: GSoC 2019 [Collect build statistics]

2019-03-24 Thread Mojca Miklavec
On Sun, 24 Mar 2019 at 01:06, Craig Treleaven wrote: > > please note that we can’t expect all ports to build successfully on the > buildbots. Nobody said that, but we cannot blame the student collecting the data from buildbot for macports internal deficiencies :) > There are a number of ports

Re: GSoC 2019 [Collect build statistics]

2019-03-24 Thread Arjun Salyan via macports-dev
On Sun, Mar 24, 2019 at 10:02 PM Mojca Miklavec wrote: > Here are some examples of why I don't see a single correct answer to > your initial question. Let's assume that you know absolutely > everything about all MacPorts installation (exact timestamp of when > each port was installed or

Re: GSoC 2019 [Collect build statistics]

2019-03-24 Thread Mojca Miklavec
On Sat, 23 Mar 2019 at 17:49, Craig Treleaven wrote: > > I see no reason to report inactive ports. Neither do I. I would remove those as I already mentioned in an earlier email. > The “OS” section for my system is: > > "os": { > "macports_version": "2.5.4", > "osx_version": "10.10", >

Re: GSoC 2019 [Collect build statistics]

2019-03-24 Thread Mojca Miklavec
On Sat, 23 Mar 2019 at 15:28, Craig Treleaven wrote: > > Our existing installation stats are, to be kind, a mess. Which is precisely why we suggested this project: to fix what we learned from the past mistakes. The submission process is mostly still ok, but the database design is flawed. I'm not

Re: GSoC 2019 [Collect build statistics]

2019-03-24 Thread Mojca Miklavec
Hi, (Sorry, this email got so long that I'll answer the others separately.) On Sat, 23 Mar 2019 at 11:26, Arjun Salyan wrote: > On Sat, Mar 23, 2019 at 3:15 PM Mojca Miklavec wrote: >> >> I would use the first definition: number of users currently having the >> port installed. It might be pretty

Re: GSoC 2019 [Collect build statistics]

2019-03-24 Thread Craig Treleaven
> On Mar 23, 2019, at 6:26 AM, Arjun Salyan via macports-dev > wrote: > > On Sat, Mar 23, 2019 at 3:15 PM Mojca Miklavec > wrote: > I would use the first definition: number of users currently having the > port installed. It might be pretty common to have to reinstall

Re: GSoC 2019 [Collect build statistics]

2019-03-24 Thread Arjun Salyan via macports-dev
Hi, I have prepared a Google Doc on the implementation of installation statistics. I do not know if this is the right way to get suggestions. But it would be great if I could get feedback and suggestions on this:

Re: GSoC 2019 [Collect build statistics]

2019-03-23 Thread Arjun Salyan via macports-dev
On Sat, Mar 23, 2019 at 7:58 PM Craig Treleaven wrote: > See: > > http://stats.macports.neverpanic.de/os_statistics#os_platform > > It says all 239 reported platforms are Darwin. So this appears to be the > conglomeration of all reporting over the past several years. This explains > why the

Re: GSoC 2019 [Collect build statistics]

2019-03-23 Thread Craig Treleaven
> On Mar 23, 2019, at 5:45 AM, Mojca Miklavec wrote: > > On Sat, 23 Mar 2019 at 10:35, Arjun Salyan via macports-dev wrote: >> >> Hi, >> I am working on the design of tables for installation statistics. I have a >> doubt here: >> >> Suppose there is a port P. Now for number of installations

Re: GSoC 2019 [Collect build statistics]

2019-03-23 Thread Craig Treleaven
> On Mar 23, 2019, at 6:26 AM, Arjun Salyan via macports-dev > wrote: > > On Sat, Mar 23, 2019 at 3:15 PM Mojca Miklavec > wrote: > I would use the first definition: number of users currently having the > port installed. It might be pretty common to have to reinstall

Re: GSoC 2019 [Collect build statistics]

2019-03-23 Thread Arjun Salyan via macports-dev
On Sat, Mar 23, 2019 at 3:15 PM Mojca Miklavec 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

Re: GSoC 2019 [Collect build statistics]

2019-03-23 Thread Mojca Miklavec
Dear Arjun, On Sat, 23 Mar 2019 at 10:35, Arjun Salyan via macports-dev wrote: > > Hi, > I am working on the design of tables for installation statistics. I have a > doubt here: > > Suppose there is a port P. Now for number of installations of P, there are > many definitions I am having in my

Re: GSoC 2019 [Collect build statistics]

2019-03-23 Thread Arjun Salyan via macports-dev
Hi, I am working on the design of tables for installation statistics. I have a doubt here: Suppose there is a port P. Now for number of installations of P, there are many definitions I am having in my mind: 1. Number of users currently having P in active_ports/ inactive_ports. [ACTIVE

Re: GSoC 2019 [Collect build statistics]

2019-03-21 Thread Arjun Salyan via macports-dev
On Thu, Mar 21, 2019 at 8:35 PM Umesh Singla wrote: > a) We have seen a quick demo of this already. However, the major part I > think is missing is the search. We can brainstorm over the details like > search-as-you-type, adding new ports etc according to the timeline. Not > sure how much

Re: GSoC 2019 [Collect build statistics]

2019-03-21 Thread Arjun Salyan via macports-dev
Hi, I have created the pull request. The new output is shown below: { * "variants" : ["debug"],* "depends_build" : ["path:bin/cmake:cmake","port:pkgconfig","path:share/ECM/cmake/ECMConfig.cmake:kde-extra-cmake-modules"], "portdir" : "audio\/phonon-backend-vlc", "depends_fetch"

Re: GSoC 2019 [Collect build statistics]

2019-03-21 Thread Umesh Singla
Hi For me, this project can be divided into three major parts: 1. ports page: a) We have seen a quick demo of this already. However, the major part I think is missing is the search. We can brainstorm over the details like search-as-you-type, adding new ports etc according to the timeline. Not

Re: GSoC 2019 [Collect build statistics]

2019-03-21 Thread Arjun Salyan via macports-dev
Thanks, it is clear now. I will do the changes and submit the PR.

Re: GSoC 2019 [Collect build statistics]

2019-03-21 Thread Mojca Miklavec
On Thu, 21 Mar 2019 at 13:29, Arjun Salyan wrote: > On Thu, Mar 21, 2019 at 5:42 PM Mojca Miklavec wrote: > >> >> Just create an empty list of maintainers. > > There are some ports which have : {ryandesign @ryandesign} nomaintainer} as > the output of maintainers . What does "nomaintainer" mean

Re: GSoC 2019 [Collect build statistics]

2019-03-21 Thread Arjun Salyan via macports-dev
On Thu, Mar 21, 2019 at 5:42 PM Mojca Miklavec wrote: > Just create an empty list of maintainers. > There are some ports which have : *{ryandesign @ryandesign} nomaintainer} *as the output of maintainers . What does "nomaintainer" mean here? > We also need to add emails. Maybe something like

Re: GSoC 2019 [Collect build statistics]

2019-03-21 Thread Mojca Miklavec
On Thu, 21 Mar 2019 at 11:27, Arjun Salyan wrote: > On Thu, Mar 21, 2019 at 10:20 AM Mojca Miklavec wrote: >> >> (2) You made a simple PR last time to fix portindex2json for a more >> reasonable output of categories. Would you be willing for a tiny bit >> more difficult task and try to improve

Re: GSoC 2019 [Collect build statistics]

2019-03-21 Thread Arjun Salyan via macports-dev
On Thu, Mar 21, 2019 at 10:20 AM Mojca Miklavec wrote: > (2) You made a simple PR last time to fix portindex2json for a more > reasonable output of categories. Would you be willing for a tiny bit > more difficult task and try to improve the output for maintainers as > well? We would want a list

Re: GSoC 2019 [Collect build statistics]

2019-03-20 Thread Mojca Miklavec
Dear Arjun, Just quickly (I'm online for a very short time) I'm listing some of the potential next steps (in no particular order), I hope that Umesh will also comment on it: (1) It would probably be time for a thorough code review. It's a bit tricky to do code reviews on your personal

Re: GSoC 2019 [Collect build statistics]

2019-03-20 Thread Mojca Miklavec
Dear Arjun, Thanks a lot for the changes. More feedback later, I just noticed that https://frozen-falls-98471.herokuapp.com/ports/gmsh/ now throws an error. Even if the port doesn't exist in the database, it should probably say that the port doesn't exist rather than throwing an error.

Re: GSoC 2019 [Collect build statistics]

2019-03-20 Thread Arjun Salyan via macports-dev
Hi Mojca, Thanks for the detailed reply. Changes can be seen for this port: http://frozen-falls-98471.herokuapp.com/ports/qt5-qtlocation/ On Wed, Mar 20, 2019 at 6:40 AM Mojca Miklavec wrote: > This is super useful. But I would

Re: GSoC 2019 [Collect build statistics]

2019-03-19 Thread Mojca Miklavec
Dear Arjun, On Tue, 19 Mar 2019 at 13:47, Arjun Salyan wrote: > > I have some more improvements to demo app: > > Build History is now Dynamic: By Making some minor tweaks to the python > script sent by Mojca, I was able to load build history from buildbot into the > database. Awesome! > I

Re: GSoC 2019 [Collect build statistics]

2019-03-19 Thread Arjun Salyan via macports-dev
I have some more improvements to demo app: - *Build History is now Dynamic: *By Making some minor tweaks to the python script sent by Mojca, I was able to load build history from buildbot into the database. I loaded only few recent logs for "*10.14_x86_64*" & " *10.13_x86_64*". Since,

Re: GSoC 2019 [Collect build statistics]

2019-03-18 Thread Arjun Salyan via macports-dev
On Mon, 18 Mar 2019 at 10:49 PM, Mojca Miklavec wrote: > And in fact I'm unable to find any indices in your DB model. Thanks, I shall add this. I am dealing with this huge data set for the first time. Also, TextField might be suitable for description etc, but for short > entries like port

Re: GSoC 2019 [Collect build statistics]

2019-03-18 Thread Mojca Miklavec
On Mon, 18 Mar 2019 at 17:37, Mojca Miklavec wrote: > On Mon, 18 Mar 2019 at 16:52, Arjun Salyan wrote: > > > All Ports and All Categories are now available (Although not all ports have > > populated yet, I am on AWS Free Tier and the process is really slow. At the > > time of drafting this

Re: GSoC 2019 [Collect build statistics]

2019-03-18 Thread Mojca Miklavec
On Mon, 18 Mar 2019 at 16:52, Arjun Salyan wrote: > > Some improvements to the Demo App: https://frozen-falls-98471.herokuapp.com Thank you very much. > All Ports and All Categories are now available (Although not all ports have > populated yet, I am on AWS Free Tier and the process is really

Re: GSoC 2019 [Collect build statistics]

2019-03-18 Thread Arjun Salyan via macports-dev
Some improvements to the Demo App: https://frozen-falls-98471.herokuapp.com - All Ports and All Categories are now available (Although not all ports have populated yet, I am on AWS Free Tier and the process is really slow. At the time of drafting this email: around 500 have populated).

Re: GSoC 2019 [Collect build statistics]

2019-03-17 Thread Mojca Miklavec
V ned., 17. mar. 2019 20:09 je oseba Arjun Salyan < arjun.salyan.ch...@itbhu.ac.in> napisala: > On Sun, Mar 17, 2019 at 1:31 AM Joshua Root wrote: > >> It would be a good idea to check if they have any changes on their end >> that we're missing, too. >> > > They have made one change: "Make

Re: GSoC 2019 [Collect build statistics]

2019-03-17 Thread Arjun Salyan via macports-dev
On Sun, Mar 17, 2019 at 1:31 AM Joshua Root wrote: > It would be a good idea to check if they have any changes on their end > that we're missing, too. > They have made one change: "Make portindex2json.tcl always work with utf-8, insensitive to local settings". Should we incorporate this change

Re: GSoC 2019 [Collect build statistics]

2019-03-16 Thread Joshua Root
On 2019-3-17 05:02 , Craig Treleaven wrote: > I believe portindex2json.tcl was created to feed Repology.org >  so if changes are made it would be polite to > indicate that it is a new version. It would be a good idea to check if they have any changes on their end that we're

Re: GSoC 2019 [Collect build statistics]

2019-03-16 Thread Craig Treleaven
> On Mar 16, 2019, at 1:00 PM, Mojca Miklavec wrote: > > Dear Arjun, > > V sob., 16. mar. 2019 21:46 je oseba Arjun Salyan napisala: > I have tried to make some changes in portindex2json.tcl so that the value of > categories is outputted as a list and not just a string. > > Can someone please

Re: GSoC 2019 [Collect build statistics]

2019-03-16 Thread Mojca Miklavec
Dear Arjun, V sob., 16. mar. 2019 21:46 je oseba Arjun Salyan napisala: > I have tried to make some changes in portindex2json.tcl so that the value > of categories is outputted as a list and not just a string. > > Can someone please review if it seems fine: >

Re: GSoC 2019 [Collect build statistics]

2019-03-16 Thread Arjun Salyan via macports-dev
I have tried to make some changes in portindex2json.tcl so that the value of categories is outputted as a list and not just a string. Can someone please review if it seems fine: https://github.com/arjunsalyan/Test/blob/master/portindex2json.tcl Sample Output (new): { "variants" :

Re: GSoC 2019 [Collect build statistics]

2019-03-16 Thread Arjun Salyan via macports-dev
On Sat, 16 Mar 2019 at 7:51 AM, Mojca Miklavec wrote: > JFYI: > > It might theoretically be a valid situation to have two entries with the > same name (software gets deleted, then two years later an unrelated > software with the same name gets added; but only one entry would have the > status

Re: GSoC 2019 [Collect build statistics]

2019-03-15 Thread Mojca Miklavec
JFYI: It might theoretically be a valid situation to have two entries with the same name (software gets deleted, then two years later an unrelated software with the same name gets added; but only one entry would have the status "active" and the others not). A lot more common case would be that a

Re: GSoC 2019 [Collect build statistics]

2019-03-14 Thread Mojca Miklavec
Dear Arjun, (Sorry if some things repeat from what Umesh sent you. I have already written the reply yesterday, but did not manage to come back online until now.) Thank you very much for your demo app. On Wed, 13 Mar 2019 at 17:52, Arjun Salyan wrote: > > As suggested, I have made an attempt at

Re: GSoC 2019 [Collect build statistics]

2019-03-14 Thread Umesh Singla
Hi Arjun On Wed, Mar 13, 2019 at 10:22 PM Arjun Salyan via macports-dev < macports-dev@lists.macports.org> wrote: > As suggested, I have made an attempt at a basic demo app: > https://frozen-falls-98471.herokuapp.com > > Please review it and let me know if this seems fine. After applying any >

Re: GSoC 2019 [Collect build statistics]

2019-03-13 Thread Arjun Salyan via macports-dev
As suggested, I have made an attempt at a basic demo app: https://frozen-falls-98471.herokuapp.com Please review it and let me know if this seems fine. After applying any further inputs, I shall proceed with the documentation to setting it up. It is not completely static. The port information is

Re: GSoC 2019 [Collect build statistics]

2019-03-11 Thread Mojca Miklavec
On Mon, 11 Mar 2019 at 09:18, Arjun Salyan via macports-dev wrote: > > I have a couple of doubts here: > > 1. Once I install mpstats does it still send weekly reports? I could not find > the required code to do this in the port files. Code for manually submitting > is available in mpstats.tcl

Re: GSoC 2019 [Collect build statistics]

2019-03-11 Thread Mojca Miklavec
On Mon, 11 Mar 2019 at 09:41, Arjun Salyan wrote: > On Fri, Mar 8, 2019 at 11:08 PM Mojca Miklavec wrote: >> >> In the case of this Django app it probably makes sense to come up with a >> proof-of-concept demo (ideally including documentation about how to set it >> up and running, and either

Re: GSoC 2019 [Collect build statistics]

2019-03-11 Thread Joshua Root
On 2019-3-11 19:18 , Arjun Salyan wrote: > I have a couple of doubts here: > > 1. Once I install mpstats does it still send weekly reports? I could not > find the required code to do this in the port files. Code for manually > submitting is available in mpstats.tcl but I am unable to locate the >

Re: GSoC 2019 [Collect build statistics]

2019-03-09 Thread Joshua Root
On 2019-3-9 22:55 , Saagar Jha wrote: > > FWIW, while I am not opposed to MacPorts adding clearly communicated, > opt-in, self-hosted analytics; I would be /very/ strongly against doing > this if any of these conditions was not met. Doubly so if the initial > discussion to do this is made without

Re: GSoC 2019 [Collect build statistics]

2019-03-08 Thread Mojca Miklavec
On Fri, 8 Mar 2019 at 15:45, Arjun Salyan wrote: > > I do not understand : "perhaps include some basic functionality to allow > checking for build reproducibility". > > Please help me with that 'build reproducibility' point Others sent you some links about what build reproducibility is, please

Re: GSoC 2019 [Collect build statistics]

2019-03-08 Thread Mojca Miklavec
Hi, On Fri, 8 Mar 2019 at 17:12, Craig Treleaven wrote: > > Have you seen the following wiki page? > > https://trac.macports.org/wiki/StatisticsIdeas > > There are some deficiencies in the current data collected. A key issue is > whether a port was requested or installed as a dependency. That

Re: GSoC 2019 [Collect build statistics]

2019-03-08 Thread Craig Treleaven
> On Mar 8, 2019, at 9:45 AM, Arjun Salyan via macports-dev > wrote: > > Thank you Mojca. > > The provided references have cleared a lot of my doubts and I am really > interested to do this project: 'Collect build statistics' > > Here is what I have understood so far: > 1. dynamic page for

Re: GSoC 2019 [Collect build statistics]

2019-03-08 Thread Marcus Calhoun-Lopez
> On Mar 8, 2019, at 7:45 AM, Arjun Salyan via macports-dev > wrote: > > Please help me with that 'build reproducibility' point and also how do I plan > from here (I know Django, but I am still learning about MacPorts)? There is a site on our Wiki on reproducible builds:

Re: GSoC 2019 [Collect build statistics]

2019-03-08 Thread Arjun Salyan via macports-dev
Thank you Mojca. The provided references have cleared a lot of my doubts and I am really interested to do this project: 'Collect build statistics' Here is what I have understood so far: *1.* dynamic page for each port displaying basic information (description, version etc.), installation stats,