All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sahil Arora <sahilarora.535@gmail.com>
To: James Cloos <cloos@jhcloos.com>,
	Till Kamppeter <till.kamppeter@gmail.com>
Cc: Nilanjana Lodh <nilanjanalodh@gmail.com>,
	Aveek Basu <aveek.basu@lexmark.com>,
	Jeff Licquia <licquia@linuxfoundation.org>,
	Jeff Licquia <jeff@licquia.org>,
	Open Printing <printing-architecture@lists.linux-foundation.org>,
	Abhijeet Dubey <dubey.abhijeet09@gmail.com>
Subject: Re: [Printing-architecture] OpenPrinting code repositories in GIT format
Date: Sat, 02 Sep 2017 01:22:04 +0000	[thread overview]
Message-ID: <CA+3yCNK0nsuUCcRbBcs6vSwAOaTjC4QbdTB75pAtQaLcbk1C3w@mail.gmail.com> (raw)
In-Reply-To: <m3a82ehvnu.fsf@carbon.jhcloos.org>

[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]

Hi there,
Github vs Gitlab vs Bugzilla vs others is a very important problem
considering the fact that changing version control systems is very
difficult, as we are facing now. Even as I was doing my GSoC project with
OpenPrinting this year, I felt it easier to use Git rather than any other
version control system(VCS).

Here are some points which I think are noteworthy:
1. Most of the modern IDEs and Code Editors support git out of the box. Not
only that, people are now shifting to git aware shells like zsh and fish.
In this case, using git will make the life of a developer far more easier
than any other VCS or bug tracking system.
2. Both Github and Gitlab support continuous integration, which I think is
missing in other tools. It will make the life of a maintainer extremely
easy once these continuous integration / continuous delivery pipelines are
integrated with the code base for the projects we would be working in the
future.

I believe platforms which run on git will be more future proof and
developer friendly than any other platform for code / bug tracking. My
personal preference would be gitlab since provides more features out of the
box even on the free version than github, but it would not matter if it's
github or gitlab unless and until it is git.

Thanks.
--
Sahil Arora

[-- Attachment #2: Type: text/html, Size: 1715 bytes --]

  reply	other threads:[~2017-09-02  1:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30 22:10 [Printing-architecture] OpenPrinting code repositories in GIT format Till Kamppeter
2017-08-31  0:17 ` Michael Sweet
2017-08-31 11:59   ` Aveek Basu
2017-09-01 23:00 ` James Cloos
2017-09-02  1:22   ` Sahil Arora [this message]
2017-09-26 20:00 ` Till Kamppeter
2017-09-26 20:04   ` Michael Sweet
2017-10-03 17:57     ` Till Kamppeter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+3yCNK0nsuUCcRbBcs6vSwAOaTjC4QbdTB75pAtQaLcbk1C3w@mail.gmail.com \
    --to=sahilarora.535@gmail.com \
    --cc=aveek.basu@lexmark.com \
    --cc=cloos@jhcloos.com \
    --cc=dubey.abhijeet09@gmail.com \
    --cc=jeff@licquia.org \
    --cc=licquia@linuxfoundation.org \
    --cc=nilanjanalodh@gmail.com \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=till.kamppeter@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.