+1! On Oct 9, 2015 10:37 PM, "Kevin Sweeney" <kevi...@apache.org> wrote:
> +1! > > On Fri, Oct 9, 2015 at 3:35 PM Marco Massenzio <ma...@mesosphere.io> > wrote: > > > +1 > > > > Dave - great stuff! > > > > *Marco Massenzio* > > > > *Distributed Systems Engineerhttp://codetrips.com <http://codetrips.com > >* > > > > On Fri, Oct 9, 2015 at 3:05 PM, Dave Lester <d...@davelester.org> wrote: > > > > > As part of the #MesosCon Europe hackathon, my team has been making > > > improvements to the website. Among these changes, we'd like to propose > > > changing where the website source files live by moving them to the main > > > Mesos codebase. Our current progress / working branch of this is > > > available on GitHub: https://github.com/fayusohenson/mesos/tree/site > > > > > > * What does this mean? * > > > We've added a /site directory to the Mesos codebase, which includes the > > > website source files. Today, these live in subversion. The rake file > and > > > other parts of building the website all work in this new environment, > > > plus a number of related fixes (image linking, etc). > > > > > > For committers that are familiar with the current model for pushing the > > > site live, this immediate change still requires us `svn commit` the > > > /publish directory for the website (static files that are generated). > > > > > > * Why this change? * > > > 1. Today we do not have an easy process for the community to contribute > > > to the project website. By merging this with the Mesos codebase, it > will > > > be significantly easier to send a review or pull request. > > > 2. It'll be easier for committers to manage the website, and check that > > > documentation changes render on the website properly before committing. > > > Because it's difficult to do today, this is often not checked. :( > > > 3. It's a solid step toward an automated deployment of the website in > > > the future: https://issues.apache.org/jira/browse/MESOS-1309 > > > > > > * Who approves of this change? * > > > As the Mesos website maintainer, I feel good about this change and its > > > direction for the project. Before committing this change, I'd like > > > community support that including this in the main Mesos codebase makes > > > sense. > > > > > > Comments? Questions? > > > > > > Dave > > > > > >
