From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga03.intel.com ([143.182.124.21]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1Suk4U-0004ou-8A for openembedded-devel@lists.openembedded.org; Fri, 27 Jul 2012 14:55:10 +0200 Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 27 Jul 2012 05:43:37 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.71,315,1320652800"; d="scan'208";a="173921439" Received: from unknown (HELO helios.localnet) ([10.252.121.30]) by azsmga001.ch.intel.com with ESMTP; 27 Jul 2012 05:43:36 -0700 From: Paul Eggleton To: openembedded-devel@lists.openembedded.org Date: Fri, 27 Jul 2012 13:43:35 +0100 Message-ID: <1642696.DpFH6cyWG1@helios> Organization: Intel Corporation User-Agent: KMail/4.8.4 (Linux/3.2.0-27-generic-pae; KDE/4.8.4; i686; ; ) In-Reply-To: References: MIME-Version: 1.0 Subject: Re: OpenEmbedded website X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jul 2012 12:55:10 -0000 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Friday 27 July 2012 13:47:32 Andrea Adami wrote: > after one year, I'd consider the transition to the oe-core development > model concluded. > Though, most people visiting the OpenEmbedded site do come on IRC or on the > ML asking about oe-classic. > > Unfortunately, the infos and the whole wiki are misgiving: there should be > immediate links to the oe-core model, to the layers, to the Yocto > documentation. > > In my opinion, we should archive the old site and restart from scratch. > > How would you improve the current (embarrassing) situation? Actually the more I think about it the more I agree we should just start from scratch - move the current one to oldwiki.openembedded.org and start a brand new one; move over content where appropriate and create new stuff for everything else. Not only will it clear stale things out, but it should create some impetus to fill the void with new up-to-date content. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre