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 17:21:19 GMT
> If there is a way I can contribute in this regards, I would do.

That would be very very welcome. If there is a specific area that requires attention in terms
of documentation, please do file and JIRA and provide the documentation through a patch. Some
notes on how to go about this can be found in https://cwiki.apache.org/confluence/display/FALCON/How+To+Contribute.

Srikanth Sundarrajan

> From: sivatumma@gmail.com
> Date: Fri, 27 Feb 2015 20:56:46 +0530
> Subject: Re: How to come up with community driven agenda for Falcon sync up meetings
> To: dev@falcon.apache.org
> Zulfi,
> One funny point why I did not join the first bi-weekly sync-up after the
> calendar schedule been sent was that the mail went to my spam. Then I was
> in need of an overview of Falcon to recommend in my workplace. This
> probably could have been the case with some other folks too.
> I am a one year noob to Big-Data. Though I have coded in plain Hadoop, it
> would be better for people like me to have some documentation. The
> challenge here is we are not sure of what we can demand for, in an Open
> Source project like this.
> You know, We were having a clear need of this kind of software, but We have
> opted out completely by choosing loggly as a choice just because lack of
> documentation for Falcon in a self intuitive way (We use AWS for
> infrastructure needs). In other words, Falcon now requires full
> documentation as it is no more an incubator. If there is a way I can
> contribute in this regards, I would do.
> -Siva P Thumma
> On Fri, Feb 27, 2015 at 11:34 AM, Zulfiqar Ali <zulfiali@gmail.com> wrote:
> > 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
> >
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message