Git/Github info

The Jira used for moving uimaj to git has these bits of information. 1) The git repos exist in 2 places.  One is on GitHub.  The other is on git system run by apache, at the url https://gitbox.apache.org/repos/asf      1a) the name of the repo follows the naming conventions used for svn: followin

Re: Git/Github info

On 4. Sep 2019, at 15:34, Marshall Schor wrote: > > 3) Both of these repos (github and gitbox.apache...) can be used as git > remotes. GitHub comes with github extras - such as issues (we don't use, we > use > jira). I'm not sure if git pull requests are available on gitbox.apache. To avoid p

[jira] [Work started] (UIMA-6121) DUCC Book - review and update shared filesystem requirements, especially for Agents

[ https://issues.apache.org/jira/browse/UIMA-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-6121 started by Lou DeGenaro. -- > DUCC Book - review and update shared filesystem requirements, especially for > Age

[jira] [Assigned] (UIMA-6121) DUCC Book - review and update shared filesystem requirements, especially for Agents

[ https://issues.apache.org/jira/browse/UIMA-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro reassigned UIMA-6121: -- Assignee: Lou DeGenaro > DUCC Book - review and update shared filesystem requirements, especial

[jira] [Updated] (UIMA-6121) DUCC Book - review and update shared filesystem requirements, especially for Agents

[ https://issues.apache.org/jira/browse/UIMA-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro updated UIMA-6121: --- Fix Version/s: 3.0.1-Ducc > DUCC Book - review and update shared filesystem requirements, especially f

[jira] [Resolved] (UIMA-6121) DUCC Book - review and update shared filesystem requirements, especially for Agents

[ https://issues.apache.org/jira/browse/UIMA-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro resolved UIMA-6121. Resolution: Fixed Change set comprising revised DUCC Book with example use of ducc_rsync to populat

[jira] [Closed] (UIMA-6121) DUCC Book - review and update shared filesystem requirements, especially for Agents

[ https://issues.apache.org/jira/browse/UIMA-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro closed UIMA-6121. -- > DUCC Book - review and update shared filesystem requirements, especially for > Agents > -

Re: Git/Github info

hmmm, this goes against one of the apache "requirements": This page: http://apache.org/dev/writable-git says ASF releases *must* be cut from the canonical ASF Git repositories. Part of this page has some out of date links, but I'm guess this means that when you do a release, you start by cloning

Re: Git/Github info

I just asked INFRA on Slack about this. Daniel Gruno said the page linked below is very outdated, git repos at ASF are no longer experimental (as the page title suggests) and that all current info can be found here: https://gitbox.apache.org/ Considering that the gitbox URL above even explicit

Re: Setting up some branching conventions?

On 3. Sep 2019, at 23:55, Marshall Schor wrote: > > Any reason not to delete these? or is there another "best practice" way to > manage these? Not that I know of. > I assume deleting them makes them disappear from this list, but they'll always > be around in the repo and digging thru some logs

Re: Setting up some branching conventions?

On 3. Sep 2019, at 23:12, Marshall Schor wrote: > > I'm not sure about the value of this; it feels more complex, and the benefits > are not clear to me. Besides being able to bulk-protected all branches with a common prefix (using some "XXX/*" pattern), graphical git clients also have a habit of

[jira] [Created] (UIMA-6123) DUCC start_ducc should display NOTOK messages

Lou DeGenaro created UIMA-6123: -- Summary: DUCC start_ducc should display NOTOK messages Key: UIMA-6123 URL: https://issues.apache.org/jira/browse/UIMA-6123 Project: UIMA Issue Type: Documentatio

[jira] [Resolved] (UIMA-6123) DUCC start_ducc should display NOTOK messages

[ https://issues.apache.org/jira/browse/UIMA-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro resolved UIMA-6123. Resolution: Fixed Change set delivered. > DUCC start_ducc should display NOTOK messages > -

[jira] [Closed] (UIMA-6123) DUCC start_ducc should display NOTOK messages

[ https://issues.apache.org/jira/browse/UIMA-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro closed UIMA-6123. -- > DUCC start_ducc should display NOTOK messages > - > >

Re: Git/Github info

On 4. Sep 2019, at 17:22, Richard Eckart de Castilho wrote: > > I just asked INFRA on Slack about this. Escalating this to legal-discuss: https://issues.apache.org/jira/browse/LEGAL-478 Cheers, -- Richard

Re: Git/Github info

excellent!  thank you :-) -Marshall On 9/4/2019 2:56 PM, Richard Eckart de Castilho wrote: > On 4. Sep 2019, at 17:22, Richard Eckart de Castilho wrote: >> I just asked INFRA on Slack about this. > Escalating this to legal-discuss: > https://issues.apache.org/jira/browse/LEGAL-478 > > Cheers, >

If you ever need to chat with INFRA or other apache project team, consider joining the-asf.slack.com

I recently was made aware (from Richard's recent dev mail post) that the asf is now using "slack" - the messaging system. I signed up ( see https://the-asf.slack.com , and see below the sign-in, the line which says If you have an *@apache.org* email address, you can create an account

Git protection for uima-uimaj

On the asf infra slack channel, I asked about protection for uima-uimaj branches, what was set, how to see, etc. The answer was: >>>right now, nothing, which is actually an oversight on my part. i need to go >>>protect the master branch. >>>protect = refs/heads/trunk refs/heads/master refs/heads

Re: Git protection for uima-uimaj

I see in the GitHub docs that just turning on protection for a branch does (at a minimum): disables forced pushes, and prevents branches from being deleted. -Marshall On 9/4/2019 5:01 PM, Marshall Schor wrote: > On the asf infra slack channel, I asked about protection for uima-uimaj > branches, w

Re: Git protection for uima-uimaj

yes, thanks, I did that (set up a repo under my own account, to have a look). >From looking at the kind of display the gitbox.a.o website has, it looks like >it might be using the built-in-to-git GitWeb.  https://git-scm.com/book/en/v2/Git-on-the-Server-GitWeb -Marshall On 9/4/2019 5:12 PM, R