Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C3B2A200B61 for ; Tue, 9 Aug 2016 21:31:26 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C2475160AA5; Tue, 9 Aug 2016 19:31:26 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 15582160A6B for ; Tue, 9 Aug 2016 21:31:25 +0200 (CEST) Received: (qmail 35537 invoked by uid 500); 9 Aug 2016 19:31:25 -0000 Mailing-List: contact dev-help@allura.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@allura.apache.org Delivered-To: mailing list dev@allura.apache.org Received: (qmail 35526 invoked by uid 99); 9 Aug 2016 19:31:25 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Aug 2016 19:31:24 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 7970C1863C5 for ; Tue, 9 Aug 2016 19:31:24 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.001 X-Spam-Level: X-Spam-Status: No, score=-0.001 tagged_above=-999 required=6.31 tests=[SPF_PASS=-0.001] autolearn=disabled Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id FcNqsZ-vTBKX for ; Tue, 9 Aug 2016 19:31:22 +0000 (UTC) Received: from mail2.brondsema.net (li236-50.members.linode.com [173.255.226.50]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id C67A95FB18 for ; Tue, 9 Aug 2016 19:31:21 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: brondsem) by mail2.brondsema.net (Postfix) with ESMTPSA id B0FFFE2D4 for ; Tue, 9 Aug 2016 19:31:20 +0000 (UTC) Subject: Re: Updating allura.apache.org website with news To: dev@allura.apache.org References: <3f8dee3f-482b-04ee-9384-9121f18a22e5@brondsema.net> From: Dave Brondsema Message-ID: <2a4c86a8-0a93-d1a7-4dc7-ad02785107b1@brondsema.net> Date: Tue, 9 Aug 2016 15:31:20 -0400 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit archived-at: Tue, 09 Aug 2016 19:31:27 -0000 On 8/9/16 11:59 AM, Rohan Verma wrote: > Hey, > > I'm working on the blog for the changes I made for GSoC atm. I'll share the > draft with you ASAP. Could we use the same for news post as well? > Sure, I think that'd be fine. Any sort of news to show visitors to website what we've been doing with the project. > Also, had installed Allura on the RaspberryPi using the makefile I had made > a long time ago yesterday. Now will try and pitch it to my University. > > Yes, we should start with discussing the next release. Also, what would be > the probable timeline for the release? Pretty much whenever we want :) https://forge-allura.apache.org/p/allura/wiki/ASF%20Release%20Guidelines/ has some notes about it, the script mentioned at the beginning does most of the work. > > BTW, Regarding the release, I was reading the meeting notes at > https://whimsy.apache.org/board/minutes/Allura.html and read somewhere that > we plan to support Apache Project hosting. Maybe we could provide a > neighborhood for Apache projects on forge-allura this time with the > release. What do you think? We did set up a Labs neighborhood for the "Apache Labs" project, but they never did anything with it. (They aren't very active any more anyway) If there was a project interested in it, we could talk with them and get it set up I think. But we'd need a project that wanted to use Allura :D Most projects already have tickets set up in JIRA or Bugzilla, and have their own wikis if they want one, etc. So for most projects it wouldn't be worth moving their stuff. Creating more importers, like pulling tickets from JIRA could help a project if they were interested. Also reaching out to projects in the Apache Incubator as they are getting started is an option. They'll want to move their content into an Apache hosted site anyway. > > On Tue, Aug 9, 2016 at 9:12 PM, Dave Brondsema wrote: > >> Our last news posting was back in April, for our 1.4.0 release. We've had >> a >> variety of changes since then - one set which is noteworthy and would be >> nice to >> talk about is the improved UI for discussions - the layout & button >> updates, as >> well as attachment display. Rohan, since you worked on that, would you be >> interested in writing a post about it? >> >> We should also start thinking about when we want to make our next release. >> >> -- >> Dave Brondsema : dave@brondsema.net >> http://www.brondsema.net : personal >> http://www.splike.com : programming >> <>< >> > > > -- Dave Brondsema : dave@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <><