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.
Sent from my iPhone > On 26 Sep 2018, at 17:30, Stephen Houston <smhousto...@gmail.com> 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. > > 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 that > gitlab provides a web interface for git, so no need for cgit. Obviously > phab provides a wiki and gitlab provides a wiki so the move from phab to > gitlab would move phab's wiki to gitlab's wiki. Again these are trivial > things that could have/should have been discussed for the many weeks that > has thread has been there. CI was also mentioned. It's a huge problem > with e5 and Stefan explained this. Gitlab has some really good CI tools, > but obviously that is one of the biggest considerations in moving as Stefan > clearly laid out. CI with E5 is crap. > > I will add a temporary move option to the vote. > > I didn't jump the gun here. The Gitlab thread has been around for a long > time now with over 50 responses and is at the point where some kind of > decisions have to be made as it is going to go stale. There is nothing > more frustrating than people who sit around and have AMPLE AMPLE time to > respond and put opinions out there and concerns and discuss things more, > and choose not to until the time comes to take the next step and they then > want to speak their mind. Communication really is key. > > Finally - This vote isn't going to set anything in stone or set anything in > motion. After weeks and weeks of responses to the thread, the vote is > simply there to guage what everybody's end goal/desire is so that we can > have more focused discussions about A. Is it possible? B. How do we > accomplish it? C. Pros/Cons D. Community buy-in > > Relax a little - Vote on the slowvote as to what your ideal situation would > be and then when the vote is over we will have a good feel of what the > community's ideal situation is and we will see if its possible to get close > to that/accomplish that. > > >> On Wed, Sep 26, 2018 at 9:49 AM Marcel Hollerbach <m...@bu5hm4n.de> 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. >> - 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 proposed in >> the "Gitlab" thread). >> >> Those questions are rather fundamental (at least to me) in order to vote >> for anything. Also, how useful is it to know that the community wants to >> have a sponsored service if there is no funding at all. >> >>> On 9/26/18 4:22 PM, Stephen Houston wrote: >>> 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 <m...@bu5hm4n.de> 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, >>>> 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? I >>>> don't even can see what kind of features would be included in case of a >>>> switch to gitlab. >>>> >>>> Greetings, >>>> bu5hm4n >>>> >>>>> On 9/26/18 3:52 PM, Stephen Houston wrote: >>>>> 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.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >>>>> >>>> >>>> >>>> _______________________________________________ >>>> enlightenment-devel mailing list >>>> enlightenment-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >>>> >>> >>> _______________________________________________ >>> enlightenment-devel mailing list >>> enlightenment-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >>> >> >> >> _______________________________________________ >> enlightenment-devel mailing list >> enlightenment-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >> > > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
