In retrospect, it may be better to make this decision now and have INFRA create the required repositories at once.
I kind of liked what Shameera started, just to rephrase: * Airavata Services * Airavata Client SDK’s * Airavata Web UI’s * Airavata GUI Tools * Airavata Admin Tools I am + 0 on this. Not sure if breaking up will reduce clutter and provide better manageability or will overwhelm. Here are some examples, if it helps: https://github.com/jclouds And the master ASF repo which is an umbrella for all apache project mirrors - https://github.com/apache Suresh On Jan 21, 2014, at 2:36 PM, Marlon Pierce <[email protected]> wrote: > For now, I want to keep the same structure with one repository. Assuming > the vote passes, this will be a simple email to Apache INFRA to do the > conversion. We can bring up reorganization separately. > > Please let me know if I am missing something, though. > > > Marlon > > On 1/21/14 2:28 PM, Shameera Rathnayaka wrote: >> Hi Marlon, >> >> do we have any idea about the git repository structure we will use? all >> Airavata code will go under one git repository or we will have separate >> repository to airavata client , airvata server and xBaya? (can be fine >> grain further if needed). >> >> Thanks, >> Shameera. >> >> >> On Tue, Jan 21, 2014 at 8:23 PM, Marlon Pierce <[email protected]> wrote: >> >>> Since this will effect everyone, I will start a 72 hour voting period >>> and discussion thread. Please vote only on the [VOTE] thread so that it >>> will be easy to count. All opinions are welcome. >>> >>> >>> Marlon >>> >>> On 1/16/14 10:51 PM, Amila Jayasekara wrote: >>>> +1 to move to Git. >>>> It seems it is easy for people to contribute with GIT. (Specially >>>> situations like GSOC). >>>> >>>> Thanks >>>> Thejaka Amila >>>> >>>> >>>> On Thu, Jan 16, 2014 at 4:54 PM, Suresh Marru <[email protected]> wrote: >>>> >>>>> Thanks Marlon for resurrecting this discussion. Its also timely to the >>>>> transition before GSOC 14 and as we move towards Airavata 1.0. >>>>> >>>>> One thing we have noticed is INFRA support for GIT transition has >>>>> increased over time. Also, the integration with GITHUB, jClouds has >>> fully >>>>> exploited this and now there may be other projects also. So all in all >>> the >>>>> timing is very good and + 1 to move foreword for Airavata. >>>>> >>>>> Suresh >>>>> >>>>> On Jan 16, 2014, at 2:50 PM, Marlon Pierce <[email protected]> wrote: >>>>> >>>>>> Hi all-- >>>>>> >>>>>> We have discussed $subject before for other reasons without much action >>>>>> [0], so I want to bring it up again. Unless the situation has changed >>>>>> recently, Apache's Jira no longer links SVN commit messages to Jira >>>>>> tickets. For background on the issues with SVN, see [1]. This ticket >>>>>> is still unresolved. >>>>>> >>>>>> The general linking of repo commits to Jira tickets through commit >>>>>> comments [2] is a good and virtuous thing. We have lost this in >>>>>> Airavata and need to get it back. This requires moving to Git [3] [4]. >>>>>> >>>>>> What other consequences are there for doing this? Let's please >>>>>> discuss. It will take a bit of time from INFRA to make the conversion, >>>>>> but this doesn't seem to be awful. We need to preserve history if we >>> do >>>>>> this. What else? >>>>>> >>>>>> >>>>>> Thanks-- >>>>>> >>>>>> >>>>>> Marlon >>>>>> >>>>>> [0] https://www.mail-archive.com/[email protected]/msg03881.html >>>>>> >>>>>> [1] https://ecosystem.atlassian.net/browse/SVN-385 >>>>>> >>>>>> [2] http://www.apache.org/dev/svngit2jira.html >>>>>> >>>>>> [3] https://git-wip-us.apache.org/ >>>>>> >>>>>> [4] >>>>>> >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20INFRA%20AND%20text%20~%20%22git%20svn%22 >>>>> >>> >> >
