Just a few comments inline:
> We ask that the project demonstrate collaboration, perhaps with a
> history of bug report or pull requests
>
>- Both in github and in OSGeo website, we show the team of
> contributors, and the steering committee members. But I got to say that
> we
>
I'm probably missing something obvious here, but it seems odd to me to make
OSGeoLive a special case at runtime. Wouldn't it make more sense to have the
OSGeoLive install_*.sh file configure the application for the paths on
OSGeoLive (which may include setting an environment variable to point
Hi list,
It would be useful for a Python Notebook (or any demo application) to know if
it is running on OSGeoLive in order to set paths to data etc.
Looking at the current system environment variables I don't think there is
something that would definitively declare a script is running on OSGeo
Hi Jody,
It means that we, as far, can become an OSGeo community project, which is
indeed the goal of this thread.
I see that we fulfill the checklist for a community project:
"""
In addition to being listed on the website, projects applying to the *OSGeo
Community* program are asked to:
Be ge
Yeah this kind of thing can be quick (many projects keep track of code from
day one) or take years (for geoserver we eventually sat down with a code
sprint and git history).
Here is a script I made, that produced a CSV file, that I then open up in a
spreadsheet:
#!/bin/bash
for file in `git ls-fi
