community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hyunsik Choi <>
Subject Re: Seoul Tajo Meetup
Date Sun, 31 Mar 2013 07:47:26 GMT
Hi Ted,

Thank you for your advice. I'm happy to learn about the Apache way from the
seniors including you.  I'll remember a couple of things you mentioned.

Best regards,

On Sun, Mar 31, 2013 at 4:29 PM, Ted Dunning <> wrote:

> Hyunsik,
> Good for you for driving community.
> There will definitely be calls from others who are not local to your meetup
> to be able to hear or see what happens and if possible to interact as well.
>  It is good if you can provide some of that.
> Also, remember that "if it doesn't happen on the mailing list, it doesn't
> happen at Apache".  This means that you should inform people about what is
> happening, but you should avoid making decisions about the project at a
> meetup like this.  Make the decisions collaboratively on the mailing list
> instead.  If there are useful discussions at the user group that seem to
> lead to decisions, have the discussions, but report them to the mailing
> list and, again, make the decisions there.
> This is very similar to the advice about avoiding a single key developer
> for a project.  Make sure you spread the load in order to build a
> survivable community.
> This is going to be much more cumbersome than the decision and interaction
> processes that the Tajo project used before it was the Apache Tajo project,
> but that is part of what comes with being an Apache project.
> On Sun, Mar 31, 2013 at 7:54 AM, Hyunsik Choi <> wrote:
> > Hi all,
> >
> > I'm a PPMC member of Tajo poddling. I will host a local meetup for Tajo
> in
> > Seoul, South Korea. You can see the mailing thread about this meetup from
> >
> >
> > I'm a newbie in ComDev. This is my first meetup for some ASF project. If
> > there are things that I should know about hosting a local meetup, please
> > let me know.
> >
> > Best regards,
> > Hyunsik
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message