falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Srikanth Sundarrajan <srik...@hotmail.com>
Subject RE: How to come up with community driven agenda for Falcon sync up meetings
Date Fri, 27 Feb 2015 07:36:01 GMT
Good suggestion Zulfi. I would recommend that we drop the date from the label. We can look
for open issues with the label for consideration.

Regards
Srikanth Sundarrajan

> Date: Fri, 27 Feb 2015 11:34:17 +0530
> Subject: How to come up with community driven agenda for Falcon sync up meetings
> From: zulfiali@gmail.com
> To: dev@falcon.apache.org
> 
> Hi,
> 
> As of now agenda for Falcon sync up meeting is prepared by picking up items
> from dev mailing list discussions, Falcon JIRAs, and items coming from
> meeting participants.
> 
> But, as not everyone from community join bi-weekly sync up meeting due to
> timezone problem etc, there is a need to come up with a better model to
> increase penetration in community and come up with more vast and richer
> agenda. A model that gives a chance to everyone to include their item in
> agenda even if they are not able to join sync up meeting.
> 
> Proposal is to come up with a unique JIRA label for each sync up. For
> example, label 'falcon-syncup-2015-03-04
> <https://issues.apache.org/jira/browse/FALCON-1038?jql=labels%20%3D%20falcon-syncup-2015-03-04>'
> is for upcoming sync up. Let community tag their JIRAs (bugs, features,
> design challenges, code reviews etc) with proper label. In sync up meeting,
> JIRAs containing this label will be discussed and outcome/views will be
> documented in JIRA itself.
> 
> So, even if you are not able to attend sync up meeting, you can tag your
> JIRA with proper sync up label. This makes sure your JIRA will be opened up
> and discussed in sync up meeting and outcome of discussion will be
> documented in your JIRA.
> 
> Please let me know your suggestions or concerns over this proposal.
> 
> Thanks
> Zulfi
 		 	   		  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message