- From: Jen Simmons <jen@jensimmons.com>
- Date: Fri, 7 Mar 2014 12:54:50 -0500
- To: Renoir Boulanger <renoir@w3.org>
- Cc: List WebPlatform public <public-webplatform@w3.org>
- Message-ID: <CAB0bRKPX=QEOuvU541Nc0mFjKkT=GbsMXCv25KsuwDye0zcp4Q@mail.gmail.com>
So, Renoir, It makes sense to me to make this repo be *the* repo for everything at web platform.org, and not on any other domains. (Easy enough since there's code for two sites in this repo currently, and we plan to delete one site — talk.webplatform.org). If this repo is the repo for everything on the main domain, www.webplatform.org, then there's no need to merge part of this into part of something else or copy (without git) pieces of it onto the server. It will be clear for anyone that ever clones this repo to work on it why all the moving pieces are for everything at www.webplatform.org. That kind of clarity would be very helpful. As it is now, with different repos getting merged together in some unknown way — it's very hard or impossible for different people to help keep things organized. I've already reorganized the stylesheets and the asset directory structure, but because I don't know what's going on on the server, I don't know what I might break with such a change. By having multiple websites in one repo or multiple repos for various parts of a single website.... everything becomes a mess. A mess that you have to clean up, or that only you understand. And I hate single points of failure, this should be dead obvious to multiple people. What do you think? If we agree, I'll set this repo up to be *the* one and only repository of everything at www.webplatform.org. Then all we have to do to launch is clone this repo to the server (or grid) that serves www.webplatform.org and pull. Any time we want to make an update, all we have to do is pull. We don't have to merge some crazy thing first. Just pull. Yes? Jen Jen Simmons designer, consultant and speaker host of The Web Ahead jensimmons.com 5by5.tv/webahead twitter: jensimmons <http://twitter.com/jensimmons> On Tue, Mar 4, 2014 at 6:18 PM, Jen Simmons <jen@jensimmons.com> wrote: > Perfect. Thanks. I'll integrate the work I did into this existing code. On > a separate branch. And then we can merge it into master. > > Jen > > Jen Simmons > designer, consultant and speaker > host of The Web Ahead > jensimmons.com > 5by5.tv/webahead > twitter: jensimmons <http://twitter.com/jensimmons> > > > > On Tue, Mar 4, 2014 at 4:48 PM, Julee Burdekin <julee@adobe.com> wrote: > >> Fantastic!!! Thanks, Renoir. J >> >> ------------------- >> Julee Burdekin >> Content Strategist >> Adobe Web Platform >> @adobejulee >> julee@adobe.com >> >> >> >> >> >> On 3/4/14, 1:42 PM, "Renoir Boulanger" <renoir@w3.org> wrote: >> >> >Hi all, >> > >> >Just a quick heads up to tell you that I made available the static >> >content on github [0]. >> > >> >We might change the way pages are generated later down the road, but for >> >now, that's how its made. >> > >> >Pull requests welcome! >> > >> > [0]: https://github.com/webplatform/static-pages >> > >> >-- >> >Regards, >> > >> >Renoir Boulanger | Developer operations engineer >> >W3C | Web Platform Project >> > >> >http://w3.org/people/#renoirb ✪ https://renoirboulanger.com/ ✪ >> >@renoirb >> >~ >> > >> >> >
Received on Friday, 7 March 2014 17:55:17 UTC