Development migrated to Private repositories?

[dcervi]

Hi,

During last weeks I saw new 4.1 unstable builds are being released, but since a month ago almost no new commits were submitted to public github or gitlab repositories.

Have development been migrated to private repositories? And if so, why?

I liked to have a look every morning to see the latest improvements. Anyone was able to learn how Recalbox works internally, and contribute with improvements or troubleshoot their problems and adapt it to their needs. Now it's impossible to do this if we want to be up to date with latest releases.

I think one of the main reasons for Recalbox becoming what it is today was it being public open source. I hope it stays this way for the future, not becoming a private/commercial project.

[acris]

Hello
Problem Server: off
developpers and admin are in holidays or lot of work in real life.

[dcervi]

New unstable releases keep coming and on public repository latest commit is from February 26. Now nobody can help with development because we don't have access to the source code for the latest changes.

I'm in no way complaining of the rather slow development of Recalbox compared to other available systems, but I think keeping all development public like before would speed things up and make Recalbox a better system overall.

[Substring]

@dcervi I understand how frustrated you can be, but it doesn't mean you can't submit any PR on the curent code available on github. Whether it's conflicting or not is our problem during the merge.

Recalbox is open source, so recalbox code will be made available when it's time to.

On what would you wish to contribute ?

[rtissera]

@dcervi : I totally agree with you.
Sounds like I will port my fixes/enhancements over batocera.linux (Recalbox fork)
http://github.com/nadenislamarre/batocera.linux/