During the Git Phase Next: Promised Land talk, it was stated that an ideal issue queue might have it's own openly commit-able repo/sandbox so that anyone can jump in and help fix problems with that issue. What REALLY helps with understanding an issue and working towards a tangible conclusion is being able to see a demo of the planned feature or fix.

What if we could leverage the Demo module to spin up a temporary multisite that showcases the sandbox's code inside a stock D7/D8 site?. It would be better than random screenshots of a point in time that could already be obsolete cause somebody else *just* committed more code. :)

Thoughts: the demo website would have to utilize a certain 'snapshot' of the repo that's tied to an issue number + comment number, or it would make no sense. Also, the person who clicks the 'make this commit into a demo site' checkbox during a comment would be the one who 'owns' that demo site, and they'd have to re-confirm their continued desire to keep this demo site alive until such time as they stop clicking 'yes' in the monthly email prompt or the issue is closed by the two-week autobot.

Comments

helmo’s picture

helmo commented

It's not the demo module but this relates to the site http://simplytest.me/

It's now integrated in Dreditor: #1921588: Improve simplytest.me integration

helmo’s picture

helmo commented
Issue summary: View changes
Status: Active » Closed (works as designed)

[Stock response from Dreditor templates and macros.]

I'm marking this as works as designed.
I assume that, from the lack of response, the issue has since been solved.

Feel free to re-open this issue if you want to provide further information. Thanks.

senpai’s picture

senpai commented
Issue summary: View changes
Status: Closed (works as designed) » Postponed

Let's do a 'postponed' for this idea, since it's still valid, and would still be useful for the community at large to be able to contribute to a project in-place without having to spin it up themselves or go to a third-party website which evaluates the codebase but doesn't take into account the potential improvements from multiple sandboxes.

(Also, it's not customary to manually take an issue directly to the 'closed' state, but instead mark is as 'fixed' so that people have a couple of weeks to respond before the autobots come by and bury it for good)

helmo’s picture

helmo commented
Status: Postponed » Postponed (maintainer needs more info)

Ok, but the lets set it to Postponed (maintainer needs more info), to let Dreditor hide it for me ;)

PS: about the fixed->closed transition ... there is no such transition to 'Closed (works as designed)' otherwise I would have used that.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)