I don't think users need to understand graph theory for git, but hardware isn't exactly like software so setting some rules about branching etc. might clarify usage. As I understand that with software commits not made to branches can be lost/deleted by git, but I'm not sure I understand how it may apply to binary files. The constant uploading of tiny changes to files small and large is why Michael had to limit the file size for the wiki. Anyway I see how you are structuring your repos so far with a few branches for features. With a few people it is basically one dev working on a branch alone. With more devs communication and team assignment of issues probably becomes important to eliminate conflicts. I'm guessing that is what you mean by peer to peer features?
I think Marcin is overeacting with git as a go no go thing. You can try it and learn it while keeping your wikis and everything. OSE don't have to migrate to git, we can just partner up with the developers that want to also learn git, and gitlab for file management and p2p cooperation. But instead of just trying to figure it out all by yourself the best is to learn with people that know the tool. Thats how we did it, I learned the tool and then gave tutorials and made practices with manolis and the rest of the team.
Feel free to invite the rest of OSE Community here, as I cannot reach them myself. I also shared you a book about open source I made with illustrations, feel free to share it as well.
actually it was a suggestion and remark from OSE
we are having duplicates in github and gitlab
but communicatio and project management takes place in gitlab
any plans to update the links on the homepage?
yes actually hehehehe
I should do it right away!
ah that is cool!!! ;)
we want to actually present repos content with gitlab APIs to filter repos per topics, for instance
Prague!! :smile:
Looks nice the robotica forum
can you share your email so I can add yo to gitlab?
first dot last at gmail
username @zwn
to update it and learn git, gitlab, etc
so the plan is to have a repo documented properly to have a demonstrator of open source documentation
but also for design improvements, etc.
is there a plan to merge them back to master?
we have different options there:
And the idea was to decide with them,
one option is to have a repo with different folders for different versions
and a well documented readme guiding the users
other is to point in the readme to different branch links
maybe in a subfolder
I think the best here is to chose a scalable model