[Incubator] August 16 Incubation Video Meeting
Jody Garnett
jody.garnett at gmail.com
Wed Aug 16 10:58:29 PDT 2023
Actions:
- Action: (volunteer) deprecate incubation-process document
- Action: (volunteer) deprecate evaluation document
- Action: (jody) Write up this application document as PDF and share
draft with the email list
Next meeting scheduled for September 16th
Incubation Video Meeting
August: 16, 2023
Attending: Regina, Tom, Jody, Angelos, Vicky
Agenda
-
qfield application
-
mentor guidelines
-
document roundup
-
video chat
Q: How to Join?
A: Send email - see
https://wiki.osgeo.org/wiki/Incubation_Committee#Committee_Operation
qfield application
-
Resubmit when statement available from qgis.org (on questions raised on
email list)
-
When clarification is public from Marco, OSGeo is in position to make
a motion for osgeo community program
-
Q: How have these conversations carefully (when public discussion is not
an option)?
A: recommend attending video meeting (such as this one)
mentor guidelines
Arnulf had some comments/discussion here.
-
https://wiki.osgeo.org/wiki/Incubation_Mentor_Guidelines
-
https://github.com/OSGeo/osgeo/tree/master/incubation/documents
(no official PDF here)
-
https://www.osgeo.org/about/committees/incubation/mentor/
-
this was a page converted from old website as an experiment
-
The decision was to make make such “content” into documents here
https://www.osgeo.org/resources/ and treat them as PDF
-
Examples:
https://www.osgeo.org/resources/individual-contributor-license/
https://www.osgeo.org/resources/osgeo-bsd-license/
https://www.osgeo.org/about/committees/incubation/incubation-process/
https://www.osgeo.org/about/committees/incubation/evaluation/
https://www.osgeo.org/about/committees/incubation/application/
-
Action (outstanding): Is to make PDF content for our official documents
-
Q: Who can update the wiki page?
A: Anyone (it is a wiki) … and not very official
Good for notes and discussion
document roundup
-
It would be good find out what documents (historical) incubation
committee is responsible for and turn them into PDFs for website
-
https://www.osgeo.org/about/committees/incubation/incubation-process/
-
https://www.osgeo.org/about/committees/incubation/evaluation/
-
https://www.osgeo.org/about/committees/incubation/application/
-
Old website?http://old.www.osgeo.org
-
Not available presently
-
Done:
-
https://github.com/OSGeo/osgeo/blob/master/incubation/documents/graduation_checklist.md
(for projects to copy and paste)
-
https://github.com/OSGeo/osgeo/blob/master/incubation/documents/graduation_checklist.pdf
(to print out and look pretty)
https://www.osgeo.org/about/committees/incubation/incubation-process/
-
Status: change to deprecated
-
Current process is on https://www.osgeo.org/about/committees/incubation/
1. Add to website, 2. Apply for community program 3. Apply for
incubation
-
Action: (volunteer) deprecate incubation-process document
https://www.osgeo.org/about/committees/incubation/evaluation/
-
Status: change to deprecated
-
The committee page communicates goals/ideals:
-
The checklist has this represented better:
-
Action: (volunteer) deprecate evaluation document
https://www.osgeo.org/about/committees/incubation/application/
-
A long list of things, resulting in a trac ticket.
-
Do we continue with trac (or email the list?)
1.
Please provide the name and email address of the principal Project Owner.
1.
On the OSGeo website page
2.
Please provide the names and emails of co-project owners (if any).
1.
We would need a contact person
3.
Please provide the names, emails and entity affiliation of all official
committers
1.
Can figure this out incubation
4.
Please describe your Project.
1.
Covered by project readme and OSGeo project website page
5.
Why is hosting at OSGeo good for your project?
1.
Hosting is the wrong word here (we are not a forge).
2.
Consider changing to:
1.
Why is this project applying to join the OSGeo Foundation?
2.
Why is this project team applying to join OSGeo Foundation?
6.
Type of application does this project represent(client, server,
standalone, library, etc.):
1.
This was established on website page
7.
Please describe any relationships to other open source projects.
1.
This was established on website page
8.
Please describe any relationships with commercial companies or products.
1.
This was established on website page
9.
Which open source license(s) will the source code be released under?
1.
This was established on website page
10.
Is there already a beta or official release?
1.
This was established on website page (we require projects to have a
release of OSGeo community program)
11.
What is the origin of your project (commercial, experimental, thesis or
other higher education, government, or some other source)?
1.
This is an interesting question with respect to sustainability
(so current funding is more important than how it started)
2.
Could be important if project was a fork or history behind the IP
used ofr the project
12.
Does the project support open standards? Which ones and to what extent?
(OGC, w3c, ect.) Has the software been certified to any standard (CITE for
example)? If not, is it the intention of the project owners to seek
certification at some point?
1.
This was established on website page (there is a section for
standards and you can choose form or add to a list)
13.
Is the code free of patents, trademarks, and do you control the
copyright?
1.
OSGeo does not require trademark transfer; but we do not wish to be
in trouble legally if you are vulnerable to trademark infringement (yes
this has happened)
2.
This may be worthwhile asking as three questions:
1.
Is your project source code free of patents?
2.
Is your project name trademarked, or making use of trademarked
technologies?
3.
Does your team control the copyright for your project source code
and documentation?
14.
How many people actively contribute (code, documentation, other?) to the
project at this time?
1.
This may be established on the website page - can have a link to repo
status?
2.
Some of this is available as stats on the repository
15.
How many people have commit access to the source code repository?
1.
This may be more tricky these days, people that can merge
pull-requests for example
16.
Approximately how many users are currently using this project?
1.
This is really hard to know, so best guess is okay
2.
Download stats do not work
3.
Open source community does not appreciate “Call-home” functionality
4.
Could be “featured” / “showcase” examples such as use-case
5.
I don’t know my users :)
6.
Can we do better wording?
1.
How actively used is your project or technology? ( number of
users, downstream applications, prominent websites, inclusion in
distribution, or something?)
17.
What type of users does your project attract (government, commercial,
hobby, academic research, etc. )?
1.
What are we trying to ask here? Sustainability or applicability or?
2.
What are the drivers for your project - share how your
project/technology is used by the public?
(government, commercial, enthusiast, academic, research,...)?
18.
If you do not intend to host any portion of this project using the OSGeo
infrastructure, why should you be considered a member project of the OSGeo
Foundation?
1.
Outdated, remove, OSGeo hosting/forge is available for pretty much
anyone because we wish to foster innovation …
19.
Does the project include an automated build and test?
1.
Can we remove this? Or is it useful here …
1.
No - it is a useful question to determine software team maturity /
responsibility
2.
Aside: This is covered in the incubation process, we ask for some
level of software maturity?
1.
Can they work on this during incubation? Yes …
3.
This could be useful in choosing an appropriate mentor
20.
What language(s) are used in this project? (C/Java/perl/etc)
1.
This already established on website page
21.
What is the dominant written language (i.e. English, French, Spanish,
German, etc) of the core developers?
1.
This is useful in choosing a mentor
22.
What is the (estimated) size of a full release of this project? How many
users do you expect to download the project when it is released?
1.
Remove: This was a forge/hosting question from the system admin
committee
Sidebar on “already established on website page”:
-
Website does not know PSC and Officer
-
We could make https://www.osgeo.org/about/board/ generated
-
Who's involved is elective; rather than a reflection of project team
-
Link to “contributors” often links to outside page
-
Idea: Make something like for the “partner” page to formally link
officer and PSC.
Action: (jody) Write up this document as PDF and share with the email list
Use of Trac:
-
Do we wish to continue using trac? Or email? Or wiki? There is a lot of
duplication …
-
Advantage: Wiki has history of changes
-
How long should applicants wait?
Really it is based on access to a mentor…
-
How long to keep trac issues open?
-
Right now people do everything: (status-quo)
-
trac first, send email to ask people to look at trac, when a wiki
once project is accepted
Video chat
-
Is this a good format?
-
It is great for sensitive topics/applications
-
How often?
-
We do not have quorum so hard to answer
-
Next? September 16th: To check in on above activities
-
Ongoing?
-
Twice a year? Perhaps not often enough to get back to projects …
-
Quarterly? May be more appropriate
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/incubator/attachments/20230816/2b543b62/attachment-0001.htm>
More information about the Incubator
mailing list