MIR residents learning about Github - a rite of passage

Makers in residence are supposed to deliver and publish on the web the output of their experience at WeMake.

Finding the right way to record and develop a innovative and open experience seemed therefore a matter of concern in designing the opencare MIR program.

During the last weeks GitHub, a social network for developers, became a obliged point of passage for some people at WeMake.

Github allows to create repositories, communities and webpages (gh_pages), among the main features. Putting a project on github makes possibile for members to contribute remotely and for anyone to view and download it.

Not only makers, but some service designers involved had to take class on GitHub as well.

The idea was to instruct participants and support them to create by github repositories and pages.

Although github is very known and used, not everybody there at WeMake is familiar with it.

I’ve been knowing Github for some years, but is interesting to follow conversations and see how different persons see and use it.

GitHub is NOT open source, use GitLab

The intention is good, but GitHub is not an open source tool. I suggest to use GitLab, which includes an issue management tool. GitLab also acquired Gitter which is an unlimited equivalent of Slack.

Different website exist that give free/libre and open source alternatives to proprietary code, such as FramaSoft.