> On Feb 12, 2017, at 2:16 PM, Justin Mclean <jus...@classsoftware.com> wrote: > > Hi, > >> The direction of Apache seems to be moving to a more project-centric >> approach like we’re seeing with ApacheCon. > > Not sure that's case, for instance the other streams include Cloud, Big Data > and IoT which involve multiple projects. The IoT stream is likely to involve > a dozen or so projects. If we can band tonight with other projects for a > steam/summit we're are more likely to attract more speakers, attendees etc. > The ASF has talked about a 50 year plan. It's not expected that the projects > that exist today will exist in 50 years. > >> We could also benefit from conferences/hackathons. > > The best way to do this is to submit talks to conferences (which I know there > has been some success at) - and promote the ApacehCon FlexJS summit :-)
Sure, and I’m going to make an effort to be there. But ApacheCon is once a year (possibly twice?) If we could help arrange smaller get-togethers around the world, it would likely be productive. >> Of course this goes into the question of #3 and #5. AFAIK, paying for >> professional services is currently a major no-no. > > I think that’s set in stone and isn't not possible. See the minutes in that > board report for instance, but it doesn’t stop other companies hiring people > and paying them to do the work. I realize this. I’m just raising the question as to whether things might change. What’s the reason for the current rule? Would the reasons be mitigated if projects raise funds? I’m trying to put out food for discussion. I don’t have an opinion yet on these issues. Harbs
