Picking up on one point On 05/12/2019 05:31, Swapnil M Mane wrote:
> -- To form an ALC, there should be at least 2 committers or 1 ASF member. I don't agree with this. I don't think this is acceptable. The bar for committership is too low to be used as a test for "Understands the Apache Way". To be clear, I'm fine with a low bar for committership. The lower the better. I'm not fine with the same low bar for "Officially representing the ASF." Perhaps mentorship (discussed else-thread) could address this but I'd suggest, based on the existing event policy [1] making this at least 2 PMC members from different projects associated with at least two different organizations. We can always be flexible on a case by case basis. Mark [1] http://www.apache.org/foundation/marks/events.html#selection > -- The ComDev PMC will look into each request and then took > the decision on forming the ALC Chapter. > -- Also as Rich suggests above, we can also assign one mentor to guide ALC. > (Thank you @Issac & @David for sharing your thoughts on this point). > > > ## 2. How we make sure that we are not having people use the Apache name > to promote messages that are not *our* message. > > *Very critical & important point!* > The ALC Indore [2] team was fortunate that we have 4 Committers, 2 PMC > members and the rest members are very active contributors to various > Apache Projects, so we feel the Apache within us. > > But it may/will not be the case with the new ALC Chapter, so here are > some solutions to address this issue. > > -- We worked on preparing some guidelines for ALC Chapter to execute > the event, https://s.apache.org/alc-guidelines > (I need your kind help in reviewing it.) > This could help us in keeping track of actions taken by ALC and > approving the event before executing it. > > @Daniel, this is exactly like you proposed, thoughts travel! :-) > > -- If we will have at least 2 committers of 1 ASF member than the > chances of misuse of our name will be reduced. > > -- We can make a list of the FAQs by the audience, and document it so > that every ALC chapter will have the answer to frequently asked > questions by the audience. > > -- We are documenting various information at > https://s.apache.org/ALC-Resources , this will also give the idea to > ALC Chapter what types of events and content they can present to the > audience. > > ## 3. Rule and regulation for ALC Chapter > > Although we should not have a hard list of rules and regulation but we > should have some rules, that will help us in managing the ALC > initiative because with time we will grow like currently there is 900+ > Google Developer Group [3] and 120+ Facebook Developer Circle [4] > present. > So, to manage and scale the ALC initiative, we should have some > rules/guidelines we prepared. Here are these rules/guidelines. > > -- There will be a single ALC chapter per town/city. > > -- The ALC members should follow the Apache code of conduct, > https://www.apache.org/foundation/policies/conduct.html > > -- It’s strictly prohibited to use ALC Chapter for profit or promoting > any company or personal agenda. > > -- If any ALC Chapter is inactive for 3 months, it will be dissolved > after communication with members of that ALC chapter because we are > having strictly one ALC chapter in a town/city. > > -- The ALC Chapter shares the status report (e.g. ALC Indore reports - > https://s.apache.org/alc-indore-reports) to ComDev in every three > months. > The report includes details on the activities performed by ALC Chapter > and it's impact. > Here is the index page for reports from each ALC > https://s.apache.org/alc-reports > And the report prepared by ALC Indore for their > August to October 2019 activities is > https://s.apache.org/alc-indore-report-aug-oct-2019 > > -- Each Chapter should follow ALC Guideline (as mentioned, need your > help in reviewing it) https://s.apache.org/alc-guidelines to execute > any event. > > -- Also as @Shane mentioned, we can also use some of the concepts and > rationale mentioned at > https://www.apache.org/foundation/marks/events > (Below is the statement from our Event Branding Policy we have already > included as suggested by from Joan previously) > ======= > The use of Apache marks in any events run by third parties must be > approved by VP, Brand Management or the VP of the relevant Apache > project > ======= > Shane, this point was raised by Joan Touzet in September > https://s.apache.org/95wu0 , so we had a discussion on this and > followed this process and included it in > https://s.apache.org/alc-guidelines > As you said, if needed we can add more points from > https://www.apache.org/foundation/marks/events > > > I feel very proud to be the part of the Apache family and in the past 6 > years every day, the ASF people inspired me to do better. And the > great things we are doing together surprise me regularly. > Thank you much for your love and support! > > Please feel free to share your comments and thoughts. > > [1] https://s.apache.org/alc > [2] https://s.apache.org/alc-indore > [3] https://developers.google.com/programs/community/gdg/ > [4] https://developers.facebook.com/developercircles/ > > > Best regards, > Swapnil M Mane, > www.apache.org > > > On Thu, Dec 5, 2019 at 4:53 AM David Nalley <da...@gnsa.us> wrote: >> >> On Wed, Dec 4, 2019 at 3:15 PM Rich Bowen <rbo...@rcbowen.com> wrote: >>> >>> I've made two posts on this list in the past couple of days regarding >>> the rising ACL effort and my concerns about it. >>> >>> I *desperately* want this kind of grass-roots enthusiast community >>> effort. I do NOT want to kill it. But I've learned from Fedora user >>> groups that allowing any random stranger to start up a group, using our >>> Trademarks, to promote whatever message comes into their head, is >>> *going* to bite us in the butt, sooner rather than later. >>> >> >> I haven't been involved with Fedora in a long while, but there were in >> early days a real struggle for how to control messaging and who could >> speak for Fedora, and how events could be handled, etc. Did the >> community own it or did Red Hat? >> >> Fedora had (at least back then) a relatively scalable and >> self-policing group called the "Ambassadors" that leveraged messaging >> and collateral provided by the Fedora Marketing Project to talk about >> Fedora in a unified fashion. There were requirements about prior >> activity and some barrier to entry to become an Ambassador, but it >> belonging to that group seems somewhat analogous to membership at the >> ASF (you had to have been involved in some other aspect of Fedora, you >> had to demonstrate some knowledge of Fedora's principles, etc) >> >> So perhaps being 'sponsored' or 'championed' by a member is the >> threshold for running an event. Any problems that arise can be >> policed from there because we know there's a member we can talk to. >> >> YMMV - I have no idea the current state of the Ambassador program at >> Fedora and whether it's considered a success of failure. >> >> --David >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
