On 2 April 2018 at 18:55, francismb <franci...@email.de> wrote: > Hi, > >> I don't want to dwell on this too much since I think we've collectively >> agreed to focus on the real-time collaboration case. But to answer the >> question, any piece of software we basically ask people to set up to be >> productive is a barrier. In North America there's is the phrase "death by a >> thousand paper cuts" and asking people to install yet more software and do >> more to get set up does have a cost where people have a personal limit how >> how many little things they are willing to put up with. > > Doesn't that mean that the solution with the least "paper cuts" would be > to put *all* on a integrated python(-dev) web platform ? motto: just log > in and start contributing :-)
That's certainly the way corporate development environments are heading with projects like Eclipse Che (the tech behind codenvy.com), and AWS Cloud9. This post from Zapier engineering covers those two, as well as one I hadn't heard of before, CodeAnywhere: https://zapier.com/engineering/best-cloud-ides/ The main challenge with covering an approach like that in the dev guide is that none of the current core developers work that way, so we'd have a hard time providing good support to any newcomers that decided to take it up. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ core-workflow mailing list -- core-workflow@python.org To unsubscribe send an email to core-workflow-le...@python.org https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
