The Weekly Forge: 10/07/2016

The biggest development this past week is work on GForge AS v6.4.3 has started and we anticipate having it available for current customers by the end of this year.  Obviously we’ll continue work on GForgeNEXT which is accurately reflected in the highlight from last week below:

  1. Git Server Side Merges – Right now server side merges work between any two branches except when the destination branch is master. Turns out the is a bug with Git itself and we already have a patch from the Git development team and we’ll continue testing that out.
  2. Continuous Integration – We’ve begun designing the mocks required for building a Continuous Integration dashboard for all GForgeNEXT projects using Jenkins. This will complete our vision of making the integration between GForgeNEXT and CI systems tighter which reflects how integral they are to software teams.
  3. GForgeNEXT iOS – The first view for the GForgeNEXT iOS app has been stubbed out and work will continue over the coming months.
  4. Dependency Management – When a ticket has predecessors (i.e. blocking dependents) when those tickets are taken care of GForgeNEXT will notify the assignee and submitter of the ticket that work can begin on that ticket.  Those notifications will happen with growls which are also sent via push notifications via Adroid/iOS application. This is a big step towards helping PMs and project leads with automated dependency management.
  5. Improved Link Handling in Docman – Currently in 6.4.2 and prior the links to documents in docman explicitly ping to the most current version (i.e. version 7). The problem is if you email that or include it in a ticket or wiki entry that version may eventually be replaced with newer ones.  We’ve made it so the links in docman will always give users the most current version.  Don’t worry you can still explicitly send the link to a specific version of a file if you want.
  6. A handful of bug fixes for v6.4.3 are being actively worked on.

GForgeNEXT Update for 9/30/2016

Beginning this month our team will be giving weekly updates on the GForgeNEXT development.  This won’t be the painful details just the good stuff boiled down to a few talking points. We should be clear that GForgeNEXT is in open beta at https://next.gforge.com so sign-up today! Before we give our first update we’d like to share what exactly where GForgeNEXT sits.

  1. Teams – You can invite new or existing GForgeNEXT users to your projects.  When you do so, you pick their role and once the invite accepted they can begin collaboration.
  2. Tickets – plan and distribute work across your team.  We honor existing workflow rules, however, administration of those rules doesn’t exist yet. Browsing and filtering of tickets works just fine.  In short while some admin function do exist yet the ticketing system is working well for day-to-day use.
  3. Stand-up Report – GForge provide each project with a stand-up report. See what each team member has accomplished, what they are working on and what they plan on working on.
  4. Git Support – Browse branches, tags and commits through the UI (merges and merge requests are under development).
  5. Continuous Integration – Our new Jenkins plugin uses the latest Jenkins release which will pave the road for new features. Right now the Jenkins plugin accurately reports build activity back to the GForgeNEXT project and this is fully tested and working. Future work will include building a CI dashboard in GForgeNEXT.
  6. Android Support – Access chatroom and tickets all while getting push notifications while you are on the go. (iOS application is under development).
  7. Language Support – GForgeNEXT will eventually support multiple languages.  Right now we support Spanish and English and the language is set based on browser preferences which is nice for new users.

Update for 9/30/2016

  1. Git – Server side merges is code complete and being tested internally. Once this is done we will move right into merge requests.
  2. Notification Center – this feature is similar to what you see on social media sites like Facebook. This week we are adding additional formatting to notifications (date of notification and project it was generated from).  The posts are also now navigable, taking the user to the proper artifact (i.e. ticket, chat, etc)
  3. iOS App – Development began last week.
  4. Responsive UI – We’ve been doing testing to ensure GForgeNEXT renders and functions properly using the small displays on mobile devices.  The only area giving us problems was the mega-menu (the main way to navigate projects on the device)
  5. Tickets – We’re making dependency management a key feature when working with tickets.  The search API for tickets in GForgeNEXT had to be expended to make this possible and we’ve updated the interface to make this as slick as possible.  We will be sure to call attention to any ticket you are viewing that has dependencies.

As always we welcome questions on any of the activity you see.

Fall 2016 HackISU Wrap-up

 

Fall 2016 HackISU Winners for “Best use of the GForgeNEXT API”. Picture (left-to-right): Mehul Shinde, Dig Vijay Kumar Yarlagadda, Chris Matthews, Brendan O’Conner

Last weekend we sponsored our second HackISU Hackathon in Ames, Iowa.  HackISU is run, in part, by both Major League Hacking and HackISU, a student ran organization.  The GForge Group sponsored a prize for “The Best Use of the GForgeNEXT API” and out of all the teams at this fall’s HackISU two demonstrated great projects!

Runner-up: GitHub Migration

The team of Gregory “Charlie” Steenhagen, Justin Wheeler, Nathan Karasch and Jonny Krysh were this semester’s runner-ups.  At the end of the Hackathon they managed to migrate a single project out of GitHub including the Git repository and issues into a GForgeNEXT project.

Winners: GForgeNEXT Chat Commands

The winners for this semester: Mehul Shinde, Dig Vijay Kumar Yarlagadda, Chris Matthews and Brendan O’Conner implemented a way to execute user-created commands that could be ran in GForgeNEXT’s chat rooms.  They demonstrated commands that searched StackOverflow, ran Google searches that both showed up in the GForgeNEXT chat room. They also managed to do simple tasks like create new tickets, update existing tickets and list users assigned to a project.

While both teams demonstrated great ideas our winners edged out the win two ways:

  1. They exercised more of the GForgeNEXT API including use of the user, tracker, project and discussion resources.
  2. GForgeNEXT’s Chat doesn’t implement a way for user’s executed homegrown scripts yet.  This means the execution of any commands isn’t natively supported by our API and the workaround they came up to this limitation was fanastic.  Their engine would poll a given chat room looking for commands (beginning with “/”) and if the command existed it would execute the associated script.  The amount of problem solving that went into dealing with this limitation was impressive.

Overall this semester’s HackISU event was the best we’ve been a part of and we look forward being a part of future event’s.  We’ll conclude with the photo below of our winners who all earned $750 each:

Join Us at HackISU this Weekend!

This weekend The GForge Group will, again, be sponsoring HackISU this weekend up in Ames.  This is a great opportunity for young developers and engineers to have fun and gain experience working with technology. For our part, we are awarding $750 per team member (up to $3,000) to the team that makes the best use of the GForgeNext API. This is similar to our award from last year but unlike last year we trying to encourage creativity by not giving specific ideas on how to use our API (nor how you might integrate it with other APIs).

So have a look at the GForgeNext API documentation, read our intro to the GForgeNEXT API and let your imagination roam.  Any questions you may have ahead of HackISU this weekend can be sent to feedback@gforgegroup.com.

Meet the GForge Team: Kyle Goranson

This is a big year for GForge Group — we have redesigned our flagship product, GForge As, and are relaunching it as GForgeNEXT. This Spring we announced that NEXT is now available in free, private beta. Behind the scenes our team of developers has been working many long hours to bring this new product to market. Over the rest of the summer, we will be posting a blog series entitled “Meet the GForge Team.” In this series will be spotlighting each member of our team, their backgrounds, roles, and unique perspectives, so you can get to know the faces behind the software at GForge.

Summer is in full swing and it’s apropos to kick off this summer series by highlighting our interns.


Kyle Goranson
Intern, GForge Group



Where do/did you go to college?
Coe College

What is/was your major?
Computer Science, Mathematics, and Physics

When did you learn to code?
My first formal coding experience (also my first reasonable language) was my computer science 1 class in my Sophomore year of college in which I learned on C++. But my first coding experience was creating programs on my TI-84 calculator in high school, which I figured out myself, and looking back, programming in TI-basic was absolutely horrible.

What is your favorite project you have developed?
I’m going to have to go with a group project that spanned a full semester which was building a class registration system in C#. But it’s not the main part of the assignment that makes it my favorite. My group was fairly far ahead so I decided that our registration system would be better if it had a retro arcade hidden within it. So I wrote Pong, Snake, Space Invaders, and Pac Man. All of which I made as close to the original as possible. To get to the arcade, on our login screen you needed to enter your username and then enter the konami code instead of your password.

What are you doing at GForge?
I am primarily working on developing an Android app for GForgeNEXT, and I am also expanding test coverage.

What attracted you to work for GForge?
I worked with Michael Tutty during HackISU where I was building an app that was integrated with the GForgeNEXT REST API. I really enjoyed the interactions I had with him.

What is your typical day like at GForge?
The first thing I do is check to make sure my queue is up to date and then join the standup. When the standup is done, I will move on to working on whatever I have for the day. When I run into issues I will ask a question in chat and this will sometimes turn into a hangout where we figure out the problem. Somewhere in there I will take a break for lunch.

What is your dream job?
That is a good question. I have no idea. Definitely something involving programming though.

When you’re not working where can you usually be found where? Doing what?
I can usually be found at my computer even when I’m not working. I will often be playing an online game with friends, the most common of which is League of Legends.

The GForgeNEXT Beta Program Expands to Central & South America

We are happy to announce that the GForgeNEXT Beta Program now supports Spanish. This announcement reaffirms our investment in Central and South America by offering the following benefits:
  • Reduce project cost by eliminating the problems associated with unclear objectives.
  • Improve customer satisfaction by using tools that improve the quality of your software.
  • Eliminate communication gaps that often lead to lost time and money.
Participants in the GForgeNEXT beta program get these benefits:
  • Create and manage multiple projects
  • Easily change between English and Spanish
  • Maintain version control using Git, and view source code, commits and diffs online
  • Assign and track project tasks
  • Collaborate with the rest of your team your project’s chat room
  • Integrate GForgeNEXT with third party software using our [link]REST API[/link]
  • Manage todo lists across multiple projects
  • Improve GForgeNEXT by submitting your ideas directly to our product development team.
Organizations that are accepted into the Beta Program can use GForgeNEXT for free until it comes out of beta, after which Beta Program participants will qualify for discounted pricing. Are you interested? Sign-up now otherwise you can send questions to feedback@gforgegroup.com

Estamos orgullos de anunciar que la versión Beta de GforgeNEXT ha incorporado soporte para el idioma español. Este anuncio reafirma nuestro compromiso con América Central y Sudamérica ofreciendo los siguientes beneficios:

  • Reducción de los costos de su proyecto eliminando los problemas asociados con objetivos poco claros.
  • Aumento de la satisfacción de sus clientes utilizando herramientas que mejoran la calidad de su software.
  • Eliminación de brechas en la comunicación que a menudo llevan a pérdidas de tiempo y dinero.

Los participantes del programa Beta de GforgeNEXT obtendrán los siguientes beneficios:

  • Crear y administrar múltiples proyectos
  • Seguir la evolución de su código fuente utilizando Git. También podrá visualizar su código fuente online, sus commits y las diferencias entre commits.
  • Asignar y mantener un registro de las tareas de su proyecto.
  • Colaborar con el resto de su equipo en el salón de chat de su proyecto.
  • Administrar su lista de tareas personal a través de varios proyectos.
  • Cambiar fácilmente el idioma (Actualmente inglés y español).
  • Colaborar en el mejoramiento de GforgeNEXT enviando ideas y sugerencias directamente a nuestro equipo de desarrollo.

Las organizaciones que se incorporen al programa Beta podrán utilizar GforgeNEXT sin costo hasta el lanzamiento de la primer versión estable, pudiendo acceder a importantes descuentos una vez finalizada la etapa beta.

¿Está interesado? Regístrese ahora a https://next.gforge.com! Ante cualquier duda, por favor envíe su consulta a feedback@gforgegroup.com

Preview of Git Support in GForgeNEXT

Last week we rolled out a preview of Git support for GForgeNEXT and we are excited to share the first few working screenshots.  Before that, let’s run down the set of Git features supported in GForgeNext:

  • Access Git via HTTPS or SSH
  • Associate tickets to Git commits via commit messages.
  • Change the status of tickets via commit messages.
  • Web-based browsing of a Git repository.
  • Browse commits and view both in-line and side-by-side diffs.

Before we get to the screenshots of the Git related pages in GForgeNext, we invite you to participate in the GForgeNext Beta Program.  Finally, please read on if you are interested in additional Git related features on our development road map.

Git Information

Git_Info_-_GForge_AS_-_MyGForge

 Browsing Git

Git_Browse_-_GForge_AS_-_MyGForge

 Navigating Commits

Git_Commits_-_GForge_AS_-_MyGForge

View Diffs

Inline

Git_Diff__54bbbfb5f0d6cc66a446780285896cfb255428e3_-_MyGForge

Side-by-Side

Git_Diff__54bbbfb5f0d6cc66a446780285896cfb255428e3_-_MyGForge

If you like what you see above, check out these additional Git featured planned for GForgeNext:

  • Merge Requests – Request and perform peer code reviews right in GForge complete with annotations.
  • Better Diffs – Select two different commits and view the diff (inline and side-by-side).
  • Chat Integration – Chat will render Git commit hashes pasted into chat giving the user a summary of the commit (e.g. who, when, number of files, number of inserts/deletions) as well as allowing the user to click the commit hash to open up the Git diff viewer.

Again, if you would like to begin working with the features we already you can sign up for the GForgeNext Beta Program.