Gsoc 18 Project | Collect build statistics

[Jackson Isaac]

On Sun, Apr 29, 2018 at 1:21 PM, Mojca Miklavec <mojca at macports.org> wrote:
>
>
> I would say that the next most reasonable step (apart from any other
> thing from the list I sent in the beginning) would be to create a
> repository and put all the documentation / plan / milestones / sample
> page etc. to that repository.
> This means:
> - deciding for the name

We can go with something like 'macports-buildstatistics' for repo name.
If it would be a branch under /macports-base then 'gsoc18-buildstatistics'.

Although having another repository under /macports makes more sense, since
the project would be unrelated to what macports-base does.

> - asking someone with permission to create a repository inside
> macports org (and make sure that Vishnu has commit rights on that
> repository)

I believe the PortMgr would be able to create the repository for us ?
I don't have the
sufficient permission to create repo under /macports is what GitHub tells me.

As for commit rights, I had sent out an email on 26 April for getting
@macports id for Vishnu.

Vishnu,
Could you please search for 'Request for macports id for GSoC 2018 student'
thread in your mailbox and reply with your preference for the username ?

> - deciding how exactly this should be done
>
> I suggest to do most of development in a separate development branch
> and make sure that whatever ends up in master gets a review. Or
> something similar. We need a way to distinguish reviewed code from
> playground.
>

Having separate branches for testing and playing around sounds good to me.
We can then cherry pick the commits and have reviewed code on master.

-- 
Jackson Isaac