I would suggest to be more specific on "relevant events", as that has been a problem in the past. Here are a few examples and how I would see it:
+1 Events that present Apache Apex and are content wise clearly Apex +1 Events that have been PMC approved or are organized with PMC involvement (note that this does not apply to any of the current meetup groups and therefore it is event by event). -1 Events that use Apex in some form but are really sales or product pitches -1 Events of meetup groups that have "Apache Apex" as topic but the event has nothing to do with it. Also see: https://www.apache.org/foundation/marks/events Thanks, Thomas On Wed, Feb 1, 2017 at 4:45 PM, Ashwin Chandra Putta < ashwinchand...@gmail.com> wrote: > +1 for community volunteers to manually maintain the list. > +1 for adding the events to the main page. > > The community as a whole is working toward Apex adoption, we should > collectively publish all relevant events that help toward the common goal. > All Apex events should be treated equally irrespective of the source. > > Regards, > Ashwin. > > On Wed, Feb 1, 2017 at 4:34 PM, Pramod Immaneni <pra...@datatorrent.com> > wrote: > > > How about asking for volunteers in the community to manually maintain the > > list. How about the specific request to add the conference link to the > main > > page? > > > > Thanks > > > > On Wed, Feb 1, 2017 at 10:33 AM, Amol Kekre <a...@datatorrent.com> > wrote: > > > > > I agree with Thomas on not putting meetup events. meetup.com does > "index > > > by > > > Apex", and the search would simply pick up anyone putting Apex in the > > event > > > and at times they are not relevant to Apex. We get too much clutter. So > > the > > > only way out is to manually select the events, and then take them out > > after > > > they are done. This does not scale well. > > > > > > I however do not agree with a hard filter on vendor content. Apex as a > > > community is losing out on a lot of content that is being created by > > > vendor(s), which helps with adoption. In longer run google search will > > > become more relevant to Apex than apex.apache.org. This is something > > that > > > Apex community should discuss and vote on. > > > > > > Thks > > > Amol > > > > > > > > > On Wed, Feb 1, 2017 at 8:55 AM, Thomas Weise <t...@apache.org> wrote: > > > > > > > Since the conference was beforehand discussed with the PMC I think > you > > > > could list it under: > > > > > > > > http://apex.apache.org/community.html#events > > > > > > > > There is already a link to all meetup groups that have "Apache Apex" > as > > > > topic. > > > > > > > > As for other meetup references, IMO direct vendor meetup group > > references > > > > don't belong on the project web site. > > > > > > > > Thomas > > > > > > > > > > > > > > > > On Wed, Feb 1, 2017 at 8:27 AM, Pramod Immaneni < > > pra...@datatorrent.com> > > > > wrote: > > > > > > > > > Hi, > > > > > > > > > > I wanted to discuss a couple of items. First, as many of you are > > > aware, a > > > > > conference specifically for apex, apex big data world 2017, is > coming > > > up > > > > in > > > > > the next couple of months. There is one in Pune India and another > in > > > San > > > > > Jose, USA. I wanted to see if we can put links/information about it > > on > > > a > > > > > section of the website. Here is the information about the event > > > > > > > > > > http://www.apexbigdata.com/ > > > > > > > > > > Other projects like flink, for example, has the details about their > > > > > conference flink forward on their website. > > > > > > > > > > Second, we used to have a section on our website that showed > upcoming > > > > > meetups and conferences. Looks like it has been removed. How about > we > > > > bring > > > > > it back. It can be in a different form, if there were issues with > how > > > we > > > > > did it before. > > > > > > > > > > While we are discussing the second point can we still go ahead and > > put > > > up > > > > > the links to the above conference on the website as soon as > possible > > as > > > > the > > > > > events are very close. > > > > > > > > > > Thanks > > > > > > > > > > > > > > > > > > -- > > Regards, > Ashwin. >
