So far that is 6 votes to move to gitlab, either on sponsored hosting or
our current infrastructure, while there are just 2 votes to remain with
Phab either on our own infrastructure or hosted.
Seems like there is a large majority wanting Gitlab instead of Phab. Let's
continue voting for another w
Morning Guys,
To answer your questions.
In regards to a server to migrate the infrastructure to I am ready to
sponsor such an endeavour. I am also ready to rebuild the existing
server.
The question here becomes is the community ready for this to happen? I
think this is what the vote is for.
On Thu, 27 Sep 2018 00:17:53 +0100 Bertrand Jacquin said:
> > OH amount of CPU is indeed not "infinite". We have plenty of disk and RAM
> > to go around. The way I see it is "keep build jobs in the background and
> > they take however long they take". Developers should be able to run builds
> > o
> OH amount of CPU is indeed not "infinite". We have plenty of disk and RAM to
> go
> around. The way I see it is "keep build jobs in the background and they take
> however long they take". Developers should be able to run builds on their own
> boxes far faster than the shared infra and all this k
Hi all,
Regardless of gitlab vs phab while Bertrand has done a great job for a
long time I think that rebuilding our infra on a more mainstream distro
makes a lot of sense, because it will be much easier to document and for
more people to understand. Whether it ends up being Centos, openSUSE
Leap
I will gladly sponsor a server to host on until we get e5 reinstalled and going
again.
I think here before a new server is mentioned, we need to see about decide
about distribution as that will open up a whole new can of worms
Sent from my iPhone
> On 26 Sep 2018, at 17:56, Stefan Schmidt wr
My suggestion would be to move to a temporary server and use the full power of
the physical server and chroots and or docker containers. I think using the
bare metal setup right on something like centos would provide us with better
stability. If more bleeding edge stuffnis needed go for fedora.
On Tue, 25 Sep 2018 22:09:22 +0100 Bertrand Jacquin said:
> On Mon, Sep 24, 2018 at 12:26:03PM +0100, Carsten Haitzler wrote:
> > On Sat, 22 Sep 2018 15:51:44 +0100 Bertrand Jacquin
> > said:
> >
> > > On Fri, Sep 14, 2018 at 09:16:23AM +0100, Carsten Haitzler wrote:
> > > > On Wed, 12 Sep 2018
On Tue, 25 Sep 2018 22:08:14 +0100 Bertrand Jacquin said:
> On Mon, Sep 24, 2018 at 11:54:16AM +0100, Carsten Haitzler wrote:
> > On Sat, 22 Sep 2018 15:57:27 +0100 Bertrand Jacquin
> > said:
> >
> > > > > This is something I do not agree with. I have been kicking into pants
> > > > > for probl
On Tue, 25 Sep 2018 22:17:29 +0100 Bertrand Jacquin said:
> On Mon, Sep 24, 2018 at 12:32:01PM +0100, Carsten Haitzler wrote:
> > On Sat, 22 Sep 2018 15:50:00 +0100 Bertrand Jacquin
> > said:
> >
> > > On Wed, Sep 12, 2018 at 06:45:20AM -0500, Stephen Houston wrote:
> > > > OSUOSL is great. But
1. Yes I'm referring to the sponsored hosting Mike referenced. As to
whether or not that is ideal - that is one of the reasons I wanted to see
people's opinions on the slowvote.
2. I'm well aware you spent time on the thread and played with the
prototype. I'm also aware that not all questions a
Hello.
On 9/26/18 5:30 PM, Stephen Houston wrote:
> A. We were assured the server could be provided free of charge. I.E.
> "Sponsored" not bought or paid for as you and raster seem to think
> sponsored means.
The server you mentioned here is the cloud hosting Mike offered? I read
nothing besides
On 9/26/18 5:27 PM, Stefan Schmidt wrote:
Hello.
On 9/26/18 4:48 PM, Marcel Hollerbach wrote:
There is a difference between a precise plan on what kind of changes are
done and what the overall plan looks like.
- What is happening to the CI, cgit, wiki etc.
A fair question.
- Is the spon
A. We were assured the server could be provided free of charge. I.E.
"Sponsored" not bought or paid for as you and raster seem to think
sponsored means.
B. If you would have spent the last month or so since that Gitlab thread
started actually testing or using the prototype set up, you would see t
Hello.
On 9/26/18 4:48 PM, Marcel Hollerbach wrote:
> There is a difference between a precise plan on what kind of changes are
> done and what the overall plan looks like.
>
> - What is happening to the CI, cgit, wiki etc.
A fair question.
> - Is the sponsoring a permanent choice, or just somet
There is a difference between a precise plan on what kind of changes are
done and what the overall plan looks like.
- What is happening to the CI, cgit, wiki etc.
- Is the sponsoring a permanent choice, or just something for a year or
so, and the overall plan is to migrate back, (this was also p
There is no point in developing a plan if we dont know what the plan is or
what the desire is of the community.
On Wed, Sep 26, 2018, 9:21 AM Marcel Hollerbach wrote:
> I don't really see where this vote does make any sense.
> There is currently no one stepping up, saying he does the migration,
I don't really see where this vote does make any sense.
There is currently no one stepping up, saying he does the migration,
there is no plan how the move should be done, there is no plan on where
the funding would come from.
How should i decide if a move would make sense or not in this stage?
Hello developers,
Please take the time to consider options and vote on a migration to Gitlab
and infrastructure possibilities here: https://phab.enlightenment.org/V39
Thanks,
Stephen
___
enlightenment-devel mailing list
enlightenment-devel@lists.source
I get the impression that almost everyone is on board with gitlab and the
debate is whether or not we should implement it on our own infra or
sponsored infra. Then the follow up becomes who will do the migration. I'll
start a slow vote and mail it out.
On Wed, Sep 26, 2018, 12:37 AM wrote:
> I a
Hello.
On 9/25/18 11:08 PM, Bertrand Jacquin wrote:
> Memory is not the issue here, CPU is. Each VM has 4GB or RAM, each build
> use -j6 and we can have up to 4 jenkins build at the same time, this on
> 3 different VM.
>
> Read this a different way: having build and servers (web, git etc) is not
I am getting many different vibes here. Are we looking at redoing the e5
setup and another server is needed in terms of sponsor ship in order to
rebuild e5?
On 2018-09-25 21:08, Bertrand Jacquin wrote:
On Mon, Sep 24, 2018 at 11:54:16AM +0100, Carsten Haitzler wrote:
On Sat, 22 Sep 2018 15:57:
Seeing as I have infra access what can I do to help?
On 2018-09-25 21:17, Bertrand Jacquin wrote:
On Mon, Sep 24, 2018 at 12:32:01PM +0100, Carsten Haitzler wrote:
On Sat, 22 Sep 2018 15:50:00 +0100 Bertrand Jacquin
said:
> On Wed, Sep 12, 2018 at 06:45:20AM -0500, Stephen Houston wrote:
> >
On Mon, Sep 24, 2018 at 12:32:01PM +0100, Carsten Haitzler wrote:
> On Sat, 22 Sep 2018 15:50:00 +0100 Bertrand Jacquin
> said:
>
> > On Wed, Sep 12, 2018 at 06:45:20AM -0500, Stephen Houston wrote:
> > > OSUOSL is great. But it's pointless when none of us can get the access we
> > > need to the
On Mon, Sep 24, 2018 at 12:26:03PM +0100, Carsten Haitzler wrote:
> On Sat, 22 Sep 2018 15:51:44 +0100 Bertrand Jacquin
> said:
>
> > On Fri, Sep 14, 2018 at 09:16:23AM +0100, Carsten Haitzler wrote:
> > > On Wed, 12 Sep 2018 06:45:20 -0500 Stephen Houston
> > > said:
> > >
> > > > OSUOSL is g
On Mon, Sep 24, 2018 at 11:54:16AM +0100, Carsten Haitzler wrote:
> On Sat, 22 Sep 2018 15:57:27 +0100 Bertrand Jacquin
> said:
>
> > > > This is something I do not agree with. I have been kicking into pants
> > > > for problems with the infra for _years_ when doing Jenkins. It has
> > > > chang
Hi Guys,
From a performance stand point wouldn't bare metal be a better option to
opt for?
On 2018-09-24 11:32, Carsten Haitzler wrote:
On Sat, 22 Sep 2018 15:50:00 +0100 Bertrand Jacquin
said:
On Wed, Sep 12, 2018 at 06:45:20AM -0500, Stephen Houston wrote:
> OSUOSL is great. But it's po
On Sat, 22 Sep 2018 15:50:00 +0100 Bertrand Jacquin said:
> On Wed, Sep 12, 2018 at 06:45:20AM -0500, Stephen Houston wrote:
> > OSUOSL is great. But it's pointless when none of us can get the access we
> > need to the server and when the person that has/controls that access takes
> > forever and
On Sat, 22 Sep 2018 15:51:44 +0100 Bertrand Jacquin said:
> On Fri, Sep 14, 2018 at 09:16:23AM +0100, Carsten Haitzler wrote:
> > On Wed, 12 Sep 2018 06:45:20 -0500 Stephen Houston
> > said:
> >
> > > OSUOSL is great. But it's pointless when none of us can get the access we
> > > need to the se
On Sat, 22 Sep 2018 15:57:27 +0100 Bertrand Jacquin said:
> > > This is something I do not agree with. I have been kicking into pants
> > > for problems with the infra for _years_ when doing Jenkins. It has
> > > changed nothing and I moved over to cloud services to get the control
> > > and flex
Hi Guys,
In terms of infra what can i help with what needs to be sorted?
On 2018-09-22 14:57, Bertrand Jacquin wrote:
> This is something I do not agree with. I have been kicking into pants
> for problems with the infra for _years_ when doing Jenkins. It has
> changed nothing and I moved over t
> > This is something I do not agree with. I have been kicking into pants
> > for problems with the infra for _years_ when doing Jenkins. It has
> > changed nothing and I moved over to cloud services to get the control
> > and flexibility I needed.
>
> This is a result of policy from Beber of givi
On Fri, Sep 14, 2018 at 09:16:23AM +0100, Carsten Haitzler wrote:
> On Wed, 12 Sep 2018 06:45:20 -0500 Stephen Houston
> said:
>
> > OSUOSL is great. But it's pointless when none of us can get the access we
> > need to the server and when the person that has/controls that access takes
> > foreve
On Wed, Sep 12, 2018 at 06:45:20AM -0500, Stephen Houston wrote:
> OSUOSL is great. But it's pointless when none of us can get the access we
> need to the server and when the person that has/controls that access takes
> forever and a day to communicate and/or wont budge. Help has been offered
> in
On Sat, 15 Sep 2018 11:13:26 + jaquil...@eagleeyet.net said:
> Here is as valid point to bring up. When was the last time the version
> of phab was updated? im sure there is a newer version that fixes alot of
> the issues that you guys might be encountering.
actually it has gotten updates e
Here is as valid point to bring up. When was the last time the version
of phab was updated? im sure there is a newer version that fixes alot of
the issues that you guys might be encountering.
On 2018-09-15 08:45, Carsten Haitzler wrote:
On Fri, 14 Sep 2018 12:57:07 +0200 Stefan Schmidt
said
Hi Guys,
So the setup for gitlab was super simple for a clean new installation.
If any one is interested do let me know and ill get you the link and
once you register and setup an account I can give you guys that will
need it gitlab admin access.
Let me know if you guys are interested.
Rega
On Fri, 14 Sep 2018 12:57:07 +0200 Stefan Schmidt
said:
> Hello.
>
> On 09/14/2018 09:48 AM, Carsten Haitzler (The Rasterman) wrote:
> > On Wed, 12 Sep 2018 12:44:52 +0200 Stefan Schmidt
> > said:
> >> This is the core problem. OSUOL has indeed doing a great job for us over
> >> the years for h
On Fri, 14 Sep 2018 12:29:43 +0200 Jonathan Aquilina
said:
> I can sponsor a Linode vps for this until we get the server back in shape
I hope you have bottomless pockets :) It won't happen if this is done. If there
is no pain there will be zero movement. By doing this you avoid pain and
"things
Hi guys,
I know alot of you havent had a chance to play around with gitlab. I am
setting up a linode instance with gitlab for playing around with I have
included backups as they are dirt cheap, and once everything is setup I
will take a snapshot so if you guys break it all you need to do is le
Hello.
On 09/14/2018 09:48 AM, Carsten Haitzler (The Rasterman) wrote:
> On Wed, 12 Sep 2018 12:44:52 +0200 Stefan Schmidt
> said:
>> This is the core problem. OSUOL has indeed doing a great job for us over
>> the years for hosting and connectivity. But they can only be as good as
>> we allow the
I’m going to check the costs of a server with 100g but Linode now supports
block storage so I can spin up the vps with that and we can run everything off
of that in terms of data storage
Sent from my iPhone
> On 14 Sep 2018, at 09:56, Carsten Haitzler (The Rasterman)
> wrote:
>
> On Thu, 13
I can sponsor a Linode vps for this until we get the server back in shape
Sent from my iPhone
> On 14 Sep 2018, at 09:48, Carsten Haitzler (The Rasterman)
> wrote:
>
> On Wed, 12 Sep 2018 12:44:52 +0200 Stefan Schmidt
> said:
>
>> Hello.
>>
>>> On 09/12/2018 10:24 AM, Carsten Haitzler (The
On Wed, 12 Sep 2018 06:45:20 -0500 Stephen Houston said:
> OSUOSL is great. But it's pointless when none of us can get the access we
> need to the server and when the person that has/controls that access takes
> forever and a day to communicate and/or wont budge. Help has been offered
> in sysadm
On Thu, 13 Sep 2018 04:20:47 + jaquil...@eagleeyet.net said:
> How much space are we looking at as I am thinking a VPS running centos
> or even debian would be enough and then docker on it
well how much runs there? all of e.org ha sa lot of data - e.g. the screenshot
collection is 3g right n
On Wed, 12 Sep 2018 12:44:52 +0200 Stefan Schmidt
said:
> Hello.
>
> On 09/12/2018 10:24 AM, Carsten Haitzler (The Rasterman) wrote:
> > On Thu, 30 Aug 2018 19:49:29 +0930 Simon Lees said:
> >
> >>
> >>
> >> On 30/08/2018 18:57, Stefan Schmidt wrote:
> >>> Hello.
> >>>
> >>> On 08/10/2018 08:0
How much space are we looking at as I am thinking a VPS running centos
or even debian would be enough and then docker on it
On 2018-09-13 00:43, Simon Lees wrote:
One positive of migrating to gitlab if its done right ie containerized
is the fact that it should be simple to move, so if someone c
One positive of migrating to gitlab if its done right ie containerized
is the fact that it should be simple to move, so if someone can provide
a machine and hosting somewhere it can sit there until the point until
it no longer works for whatever reason or someone comes along with a
better solution,
To be fair I am more than willing ot sponsor a server at OVH and give
ssh access to those that need it.
On 2018-09-12 11:45, Stephen Houston wrote:
OSUOSL is great. But it's pointless when none of us can get the access
we
need to the server and when the person that has/controls that access
tak
OSUOSL is great. But it's pointless when none of us can get the access we
need to the server and when the person that has/controls that access takes
forever and a day to communicate and/or wont budge. Help has been offered
in sysadmin for years from multiple devs who are sysadmins by trade and who
Hello.
On 09/12/2018 10:24 AM, Carsten Haitzler (The Rasterman) wrote:
> On Thu, 30 Aug 2018 19:49:29 +0930 Simon Lees said:
>
>>
>>
>> On 30/08/2018 18:57, Stefan Schmidt wrote:
>>> Hello.
>>>
>>> On 08/10/2018 08:09 PM, Mike Blumenkrantz wrote:
Q: Where would this be hosted?
A:
On Thu, 30 Aug 2018 19:49:29 +0930 Simon Lees said:
>
>
> On 30/08/2018 18:57, Stefan Schmidt wrote:
> > Hello.
> >
> > On 08/10/2018 08:09 PM, Mike Blumenkrantz wrote:
> >>
> >> Q: Where would this be hosted?
> >> A: The provided link here is a cloud service which will be funded for the
> >>
On Thu, 30 Aug 2018 13:11:54 +0200 Xavi Artigas said:
> Hi,
>
> Since you explicitly asked for my opinion... I know git, but I have never
> used Gitlab (or Github) to submit patches for review, and I only learned
> Phab when I got here. Therefore I have too little background to be of any
> help,
On Mon, 3 Sep 2018 12:05:12 +0200 Vincent Torri said:
> On Mon, Sep 3, 2018 at 10:59 AM Al Poole wrote:
> >
> > Hello,
> >
> > I agree with you there Marcel. It's an awful lot of work with zero
> > guaranteed improvement
>
> and a lot of time not spent on development nor fixing bugs
That is wh
On 07/09/2018 01:36, Christopher Michael wrote:
> Having never used GitLab before, I cannot really form an opinion here.
> Yea, I took a few minutes to check out the link that was sent to the
> read-only instance, however that is not really enough to make any kind
> of informed decision as I am una
+1 for Gitlab.
I have been back and forth on this thread, and couldn't pinpoint where I
should comment. So I comment on OP.
It felt to me that using Phabricator had become quite a burden, and
while git-phab tries to bridge to methodologies like reviewing whole
branches, Gitlab offers it out
Having never used GitLab before, I cannot really form an opinion here.
Yea, I took a few minutes to check out the link that was sent to the
read-only instance, however that is not really enough to make any kind
of informed decision as I am unable to "kick the tires" on it (as in,
try it out in
I am interested in helping with this project. I would also be very
interested in taking charge of a bug triaging team. and closing out
fixed bugs as well as this will give us a chance to have a clean tracker
with only open and valid bugs
On 2018-09-06 15:07, Mike Blumenkrantz wrote:
We've had
We've had some great feedback in this thread, but this is a big decision
and there are still a number of key people who have not replied, making any
sort of transition infeasible at this time.
As for who is doing migration: I am willing to help with this and teach
people everything that is needed
Hello.
I can't find answers to my questions raised in this reply.
As I just had a private conversation with q66 on the potential move let
me ask one core question again.
Who is driving this transition and doing the work to get it all deployed?
People seem to be under the impression it would be
I've uploaded the script from my intern here:
https://git.enlightenment.org/devs/zmike/bztogl.git/
In the event that anyone is interested in using this script on a different
gitlab instance (which can be trivially set up locally using the official
community edition gitlab docker image):
* have pha
On Mon, Sep 3, 2018 at 10:59 AM Al Poole wrote:
>
> Hello,
>
> I agree with you there Marcel. It's an awful lot of work with zero
> guaranteed improvement
and a lot of time not spent on development nor fixing bugs
Vincent
-
Hello,
I agree with you there Marcel. It's an awful lot of work with zero
guaranteed improvement.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slash
Hello,
On 8/30/18 10:41 AM, Stefan Schmidt wrote:
Hello.
On 08/28/2018 05:08 PM, Stephen Houston wrote:
Hello,
Just checking in here on the status of this - Does there need to be a
slowvote or does it seem that everyone is on board here or do people
disagree and want to voice why?
I have no
On Thu, Aug 30, 2018, at 10:41, Stefan Schmidt wrote:
> Hello.
>
> On 08/28/2018 05:08 PM, Stephen Houston wrote:
> > Hello,
> >
> > Just checking in here on the status of this - Does there need to be a
> > slowvote or does it seem that everyone is on board here or do people
> > disagree and want
Hi,
Since you explicitly asked for my opinion... I know git, but I have never
used Gitlab (or Github) to submit patches for review, and I only learned
Phab when I got here. Therefore I have too little background to be of any
help, I think
However, if somebody could explain what would change regar
On 30/08/2018 18:57, Stefan Schmidt wrote:
> Hello.
>
> On 08/10/2018 08:09 PM, Mike Blumenkrantz wrote:
>>
>> Q: Where would this be hosted?
>> A: The provided link here is a cloud service which will be funded for the
>> foreseeable future.
>
> This is a crucial point here. Business decisions
Hello.
On 08/10/2018 08:15 PM, Mike Blumenkrantz wrote:
> To list some pros and cons for a switch:
>
> PROS:
> * Greatly improved patch review UI
> Gitlab is similar in workflow and usage to Github, so it will be much
> easier to use the patch review tools
What patch review tools are you talking
Hello.
On 08/10/2018 08:09 PM, Mike Blumenkrantz wrote:
>
> https://gitlab-prototype.s-opensource.org/
Thanks to the intern without name to get a real PoC out for this.
While people have advocating for such a move no one before her/him spent
the actual time to get this demonstrated!
This will h
Hello.
On 08/28/2018 05:08 PM, Stephen Houston wrote:
> Hello,
>
> Just checking in here on the status of this - Does there need to be a
> slowvote or does it seem that everyone is on board here or do people
> disagree and want to voice why?
I have not replied to this so far (a longer reply to M
Hello,
Just checking in here on the status of this - Does there need to be a
slowvote or does it seem that everyone is on board here or do people
disagree and want to voice why?
Stephen
On Fri, Aug 17, 2018 at 9:02 PM Carsten Haitzler
wrote:
> On Thu, 16 Aug 2018 10:29:15 -0400 Mike Blumenkran
On Thu, 16 Aug 2018 10:29:15 -0400 Mike Blumenkrantz
said:
> I am a bit curious where you think we need this much work with triaging?
>
> The biggest issue that we will have here is actually from our
> passive-aggressive method of rejecting things we don't like. For example,
> there are many, ma
Also to add I think stuff wiht lack of activity or things have changed
for now should be closed as well. I see the issue tracker as something
for key issues that are reproducible as well as key things that need to
get done that are key for a release or bugs to be fixed.
On 2018-08-16 14:38, Jo
The way I see it if there is lack of activity it gets closed and if need be
reopened when the issue resurfaced
Sent from my iPhone
> On 16 Aug 2018, at 16:29, Mike Blumenkrantz
> wrote:
>
> I am a bit curious where you think we need this much work with triaging?
>
> The biggest issue that we
I am a bit curious where you think we need this much work with triaging?
The biggest issue that we will have here is actually from our
passive-aggressive method of rejecting things we don't like. For example,
there are many, many patches that have been rejected and are idle for a
long time but not
On 08/10/2018 08:09 PM, Mike Blumenkrantz wrote:
for a Gitlab migration:
https://gitlab-prototype.s-opensource.org/
+1 for quitting phabricator..
--
Check out the vibrant tech community on one of the world's most
+1 (both for using gitlab and the hosting)
2018-08-12 2:04 GMT+02:00 Simon Lees :
>
>
> On 11/08/18 03:39, Mike Blumenkrantz wrote:
> > Hello,
> >
> > For some time now, everyone in the community has been expressing
> > significant dissatisfaction with the current project management software,
> >
On 11/08/18 03:39, Mike Blumenkrantz wrote:
> Hello,
>
> For some time now, everyone in the community has been expressing
> significant dissatisfaction with the current project management software,
> Phabricator. A number of individuals have proposed switching to Gitlab for
> various reasons.
>
On 12/08/18 07:09, Vinícius dos Santos Oliveira wrote:
> Just curious. I'm not a developer.
>
> But what will happen to Gerrit? I remember one comment of Rasterman years
> ago that he fell in love with Gerrit. What will the migration mean to
> Gerrit?
>
Last time we changed our tools / process
Just curious. I'm not a developer.
But what will happen to Gerrit? I remember one comment of Rasterman years
ago that he fell in love with Gerrit. What will the migration mean to
Gerrit?
2018-08-10 15:09 GMT-03:00 Mike Blumenkrantz :
> Hello,
>
> For some time now, everyone in the community has
I'm all in favour moving to a self-hosted Gitlab instance. Phabricator
is pretty awful and is not very approachable. Also, Gitlab has really
overtaken Phab in both popularity and maturity in the last 5 years
since we switched.
This will also reduce the admin burden of managing Gitolite, and
needin
Guess then would be to migrate everything and I’ll work on triaging the bigs
after
Sent from my iPhone
> On 11 Aug 2018, at 08:23, Pierre Couderc wrote:
>
>> On 08/11/2018 07:30 AM, jaquil...@eagleeyet.net wrote:
>> If we are going to migrate I think we should migrate tickets slowly to see
>>
On 08/11/2018 07:30 AM, jaquil...@eagleeyet.net wrote:
If we are going to migrate I think we should migrate tickets slowly to
see which ones are still valid and not pollute the new tracker with
issues that are either moot or no longer valid.
Mmm, it is not logical. Migrate is a thing. Process
If we are going to migrate I think we should migrate tickets slowly to
see which ones are still valid and not pollute the new tracker with
issues that are either moot or no longer valid.
On 2018-08-10 18:09, Mike Blumenkrantz wrote:
Hello,
For some time now, everyone in the community has been
I am 100% for this move. Both to gitlab and regardless of gitlab, to a new
infrastructure. I would add another plus... gitlabs CI/CD tools seem to be
way better than phabs.
On Fri, Aug 10, 2018, 1:16 PM Mike Blumenkrantz <
michael.blumenkra...@gmail.com> wrote:
> To list some pros and cons for a
To list some pros and cons for a switch:
PROS:
* Greatly improved patch review UI
Gitlab is similar in workflow and usage to Github, so it will be much
easier to use the patch review tools
* Simplified patch submission workflow
Gitlab uses git and does not require external tools such as arc/git-ph
Hello,
For some time now, everyone in the community has been expressing
significant dissatisfaction with the current project management software,
Phabricator. A number of individuals have proposed switching to Gitlab for
various reasons.
Some will recall that recently all of the FDO infrastructur
87 matches
Mail list logo
