ProjectDeliverable

D8.1InternalandExternalIT

CommunicationInfrastructureProjectNumber 700692ProjectTitle DiSIEM–Diversity-enhancementsforSIEMsProgramme H2020-DS-04-2015Deliverabletype ReportDisseminationlevel PUSubmissiondate 30thNovember2016Responsiblepartner FFCULEditor AlyssonBessaniRevision 1.0

The DiSIEM project has received funding from the European Union’s Horizon 2020researchandinnovationprogrammeundergrantagreementNo700692.

D8.1

2

EditorAlyssonBessani,FFCULContributorsAlyssonBessani,FFCULIgnacioRobla,ATOSElsaPrietoPerez,ATOS

D8.1

3

ExecutiveSummaryThis deliverable marks the launch of the internal and external DiSIEM ITcommunication infrastructure. The internal infrastructure includes theestablishment ofmailing lists, and a file repositorywith version control,whilethe external infrastructure corresponds to the official disseminationmaterialsand channels, including the project website. The report also describes theprocedures and policies for dissemination and communication in the DiSIEMproject.Furthermore,wedefinethemeansforcommunicationtoexternaltargetgroupsincludingmarketingmeasuresandcommunicationchannels.

D8.1

4

TableofContents1 Introduction...................................................................................................................................71.1 OrganizationoftheDocument......................................................................................7

2 ExternalDisseminationandCommunication..................................................................82.1 RolesandResponsibilities..............................................................................................82.2 TargetUsers..........................................................................................................................82.3 Keymessages........................................................................................................................82.4 Visualidentity.......................................................................................................................92.5 CommunicationPolicy...................................................................................................102.5.1 IPRconflictinpublications.................................................................................102.5.2 DisclosureofPUdeliverables.............................................................................102.5.3 Implementationofopengreenaccess............................................................112.5.4 EUdisclaimerandEUemblem..........................................................................11

2.6 KeyPerformanceIndicators........................................................................................112.7 Communicationanddisseminationmaterials.....................................................132.8 Communicationanddisseminationchannels......................................................152.9 Projectwebsite..................................................................................................................16

3 InternalCommunicationInfrastructure.........................................................................183.1 Projectmailinglists.........................................................................................................183.2 Instantmessaging............................................................................................................183.3 Tele-conferences..............................................................................................................183.4 Projectrepository............................................................................................................18

4 SummaryandConclusions...................................................................................................20References...........................................................................................................................................21Appendix:AverybriefintroductiontoGit............................................................................22

D8.1

5

ListofFiguresFigure1DiSIEMvisualidentity....................................................................................................9Figure2DiSIEMlogoandvisualidentity..................................................................................9Figure3DiSIEMleaflet.Theleafletisavailableathttp://disiem-project.eu/wp-

content/uploads/2016/12/DiSIEM-leaflet.pdf........................................................14Figure4Projectwebsite...............................................................................................................17

D8.1

6

ListofTablesTable1KPIfordisseminationandcommunicationactivities......................................12Table2Importantgitcommands..............................................................................................22

D8.1

7

1 IntroductionThis document describes the procedures, policies and infrastructures fordisseminationandcommunicationactivitiesintheDiSIEMproject.Dissemination is mostly related with the knowledge diffusion to the peers,usuallyotherresearchersandorganisationsworking in theareaof theproject.Typical forms of dissemination are the website, presentation at a scientificaudience,etc.Communication is aimed at non-specialists, a wider audience, includingstakeholders and end-users interested in the innovations produced during theproject.Typicalexamplesofcommunicationactivitiesarepressreleasesspreadingeneralpublicmediaat the startof theproject, localworkshops targetedataudiences forwhich the action is of interest, brochures/leaflets to explain theaction’swork,etc.Thisreportfocusesontheexternalcommunicationanddissemination,aswellasthe internal communication infrastructure for theDiSIEMproject.Theexternalcommunicationanddisseminationinfrastructuresubsumesthemeansandtoolsfor communication of the project to external target groups includingconferences, marketing measures and communication channels. This includesalsothedefinitionofclearpoliciesforusingandproducingcommunicationanddisseminationmaterials. The internal communication infrastructure of DiSIEMincludes the mailing lists, tele-conference and instant message tools, and aninternalfilerepositorywithversioncontrol.

1.1 OrganizationoftheDocumentThisshortreportcontainsthreechapters(besidesthisintroduction).Chapter2describes the external communication and dissemination procedures andchannelsoftheproject.Chapter3describestheinternalITinfrastructureoftheproject.Finally,weconcludeandsummarizethereportinChapter4.

D8.1

8

2 ExternalDisseminationandCommunicationIn this chapter we define the main procedures, materials and channels forrealizingbothdisseminationandcommunicationactivitiesduringtheproject.

2.1 RolesandResponsibilitiesAstheprojectcoordinator,FFCULisresponsibleforleadingthecommunicationanddisseminationtaskofDiSIEM.However,allpartnershavePMs in thisWP8and it is expected that they contributewith communication anddisseminationactivities of DiSIEM by raising awareness about the project within theirorganization and community, and giving talks in conferences and workshopsabouttheprojectresults.Intermsofeffort,weitisexpectedtheseactivitiestakebetween1-2PMsperpartnerduringthethreeyearsoftheproject.

2.2 TargetUsersThedisseminationandcommunicationstrategyof theproject isdivided in twomainphases.On the firstyearof theprojectwearemore interested in raisingawarenessaboutit,socommunicationactivitieswillbeprivileged.OnthesecondandthirdyearsofDiSIEMourfocusshiftmoretodisseminationasweexpecttohavealreadyimportantresultstodisseminate.Giventhisstrategy,ourtargetswillalsochange:atthebeginningismoregeneralaudience,thenwecantrytoreachmoretechnicalpeople,andfinallywetendtoexploitation/adopters.

2.3 KeymessagesTherearesomekeyconceptsandmessagesofDiSIEMthatneedtobestressedineverydisseminationandcommunicationactivity.Theyare:

• DiSIEM is an innovation project that aims to improve the capacity ofSIEMstodealwithmodern/advancedpersistentthreats;

• DiSIEM will produce several components that (in principle) can beintegratedinanyexistingSIEMsystems;

• The project will exploit OSINT data (security feeds, indicators ofcompromise repositories, blogs, social networks, etc.) and machinelearning techniques to detect, inform and propose actions to deal withnovelthreatsagainstacyberinfrastructure;

• The project will equip existing SIEMs with the capability of evaluatingdiverse configurations of monitoring and protection devices, novelapplication-basedmisusedetectionandsecurecloud-basedevenarchival.

D8.1

9

2.4 VisualidentityWeestablishedthevisualidentityoftheproject,includingtheprojectlogo(withvariants) and templates for presentations and deliverables (used in thisdocument).Figure1presentsthebasiciconographyoftheprojectlogo.

Figure1DiSIEMvisualidentity.

The project’s brand was inspired by visually connecting three concepts thatdefine DiSIEM:cyber-security (represented by a shield); data streams(represented by vertical lines with different sizes); and diversity of inputs(representedbythemulti-coloringoftheverticallines).Figure2presentsthefinalproject logowithinthecolourandbackgroundsthatarerecommendedforkeepingaconsistentvisualidentityforDiSIEM.

Figure2DiSIEMlogoandvisualidentity.

LOGÓTIPO SÍMBOLO

IDENTIDADE

D8.1

10

All communication and dissemination activities of the project should try tocomplywithlogoandcoloursdefinedinourvisualidentity.Inordertopreservecoherenceandharmony throughout the communication, some typographywasselected,andit’srecommendedtobeusedinallgraphicpieces:

• Titles:Furore• Text:Gotham

More details and logo variants are available on the project repository for thepartnerstoinspect.

2.5 CommunicationPolicyTheprojectconsortiumimplementsapublicationprocesstoensurethequalityof deliverables and of any other external publication. It ensures that the IPR(IntellectualPropertyRights)ofthepartnersareadequatelyverifiedbeforethedisseminationofanyprojectresults.This section defines the policy for dissemination of project results anddeliverables.SomeoftheinformationinthissectioncontainsminorrevisionsontheplandescribedinPartBoftheDiSIEMGrantAgreement(Section3.2.2).

2.5.1 IPRconflictinpublicationsFor general dissemination activities, the partners need to communicate theconsortiumaboutthedisseminationatleastoneweekbeforeitismadepublic.In the particular case of conferences and journals, the partners shoulddisseminate a draft of the paper before submission. In the worst case, anacceptedpapermustbedisseminated to the consortiummembers at least oneweekbeforethecamera-readyversionissubmitted.Theaforementioned communicationmustbedone through theprojectmailinglist (disiem-technical, see Section 3.1) and the draft of the paper/presentation/articlemustbemadeavailableontherelevantWPdirectoryontheprojectrepository.Once the paper, presentation, or article is made available to the consortium,partners have the chance to review the content to identify potential conflictswithconfidentialinformation.Partnershaveoneweektoexpresstheirobjectiontothepublication.Silenceisconsideredatacitapproval.

2.5.2 DisclosureofPUdeliverablesForofficialprojectdeliverables,therewillbeaspecificprocessofreviewbeforethe submission to EC. This guarantees that the qualitative targets are reachedwith regards the technical content, the objectives of the project and adhere to

D8.1

11

formalrequirementsestablishedintheGrantandConsortiumAgreements.Thereview process should be done in accordancewith the formal review processdefinedinD9.1(ProjectQualityPlan).AfterthesubmissionofadeliverabletotheEC,thedocument/softwarepackagewill be made available on the DiSIEM website within one week (for publicdeliverables). We will clearly mark each deliverable as “Under Review” or“Approved”inthewebsite.

2.5.3 ImplementationofopengreenaccessTheDiSIEMproject is fully committedwith open green access of publications.This means that any paper reporting work supported by DiSIEM must bepublishedalsoinanopen-accessrepository.AswithseveralH2020projects,weplan to have the pre-print of all papers on the Zenodo EU-funded repository[Zenodo].Theversiononthisrepositorywillbelinkedtotheprojectwebpage.

2.5.4 EUdisclaimerandEUemblemThe following statements must be added to every dissemination and/orcommunicationitem.Forpresentations,blogpostsorwebpages:

The DiSIEM project has received funding from the European Union’s Horizon 2020researchandinnovationprogrammeundergrantagreementNo700692.

Forpapers,ashorterversionsuffices:Thiswork is supportedby theEuropeanCommission throughtheH2020programmeundergrantagreement700692(DiSIEM).

2.6 KeyPerformanceIndicatorsCommunication and dissemination activities must be measured by keyperformance indicators (KPIs)definedby the consortium.These indicatorsareintended to demonstrate how effective communication and disseminationactivities are, in terms of quantity and quality. On one hand, the quantity ismeasuredby controlling the frequencyof the communicationactivities.On theother hand, the quality is evaluated with the specialized research capacitydemonstratedintheresultingimpact.Table1describestheKPIproposedintheproject,whichwillbemonitored,andspecificactionswillbedefinedaccordingly.

D8.1

12

Table1KPIfordisseminationandcommunicationactivities.

Category QuantitativeKPIsQualitativeKPIs(Optional)

Branding

Leaflets Numberofleafletsproduced

Typeofeventswheretheleafletswerehandedout(e.g.,tradefair,researchconferences)

Leaflets Numberofeventswhereleafletswerehandedout

Pressreleases

NumberofpublishedPRImpactsofpublishedPR(inothermedia)Publicationinothermedia(newsletters,clusterswebsite)

Publications

Papers Numberofpapersproduced

Conferencerankwherethepaperhasbeenaccepted

Articles Numberofpublishedarticles Blogs,specializedwebs

Numberofmentionsinspecializedblogs,websofthepartners

Events

Conferences NumberofattendedthirdpartyconferencesSizeofaudience

Typeofaudience

Workshops

NumberofattendedthirdpartyworkshopsSizeofaudienceNumberoforganizedworkshopsSizeofaudience

Typeofaudience

Events NumberofattendedthirdpartyeventsSizeofaudience

Typeofaudience

Webinars NumberoforganizedwebinarsSizeofaudience

Typeofaudience

Socialmedia

WebsiteMetricsofthewebsite,includingthenumberofvisitors,countriesofthevisitors,andnumberofdownloadsofdisseminationfiles

Socialaccounts

Socialnetworkmetricssuchasnumberoffollowers,numberoftweetswith@disiemproject,#DiSIEM,#disiemproject,andnumberofreactionsinthefeedsof@disiemprojectaccount

Face-to-facecontacts

Face-to-facecontacts Numberofcontactswithpotentialtargetusers

Relevanceofthecontactwithtargetusers

D8.1

13

CollaborationwithR&Dprojects

ClustersNumberofclusterstobelongNumberofdevelopedactivitiesinsidetheclusters

Typeofcollaboration

Actionswithotherprojects Numberofactionswithotherprojects Typeof

collaborationMentions

Mentionsinthirdpartymedia

NumberofmentionstoDiSIEMprojectinothersocialmedia(e.g.,twitter,facebook)externaltoDiSIEMpartners;NumberofmentionsinwebsitesexternaltoDiSIEMpartners

2.7 CommunicationanddisseminationmaterialsWepreparedsevenmaterialsforcommunicatingtheoverallideasoftheproject.

• Announcementletter.Ashortdocumentinformingaboutthestartoftheproject.

• Press release. An official statement issued to disseminate to the pressandpartnersinstitutions.

• Leaflet. Information material to raise awareness on project targets,opportunities and partners, which can be distributed via e-mail ordirectlyinmeetings/conferences.TheleafletispresentedinFigure3.

• Short project description. A very short introduction about theobjectives and expected contributions of the project. To be included inpartner’swebsites,booklets,etc.

• Project presentation. A half-hour presentation about the project thatcanbeusedbythepartnersinworkshops,innovationboards,etc.

• Projectvideo.Inthenextmonths,weplantohavepromotionalvideooftheprojectandonenewsletteroftheprojecteachsixmonths.

D8.1

14

Figure3DiSIEMleaflet.Theleafletisavailableathttp://disiem-project.eu/wp-

content/uploads/2016/12/DiSIEM-leaflet.pdf.

All communication material will be available in the project webpage, in the“PublicationsandDeliverables”section.

D8.1

15

2.8 CommunicationanddisseminationchannelsFindingthebestchannelsforcommunicatinganddisseminatingtheprojectandits results is crucial for broadening the impact of DiSIEM. These availablechannels include the participation in academic and industrial events such asconferences, workshops, meetings and fairs, the press, partner’s blogs andnewsletters, amongothers.Theprojectwebsite (described in thenext section)shouldbethemainconcentratorofalltheseactivities.BelowwelistthemainchannelsconsideredinDiSIEM.

• Projectwebpage.Channeltodisseminateinformationontheprojectanditsimpactoninterestedpartiesworldwide(e.g.,newssuchasconferencetalks,publicationsanddeliverables,involvedpartners,links,etc.)

• Project newsletter. Starting at month six, we plan to summarize themainachievementsof theprojectevery threemonths inanewsletter tobepublishedonthewebpageandsenttointerestedparties.

• Partner’s blogs and newsletters. Several partners maintain blogs,magazines and newsletters that should be used to communicate theproject.Tocitejustsome:

o Ascent(https://ascent.atos.net/)(AtosWebsite forTechnicalandResearch contents, designed to share with Atos partners andcustomersinnovationandthoughtleadershiponemergingtrendsin many areas. This publication is linked to the Atos scientificcommunityinchargeofidentifythemostinnovativetechnologicaltrends.

o Twitteraccount:@AtosES;o AXIA:AtosSpainCorporatemagazine(onlyeditedinSpanish).The

aimof “axia” is to reinforceAtos corporate image and effectivelycommunicatethecompany’sknowledgeandsuccessstoriesintheInformationTechnologymarket;

o Ascent Journey: series of yearly publications, a comprehensivedocumentfromAtoswherewepresentourpredictionsandvisionfortechnologythatwillshapebusinessthroughtothenext3years;

o DigitalMRblog(http://www.digital-mr.com/blog)andnewsletter:(http://www.digital-mr.com/archive/archives/category/Social-Media-Research-Digest/page/1);

o All partners also have their institutional webpages, and it isexpectedthat thesechannelsareusedforcommunicatingDiSIEMideasandresults.

• Academic events. Academic events are important for reaching thescientific audience. In DiSIEM, the dissemination activities includes theattendees of someof the top conferences in security anddependability,such as IEEE/IFIP Dependable Systems and Networks, IEEE Security &Privacy, IEEE International Symposium on Software ReliabilityEngineering, ACM Computer and Communication Security, USENIXAnnual Technical Conference, European Symposium on Research inComputer Security and USENIX Security, to cite just some. In additionvisualisation related activities will be presented in top venues such as

D8.1

16

IEEE VIS, EuroVis, and themore security oriented IEEE Symposium onVisualisationforCyberSecurity.

• Industry events. For the technical and industry audience, we envisionthepromotionofDiSIEManditsresultsinindustry-focusedmeetingsandfairssuchasWebSummit,InfoSec,CeBIT,CyberSecurityforEnergyandUtilities, among others. Selected results of the project can also bepresented in international industry-focused conferences about socialmedia,suchasiStrategyConference,SocialMediaWorldForum,Innovate,andTheSocialMediaStrategiesSummit.

• Journals andmagazines. There aremany journals andmagazines thatcanbeusedfordisseminatingtheideasoftheproject.Wewanttohaveatleast one paper for disseminating the overall ideas of the project in amagazine such as IEEE Security & Privacy magazine and Computer &Security. Besides that, it is expected that the partners publish some oftheirscientificworkinhigh-reputableacademicjournals.

• Social networks.Werecentlycreatedatwitteraccount@disiemprojecttodisseminatemaintheachievementsoftheprojectandasanadditionaltool to create a community around the project. This account is underresponsibilityofCity,butotherpartnerssuchasATOSandFFCULcanalsopostusingthisaccountthroughtheuseofTweetdeck[Tweetdeck].

• Press.Everypartner is responsible to try to reach the (technical)pressfordisseminatingtheDiSIEMprojectanditsresults,thusbroadeningtheaudienceofthecommunicationactivities.

• Liaisonwithrelatedresearchprojects.AfinalchannelthatweplantoexploreisthepossiblecollaborationswithotherH2020projectssuchasSUPERCLOUD,CIPSEC,COMPOSITION,andANASTACIA,tocitejustsome.

2.9 ProjectwebsiteTheDiSIEMprojectwebsiteisthemostimportantdisseminationchanneloftheproject. FFCUL is themain responsible for building,maintaining and updatingthe website, which is hosted in University of Lisbon, Faculty of Sciencespremises. Thewebsite is accessible since the end of October 2016 though theaddresseswww.disiem-project.eu,disiem-project.eu,anddisiem.lasige.di.fc.ul.pt.Figure 4 presents the initial page of the projectwebpage. As can be seen, themainsectionsofthewebsiteare:

• The Project. This section presents an overview of the key facts,objectives, main innovation vectors, and the methodology we want toemploy.

• News.This sectioncontainsall thenewsof theproject.Wewant touse

thissectionalsotopublishshortblog-likeposts informingaboutprojectkeyresultsandmilestones.

• Consortium.Thissection listsprojectpartner institutionstogetherwith

keypersonsineachoneofthem.

D8.1

17

• Publications. This section lists, in separated sections, the scientific

publications,deliverables(reports),andthecommunicationmaterial(e.g.,leaflet,newsletters,overviewdocuments)oftheproject.

• Contact. This last section lists the contact of all partners andmeans to

easilycontacttheprojectcoordinator.ThisstructurecanbeeasilychangedincaseofneedasthewebpageisbuiltusingtheWordPresscontentmanagementsystem[WordPress].

Figure4Projectwebsite.

D8.1

18

3 InternalCommunicationInfrastructureThis chapter describes the main internal communication infrastructure of theDiSIEM project. In particular,we detail themost important infrastructures forcollaboration:mailing lists, instantmessaging, tele-conferences and theprojectfilerepository.

3.1 ProjectmailinglistsWe have twomailing lists for internal communication on the project, one fortechnicaldiscussions(disiem-technical@listas.di.ciencias.ulisboa.pt)andanotherfor administrative issues (disiem-administrative@listas.di.ciencias.ulisboa.pt).Any partner can subscribe members in these lists at any time by asking theprojectcoordinator.

3.2 InstantmessagingThe project coordinating team did not defined a specific tool for instantmessagingasourexperienceinpreviousprojectisthatfewpeoplestayonlineintheseprivatechattools.Therefore,partnersareusingmostlySkype[Skype]forexchanging messages on real time. Other possible tools are Gtalk/GoogleHangout [Hangouts].EverypersonworkingonDiSIEMmaintains itsSkypeandGtalkcontactsonthecontact-list.csvfileonourprojectrepository.

3.3 Tele-conferencesEveryteleconferencemeetingwillhaveahostpartner,whomisresponsibleforsetting up the tele-conference (telco) system and invite the other participants.CurrentlywearehostingtelcosusingbothSkypecorporate[Skype]andWebEx[WebEx],butGoogleHangouts[Hangouts] isalsoapossibility. Inanycase, it isexpected that the host partner send the invitation to all other by email usingeithertheprojectmailinglistorindividualemailsfoundinthecontactlistontheprojectrepository.

3.4 ProjectrepositoryForthisproject,wehostthefileswithversioncontrolbasedonGIT.Inparticular,wesetupaGitLabserver[GitLab]ontheFCULinfrastructure.Thisserverhostsamasterrepositorythatotherpartnerscancloneintheirhostsandcontributeto.The server repository can be found at http://git.lasige.di.fc.ul.pt/root/DiSIEM(viaweb),ordirectlythroughagitURLgit@git.lasige.di.fc.ul.pt:root/DiSIEM.git.Accessing this server requires an account created at FCUL, and an explicitinvitationbytheprojectcoordination.Anypartnercanaskaccessatanytimebycontactingtheprojectcoordinator.

D8.1

19

Theprojectrepositoryisorganizedwiththefollowingmaindirectories:

• 00-Project-Info. Communication and dissemination material about theproject, including the logo, leaflet, templates and other materialsdescribedinSection2.7;

• 01-Official-Documents. This directory contains the Grant Agreement,Submitted deliverables, Published papers and any other officialdocumentationrelatedwiththeproject;

• 02-Workpackages. Here we have one subdirectory for each workpackage of the project. WP coordinators must use this space as arepositoryforWPwork;

• 03-Meetings-Telcos.Storesinformationaboutallphysicalmeetingsandtelcosdoneintheproject,separatedperyearandmeeting;

• 04-Other-Info. This is directory for storing other stuff, such as generalrelatedworkabouttheproject.

If the need arises, we can change this structure for accommodating furtherneeds.We provide a short introduction to Git in the appendix of this report as areferencetoprojectpartners.

D8.1

20

4 SummaryandConclusionsThis deliverable described the DiSIEM internal and external infrastructure forcommunication and dissemination. In particular, we defined the channels,materials and procedures for executing external communication anddissemination activities in the project. Regarding the internal communicationinfrastructure, we describe all the fundamental elements for establishing asuccessful collaboration:mailing lists, telco and instantmessage tools, and theprojectrepository.With all these procedures and infrastructures set, we now have the tools andmethodsforcommunicatinganddisseminatingtheDiSIEManditsinnovations.

D8.1

21

References[Chacon and Straub 2014] Scott Chacon and Ben Straub. Pro Git. 2nd Edition.2014.Freelyavailableathttps://git-scm.com/book/en/v2.[GitLab] GitLab open source git server. https://about.gitlab.com/. Accessed inNovember2016.[Hangouts] Google Hangouts. https://hangouts.google.com/. Accessed inNovember2016.[Skype]Skype.https://www.skype.com/.AccessedinNovember2016.[SVN] Apache Subversion. https://subversion.apache.org/. Accessed inNovember2016.[TweetDeck]TweetDeck.https://tweetdeck.twitter.com/.AccessedinNovember2016.[WebEx]CiscoWebEx.https://www.webex.com/.AccessedinNovember2016.[WordPress]WordPressContentManagementSystem.https://wordpress.org/.AccessedinNovember2016.[Zenodo]ZenodoRepository.https://zenodo.org.AccessedinNovember2016.

D8.1

22

Appendix:AverybriefintroductiontoGitIn the following we describe some of the basic commands for operating acommand-line git tool and suggest some graphical interfaces for using git ondifferentoperatingsystems.Ourpurposehereisnottobeextensivebutprovidesome basic information for partners’ non-familiar with this tool to use therepository.Git isaversioncontrol systemsimilar to svn [SVN]Thebigadvantageofgit isthat it is distributed: a “master” repository can be cloned, modified, locallycommitted and latter on pushed for integrating the updates to the masterrepository. When compared with svn, the big difference is that updatescommittedtotherepositoryaredoneonlylocally,andthusneedtobepushedtothe master repository (hosted at FCUL in case of DiSIEM). Error! Referencesource not found. presents some basic commands for operating the DiSIEMrepository. For more information, we refer the reader to [Chacon and Straub2014].

Table2Importantgitcommands.

Action CommandCloningremote“master”repository

git clone git@git.lasige.di.fc.ul.pt:root/DiSIEM.git

Inspect(andchange)repositoryconfigurations

git config –l (to list configs) See other options for values

Synchronizelocalrepositorywithmasterrepository(master->local)

git pull

Statusoflocalrepository git status

Statusofmasterrepository

git remote status

AddorUpdatefiles git add, git commit

Synchronizemasterrepositorywithlocalrepository(local->master)

git push origin master

Therearesomegraphical interfaces forusinggit,werecommendthe followingtwoforthepartnerslessinclinedtousethecommandline:

• http://www.syntevo.com/smartgit/(Windows,MacOS,Linux)• https://tortoisegit.org/(Windows)• https://gitextensions.github.io/(Windows)