[Unity-idm-discuss] Unity travels to GitHub

[Krzysztof B. <kb...@un...>]

Dear Subscribers,

It is time to make this official:

after couple of days of very intensive work Unity was moved to GitHub 
from Assembla which hosted the project for nearly 5 years.

The new source code repository address is:

https://github.com/unity-idm/unity

This change was motivated by the fact that Assembla resigned some time 
ago from providing free hosting for Open Source projects. Unity project 
was not closed (nor there were any treats from Assembla) but there were 
numerous signs that the plan that Unity project was using is deprecated 
if not abandoned. What is more using Assembla for outsiders started to 
be a pain and some of the features stopped to work correctly.

GitHub was a natural choice, as de facto standard hosting provider for 
Open Source community. Hopefully most of you have already GitHub 
accounts so collaboration should not be disturbed.

Currently the wiki is still in the process of being migrated. Eventually 
will land on Github wiki space.

There are no planned changes as of now wrt to this mailing list and SF 
as the distribution point, both work pretty well.

Assembla project will not be closed, but to ensure that it is not 
actively used I'll change all members' permissions to read-only access.

Unity issues tracker was moved to our own JIRA instance. We managed to 
preserve a complete history, loosing only some minimal parts of tickets 
metadata. There is public read only access enabled.

https://dev.unity-idm.eu/jira/projects/UY/issues

The issues tracker is one of the open points. JIRA that we moved too 
provides us with all required features to have a flexible project 
management. However, we have a license with a restricted number of users 
- suitable for the core team. Therefore we plan to collect your feedback 
from this ML and other ML channels that we have established and convert 
it to tickets on our own. We hope this will work out fine. In case a 
more direct collaboration will be required we can consider some 
alternatives, as for instance enabling the simple GitHub tracker as a 
frontend tracker.

Cheers,
Krzysztof