[Marketing] component 2 website review

So this is the big one, in part because it is a review for both Get Interactive (any missing functionality or migrated content) and for our OSGeo contributors (and missing content we need to write).

Get Interactive is well in hand with a short list of “bugs”: https://github.com/OSGeo/osgeo/issues?q=is%3Aissue+is%3Aopen+label%3Abug

For our OSGeo contributors we have a number of content issues we can address with the tools provided: https://github.com/OSGeo/osgeo/issues?q=is%3Aissue+is%3Aopen+label%3Acontent

And “help wanted” issues where functionality is stuck waiting on our contributors or direction: https://github.com/OSGeo/osgeo/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22

Priorities for this week:

  1. I have a hangout today with Marc (hi Marc where are you!) to go over the “content inventory and site map”:

Content Inventory and Site Map

This is a short list of all the content that needed to be migrated or written for the website. In last week’s meeting we did a quick pass to verify what content migration has occurred (all the news items yay!). This needs to be double checked, creating a “bug” or “content” issue for anything that is missing.

···
  1. Get Interactive is squashing outstanding bugs and sending out a feedback survey. Some of the issues, like how to handle location, may be tricky.

  2. Resolve hosting issue with SAC, it appears as if there is an Oct 10th meeting taking shape. I am not sure if we have managed to communicated to SAC members that the website is not ready yet (nor likely to be until hosting and access is resolved allowing our members to complete a round of writing).

So what are we missing here? A strategy for handling enhancements requested by our community, either already reported to github, or via feedback survey being sent out after issues resolved. While we have our hands full confirming content please consider what you would like to see happen.

Jody Garnett

Website crew:

If you are available for this activity it would be good to have our content story straight so we can confirm component 2 is delivered and plan for community engagement and delivery.

···

On 8 October 2017 at 12:33, Jody Garnett <jody.garnett@gmail.com> wrote:

So this is the big one, in part because it is a review for both Get Interactive (any missing functionality or migrated content) and for our OSGeo contributors (and missing content we need to write).

Get Interactive is well in hand with a short list of “bugs”: https://github.com/OSGeo/osgeo/issues?q=is%3Aissue+is%3Aopen+label%3Abug

For our OSGeo contributors we have a number of content issues we can address with the tools provided: https://github.com/OSGeo/osgeo/issues?q=is%3Aissue+is%3Aopen+label%3Acontent

And “help wanted” issues where functionality is stuck waiting on our contributors or direction: https://github.com/OSGeo/osgeo/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22

Priorities for this week:

  1. I have a hangout today with Marc (hi Marc where are you!) to go over the “content inventory and site map”:

Content Inventory and Site Map

This is a short list of all the content that needed to be migrated or written for the website. In last week’s meeting we did a quick pass to verify what content migration has occurred (all the news items yay!). This needs to be double checked, creating a “bug” or “content” issue for anything that is missing.

  1. Get Interactive is squashing outstanding bugs and sending out a feedback survey. Some of the issues, like how to handle location, may be tricky.

  2. Resolve hosting issue with SAC, it appears as if there is an Oct 10th meeting taking shape. I am not sure if we have managed to communicated to SAC members that the website is not ready yet (nor likely to be until hosting and access is resolved allowing our members to complete a round of writing).

So what are we missing here? A strategy for handling enhancements requested by our community, either already reported to github, or via feedback survey being sent out after issues resolved. While we have our hands full confirming content please consider what you would like to see happen.

Jody Garnett


Jody Garnett

Reminder - we need to follow up on this, it is our last remaining activity for the website/rebranding initiative.

···

On 13 October 2017 at 13:17, Jody Garnett <jody.garnett@gmail.com> wrote:

Website crew:

If you are available for this activity it would be good to have our content story straight so we can confirm component 2 is delivered and plan for community engagement and delivery.


Jody Garnett


Jody Garnett

On 8 October 2017 at 12:33, Jody Garnett <jody.garnett@gmail.com> wrote:

So this is the big one, in part because it is a review for both Get Interactive (any missing functionality or migrated content) and for our OSGeo contributors (and missing content we need to write).

Get Interactive is well in hand with a short list of “bugs”: https://github.com/OSGeo/osgeo/issues?q=is%3Aissue+is%3Aopen+label%3Abug

For our OSGeo contributors we have a number of content issues we can address with the tools provided: https://github.com/OSGeo/osgeo/issues?q=is%3Aissue+is%3Aopen+label%3Acontent

And “help wanted” issues where functionality is stuck waiting on our contributors or direction: https://github.com/OSGeo/osgeo/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22

Priorities for this week:

  1. I have a hangout today with Marc (hi Marc where are you!) to go over the “content inventory and site map”:

Content Inventory and Site Map

This is a short list of all the content that needed to be migrated or written for the website. In last week’s meeting we did a quick pass to verify what content migration has occurred (all the news items yay!). This needs to be double checked, creating a “bug” or “content” issue for anything that is missing.

  1. Get Interactive is squashing outstanding bugs and sending out a feedback survey. Some of the issues, like how to handle location, may be tricky.

  2. Resolve hosting issue with SAC, it appears as if there is an Oct 10th meeting taking shape. I am not sure if we have managed to communicated to SAC members that the website is not ready yet (nor likely to be until hosting and access is resolved allowing our members to complete a round of writing).

So what are we missing here? A strategy for handling enhancements requested by our community, either already reported to github, or via feedback survey being sent out after issues resolved. While we have our hands full confirming content please consider what you would like to see happen.

Jody Garnett