Is this project maintained?

[kevinburke]

It is linked from the official Google environment, yet shows 3 commits (the latest was november 2013). Wondering whether this is a one off or whether there is someone at Google who is committed to maintaining this project.

[henriquez]

Hi Kevin

Yes the App Engine team is maintaining this project. That said, its a very simple illustration of how to get flask to work on App Engine, so I don't anticipate many changes going forward. Did you have a specific interest in the project?

[webmaven]

@henriquez @dansanderson @proppy what is the difference between this project and https://github.com/GoogleCloudPlatform/appengine-try-python-flask ?

There is a similar question on that repo: googlearchive/appengine-try-python-flask#1

[dansanderson]

The appengine-try-* projects are all used on this page via Cloud Playground
(the editor):
https://console.developers.google.com/start/appengine

We've discussed merging them with the similar repos, but nobody has stepped
up to own keeping a general purpose repo in sync with the needs of the "Try
Google App Engine Now" page. Without some coordination, the team that owns
that page should have exclusive rights to the repo because they use
analytics to measure the performance of the page, and (in theory) we don't
want stray edits unrelated to the goals of that page to affect those
metrics. Entirely doable, but someone who wants to change this repo needs
to reach out to the team to work that out.

-- Dan

On Sun, Jul 6, 2014 at 11:11 AM, Michael R. Bernstein <
[email protected]> wrote:

@henriquez https://github.com/henriquez @dansanderson
https://github.com/dansanderson @proppy https://github.com/proppy
what is the difference between this project and
https://github.com/GoogleCloudPlatform/appengine-try-python-flask ?

There is a similar question on that repo:
googlearchive/appengine-try-python-flask#1
googlearchive/appengine-try-python-flask#1

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

[webmaven]

Thanks for the explanation @dansanderson.
Editing the project descriptions and README files to reflect the slightly different purposes of the projects might help avoid confusion.

[theacodes]

The try repos have been deprecated. These skeleton repos are now the source of truth.