DOCSLIB.ORG

Gforge AS User Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Gforge AS User Manual GForge AS User Manual Version 5.4 © 2005-2007 GForge Group, LLC – All Rights Reserved GForge Group, L.L.C. ♦ 1200 Valley West Drive ♦ Suite 304 to 325 ♦ West Des Moines, Iowa 50266 ♦ USA Phone: 408.837.0106 ♦ www.gforgegroup.com♦ Fax: 504.910.3655 Copyright © 2005-2007, GForge Group, LLC. All rights reserved. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other marks are the property of their respective owners. While this information is presented in good faith and believed to be accurate, GForge Group, LLC does not guarantee satisfactory results from reliance upon such information. Nothing contained herein is to be construed as a warranty or guarantee, express or implied, regarding the performance, merchantability, fitness or any other matter with respect to the products, nor as a recommendation to use any product or process in conflict with any patent. GForge Group, LLC reserves the right, without notice, to alter or improve the designs or specifications of the products described herein. GForge User Manual ii ©2007 GForge Group, L.L.C. Table of Contents Table of Contents Section 1 – Introduction to GForge..................................................................................................... 1-1 1.1 GForge Modules............................................................................................................................... 1-2 1.1.1 Professional Services ............................................................................................................................... 1-2 1.2 Registering a New GForge User ...................................................................................................... 1-3 1.2.1 Adding a New User.................................................................................................................................. 1-5 1.2.2 Logging In and Out of GForge ................................................................................................................ 1-7 1.3 Contacting GForge Group.............................................................................................................. 1-11 Section 2 – Home.................................................................................................................................... 2-1 2.1 Getting Started.................................................................................................................................. 2-2 2.2 Translations ...................................................................................................................................... 2-2 2.3 Eclipse, Visual Studio, MS Project Plugins, and Documentation.................................................... 2-2 2.4 Running a Public Website or OSS Project ....................................................................................... 2-2 2.5 Recent News..................................................................................................................................... 2-2 2.6 Activity............................................................................................................................................. 2-2 2.7 Recently Registered Projects............................................................................................................ 2-3 2.8 Top Project Downloads.................................................................................................................... 2-3 2.9 Support and Docs............................................................................................................................. 2-3 2.10 Site Search...................................................................................................................................... 2-4 Section 3 – My Stuff............................................................................................................................... 3-1 3.1 My Queue......................................................................................................................................... 3-1 3.1.1 Adding Tracker Items to Your My Queue............................................................................................... 3-1 3.1.2 Deleting Tracker Items From Your My Queue........................................................................................ 3-2 3.1.3 Saving Your Tracker Items in My Queue................................................................................................ 3-2 3.2 My Stuff Tracker Items and Projects ............................................................................................... 3-2 3.2.1 Assigned Tracker Items Tab.................................................................................................................... 3-2 3.2.2 Submitted Tracker Items Tab .................................................................................................................. 3-3 3.2.3 Projects Tab ............................................................................................................................................. 3-4 3.3 My Account...................................................................................................................................... 3-5 3.4 Change Password............................................................................................................................. 3-6 3.5 Change E-Mail................................................................................................................................. 3-7 3.6 Plugins.............................................................................................................................................. 3-7 3.6.1 Edit SSH Keys ......................................................................................................................................... 3-8 3.7 Register Project................................................................................................................................ 3-8 3.8 Monitoring...................................................................................................................................... 3-11 3.9 Dashboard....................................................................................................................................... 3-12 3.10 Activity........................................................................................................................................... 3-13 3.11 Gantt View.................................................................................................................................... 3-14 3.12 Monitored Forums ........................................................................................................................ 3-15 3.13 User Wiki...................................................................................................................................... 3-16 3.14 Files............................................................................................................................................... 3-16 3.14.1 Adding a New User File ..................................................................................................................... 3-17 3.14.2 Deleting a User File............................................................................................................................ 3-18 GForge User Manual iii ©2007 GForge Group, L.L.C. Table of Contents Section 4 – Users..................................................................................................................................... 4-1 4.1 User Summary.................................................................................................................................. 4-2 4.2 User Projects..................................................................................................................................... 4-2 4.3 User Wiki ......................................................................................................................................... 4-3 4.4 Files .................................................................................................................................................. 4-3 Section 5 – Projects ................................................................................................................................ 5-1 5.1 Trove Categorization........................................................................................................................ 5-2 Section 6 – Snippets ............................................................................................................................... 6-1 6.1 Viewing Code Snippets.................................................................................................................... 6-2 6.2 Adding a New Code Snippet............................................................................................................ 6-3 6.3 Editing a Code Snippet..................................................................................................................... 6-5 6.4 Deleting a Code Snippet................................................................................................................... 6-6 Section 7 – Project Summary................................................................................................................ 7-1 7.1 Recent News....................................................................................................................................
Load more

Recommended publications
  • Auswirkungen Der Benutzung Von Zentralen Und Dezentralen Versionsverwaltungssystemen in Open Source Projekten
    Auswirkungen der Benutzung von zentralen und dezentralen Versionsverwaltungssystemen In Open Source Projekten Masterarbeit an der Freien Universität Berlin für den Abschluss zum Master of Computer Science Jana von dem Berge 16. April 2009 Fachbereich Mathematik und Informatik Arbeitsgruppe Software Engineering Betreuer: Christopher Oezbek II Selbstständigkeitserklärung: Hiermit erkläre ich, dass ich diese Arbeit vollkommen selbständig verfasst und keine anderen als die angegebenen Quellen und Hilfsmittel benutzt sowie Zitate kenntlich gemacht habe. Berlin, 16. April 2009 Jana von dem Berge III IV Inhalt 1 Einleitung............................................................................................................. 1 1.1 Open Source Projekte .................................................................................. 1 1.2 Aufgabenstellung.......................................................................................... 1 1.3 Versionsverwaltungssysteme....................................................................... 3 1.3.1 Einführung............................................................................................. 3 1.3.2 Zentrale Versionsverwaltungssysteme.................................................. 5 1.3.3 Dezentrale Versionsverwaltungssysteme ............................................. 8 2 Forschungsmethode.......................................................................................... 10 2.1 Grounded Theory ......................................................................................
    [Show full text]
  • Gforge-Lists-Mailman Apache2 0. Mailman 0. Gforge-Db-Postgresql
    llvm-2.8-dev mongodb-clients libfpdi-php lazarus-ide-gtk2 libecpg6 libtulip-ogl-dev gnome-mime-data 0. 0. 0. libparrot3.3.0 libwnck-3-0 0. 0. libjaxp1.3-java-gcj 0. libusbmuxd1 erlang-public-key 0. 1.93236714976 0. llvm-2.8 mongodb-dev libfpdf-tpl-php 0. libecpg-compat3 0. lazarus-ide libgemplugin-ruby1.8 0. 0. 2.24719101124 0. libtulip-dev 3.33333333333 0. 0. 0. 0. 0. 0. 0. 0. libgnomevfs2-0 gnome-desktop3-data 0. 0. 0. 1.68269230769 libopenr2-3 gir1.2-wnck-3.0 0. libxalan2-java-gcj 2.22222222222 libimobiledevice1 3.22580645161 erlang-inets 0. libgpg-error0 libblkid1 0.24154589372 libparrot-dev parrot llvm-2.8-runtime mongodb-server pnp4nagios-web libpgtypes3 libtulip-qt4-dev libnet-daemon-perl lazarus-src 0.0. 0. 0. 0. libgemplugin-ruby kdebase-workspace-data libecore-input1 0. libbft-dev libgtk2.0-common 0. 0. 0. 0.70949940875 0.749506903353 libeet-dev python-lazr.uri 0. 4.54674623473 0. cl-alexandria libxau6 0. pia freespacenotifier libksieve4 libtasn1-3 libgnutls26 0.45045045045 libwnck-3-common usbmuxd erlang-ssl libxerces2-java-gcj libgnomevfs2-common 0.0426257459506 0. gir1.2-gnomedesktop-3.0 fxload 0. dahdi-linux 0. 0. libcgns-dev 0. 0. 0. 0. mount initscripts sysvinit-utils 0. 0. reportbug libdbi-perl geant321-data 0.0394477317554 0.355029585799 0. 0. 4.07786302927 llvm-2.9 libecore-evas1 libecore-fb1 0. 0. 0.1574803149611.06709047565 libatk1.0-0 0. sugar-presence-service-0.90 0. 0. 0. 0. parrot-minimal mongrel 1.41899881751.45956607495 libgcrypt11 0. ksysguard kdebase-workspace-bin 0.
    [Show full text]
  • Gestión De Proyectos Software
    Proyecto Fin de Carrera AITForge: Gestión de Proyectos Software Autor: Antonio Domingo Lagares Alfaro Titulación: Ingeniero de Telecomunicación (Plan 98) Especialidad: Telemática Año: 2005 Tutor: Antonio Estepa Alonso AITForge: Gestión de Proyectos Software Índice de contenido 1 Prefacio..................................................................................................................6 2 Portales de Desarrollo Colaborativo......................................................................7 2.1 Introducción a los Entornos Colaborativos....................................................8 2.1.1 Hosting de Proyectos de Software Libre (FOSPHost)...........................9 2.1.2 ¿Software Libre y Software de Fuentes Abiertas?...............................10 2.1.3 Prácticas deseables en Software Libre................................................11 2.1.4 El nacimiento de una nueva filosofía de trabajo...................................13 2.1.5 Objetivos de los sistemas libres de FOSPHost....................................14 2.1.6 Principales características de los sistemas FOSPHost........................16 Características intrínsecas..........................................................................16 Características de utilidad...........................................................................17 Características de usabilidad......................................................................18 Características contextuales.......................................................................19 2.1.7
    [Show full text]
  • 0000000000000000000000000
    Why use version control? Setting up CVS Saves all previous versions of all files so that Create the repository: you can undo (buggy) edits. % mkdir ~/cvsroot % [set permissions for ~/cvsroot] % setenv CVSROOT ~/cvsroot Logs changes to files so you can trace how % cvs init your sources have evolved over time. Set the CVSROOT environment variable in Mediates conflicting changes made by your .cshrc file. several different users---helps keep consistency. Repository Creating a Project Project 1 Project 2 Project 3 Create a project from existing files: % cd base64 % cvs import -m “base64” base64 carlk start Checkout the new project and delete the old files. % cvs checkout base64 Working copies Development Process with CVS Dealing with Conflicts If another user has committed changes to Get working copy Get any changes cvs checkout cvs update lines you have edited, CVS will report a conflict. Your version Edit files decode (infile, stdout); <<<<<<< decode64.c if( fclose (infile) ) return 0; ======= cvs commit if( fclose (infile) ) printf(" couldn't close file."); >>>>>>> 1.5 no Repository version Conflicts? Manually edit to remove the conflict. yes cvs update Edits on different lines are automatically Most of the merged. Resolve time you stay conflicts in shaded loop. 1 Frequently Used Commands Keywords Get the latest revisions of files with: Useful to put dynamic information in source file. % cvs update When you get a new revision, keywords are replaced with information about the file. Write changes back to repository with: % cvs commit -m“log msg” Keyword Replaced with $Author$ Username who checked in this revision. If you omit –m the editor given in the EDITOR $Date$ Date the this revision was checked in.
    [Show full text]
  • This Book Doesn't Tell You How to Write Faster Code, Or How to Write Code with Fewer Memory Leaks, Or Even How to Debug Code at All
    Practical Development Environments By Matthew B. Doar ............................................... Publisher: O'Reilly Pub Date: September 2005 ISBN: 0-596-00796-5 Pages: 328 Table of Contents | Index This book doesn't tell you how to write faster code, or how to write code with fewer memory leaks, or even how to debug code at all. What it does tell you is how to build your product in better ways, how to keep track of the code that you write, and how to track the bugs in your code. Plus some more things you'll wish you had known before starting a project. Practical Development Environments is a guide, a collection of advice about real development environments for small to medium-sized projects and groups. Each of the chapters considers a different kind of tool - tools for tracking versions of files, build tools, testing tools, bug-tracking tools, tools for creating documentation, and tools for creating packaged releases. Each chapter discusses what you should look for in that kind of tool and what to avoid, and also describes some good ideas, bad ideas, and annoying experiences for each area. Specific instances of each type of tool are described in enough detail so that you can decide which ones you want to investigate further. Developers want to write code, not maintain makefiles. Writers want to write content instead of manage templates. IT provides machines, but doesn't have time to maintain all the different tools. Managers want the product to move smoothly from development to release, and are interested in tools to help this happen more often.
    [Show full text]
  • Cross-Platform Environment for Application Life Cycle Management
    International Journal “Information Theories and Applications”, Vol. 24, Number 2, © 2017 177 CROSS-PLATFORM ENVIRONMENT FOR APPLICATION LIFE CYCLE MANAGEMENT Elena Chebanyuk, Oleksii Hlukhov Abstract: “Application Lifecycle Management (ALM) integrates and governs the planning, definition, design, development, testing, deployment, and management phases throughout the application lifecycle” [OMG, 2006]. This paper is devoted to designing of ALM for supporting all software development processes. A review of papers, making strong contribution for improving software development life cycle processes is represented. This review touches three branches of investigation, namely papers, related to: (1) improving of communication processes between stakeholders; (2) increasing effectiveness of some operations in software development life cycle processes; (3) developing fundamental methods and tools for performing different operations related to several software development life cycle. Then comparative analysis of such ALM environments as Visual Studio, Team Foundation Server, FusionForge, TeamForge, IBM Rational Team Concert, IBM Rational Software Architect, and IBM Rational Functional Tester, is performed. Comparison of different ALM environments’ functionality lets to formulate requirements for designing cross-platform ALM environment. Then the conceptual schema of cross-platform ALM based on Eclipse environment is proposed. All plugins’ functionalities were properly tested. Collaboration of plugins for supporting several software development tasks
    [Show full text]
  • Technical Report
    Eric-Hg Technical Report S-PM 140524 Mercurial Version Control of Eric Projects Technical Report – 1 – Eric-Hg Technical Report Copyright Page S-PM 140400 No commercial uses, No modifications allowed; Jurisdiction International, Format Text This work is licensed under the Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-nd/3.0/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA. Current edition PDF file, Eric_Deliver site URL: http://www.box.net/shared/k64yenrpey under the “Creative Commons License” Disclaimer The information in this document is subject to change without notice. The author and publisher have made their best efforts about the contents of this book, nevertheless the author and the publisher make no representation or warranties of any kind with regard to the completeness or accuracy of the contents herein and accept no liability of any kind including but not limited to performance, merchantability, fitness for any particular purpose, or any loss or damages of any kind caused or alleged to be caused directly or indirectly from this book. Brand Names Brand names such as Linux, Windows, Python are assumed to be universally known, and are here used in full respect of their respective owners. Planned edition On paper, under traditional copyright Published by [not yet—just appointed] Town & Country Reprographics, Inc. 230 N Main St Concord, NH 03301 (U.S.A.) All rights reserved No part of this book may be reproduced, if not for personal use, in any form or by any means, such as: graphic, electronic, or mechanical, including photocopying, recording, videotaping, or information storage and retrieval systems, without written permission of the publisher.
    [Show full text]
  • Download, Copy, Distribute, Print, Search, Or Link to the Full Texts of Articles
    Interdisciplinary Journal of Problem-Based Learning Volume 4 | Issue 2 Article 6 Published online: 9-19-2010 An Investigation of an Open-Source Software Development Environment in a Software Engineering Graduate Course Xun Ge University of Oklahoma, [email protected] Kun Huang University of Oklahoma, [email protected] Yifei Dong Openseed Institute, [email protected] IJPBL is Published in Open Access Format through the Generous Support of the Teaching Academy at Purdue University, the School of Education at Indiana University, and the Jeannine Rainbolt College of Education at the University of Oklahoma. Recommended Citation Ge, X. , Huang, K. , & Dong, Y. (2010). An Investigation of an Open-Source Software Development Environment in a Software Engineering Graduate Course. Interdisciplinary Journal of Problem-Based Learning, 4(2). Available at: https://doi.org/10.7771/1541-5015.1120 This document has been made available through Purdue e-Pubs, a service of the Purdue University Libraries. Please contact [email protected] for additional information. This is an Open Access journal. This means that it uses a funding model that does not charge readers or their institutions for access. Readers may freely read, download, copy, distribute, print, search, or link to the full texts of articles. This journal is covered under the CC BY-NC-ND license. An Investigation of an Open-Source Software Development Environment in a Software Engineering Course Xun Ge, Kun Huang, and Yifei Dong Abstract A semester-long ethnography study was carried out to investigate project-based learning in a graduate software engineering course through the implementation of an Open-Source Software Development (OSSD) learning environment, which featured authentic projects, learning community, cognitive apprenticeship, and technology affordances.
    [Show full text]
  • Tortoisecvs User's Guide Version 1.8.0
    TortoiseCVS User's Guide Version 1.8.0 Ben Campbell Martin Crawford Hartmut Honisch Francis Irving Torsten Martinsen Ian Dees Copyright © 2001 - 2004 TortoiseCVS Table of Contents 1. Getting Started What is CVS? What is TortoiseCVS? Where to Begin? 2. Basic Usage of TortoiseCVS Sandboxes Checking out a Module Windows Explorer and TortoiseCVS Total Commander and TortoiseCVS Updating your Sandbox Committing your Changes to the Repository Resolving Conflicts Adding Files and Directories to the Repository 3. Advanced Usage of TortoiseCVS Creating a New Repository or Module Watch, Edit and Unedit Tagging and Labeling Reverting to an Older Version of a File Branching And Merging Creating a Branch Selecting a Branch to Work On Merging from a Branch Going Back to the Head Branch Binary and Unicode Detection File Revision History History Dialog Revision Graph Dialog Web Log Making a Patch File 4. Customizing TortoiseCVS Overlay Icons Selecting a Different Set of Overlay Icons Changing how the Overlay Icons Work 5. Command Reference for TortoiseCVS Installing TortoiseCVS Obtaining a Working Copy: CVS Checkout... Getting Other People's Changes: CVS Update CVS Update Special... Making Your Changes Available to Others: CVS Commit... Adding New Files: CVS Add and CVS Add Contents... Discarding Obsolete Files: CVS Remove Finding Out What Has Changed: CVS Diff... Making a Snapshot: CVS Tag... Lines of Development: CVS Branch... CVS Merge... CVS Make New Module Watching And Locking Finding Out Who to Blame: CVS Annotate Showing More Information: CVS Explorer Columns Keyboard Shortcuts How Web Log Autodetects the Server URL 6. Dialog Reference for TortoiseCVS Add Dialog Checkout Dialog Update Special Dialog Commit Dialog Branch Dialog Make New Module Dialog Progress Dialog Tag Dialog Preferences Dialog Merge Dialog History Dialog Revision Graph Dialog About Dialog 7.
    [Show full text]
  • Githosting Public Git Hosting Sites
    GitHosting From Git SCM Wiki Public Git hosting sites Here are some places that provide free Git hosting. Check on GitServer if you want to host your own repository. List is limited to sites that provide explicit Git hosting, not including generic hosting sites that can be used to host Git repositories. Framework is Support for Open-source Space Free private Provider open-source? other SCM repositories (GB) repositories Assembla (http://www.assembla.com/catalog/51-free-private- No SVN/Hg/P4 Yes 0.15 1 project, 3 users git-repository-package?type=private&ad=git-wiki) Beanstalk (http://beanstalkapp.com/?ad=git-wiki) No SVN No 0.1 1 projects, 1 user Unlimited projects, 5 bitbucket.org (http://bitbucket.org/) No Mercurial Yes Unlimited collaborators 5 repositories, 5 Codetidy (https://codetidy.net) No No No 0.1 collaborators Public access 1 project (unlimited Codebase (http://codebasehq.com) No Mercurial/SVN 0.05 available repos), 2 collaborators CloudForge (http://www.cloudforge.com/) No CVS/SVN Yes 0.2 1 user only Unlimited projects, 6 Deveo (https://deveo.com/) No Mercurial/SVN No Unlimited collaborators Unlimited projects, 10 GitEnterprise (http://www.gitenterprise.com/) No No No 1 collaborators GitHub (http://github.com/) No SVN Yes Unlimited No Unlimited projects, GitLab.com (https://about.gitlab.com/gitlab-com/) Yes No Yes Unlimited unlimited collaborators Pikacode (http://pikacode.com/) No Mercurial Yes 1 No 1 project, 2 ProjectLocker (http://www.projectlocker.com) No SVN Read-only http 0.2 collaborators repo.or.cz (http://repo.or.cz/)
    [Show full text]
  • Collaborative Software Development Using R-Forge
    INVITED SECTION:THE FUTURE OF R 9 Collaborative Software Development Using R-Forge Special invited paper on “The Future of R” Forge, host a project-specific website, and how pack- age maintainers submit a package to the Compre- by Stefan Theußl and Achim Zeileis hensive R Archive Network (CRAN, http://CRAN. R-project.org/). Finally, we summarize recent de- velopments and give a brief outlook to future work. Introduction Open source software (OSS) is typically created in a R-Forge decentralized self-organizing process by a commu- nity of developers having the same or similar inter- R-Forge offers a central platform for the develop- ests (see the famous essay by Raymond, 1999). A ment of R packages, R-related software and other key factor for the success of OSS over the last two projects. decades is the Internet: Developers who rarely meet R-Forge is based on GForge (Copeland et al., face-to-face can employ new means of communica- 2006) which is an open source fork of the 2.61 Source- tion, both for rapidly writing and deploying software Forge code maintained by Tim Perdue, one of the (in the spirit of Linus Torvald’s “release early, release original SourceForge authors. GForge has been mod- often paradigm”). Therefore, many tools emerged ified to provide additional features for the R commu- that assist a collaborative software development pro- nity, namely a CRAN-style repository for hosting de- cess, including in particular tools for source code velopment releases of R packages as well as a quality management (SCM) and version control.
    [Show full text]
  • When Developers Build Software, They're Able to Keep Track of All The
    < Day Day Up > Practical Perforce By Laura Wingerd ............................................... Publisher: O'Reilly Pub Date: November 2005 Print ISBN-10: 0-596-10185-6 Print ISBN-13: 978-0-59-610185-5 Pages: 358 Table of Contents | Index When developers build software, they're able to keep track of all the different versions and all the components they use with software configuration management (SCM) systems. One of the more popular SCM products is Perforce. Authored by Perforce's own VP of product technology, Practical Perforce is the ideal complement to the existing product manual, focusing less on the 'how" and more on the "why" and "when." The book is not only a helpful introduction to Perforce, it's an enlightening resource for those already familiar with this versatile SCM product. Whether you're a programmer, product manager, or build engineer, you stand to benefit from the many insider tips and ideas presented in this convenient guide. Practical Perforce is divided into two main parts. Part I offers a whirlwind technical tour, complete with careful descriptions of basic and advanced Perforce commands designed to give you a baseline knowledge. Part II describes the big picture-using Perforce in a collaborative software development. It outlines recommended best practices and quickly shows how to implement them with the Perforce operations introduced in Part I. Throughout the book, you'll learn how to maximize Perforce so it completes tasks like these in the most efficient manner possible: Keep track of changes as you conduct concurrent parallel work on files Log activity Generate reports on who did what when Compare, merge and branch files Store files and file configurations Restore lost bug fixes Recognizing the pitfalls and practices of an SCM system like Perforce is absolutely essential to producing good software.
    [Show full text]