FEATURES OF TRAINING OF FUTURE INFORMATICS TEACHERS WORKING WITH THE GIT VERSION CONTROL SYSTEM GIT

Teamwork is the most important soft skill of the modern specialist, not to mention a teacher. It is also undisputed that skills development is very important to start at school, in particular at computer science lessons. Accordingly, a future teacher of computer science has to know version control systems and use one of them to organize collective student's work like in class and in the process of preparing for science competitions of the Junior Academy of Sciences of Ukraine. This topic of the article is relevant because it doesn't fully describe in the scientific and methodological resources. The main goal of this article is to open the main features of teaching students to work with version control systems on the example of Git. The systematic approach was the methodological basis for the investigation discovery. But besides, the researcher analyzed, compared, and summarized the investigation and experience of the leading scientists. As the result of the article the author rise to the following conclusions that the knowledge of version control systems (in particular Git) is an important part of the preparation of computer science teachers; teaching students to work with such programs have to be combined with the study of programming; should be encouraged students to complete labs and case studies using Git; teachers have to demonstrate through examples the correct organization and culture of work with such programs. The writer is also considering using the GitHub Classroom service to organize the educational process subjects such as programming and page making of web pages.

Tools for organizing teachers-students interaction using version control systems

The article describes an approach to organizing the teacher-students interaction in programming courses using the Git version control system. In order to select the most suitable and affordable system for educational needs a comparative analysis of different Git repository management systems was carried out. Based on the experience of various educational institutions that use version control systems in their courses, the advantages and disadvantages of using these systems in teaching were identified. Taking into account the existing problems, a software solution was developed based on the GitLab system. As part of this solution, a method is proposed for organizing the work of a teacher and students in disciplines that use version control systems. This approach implies using both GitLab and additional system, which serves as a manager for Git repositories and is designed to facilitate the work of the teacher and administrator by automating the tasks they perform. The main purpose of the article is a detailed description of this approach: limiting permissions to both teachers and students, GitLab organization and functionality, a list of use cases for each user. The article also presents common workflows of the additional system, its main entities and their relationships and an overview of the features that the system provides.

A Rapid Transition from Subversion to Git: Time, Space, Branching, Merging, Offline commits & Offline builds and Repository aspects

Background: Software development is being transitioned from centralized to decentralized version control systems. This transition is driven by the limited features of centralized version control systems in terms of branching, merging, time, space, offline commits & builds, and repository aspects. Transition from Subversion, a centralized version control system, to Git, a decentralized version control system, has been focused in a limited way. Objective: In this work, the transition process from Subversion Version Control System (VCS) to Git VCS has been investigated in terms of time, space, branching, merging, and repository aspects from the software developer point of view working individually or in a large team over a large and complex software having a legacy of many decades. Experimentation was conducted in SRLC Software Research Lab, Chicago, USA. Methods: Various scripts have been developed and executed for version control using Git and performed over a few legacy software. Results: The results show that branching in Git and Subversion has a difference of about 39 times, i.e., branching operation of Git is about 39 times faster than Subversion. Merging in the case of Git is trivial and automatic, while Subversion needs a manual process of merging, which is error-prone. Using an example of Mozilla with FSFS backend, it is observed that disk space can be saved up to 30 times in Git compared to Subversion. By taking a typical example of a large-sized project, it is observed that Git requires almost half of the revisions compared to Subversion; furthermore, with FSFS backend, a project having ten years of history with 240,000 commits needs 240 directories in case of Subversion, while Git requires only 2 directories. Using offline commits and offline builds of Git, it is observed that in Git, whitespace changes, in contrast to significant business logic changes, can be staged in one commit only. These are not possible in Subversion, which requires a complicated system of diffing to temporary files. It is also observed that Git provides an offline commit facility, i.e., in case if, for some reason, the remote repository is unavailable due to disaster or network failure, then developers can still offline commit their code and execute the offline build. Conclusion: However, no previous study was found that focused on how the choice actually affects software developers and this formed the motivation for the present work. In this work, a list of how the choice between Git and Subversion affects software developers is worked out. Although software developers in many aspects are unaffected by the choice, few interesting findings were achieved. One of the most interesting findings of the proposed work is that software developers seem to publish their code to the main repository more often in Git than in Subversion. It is also found that the majority of the software developers perform at least two commits per push, which means that Git repositories will contain a lot more saved points in history than Subversion repositories.

Versioning Biological Cells for Trustworthy Cell Engineering

Abstract“Full-stack”biotechnology platforms for cell line (re)programming are on the horizon, due mostly to (a) advances in gene synthesis and editing techniques as well as (b) the growing integration with informatics, the internet of things and automation. These emerging platforms will accelerate the production and consumption of biological products. Hence, transparency, traceability and -ultimately-trustworthiness is required -from cradle to grave- for engineered cell lines and their engineering processes. We report here the first version control system for cell engineering that integrates a new cloud-based version control software for cell lines’ digital footprint with molecular barcoding of living samples. We argue that version control for cell engineering marks a significant step towards more open, reproducible, easier to trace and share, and more trustworthy engineering biology.One Sentence SummaryWe demonstrate a transparent and open way of engineering and sharing cell lines.

Model Architecture for Subversion Software Repositories System

In the development cycle of any software, software evolution plays an important role. Software Evolution is essential and challenges characteristics in the field of software engineering. Many research studies have concluded that 60-80% of efforts are spent on the evolution and maintenance of the software. Software repositories, for example, version control and bug tracking systems, are vital fragments of numerous software maintenance activities. The version control system is an incremental version tracking system, introduced to avoid unnecessary overwriting of files such as programming code, web pages, and records. It also helps to decrease the confusion affected by duplicate or outdated data. In this proposed research, the SVN repository was maintained and analyzed for msitone.wikispaces.com to minimize the efforts as well as resources for future users. Two semesters' data was taken as the observations for the analysis. The obtained archives were implemented and deployed for postulating the local archives to the online server via the Visual SVN server, allowing remote users to access a repository.The tortoise SVN tool is used as an SVN client to access the repository of Wiki spaces. Analyses were observed with and without implementing the SVN repository. The result shows that implementing the SVN repositories is helpful for the maintenance of the Wiki spaces. It also reduces the cost, time and efforts for their evolution. Whereas without implementing the SVN repositories, Wikis paces were just supposed to be building the house byputting each brick from the start.

EXACT: a collaboration toolset for algorithm-aided annotation of images with annotation version control

In many research areas, scientific progress is accelerated by multidisciplinary access to image data and their interdisciplinary annotation. However, keeping track of these annotations to ensure a high-quality multi-purpose data set is a challenging and labour intensive task. We developed the open-source online platform EXACT (EXpert Algorithm Collaboration Tool) that enables the collaborative interdisciplinary analysis of images from different domains online and offline. EXACT supports multi-gigapixel medical whole slide images as well as image series with thousands of images. The software utilises a flexible plugin system that can be adapted to diverse applications such as counting mitotic figures with a screening mode, finding false annotations on a novel validation view, or using the latest deep learning image analysis technologies. This is combined with a version control system which makes it possible to keep track of changes in the data sets and, for example, to link the results of deep learning experiments to specific data set versions. EXACT is freely available and has already been successfully applied to a broad range of annotation tasks, including highly diverse applications like deep learning supported cytology scoring, interdisciplinary multi-centre whole slide image tumour annotation, and highly specialised whale sound spectroscopy clustering.

Deploying an Application to Cloud Platform Using Continous Integration and Continous Delivery

Cloud Computing is the best way for bussiness owner deploy an application to reduce cost issue because it is implement pay as you go concept. Generally, an application on production level or deployed into cloud instance should not have any error or bug. It should be tested and maintain properly. The problem when an application have intensive development that takes more effort to test the application and deploy. So, need a strategy to deploy an application into cloud instance to make the proccess more efficient. Nowadays, Version Control System (VCS) platform provide Continous Integration and Continous Delivery (CI/CD) feature. Users can utilize that platform to perform automated test and deployment easily. This reasearch purposed to examine how to use CI/CD feature and evaluate it in case of deploying web application to Cloud Platform. Researcher use Gitlab wich is provide CI/CD feature for free and deploy the app to Amazon Web Service. The researcher also utilize docker container to accommodate all processes. The result are Continous Integration can improove application quality because most lines of codes are tested using unit or feature test scenario. Using CI/CD feature improove security issue of deployment. Deployment proccess run automatically without human intervention so it will reduce human error factors. This feature also ensure high availability of an application. Deployment proccess will take zero downtime. The application can quickly update without any downtime and configuration. Last, docker container take an important role for deployment of application into cloud instance.