Re: [sword-devel] CrossWire and git

Hi Troy, Greg! Any progress on this initiative? :) Best regards, Tobias On 3/17/23 8:09 PM, Troy A. Griffitts wrote: I don't want this to turn into a debate. I agree, we need to move source control to git. I even mostly agree we should do most of our dev work on github for the visibility

Re: [sword-devel] CrossWire and git

WORD Developers' Collaboration Forum" Betreff: Re: [sword-devel] CrossWire and git Private repos on GitHub free have very limited access controls (I don't know about Gitlab).   I have no objection to using GitHub.    On Sat, Mar 18, 2023, 15:25 Karl Kleinpaste <k...@kleinpaste.org>

Re: [sword-devel] CrossWire and git

Private repos on GitHub free have very limited access controls (I don't know about Gitlab). I have no objection to using GitHub. On Sat, Mar 18, 2023, 15:25 Karl Kleinpaste wrote: > On 3/18/23 07:40, Peter von Kaehne wrote: > > GitLab allows private repos > > > I don't know where the idea

Re: [sword-devel] CrossWire and git

On 3/18/23 07:40, Peter von Kaehne wrote: GitLab allows private repos I don't know where the idea comes from, that GitHub doesn't have private repos. It certainly does, as I use one, for a network project/toy most of you have never heard of (and probably never

Re: [sword-devel] CrossWire and git

On 2023-03-18, 14:57 GMT, Troy A. Griffitts wrote: > Guys who prefer GitLab, I am sorry. No university research > project, no commercial job has ever asked me to use GitLab. They > have all asked me use GitHub. From a purely popular choice and > to prevent all of us from having to create yet

Re: [sword-devel] CrossWire and git

I'm familiar with both. GitLab at work (privately hosted) and GitHub for my open source work. I like GitLab. However, I think the GitHub CI infrastructure is more powerful. Furthermore, pretty much all SWORD frontends are already on GitHub (except Bishop). Best regards, Tobias Am 18. März

Re: [sword-devel] CrossWire and git

On Sat, Mar 18, 2023, 13:30 Fr Cyrille wrote: > > > Le 18/03/2023 à 15:57, Troy A. Griffitts a écrit : > > Guys who prefer GitLab, I am sorry. No university research project, no > commercial job has ever asked me to use GitLab. > > The french wikipedia says about : The software is used by

Re: [sword-devel] CrossWire and git

Le 18/03/2023 à 15:57, Troy A. Griffitts a écrit : Guys who prefer GitLab, I am sorry. No university research project, no commercial job has ever asked me to use GitLab. The french wikipedia says about : The software is used by several large IT companies, including IBM, Sony, the Jülich

Re: [sword-devel] CrossWire and git

>From an administration and uptime point of view, I'm in support of GitHub. The only place I've used Gitlab is at Red Hat and only for internal projects there. From a pragmatic standing I'm in full support of GitHub, and with an existing Gitlab instance, we're already set if something comes up in

Re: [sword-devel] CrossWire and git

No objection - as long as it is accepted that the modules stay in GitLab.      Gesendet: Samstag, 18. März 2023 um 14:57 Uhr Von: "Troy A. Griffitts" An: "SWORD Developers' Collaboration Forum" , "Greg Hellings" Betreff: Re: [sword-devel] CrossWire and git Guys

Re: [sword-devel] CrossWire and git

Guys who prefer GitLab, I am sorry. No university research project, no commercial job has ever asked me to use GitLab. They have all asked me use GitHub. From a purely popular choice and to prevent all of us from having to create yet another account (I am sure most everyone already has a GitHub

Re: [sword-devel] CrossWire and git

On Sat, Mar 18, 2023, 06:41 Peter von Kaehne wrote: > GitLab vs GitLab > > [image: image3-1.png] > > GitLab vs GitHub: Top 10 Differences between GitHub and GitLab > > intellipaat.com >

Re: [sword-devel] CrossWire and git

GitLab vs GitLabGitLab vs GitHub: Top 10 Differences between GitHub and GitLabintellipaat.comThere is plenty more but this gives a decent summary. GitLab allows private repos which I think are a really useful thing. I think it should also be easier to integrate our own GitLab stuff or move it if

Re: [sword-devel] CrossWire and git

On 2023-03-18, 09:55 GMT, Fr Cyrille wrote: > I am very happy with this progress in your thinking about git. I just > reiterate my preference for gitlab, where as Peter has already pointed > out we now have all our modules. It would be consistent to add the sword > sources there as well. >

Re: [sword-devel] CrossWire and git

I am very happy with this progress in your thinking about git. I just reiterate my preference for gitlab, where as Peter has already pointed out we now have all our modules. It would be consistent to add the sword sources there as well. @David I don't particularly use github for my personal

Re: [sword-devel] CrossWire and git

Yay! Thanks for your efforts to move into this direction! :) Exciting news! Best regards, Tobias On 3/17/23 8:27 PM, Greg Hellings wrote: Troy, I know we've discussed the merge issue in the past. In order to help point in the right direction, a couple of questions: Do you still envision

Re: [sword-devel] CrossWire and git

Now I'm attaching a simplified version of the CODEOWNERS for just the sword repository. I've combined the configure.ac, Makefile.am, and CMakeLists.txt entries to single entries and I've sorted the entries alphabetically (I think...) ignoring any leading "/" characters. I've also substituted

Re: [sword-devel] CrossWire and git

I'm attaching a Python file that gives a basic go at parsing the access file into a GitHub CODEOWNERS file, along with the output I get from it. It's not flawless, but it does properly transform group names to "@crosswire/group-name". It also assumes users have the same username between Crosswire

Re: [sword-devel] CrossWire and git

I apologize, I notice some of the file was cut. What I sent gives the idea. If it's helpful for me to send everything then I will do that. *--Timmy BraunCell: +501-615-4531* On Fri, Mar 17, 2023 at 3:44 PM Timmy wrote: > Also, if there's code that should not be available to the public it

Re: [sword-devel] CrossWire and git

Also, if there's code that should not be available to the public it would have to be put in a separate private repository with access granted just to the person(s) or team(s) that should have access. *--Timmy BraunCell: +501-615-4531* On Fri, Mar 17, 2023 at 3:42 PM Timmy wrote: > From my

Re: [sword-devel] CrossWire and git

>From my research and some help from ChatGPT, I think the below text would be the replacement for the access file (for GitHub CODEOWNERS). Note that I've simplified the Makefile.am, configure.ac, CMakeLists.txt files to one line. This means all files with that name would be included (saying in

Re: [sword-devel] CrossWire and git

This thread so far mentions GitHub but some of our projects for module content development have been hosted on GitLab and some on the GitLab instance installed on the CrossWire server. IIRC, Peter owns and manages users on the latter (git.crosswire.org), and possibly also the CrossWire

Re: [sword-devel] CrossWire and git

Just one suggestion - a huge amount of our module work happens already on GitLab rather than GitHub. I think the reasons were to do with unfriendly policy changes of GitHub - but I am not entirely sure anymore. Cyrille, Dominique or David might know. We already run a GitLab instance on our

Re: [sword-devel] CrossWire and git

Current owners are myself, DM, Karl, and Doug Campos. I sent Troy an invite to it. --Greg On Fri, Mar 17, 2023 at 3:09 PM Peter von Kaehne wrote: > I think I own the CrossWire organization though not sure anymore. I will > look into it this weekend and approve you to the highest level if I can

Re: [sword-devel] CrossWire and git

I think I own the CrossWire organization though not sure anymore. I will look into it this weekend and approve you to the highest level if I can do soSent from my phone. Please forgive misspellings and weird “corrections”On 17 Mar 2023, at 19:28, Greg Hellings wrote:Troy,I know we've discussed

Re: [sword-devel] CrossWire and git

Troy, I know we've discussed the merge issue in the past. In order to help point in the right direction, a couple of questions: Do you still envision self hosting the repository as you have SVN and using GitHub to mirror, or do you anticipate self hosting a repository that is just an insurance