Re: Considering to move uimaFIT to git - comments?
congratulations! -M On 4/27/2018 4:05 AM, Richard Eckart de Castilho wrote: > uimaFIT is now officially on Git :) > > If you wish to commit via GitHub, please visit > https://gitbox.apache.org/setup/ to link your ApacheID to your GitHub account. > > There is a uima committers team. I believe if you link your Apache ID to your > GitHub account and have commit permissions on Apache, then you'll be added to > that team automatically. > > The repo is here: https://github.com/apache/uima-uimafit > > (and there is an Apache mirror of course). > > -- Richard > >> On 13.04.2018, at 05:12, Richard Eckart de Castilho wrote: >> >> Requested SVN->GIT migration for uimaFIT: >> >> https://issues.apache.org/jira/browse/INFRA-16347 >> >> -- Richard >
Re: Considering to move uimaFIT to git - comments?
uimaFIT is now officially on Git :) If you wish to commit via GitHub, please visit https://gitbox.apache.org/setup/ to link your ApacheID to your GitHub account. There is a uima committers team. I believe if you link your Apache ID to your GitHub account and have commit permissions on Apache, then you'll be added to that team automatically. The repo is here: https://github.com/apache/uima-uimafit (and there is an Apache mirror of course). -- Richard > On 13.04.2018, at 05:12, Richard Eckart de Castilho wrote: > > Requested SVN->GIT migration for uimaFIT: > > https://issues.apache.org/jira/browse/INFRA-16347 > > -- Richard
Re: Considering to move uimaFIT to git - comments?
Requested SVN->GIT migration for uimaFIT: https://issues.apache.org/jira/browse/INFRA-16347 -- Richard
Re: Considering to move uimaFIT to git - comments?
Hi, thanks for the answers! -Marshall On 4/12/2018 2:35 PM, Richard Eckart de Castilho wrote: >> On 12.04.2018, at 14:34, Marshall Schor wrote: >> >> +1 >> >> Good to start with a contained sub-part, and see how it goes, and see how the >> community reacts, etc. >> >> I have some confusion on whether this is a move to "github" or "git"? > Both. Maybe it would be possible to have an ASF-only git repo without making > use of GitHub, but actually one of the reasons I want to make the move is > to be able to make use of the GitHub Pull-Request / code review feature. > > INFRA will set up the repo such that mails generated from discussions on pull > requests will be send to one of our mailing lists, probably dev. This seems > to be one of the *special* features of the ASF<->GitHub integration, because > afaik GitHub itself does not have a feature to send issue/PR mails to a > mailing list. > >> If to github, that comes with lots of "extra" things, like issue tracking, >> wiki's, a >> static-web-page web-site (much like Apache). > I will not make use of these features for the time being. Issues continue > on Jira. The wiki will be turned off (if we need one, we have Confluence). > Also, we already have a website and do not need another one. > >> GitHub supports a bit of >> hierarchical organization, e.g. "Organizations" with various teams having >> various permissions (I may have this not quite right, I'm not an expert). >> >> How are permissions handled by ASF's use of GIT? Are there "teams" that >> correspond to commit access for UIMA projects? > There is an Apache organization on GitHub. I didn't ask INFRA how they handle > teams and committership on GitHub. I expect there will be a > "uimafit-committers" > team with people who have write access to the uimafit repo (I can see e.g. a > "SkyWalking-committers" team in the ASF organization). > > Every non-committer only has read access. Furthermore, certain branches will > be > protected from potentially harmful activities (i.e. history rewrites). I > believe > INFRA sets this up by default, if not I will ask them to. > >> Also, I take it your repo would be 1 repo for all of uimaFIT, correct? > Yes. Basically the https://github.com/apache/uima-uimafit repo. Mind that > this repo > does not contain the uimaFIT v3 code. I would try moving the v3 code from its > present location under the general v3 subtree into the "regular" branches > folder. > That should make it appear in the GitHub mirror. Not entirely sure about how > much > of the v3 history will be retained in this process, but then again, there is > not > much history to retain anyway. > >> I curious if I clone this repo if I would be able to access the change >> history, >> going back before the time of the conversion? > A git repository by default contains the entire history, yes. For special > cases, > it is possible to create a "shallow clone" but it has limited functionality. > E.g. > one can not push changes made to a shallow clone to another repository. > > So, when you clone the repo, you have access to the entire history. You can > also > view the entire history here: > https://github.com/apache/uima-uimafit/commits/trunk > > All questions answered? > > Cheers, > > -- Richard
Re: Considering to move uimaFIT to git - comments?
> On 12.04.2018, at 14:34, Marshall Schor wrote: > > +1 > > Good to start with a contained sub-part, and see how it goes, and see how the > community reacts, etc. > > I have some confusion on whether this is a move to "github" or "git"? Both. Maybe it would be possible to have an ASF-only git repo without making use of GitHub, but actually one of the reasons I want to make the move is to be able to make use of the GitHub Pull-Request / code review feature. INFRA will set up the repo such that mails generated from discussions on pull requests will be send to one of our mailing lists, probably dev. This seems to be one of the *special* features of the ASF<->GitHub integration, because afaik GitHub itself does not have a feature to send issue/PR mails to a mailing list. > If to github, that comes with lots of "extra" things, like issue tracking, > wiki's, a > static-web-page web-site (much like Apache). I will not make use of these features for the time being. Issues continue on Jira. The wiki will be turned off (if we need one, we have Confluence). Also, we already have a website and do not need another one. > GitHub supports a bit of > hierarchical organization, e.g. "Organizations" with various teams having > various permissions (I may have this not quite right, I'm not an expert). > > How are permissions handled by ASF's use of GIT? Are there "teams" that > correspond to commit access for UIMA projects? There is an Apache organization on GitHub. I didn't ask INFRA how they handle teams and committership on GitHub. I expect there will be a "uimafit-committers" team with people who have write access to the uimafit repo (I can see e.g. a "SkyWalking-committers" team in the ASF organization). Every non-committer only has read access. Furthermore, certain branches will be protected from potentially harmful activities (i.e. history rewrites). I believe INFRA sets this up by default, if not I will ask them to. > Also, I take it your repo would be 1 repo for all of uimaFIT, correct? Yes. Basically the https://github.com/apache/uima-uimafit repo. Mind that this repo does not contain the uimaFIT v3 code. I would try moving the v3 code from its present location under the general v3 subtree into the "regular" branches folder. That should make it appear in the GitHub mirror. Not entirely sure about how much of the v3 history will be retained in this process, but then again, there is not much history to retain anyway. > I curious if I clone this repo if I would be able to access the change > history, > going back before the time of the conversion? A git repository by default contains the entire history, yes. For special cases, it is possible to create a "shallow clone" but it has limited functionality. E.g. one can not push changes made to a shallow clone to another repository. So, when you clone the repo, you have access to the entire history. You can also view the entire history here: https://github.com/apache/uima-uimafit/commits/trunk All questions answered? Cheers, -- Richard
Re: Considering to move uimaFIT to git - comments?
+1 Good to start with a contained sub-part, and see how it goes, and see how the community reacts, etc. I have some confusion on whether this is a move to "github" or "git"? If to github, that comes with lots of "extra" things, like issue tracking, wiki's, a static-web-page web-site (much like Apache). GitHub supports a bit of hierarchical organization, e.g. "Organizations" with various teams having various permissions (I may have this not quite right, I'm not an expert). How are permissions handled by ASF's use of GIT? Are there "teams" that correspond to commit access for UIMA projects? Also, I take it your repo would be 1 repo for all of uimaFIT, correct? I curious if I clone this repo if I would be able to access the change history, going back before the time of the conversion? -Marshall On 4/11/2018 8:07 PM, Richard Eckart de Castilho wrote: > Hi all, > > I am considering moving the uimaFIT codebase from SVN to git. INFRA told me > it is possible to move individual sub-projects of a TLP off SVN and onto git; > i.e. it is not necessary to convert the entire TLP from SVN to git at once. > > It (hope) it will facilitate my work on uimaFIT and it could be a guinea pig > for the UIMA project to gather some (more) experience with git and especially > git@ASF. > > Mind, I'd continue to use JIRA for issue tracking. > > Any objections / comments? > > Cheers, > > -- Richard > >
Re: Considering to move uimaFIT to git - comments?
+1 Am 12.04.2018 um 02:07 schrieb Richard Eckart de Castilho: > Hi all, > > I am considering moving the uimaFIT codebase from SVN to git. INFRA told me > it is possible to move individual sub-projects of a TLP off SVN and onto git; > i.e. it is not necessary to convert the entire TLP from SVN to git at once. > > It (hope) it will facilitate my work on uimaFIT and it could be a guinea pig > for the UIMA project to gather some (more) experience with git and especially > git@ASF. > > Mind, I'd continue to use JIRA for issue tracking. > > Any objections / comments? > > Cheers, > > -- Richard > -- Peter Klügl R&D Text Mining/Machine Learning Averbis GmbH Tennenbacher Str. 11 79106 Freiburg Germany Fon: +49 761 708 394 0 Fax: +49 761 708 394 10 Email: peter.klu...@averbis.com Web: https://averbis.com Headquarters: Freiburg im Breisgau Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080 Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó
Re: Considering to move uimaFIT to git - comments?
On 11.04.2018, at 22:15, Benedict Holland wrote: > > Sounds fine. There is also an svn2git tool that I used successfully on a > lot of projects. We already have a mirror of uimaFIT on GitHub: https://github.com/apache/uima-uimafit I had a quick chat with INFRA over on Hipchat. My understanding is that in a move to Git, INFRA would upgrade this mirror to a writable repository which is synced with an internal ASF repo for tracking of provenance. So in fact, the canonical repo would be at the ASF, but one can still use the GitHub repo for pulling/pushing and for doing PRs. As far as I understood, ASF INFRA takes care of the entire migration process. We just have to file an issue with them to trigger it. What's also nice: the ASF Jenkins can watch and build PRs :) Cheers, -- Richard
Re: Considering to move uimaFIT to git - comments?
Sounds fine. There is also an svn2git tool that I used successfully on a lot of projects. On Wed, Apr 11, 2018 at 8:18 PM, Lou DeGenaro wrote: > +1 > > Lou. > > On Wed, Apr 11, 2018 at 8:07 PM, Richard Eckart de Castilho < > r...@apache.org> > wrote: > > > Hi all, > > > > I am considering moving the uimaFIT codebase from SVN to git. INFRA told > > me it is possible to move individual sub-projects of a TLP off SVN and > onto > > git; i.e. it is not necessary to convert the entire TLP from SVN to git > at > > once. > > > > It (hope) it will facilitate my work on uimaFIT and it could be a guinea > > pig for the UIMA project to gather some (more) experience with git and > > especially git@ASF. > > > > Mind, I'd continue to use JIRA for issue tracking. > > > > Any objections / comments? > > > > Cheers, > > > > -- Richard > > > > >
Re: Considering to move uimaFIT to git - comments?
+1 Lou. On Wed, Apr 11, 2018 at 8:07 PM, Richard Eckart de Castilho wrote: > Hi all, > > I am considering moving the uimaFIT codebase from SVN to git. INFRA told > me it is possible to move individual sub-projects of a TLP off SVN and onto > git; i.e. it is not necessary to convert the entire TLP from SVN to git at > once. > > It (hope) it will facilitate my work on uimaFIT and it could be a guinea > pig for the UIMA project to gather some (more) experience with git and > especially git@ASF. > > Mind, I'd continue to use JIRA for issue tracking. > > Any objections / comments? > > Cheers, > > -- Richard > >
