#2018: Website/Reboot Component 2 Handover to OSGeo
---------------------------+---------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: major | Milestone:
Component: Systems Admin | Keywords: website
---------------------------+---------------------
I have an action item out of todays website/rebranding meeting:
* Ask Alex to discuss how to hand over source code with SAC.
The contract with Get Interactive indicated we wanted all the source code
for the website in version control at the end of the project.
Options discussed in this mornings meeting:
* !GitHub Private
* !GitHub Public
* !GitLab
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2018>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2018: Website/Reboot Component 2 Handover to OSGeo
---------------------------+--------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: major | Milestone:
Component: Systems Admin | Resolution:
Keywords: website |
---------------------------+--------------------
Comment (by jive):
I am sorry I do not quite know what to expect for "website source code",
perhaps someone with more word press experience can answer.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2018#comment:1>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2018: Website/Reboot Component 2 Handover to OSGeo
---------------------------+--------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: major | Milestone:
Component: Systems Admin | Resolution:
Keywords: website |
---------------------------+--------------------
Comment (by wildintellect):
Depends on the products, from the sounds of it, the Theme files are the
only "source" code they created related to the new site. Should be img,
js, php, css, xhtml [1]
[1] https://codex.wordpress.org/Theme_Development
* Github Public
* OSGeo Git
Seem like the right options. Will put the question on tomorrow's meeting
agenda.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2018#comment:2>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2018: Website/Reboot Component 2 Handover to OSGeo
---------------------------+--------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: major | Milestone:
Component: Systems Admin | Resolution:
Keywords: website |
---------------------------+--------------------
Comment (by robe):
We've decided to do OSGeo Git. strk I'm sure you have instructions for
setting this up somewhere.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2018#comment:3>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2018: Website/Reboot Component 2 Handover to OSGeo
---------------------------+--------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: major | Milestone:
Component: Systems Admin | Resolution:
Keywords: website |
---------------------------+--------------------
Comment (by strk):
It should be intuitive, head over https://git.osgeo.org/gogs/, sign in,
create new repository.
Maybe under the "sac" organization, or "osgeo" one, you decide 
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2018#comment:4>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2018: Website/Reboot Component 2 Handover to OSGeo
---------------------------+--------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: major | Milestone:
Component: Systems Admin | Resolution:
Keywords: website |
---------------------------+--------------------
Comment (by robe):
It probably should go under osgeo but it seems I have no access to osgeo
org.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2018#comment:5>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2018: Website/Reboot Component 2 Handover to OSGeo
---------------------------+--------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: major | Milestone:
Component: Systems Admin | Resolution:
Keywords: website |
---------------------------+--------------------
Comment (by robe):
actually all osgeo stuff looks like it's osgeo live. Would it be bad if
we create another org, like maybe marketing?
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2018#comment:6>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2018: Website/Reboot Component 2 Handover to OSGeo
---------------------------+--------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: major | Milestone:
Component: Systems Admin | Resolution:
Keywords: website |
---------------------------+--------------------
Comment (by robe):
As noted in #2029 let's have osgeo-live have its own and then osgeo
website would go under osgeo.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2018#comment:7>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2018: Website/Reboot Component 2 Handover to OSGeo
---------------------------+--------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: major | Milestone:
Component: Systems Admin | Resolution:
Keywords: website |
---------------------------+--------------------
Comment (by strk):
To avoid waiting for OSGeo Live people to move I'd go Marketing org.
We do have a "sac" org too so it make sense to have an org for
each commettee..
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2018#comment:8>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2018: Website/Reboot Component 2 Handover to OSGeo
---------------------------+--------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: major | Milestone:
Component: Systems Admin | Resolution:
Keywords: website |
---------------------------+--------------------
Comment (by cvvergara):
I don't like the word "marketing" because it can be misleading because
OSGeo is a non for profit organization, When looking up the definition of
the word includes the word "selling" and that word can make think people
that is for profit.
Marketing: "the action or business of promoting and selling products or
services, including market research and advertising."
On how to handle it because of OSGeoLive.. I think we can have the website
repository regardless of the OSGeoLive repositories existence, but contact
incubation, talking about the issues that we are having because of having
OSGeoLive as part of trac (No movement yet from the OSGeoLive project) and
as part of OSGeo gogs (yet to inform OSGeoLive about this issue)
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2018#comment:9>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2018: Website/Reboot Component 2 Handover to OSGeo
---------------------------+--------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: major | Milestone:
Component: Systems Admin | Resolution:
Keywords: website |
---------------------------+--------------------
Comment (by robe):
Too late I added the marketing committee
and made Jody Garnett one of the owners. strk should all ldap accounts be
addable in Gogs. I can't even add Vicky's to OSGeo one? Or do I have to
create the account first
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2018#comment:10>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2018: Website/Reboot Component 2 Handover to OSGeo
---------------------------+--------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: major | Milestone:
Component: Systems Admin | Resolution:
Keywords: website |
---------------------------+--------------------
Comment (by jive):
So while I am signed in to https://git.osgeo.org/gogs I am not quite sure
what I am being asked to do.
The repository for website theme assets should be under the SAC
organization, since this is the group responsible for keeping the server
going.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2018#comment:11>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2018: Website/Reboot Component 2 Handover to OSGeo
---------------------------+--------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: major | Milestone:
Component: Systems Admin | Resolution:
Keywords: website |
---------------------------+--------------------
Comment (by jive):
Replying to [comment:9 cvvergara]:
See the wiki https://wiki.osgeo.org/wiki/Marketing_Committee for the
responsibilities of the committee (not focused on selling). It looks like
the original name was visibility committee, I have suggested renaming it
to outreach committee last year.
For a larger discussion on marketing and not-for-profits there are plenty
of examples; they key is to focus on communication of the groups intent.
And not get distracted by fundraising, or in the case of OSGeo asking for
volunteers for all our worthy activities.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2018#comment:12>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2018: Website/Reboot Component 2 Handover to OSGeo
---------------------------+--------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: major | Milestone:
Component: Systems Admin | Resolution:
Keywords: website |
---------------------------+--------------------
Comment (by jive):
Follow up to IRC discussion:
* group "osgeo"
* repo "wordpress"
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2018#comment:13>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2018: Website/Reboot Component 2 Handover to OSGeo
---------------------------+--------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: major | Milestone:
Component: Systems Admin | Resolution:
Keywords: website |
---------------------------+--------------------
Comment (by robe):
done. I'll give Jeff access once he's logged in, you should be able to
access now.
FWIW I like Outreach better than Marketing.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2018#comment:14>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2018: Website/Reboot Component 2 Handover to OSGeo
---------------------------+--------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: major | Milestone:
Component: Systems Admin | Resolution:
Keywords: website |
---------------------------+--------------------
Comment (by jive):
Can this issue be closed now?
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2018#comment:15>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2018: Website/Reboot Component 2 Handover to OSGeo
---------------------------+---------------------
Reporter: jive | Owner: sac@…
Type: task | Status: closed
Priority: major | Milestone:
Component: Systems Admin | Resolution: fixed
Keywords: website |
---------------------------+---------------------
Changes (by robe):
* status: new => closed
* resolution: => fixed
Comment:
yes
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2018#comment:16>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.