Dec 15, 2025, 9:15:45 PM
|
Sweet Home 3D Forum » List all forums » » Forum: Developers » » » Thread: Move to git (and github)? » » » » Post: Re: Move to git (and github)? |
Print at Dec 15, 2025, 9:15:45 PM |
| Posted by Kunda at Aug 6, 2018, 12:23:07 PM |
|
Re: Move to git (and github)? @Puybaret fair enough though I do have some responses if you'd be interested to hear? For your information, contributors to Sweet Home 3D are mainly translators, 3D model designers and people helping other users in this forum or with documents they share. These people are rarely aware of how a repository works, and I take care to integrate their contributions obtained through other easier means (mails or SourceForge tickets). This is typical, right? A large part of the community usually isn't oriented toward infrastructure so much. Though, and this is not what I'm recommending, they could be captivated to learn more in that direction. End-users are educable. Again I'm not advocating for this per se. There are also a few programmers who proposed some plug-ins and until now, this seems to have been a good way to learn Sweet Home 3D architecture and integrate additional features, without taking the risk to deteriorate its quality. This is the power user/developer portion of the community. They have a lot more perseverance, interest, and captivation to learn and contribute. It seems that they can code plugins independent of having you merge their code in to trunk. Beside that, I'm the only developer of Sweet Home 3D application, which makes me wonder how useful it will be to take care of another repository system. This is an important reason, time-management and learning a whole other repository system. So in this regards, Github/Gitlab acting as a mirror, you can choose to remove the option for people to report issues/bugs and just soley accept Pull Requests. To me this is not much work. I anticipate there will be people that would want to converse with you about the PR but you can simply respond to them either there or direct them to this forum for further discussion. Also I will say in thread #3113 the OP was asking to look at past commits in order to learn, I'm assuming about, how you approached fixes. I personally find SF not a very friendly interface to use to browse code especially code history, it takes many clicks and the interface is clunky. Essentially creates a high barrier for entry and simplicity in these more modern times when devs are used to slicker and more robust UIs. All I ask is to consider this idea and if you're inclined, try a test run...maybe a few months. If you need help with writing documentation on how to submit PRs etc...I'd be happy to. I've written some for other projects already. I think we may be surprise at what independent devs may submit, especially to a project like this one. Though, Java isn't the most perceived collaborative language on repository sites like Github or Gitlab, I thunk we'll still be pleasantly surprised. |
|
|
Current timezone is GMT Dec 15, 2025, 9:15:45 PM |