Github Restructuring

[ghindman]

All,

We have some pending product requirements that will necessitate getting some OpenAvnu components into common distros. Towards that end I would like to reopen the discussion on restructuring the OpenAvnu repo to make the various components more consumable by external distributions.

We would like to start with breaking the following folders out into top-level repos under the AVnu github project: kmod/igb lib/igb lib/libavtp daemons/gptp

If github admins can create the top-level repos I will commit to moving the code over and untangling any build/test dependencies so that everyone still builds properly.

From a timing/coordination standpoint, if we do a clone then no exiting project dependencies will be broken until everything is fixed up, the only downside would be changes would have to be tracked between the master and the clone until the master is retired. Alternatively we could either freeze those project until completed, or push all of the changes at once, but the latter would require considerable coordination.

Thoughts/concerns?

[avinash-palleti]

git rebase the forked repo on top of the initial commit.

That's when i got so many merge conflicts. Anyway i did force push all the commits to gptp repo now.

[aguedes]

I merged libavtp to master. Want branch/merge policy do we want for libavtp? OpenAvnu uses the convention that all pull requests come to open-avb-next. Do we want something similar in libavtp? I don't much mind what is decided as long as it is written up in the readme. Comments?

About this, I suggested something in https://github.com/AVnu/libavtp/issues/2. Let's keep this conversation centralized there please :)

[ghindman]

@avinash-palleti was this fully completed? https://github.com/AVnu/gptp/issues/16 indicates Travis is still not picking up the gptp job