Mailing-List: contact dev-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
Subject: Re: Review and Tidy Up of Existing ComDev Jira Issues
To: dev@community.apache.org
References: <pony-31e1cbf2b23a01ea035ee3323fe2ab95950c8284-98cd6e312373913df8a094c3a5314cfc4b9588fc@dev.community.apache.org>
From: Shane Curcuru <asf@shanecurcuru.org>
Message-ID: <7fdc532d-97fd-cb9a-1d1c-3a43742705d3@shanecurcuru.org>
Date: Sun, 5 Nov 2017 10:34:06 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0)
 Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <pony-31e1cbf2b23a01ea035ee3323fe2ab95950c8284-98cd6e312373913df8a094c3a5314cfc4b9588fc@dev.community.apache.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
archived-at: Sun, 05 Nov 2017 15:33:38 -0000

Question: What to do about past GSOC issues that have had some work done
on them?  There are a few GSOC issues for *other* projects in the COMDEV
JIRA - from the project perspective, they're no longer valid, but I'd
hate to blindly close an issue if some student is still hoping for
feedback or something.

Close them all, transfer to other projects, or...?

Sharan Foga wrote on 11/5/17 8:20 AM:
> Hi All
> 
> I think it would be good for us to start reviewing and tidying up the list of open issues we have in our ComDev Jira to see if they are still valid, need updating or simply need to be closed.
> 
> Having visible tasks that we need to focus on or are currently working on in our Jira also opens up opportunities for others to help out (as witnessed with our brochure translation work).
> 
> So please feel free to take a look, comment or work on them.

-- 

- Shane
  https://www.apache.org/foundation/marks/resources

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org