moved xdi2-zephyr to Github organization

[Markus Sabadello]

Hi Shrey and others,

So I think I understand the most basic collaboration mechanisms of Github pretty well, i.e. forks and pull requests.

This is what Animesh and I used very effectively when we implemented link contracts a while ago.

Now I began wondering how 1. Github organizations and members, and 2. issue tracking really work.

This would be useful for Shrey and me I think.

So I moved the xdi2-zephyr repository into an "organization", and its URL is now

https://github.com/projectdanube/xdi2-zephyr

instead of

https://github.com/peacekeeper/xdi2-zephyr

The advantage of this, as I understand it, is that we can create "issues" that both Shrey and I can see and keep track of.

I played with this and created a few such issues:

https://github.com/projectdanube/xdi2-zephyr/issues

Shrey did you get any notifications that I created the issues? What do you think about this approach?

This doesn't change anything about the code development, i.e. Shrey and I would still have our own copy (fork) of the "xdi2-zephyr" repository and can pull and merge code.

Markus

[Shrey Mehrotra]

Hi Markus,

I got the notification mail of issues that you have assigned to me.

 I think this would be a good practice as:

1. The list of open issues is available to all who would be going to use this project or work on this project.

2. If any issue has been found, it can be easily assigned or communicated to concerned person.

3. Enhancements/Suggestions could also be added and assigned in the list.

It is good to use this Issue/Enhancement tracking feature of github, I will look into the detailed working of this.

Regards,

Shrey

[Markus Sabadello]

Okay sounds good, yes let's just start playing with these initial 3 issues that I added, and we can create new ones as they come up.

thanks,

Markus