1. Messages
  2. Community management of main fd.io website

Locked Re: Community management of main fd.io website

Edward Warnicke
 

Totally.  There was some discussion after you left about whether to take a vote or wait a week.  The consensus was that you had seemed very supportive, and so we felt comfortable proceeding.
Our intention was not to preclude any further discussion you think might be productive.  Lets talk about it tomorrow :)

Ed

On Wed, Jun 5, 2019 at 12:13 PM Kinsella, Ray <ray.kinsella@...> wrote:

Hi Ed,

 

Looks like this vote occurred after I left the call, so I missed it.

 

I very much want to commend the work that John DeNisco in particular has done here, it is really impressive.

John has been working tirelessly on the FD.io documentation and the website since this time last year, he deserves a lot of recognition for this.

 

However I think this bears a little further discussion at the TSC.

For instance, I understand that this will make technical contributors such as PTL’s lives easier.

I am 100% on that page, however do we have input from the FD.io marketing committee on the change?

What happens to Linux Foundation marketing support after this change is made?

 

Could we schedule it as an agenda item tomorrow?

 

Thanks,

 

Ray K

 

From: main@... [mailto:main@...] On Behalf Of Edward Warnicke
Sent: Thursday 30 May 2019 18:04
To: main@...
Subject: [FD.io] Community management of main fd.io website

 

In todays FD.io TSC meeting, the TSC voted to take steps to allow the FD.io community to manage the main fd.io website.

 

As part of the discussion, John DeNisco showed off a Github+Hugo+Netlify version of the fd.io site, which you can see here:

 

 

It is driven by PRs to a github repo.  The repo for the above demo is:

 

https://github.com/jadenisco/fdiomain if you want to take a look at how it works.

 

We will be moving this to fdio/site in Github as part of this process.

 

Anyone can push a PR to alter the website (example).  The PRs generate preview site that can be examined prior to merge.  Deployment of merged content to the main site is automatic.

 

The other thing the TSC decided today was to ask the PTL of each project to propose 1-2 representatives to get access to review site changes in Github and have access to the Netlify org.

 

So PTLs, please respond to this email indicating your nominees for those roles.  Please cc them so I have emails to use to invite them to various things.  Bonus points if you can include their Github ids :)

 

In particular there is a place for each project to list content about themselves here:

 

 

There are some mockups for vpp and CSIT, we would like all active projects to provide content.
Join {main@lists.fd.io to automatically receive all group messages.