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

Offline sodev

  • Regular
  • ***
  • Posts: 427
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: 13196
    • 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

  • Single posting newcomer
  • *
  • Posts: 8
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

  • Single posting newcomer
  • *
  • Posts: 8
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: 13196
    • 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: 13196
    • 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!]