SAC Meeting 2017-05-20

From OSGeo
Revision as of 21:19, 19 May 2016 by Wildintellect (talk | contribs) (adding and more details)
Jump to navigation Jump to search


Please list the meeting topics, and link to relevant SAC tickets when possible. Meeting will be for assigning tasks, updating status, and voting. Majority of discussions should happen on the mailing list and IRC in before and after meetings. Estimated 30-60 minutes.

Time and Date set via email list poll.


  • SSL certificate Update
  • Budget Report
    • What we've spent the last few years.
    • Upcoming costs
    • What's left
  • Hardware Migration
    • Finish moving things off OSGeo4 and retire
      • Adhoc - Mapserver Demo,, ?
      • QGIS VM - run's their bugtracker (up for retirement)
    • Virtualization, Docker, or some other Sandbox
    • Plan for replacing OSGeo3 next year
  • Versioning Configuration files
  • Clean up wiki pages
  • Expand download area capacity ( TODO: Link OSUOSL discussion on dedicated download cluster service )


  • Paid Proposal System - Formalize a method for proposing tasks that require payment to make it happen in a timely manner.
    • Method for taking proposals on tasks
    • Method for soliciting vendors to fulfill tasks
    • Method for approving bids that minimizes conflict of interest (SAC members may sometimes bid)
  • LDAP
    • Merging LDAP/Wiki logins
    • LDAP user facing password reset (via email tokens)
    • Implementing OpenID so github, launchpad, google etc, work with OSGeo IDs
  • OWASP security implementation
  • Anti spam measures, and automated detection
  • HTTPS option for all hosted sites
    • Using letsencrypt certificates
    • Target foss4g archives 1st

Funding sysadmin work

The SAC Chair (Alex Mandel) suggested to write down possible handling of payed sysadmin work. It was suggested:

* Nominate an emergency response retainer
* Set up a Time and Material contract
* Set up a Proposal and Bid system


* How do we solicit bids ?
   strk> a call for interest on SAC list (priority line), on discuss list if needed (second choice)
* How much to reserve for such contract ?
   strk> current budget seems too low to allow for a new contract, so I think we should be asking for more