Gsoc 18 Project | Collect build statistics

[Vishnu]

Hi

Yes I was laos thinking about it for some time.

Please someone from infra team create another repository.
There I will maintain code in a proper way by Using Pull Requests.So that
code gets merged only if clean.


Regarding your general remarks.
I will look into them.
Please make the repo as soon as possible.


Things I will be doing:

- Limit testing.json to 1000 ports only.
- Implement Categories table and the modified port table.
- Implement some sort of test atleast very trivial but will
- Did not index the port table so far.But will now index the table.



Things discussed in the last meeting:

Implement these as well
- Implement ability to mark deleted ports in the port table itself
- For every port just display the last 5 - 10 commits on the ports
- Just mention the version everywhere. No portversion id.
- When build started and ended.

Future Goals:
- implment obsolete
- Fix portindex2json, atleast maintainers
- Differential feature to be in stretch goals
- Port History
- Port Version table

Also I think finalising the database ticket will be for long.As we are
continusally evolving it so... Probably the milestone to create Database
structure within the week may not be possible.

Mojca you said something about static files.
I think we should have all Javascript also in a separate individual file.
That's why in a seperate individual file.


Thanks

On 15 May 2018 at 02:53, Mojca Miklavec <mojca at macports.org> wrote:

> Dear Vishnu,
>
> I just wanted to say that we *really really really* need to fix the
> repository since it's unacceptably large (some commits checked out are
> 240 MB, the size to transfer the contents is 133 MB).
>
> No matter what you think of it regarding breaking links etc., we
> definitely won't be hosting your linux bootloading images in our repo.
> This is one of the reasons where ... pull request make a huge
> difference over simple commits because such errors would be caught
> early on.
>
> Other general remarks:
> - please delete database_design.txt now that you have the markdown document
> - you should not commit __pycache__ folders
> - in dropdown.css you are mixing tabs and spaces; pick one and use it
> consistently, don't mix the two (and if you use spaces, use 2 or 4,
> not 9; identing is totally lacking)
> - by asking you to move code to static I did not mean that you should
> put data points for a graph to static files.
> - do not put 20 MB json files with sample data to the repository
>
> My suggestion would in fact be to start with an empty repository again
> and ask you to create your first pull request with cleaned up data.
>
> Mojca
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20180515/3a616792/attachment-0001.html>