#572 Move to git (and github)?

[Vanuan]

It's been a long time since the last version of cvs is released.
Maybe, it's the time to move to a more modern VCS?

[Vanuan]

BTW, I didn't find contribution guide anywhere.

I've imported SweetHome3D module's cvs history to GitHub:

https://github.com/Vanuan/sweethome3d

[Emmanuel Puybaret]

CVS is available by default in Eclipse, simple to learn and works very well for me.
I prefer to program new features in Sweet Home 3D than losing my time learning an other VCS.

[Hugo Ribeiro]

I don't think you will lose your time learning another VCS (or language or whatever) ;)

Also think that is OK use CVS if this solve your version control problems. Only because another one is modern or a trend, is not a good reason to change.

Maybe contributions workflows is more helpful here:

Sourceforge CVS contributions (1):

• Contributor contact Main developer requesting access for commits on CVS;
• Main developer grants or deny CVS access for commits;
• Contributor commit changes;
• Main developer review/accept/reject changes;
• Main developer merge changes;

GIT contributions (2):

• Contributor commit changes to his own public git repository;
• Main developer review/accept/reject changes;
• Main developer merge changes;

We can do 2 with CVS but VCS 'translation' can lose information and require manual merge/rebase.

[Vanuan]

FYI: Some time ago I've managed to translate CVS to git: https://github.com/Vanuan/sweethome3d/commits/master

But now I'm struggling with on how to make this translation incremental and automatic.

[Vanuan]

Is there a way I can contribute? Do you accept patches?

[Emmanuel Puybaret]

Sorry I forgot to answer to the question about contribution guide, which doesn't really exist. The plug-in developer's guide will bring you a general idea of Sweet Home 3D architecture, and you could read also this subject in the forum, as well as this other one.

You can contribute some 3D models, some plug-ins or some patches for Sweet Home 3D itself. But as I'm the only developer of the core part of the software, I'll keep the right to integrate your patches or not, and I'll request that you give up your copyrights on submitted patches. Otherwise, copyrights management would become too complicate.

What do you have in mind?

[Vanuan]

I don't have any patches yet. Here are my thoughts to work on: https://github.com/Vanuan/sweethome3d/issues

Those are basically ideas. I neither have an experience to implement them nor I have any specific plans. Maybe I'm just not experienced with SH3D, and these are easy "fixable" by using a specific technique.

I asked about contribution guide to get a feeling "how open this project to contributions" and what is a potential to integrate my changes back if I end up with something useful.

Thanks for your answers.

[Emmanuel Puybaret]

Please prefer to discuss features in Sweet Home 3D forum.

Hope you can understand that I don't want to scatter comments about Sweet Home 3D development in many places.

[Emmanuel Puybaret]

Just moved Sweet Home 3D repository from CVS to SVN.

[Klemen Skerbiš]

Hi. It would be great if this project's source code moved to Github or Gitlab, as they are much more convenient, have a bigger user base and are just better. I think that this great project would benefit from this.

[Arthur Moore]

I'm going to +1 moving to Git.

I think the major pros you'll see are:

• Easier for developers to submit fixes
• Easier to do multiple small commits
• Easier to work on a specific issue without touching other branches
• Being able to swap branches without having to have another complete copy locally
• More freedom in platforms
• Can do commits offline and sync with the server when you get the chance.
• Most IDEs, and the Git GUI support per-line commits.

When it comes to fixes and patches, someone can make multiple small commits, do a "Merge Request", then when you request changes they can commit those changes and they will show up in the merge request.

The largest two issues I see new people have with git are:

• Branches are all in the same folder. You use git branch to change which one you're working on.
• You have a remote and local copy of the source, and have to sync them.

Most IDEs make this super simple, and can save tons of headache compared to SVN or similar.

[Bob van der Linden]

I love this software and I see a lot of potential for the JS version. I wish it was more well-known and got more outside contributions. It's hard to say for sure whether GitHub would help, but for me personally it would. It has taken me quite a while to find that there was a feature request section on the site 😅

[Emmanuel Puybaret]

Sorry but there are very little chances that Sweet Home 3D moves to GitHub in the close future. SourceForge.net provides also good services and many links go here.

[Bob van der Linden]

That's unfortunate, but understandable. It's a big shift.