veyepar: The life of open source spatial with QGIS - From hobby to grown up, with bonus growing pains

Author(s):	Nathan Woodrow
Location	Room 6
Date	jan Fri 17	Days Raw Files
Start	13:30	First Raw Start	error-in-template
Duration	0:45:0	Offset	None
End	14:15	Last Raw End
Chapters
Total cuts_time	None min.

https://lca2020.linux.org.au/schedule/presentation/56/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf The_life_of_open_source_spatial_with_QGIS_From_hobby_to_grown_up_with_bonus_growing_pains.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

QGIS started back in 2002 as a simple hobby project with only a handful of developers and a small user base. Since then, it has grown into one of the most popular cross-platform open source spatial desktop tools available, with an ever-growing developer and user base, widely used in many sectors, even as a full replacement for commercial offerings.  This growth has not come without cost or growing pains to the project and community.  A growing user base and an ongoing effort to be taken as a serious alternative to commercial offerings have led to a shift in developer and user expectations for the project.

As QGIS has grown into areas and user bases the early developers never dreamed of, some of the feelings the project had have changed, and this might have zapped some of the fun.  Was this inevitable, as we pushed the project with more and more features and promotion in the spatial community?  How do you maintain the same feel for the project, while at the same time becoming more serious?

What about the users and the community?  Have their expectations now changed for the project? At what point did we notice a change in the community and the levels of service we were required to live up to?

Long-term-release, better build process, better documentation, UI translations into many languages; these all make great software, but at a cost for a mostly volunteer-run project. When does the project switch from pure volunteer to a more commercial entity?

Comment:

production notes