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
userna
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 a
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 wou
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
>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 cas
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 organisa
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 CrossWir
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
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 th
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 po
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 to draw other developers.
To move forward with this:
1) I would actually need access to the github 'crosswire' organizat
Indeed. It's not a principled stand that I'm refusing to get Subversion
going. It's simply that it's too much work that I haven't bothered and
don't foresee doing so anytime soon.
And, with no setup to automatically test the scripts in all the
environments they must support, it's not likely others
12 matches
Mail list logo
