Re centralization: I have been using gitlab for a while. It offers all and more than github for free and even allows you to install the code to run on your own server.
gitlab.com Chris On Sun, Nov 6, 2016 at 3:23 PM, Offray Vladimir Luna Cárdenas < [email protected]> wrote: > Hi, > > I would prefer to continue discussions here instead of github. I use it > for almost nothing and seems pretty dangerous the centralization of > infrastructure in private hands. The ironies of GitHub centralizing a > descentralized infrastructure and making developers to rely in a tool they > can't not change are explaned in detail at We’re in a brave, new post open > source world here: > > https://medium.com/@nayafia/we-re-in-a-brave-new-post-open- > source-world-56ef46d152a3#.fbzv8xjgj > > So would be really good to keep this forum open for those who have to have > something to say about Leo, but doesn't understand, like or use GitHub a > lot. I think that these easy ways to belong to a community should be kept > open. > > Cheers, > > Offray > > > On 06/11/16 10:24, 'Terry Brown' via leo-editor wrote: > >> On Sun, 6 Nov 2016 06:03:51 -0800 (PST) >> "Edward K. Ream" <[email protected]> wrote: >> >> On Sunday, November 6, 2016 at 8:01:53 AM UTC-6, Edward K. Ream wrote: >>> >>> Several high-profile projects now use GitHub their issue tracker for >>> *all* >>> >>>> discussions. >>>> >>>> There are substantial benefits to doing so: >>>> >>>> >>> 4. And it's possible to change the name of the issue, unlike here. >>> >>> 5. It's easy to categorize and prioritize discussions. >>> >>> I'm sure there are more benefits. Anyone see any problems? >>> >>> EKR >>> >> Personally I'd be fine with that, but I think it will be hard to get >> more than 50% adoption, so things will still be split. E-mail lets >> people pick their own environment, rather than requiring use of the >> GitHub web interface. Well, maybe that's not a requirement seeing >> you can subscribe to all issues and get them in your email, but I think >> you'd at least have to start the thread with the GitHub web interface. >> >> Looking at it just now, it doesn't seem to handle nested quoted replies >> properly. In fact quoting in replies isn't really obvious at all. You >> select the text you want to reply to (can't see how to skip this when >> you want to quote the whole message) and hit `r`. But any quoting >> already present in the selecting text is lost. >> >> Another drawback is that people who aren't subscribed to all issues as >> you and I are won't see them on the mailing list - fine if GitHub >> replaces the mailing list, but I don't think it will or should, for the >> same reasons I don't think we should insist on using git to get Leo >> (other than version releases). Use of GitHub is by no means universal >> even among programmers, and Leo has a lot of non-programmer users. >> >> So... it would work for me, quoting issues aside, but not sure it's a >> one stop solution. OTOH in the past people asking questions / starting >> discussions of possible bugs on GitHub have been told to not open >> non-bug issues without discussing in the forum first, I think it's a >> step forward if we just respond to those threads on GitHub - it's not >> just for bugs... which is I guess your original point :-) >> >> Cheers -Terry >> >> > -- > You received this message because you are subscribed to the Google Groups > "leo-editor" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/leo-editor. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
