Author Topic: Will C::B ever move to Git w/ Github or Gitlab?  (Read 7666 times)

Offline sodev

  • Regular
  • ***
  • Posts: 432
Re: Will C::B ever move to Git w/ Github or Gitlab?
« Reply #15 on: May 03, 2021, 07:16:51 pm »
GitHub is the Facebook/Instagram for developers, this is where the cool kids hang out these days 8). Getting likes (== lines of code) is serious business. And people are lazy, they can't be bothered with another development account beside the GitHub one ;D.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13409
    • Travis build status
Re: Will C::B ever move to Git w/ Github or Gitlab?
« Reply #16 on: May 03, 2021, 07:27:44 pm »
GitHub is the Facebook/Instagram for developers, this is where the cool kids hang out these days 8). Getting likes (== lines of code) is serious business. And people are lazy, they can't be bothered with another development account beside the GitHub one ;D.
Yes, but neighter C++, nor wxWidgets, nor native GUI development is cool in 2021.
So if someone wants to be cool he/she has to do something else like rust, haskell, modern javascript (I don't know what the cool kids use today) programming.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Lazauya

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: Will C::B ever move to Git w/ Github or Gitlab?
« Reply #17 on: May 03, 2021, 07:36:20 pm »
Why do you want the whole project to be on github? What would be the benefit for you as an external to C::B developer if the whole project is on github (sans the requirement to have a forum/sf.net login)?

It increases visibility and transparency. Just speaking anecdotally, it took me half an hour just to find the main repository for C::B. (Granted I'm not always the sharpest.) I truly think that switching would increase the amount of contribution, which would generally benefit users of C::B. Git is the current standard, and it doesn't seem to be going away any time soon. I don't have anything against Sourceforge or SVN except for their generally accepted antiquated-ness. I just think that, for an open source project, C::B seems opaque from the outside, a problem I feel could be alleviated by switching off of Sourceforge.

When I say switch to Git I don't mean Github necessarily. There's also Gitlab, which offers essentially the same services as Github.

Set up what? You don't have full access to the sf.net project, so you probably cannot dump and import the tickets. You'll have to do some kind of user remapping which you cannot do without talking to devs and other users which have posted tickets.

Set up CI. You said earlier that you were having troubles with Windows & CI. I have plenty of Windows development experience.

The tickets issue could be alleviated by a transition period. Just ignore new tickets on SF and tell everyone to post on whatever is switched to.

Offline Lazauya

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: Will C::B ever move to Git w/ Github or Gitlab?
« Reply #18 on: May 03, 2021, 07:38:19 pm »
Yes, but neighter C++, nor wxWidgets, nor native GUI development is cool in 2021.
So if someone wants to be cool he/she has to do something else like rust, haskell, modern javascript (I don't know what the cool kids use today) programming.

It is cool, but only for "punks" who write make game engines or write graphics libraries LOL.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13409
    • Travis build status
Re: Will C::B ever move to Git w/ Github or Gitlab?
« Reply #19 on: May 04, 2021, 01:19:34 am »
Set up CI. You said earlier that you were having troubles with Windows & CI. I have plenty of Windows development experience.
I know how to setup CI.
I know what I have to do to make it work, but given that it won't be reliable I won't bother for now.
Someday if I (or someone else) port the build system to cmake or meson, I'll give it another try.

But this is unrelated to git/github/gitlab.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline WinterMute

  • Multiple posting newcomer
  • *
  • Posts: 24
    • devkitPro
Re: Will C::B ever move to Git w/ Github or Gitlab?
« Reply #20 on: May 04, 2021, 11:37:11 am »
Thing about github though is that some employers like to look at a candidate's github commit history and upstream contributions. If you just give credit in the commit message then they won't show up in the contributor list.
You can list the hashes in a repo in your resume/cv if this is the only public thing you've done and you're proud of it and thinks it is important.

No offence but this is a completely absurd statement. No employer is going to look at a list of hashes in a CV and cross reference them against an unofficial mirror of a subversion repository. I feel like you're just trolling with quite a lot of these answers. It's perfectly acceptable to just say you don't want to move to github you knpw.

Quote
I only use svn to checkout the repo in order to make ubuntu night builds. I use git exclusively for everything else, I'm fine if you post git patches or pull requests. So C::B is not requesting svn patches only. But the github trolls insist that the whole project needs to be on github otherwise they won't contribute.

I don't really understand why you'd use subversion for anything if you've essentially already moved to git. Why are you using subversion for that?

Everything else I kind of feel is people talking at cross purposes. It's not necessary to move everything to github. I'd be more than satisfied with an official github repository where PRs can be made and discussed. Where PRs could be merged once they're acceptable. Ideally using the git workflow that then leaves the author intact so it shows up on github stats. So git blame works and you know who to ask about particular code if it's confusing.

I guess the real question is do any current code::blocks devs not use git for development? Is there any reason not to switch development completely to git now? Forget about github and all the other stuff. Would it be possible to have the code maintained in a git repository & contributions made via git format-patch style patchsets at the very least?

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13409
    • Travis build status
Re: Will C::B ever move to Git w/ Github or Gitlab?
« Reply #21 on: May 04, 2021, 12:54:08 pm »
I don't really understand why you'd use subversion for anything if you've essentially already moved to git. Why are you using subversion for that?
There was a discussion in the past, there were people against a move to git and that's it. I've not bothered to reopen it since, because it doesn't matter that much. I have better things to spend my time.

Where PRs could be merged once they're acceptable. Ideally using the git workflow that then leaves the author intact so it shows up on github stats. So git blame works and you know who to ask about particular code if it's confusing.
git blame still works, because we keep the original author mostly in tact. We use ticket ids and so on.
The PR workflow on github is horrendous IMO, so even if we switch on git I'd not auto-merge PRs.
I don't know how you ask people on random commits, github doesn't allow it, the email in git doesn't need to be a real one. Sometimes I use my real email, but most of the times it is an email I don't even have access to.

I guess the real question is do any current code::blocks devs not use git for development?
No idea, I've not bothered with this topic in the last 5 years.

Is there any reason not to switch development completely to git now?
Answered already above.

Would it be possible to have the code maintained in a git repository & contributions made via git format-patch style patchsets at the very least?
You can do this already. I'll take the patches apply them, add the contribution info, edit them if required (most of the patches do require edits anyway) and push them to svn.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Lazauya

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: Will C::B ever move to Git w/ Github or Gitlab?
« Reply #22 on: May 12, 2021, 03:48:08 am »
Someday if I (or someone else) port the build system to cmake or meson, I'll give it another try.

I started migrating to cmake. I know you said that this wasn't directly related to Git, but I do hope it makes Github/Gitlab integration easier. I couldn't create a branch on your repository, so I forked it and created the branch on mine. Here's the branch: https://github.com/Lazauya/codeblocks_sf/tree/cmake

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13409
    • Travis build status
Re: Will C::B ever move to Git w/ Github or Gitlab?
« Reply #23 on: May 12, 2021, 10:14:39 am »
Deleting autotools as a first step is the wrong move...
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Lazauya

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: Will C::B ever move to Git w/ Github or Gitlab?
« Reply #24 on: May 12, 2021, 06:06:30 pm »
Deleting autotools as a first step is the wrong move...

I don't have the authority to delete anything from any official repositories. If you're referencing how it's gone from my branch, that was just for making the conversion easier. The only thing thay would be incompatible would be the config.h.in, so maintaining the legacy build system alongside cmake should be simple enough.

In any case, what would be the first step? What can I do to make this happen? You said that you you don't want to spend your time doing it, but I do.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13409
    • Travis build status
Re: Will C::B ever move to Git w/ Github or Gitlab?
« Reply #25 on: May 12, 2021, 07:32:49 pm »
If you delete the autotools build system we don't have the official/current build system (used to make linux packages) to compare if the cmake system is correct or not.
So deleting it as a first step is wrong, at least if your goal is to be able to merge your branch in the official repo.
So if you want to have a chance of the work being integrated in the official repo, please leave autotools intact. Deleting it is the easiest thing.
On the other hand if you just want to play with cmake and then drop the thing after a while then it is fine to delete autotools or do whatever you want. :)

Also I'm not sure I like the idea of config.h.in. I'd rather not use it. The internal C::B build system doesn't use it and we're fine, without it.

p.s. The switch to git doesn't depend on using cmake or not, these two are orthogonal. Mentioning this to prevent some possible confusion.
p.p.s. It is a requirement that you preserve the internal build system, too.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13409
    • Travis build status
Re: Will C::B ever move to Git w/ Github or Gitlab?
« Reply #26 on: May 12, 2021, 07:46:53 pm »
Also it would be best to start a separate topic about the cmake stuff when you have something that works...
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Lazauya

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: Will C::B ever move to Git w/ Github or Gitlab?
« Reply #27 on: May 12, 2021, 08:01:51 pm »
If you delete the autotools build system we don't have the official/current build system (used to make linux packages) to compare if the cmake system is correct or not.
So deleting it as a first step is wrong, at least if your goal is to be able to merge your branch in the official repo.
So if you want to have a chance of the work being integrated in the official repo, please leave autotools intact. Deleting it is the easiest thing.
On the other hand if you just want to play with cmake and then drop the thing after a while then it is fine to delete autotools or do whatever you want. :)

Like I said before, this is a non-issue. Adding back autotools is simple. I'll add it back before I even try merging to master, of course. (Or move the CMake files to a clone of the original, whatever works better in the end.)

Also I'm not sure I like the idea of config.h.in. I'd rather not use it. The internal C::B build system doesn't use it and we're fine, without it.

Perfect. Then I'll just remove it altogether in my next commit.

p.s. The switch to git doesn't depend on using cmake or not, these two are orthogonal. Mentioning this to prevent some possible confusion.

So what DOES moving to Git depend on? I want to do THAT along with moving to CMake; I think using CMake is a very necessary modernization, and so I will continue until it's as feature complete as I can make it. However, I think moving the project to a more modern platform like Github, Gitlab, or even an org-maintained Git repo (like what Blender has) is a must. I like full IDE's and CB. I really don't want this project to be a relic any longer. I don't think bug fixes and QOL improvements will fix that, I think it needs more radical change. But that's just me.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13409
    • Travis build status
Re: Will C::B ever move to Git w/ Github or Gitlab?
« Reply #28 on: May 12, 2021, 08:20:40 pm »
So what DOES moving to Git depend on?
It depends on the development team deciding that moving to git, github, gitlab or anything like that is worth the effort and it is beneficial.

I want to do THAT along ...
It is not up to you to do that or to decide it at. At least at the moment.
If you contribute enough good work you can request being added to the development team.

I like full IDE's and CB. I really don't want this project to be a relic any longer.
It will stop being a relic if people work more on it. Your proposition is that the use of svn/sf.net stops quality work being contributed.
I don't believe this to be true and it is hard to measure it, so it is for you hard to prove it. And we're actually on github and we're actually using git...

I don't think bug fixes and QOL improvements will fix that, I think it needs more radical change. But that's just me.
So you think that switching to git magically would make the debugger plugin to actually work in the real world?
Or it will auto integrate something like LSP to make CC support C++2099?
Or it will make the build system to utilize modern mutli-core cpus?
Or it will add better cmake/meson support...

I'm out of this topic. If you want to discuss your cmake contribution please start new one.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Lazauya

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: Will C::B ever move to Git w/ Github or Gitlab?
« Reply #29 on: May 12, 2021, 10:26:52 pm »
So you think that switching to git magically would make the debugger plugin to actually work in the real world?
Or it will auto integrate something like LSP to make CC support C++2099?
Or it will make the build system to utilize modern mutli-core cpus?
Or it will add better cmake/meson support...

Looks like I got my laundry list. I'll get to work.