[SAC] website/rebranding meeting follow up

Jeffrey Johnson ortelius at gmail.com
Thu May 18 11:55:58 PDT 2017


I'd prefer that every project on osgeo live just includes a .about.yml
in their repo. But we can discuss the best path forward.

On Thu, May 18, 2017 at 11:54 AM, Jody Garnett <jody.garnett at gmail.com> wrote:
> Recommend using a distinct repo for your yaml files, and OSGeo live build
> can pull that in via git externals.
>
> --
> Jody Garnett
>
> On 18 May 2017 at 11:52, Jeffrey Johnson <ortelius at gmail.com> wrote:
>>
>> On Thu, May 18, 2017 at 11:51 AM, Jeffrey Johnson <ortelius at gmail.com>
>> wrote:
>> > Hi All,
>> >
>> > Jody and I can work on preparing a sort of "Statement of Work" for the
>> > things we need. I've summarized them below.
>> >
>> > * Setup Wordpress on OSGeo server/VM for staging/production
>> > * Configure https etc
>> > * Configure Plugins per vendor
>> > * Configure Backup/Restore etc
>> > * Configure LDAP and other Auth (google, github etc)
>> > * Configure Group permissions for content management
>> > * Facilitate content migration from dev site to staging/production with
>> > vendor
>> > * Participate in Acceptance testing process with vendor
>> >
>> > We also would like to adopt this kind of format for projects to
>> > maintain their own details in their own repos
>> > https://github.com/18F/about_yml so we would like to figure out how to
>> > setup a cron or similar to harvest this information and store it in
>> > the appropriate place so the website can use it in its pages. This
>> > will take some basic development work in wordpress and shell
>> > scripting. We would like to use this same kind of methodology for
>> > Service Providers and resources so that people can submit new/updated
>> > content via PR when they are comfortable doing so.
>>
>> I've cc'd cameron shorter here (not sure if he is on this list). He is
>> particularly interested in making sure that this process is harmonized
>> with the OSGeo Live docs production such that the same pages from the
>> site are included in osgeolive and we have only one source of truth
>> for these data.
>>
>> > Im sure we can think of a few more nice to haves, but this is the
>> > basic stuff we are looking for.
>> >
>> > Happy to join a chat or call to discuss.
>> >
>> > Jeff
>> >
>> > On Thu, May 18, 2017 at 11:39 AM, Jody Garnett <jody.garnett at gmail.com>
>> > wrote:
>> >> I just went and updated the budget wiki page based on amendments  -
>> >> https://wiki.osgeo.org/wiki/OSGeo_Budget_2017
>> >>
>> >> There is 3,000 USD allocated to SAC for this activity if that helps.
>> >>
>> >> For reference here is the timeline (next milestone 3 May 26th).
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Jody Garnett
>> >>
>> >> On 12 May 2017 at 10:36, Jody Garnett <jody.garnett at gmail.com> wrote:
>> >>>
>> >>> We have an action item for Harrison / SAC coming out of wednesday's
>> >>> meeting:
>> >>>
>> >>> * Setup LDAP and acceptance environments
>> >>>
>> >>> There is a payment milestone coming for the contractor at the end of
>> >>> the
>> >>> month, I want to make sure we are not holding things up.
>> >>> --
>> >>> Jody Garnett
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> Sac mailing list
>> >> Sac at lists.osgeo.org
>> >> https://lists.osgeo.org/mailman/listinfo/sac
>> _______________________________________________
>> Sac mailing list
>> Sac at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/sac
>
>
>
> _______________________________________________
> Sac mailing list
> Sac at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/sac


More information about the Sac mailing list