Hi John, I can confidently report that it is list first with Edgent. I work in the same office with many of the committers and conversations seem limited to "Hey, can you please look at my email to the list?", who can go to Apachecon, etc. There were a few very early, "Ya, best to ask on the list about that" moments, but they totally got it in no time and I haven't heard myself or Dan say that for a very long time.
I think pre diversity graduation might help with adoption as some folks don't really want to adopt an incubating solution. I certainly feel that the current committers and ppmc members would continue to act independently of single employer influence [1] , but realistically, it might be a risk to the longevity of the project if we can't achieve diversity post graduation. So, yes, it might make it easier to swim if we take the incubation life vest off, but... Diversity was a struggle years ago when I first started with Derby. Today, with Derby, it is those committers that were not from the original code donor that keep the project going. Whether before or after graduation, diversity is a critical health component. Best, Katherine [1] http://theapacheway.com/diversity/ Sent from my iPhone > On May 16, 2017, at 7:16 PM, John D. Ament <[email protected]> wrote: > > Will, > > (moving general@incubator to BCC) > > I'll point out that the expectations of a podling are skewed based on how > that podling is operating. If we see a high level of on list activity, > making it clear that its list first, it may make sense to graduate a less > diverse podling, simply because its clear that the podling understands the > expectations and will be clear about their decision making. We can also > bank on mentors sticking around the PMC to keep them moving. > > FWIW, my background is in messaging so I suspect from a technical > standpoint I get some of the integrations you're working on. My eyes > always light up when I see MQTT or AMQP on a slide. > > The easiest way to get more users is to leech on to existing projects that > seem to be going well. Yes, I know "leech on" can be seen as negative, but > it helps draw some notion of what you're really after. For instance, we > saw an IoT Operating System right before Edgent, is there an opportunity to > bake in a Mynewt distribution that includes Edgent, produced by the Edgent > community? And if such a thing did exist, would existing Mynewt users > potentially use Edgent for their analytics? You also listed a limitation > in the Edgent platform, focused on Java. Does it make sense to produce a > Swift based client? > > John > >> On Tue, May 16, 2017 at 9:25 PM William Marshall <[email protected]> wrote: >> >> Hi John, I'm glad you enjoyed the presentation, ApacheCon was a great >> forum. >> >> All mentors are currently active, and right now the way in which Edgent >> most needs mentorship is in its outreach to developers. From a technical >> perspective, I think Edgent is mature for its age and number of committers, >> but to date we've only seen a few users actually adopt it in an >> application. This is strange, given the amount of initial interest, but I >> sense this is in part due the the name change from Quarks to Edgent. >> >> Since Kathey is likely stepping down soon, you would be the 4th mentor (not >> the there's any hard limit, as far as I'm aware). Given your experience >> with podlings I think you would fit the role well. Any thoughts on the >> outreach problem? >> >> -Will >> >> On Tue, May 16, 2017 at 3:21 PM, Katherine Marsden <[email protected]> >> wrote: >> >>>> On 5/16/17 2:17 PM, John D. Ament wrote: >>>> >>>> William, >>>> >>>> Great presentation this afternoon. >>>> >>>> I'd like offer to help you guys as a mentor, you do currently have 4 >>>> mentors. Are all 4 mentors active in the project? >>>> >>>> >>> Hi John, I am not involved in the project from a technical perspective, >>> except I helped initially setting up the website and have done some >> release >>> testing and filed a few bugs. >>> >>> As mentor I have been mostly just offering solicited and unsolicited >>> advice and maintaining the project status page (hmmm haven't looked at >> that >>> in a while, better check), posting the maturity model to the wiki and >>> reviewing and signing off on reports, etc. >>> >>> I would be happy to commit to continuing with this minimal role as >>> mentor or step aside if that makes more sense given the number of >> mentors >>> if you will take over maintaining the project status page. I think the >>> project needs your help a lot more than mine right now as the folks >> working >>> on the project seem to totally have a handle on everything on which I >> could >>> provide guidance. If anyone on the project has questions that I could >>> answer, I still certainly would be available to answer. One ppmc member >>> requested I stay on for my "timely advice" [1] but I certainly am never >> shy >>> about giving advice no matter my formal role. I am sure she wouldn't >> mind >>> if I stepped down in my formal mentor role if I stuck around on the dev >>> list which I plan to. >>> >>> Best >>> >>> Kathey >>> >>> >>> [1] https://mail-search.apache.org/members/private-arch/edgent- >>> private/201704.mbox/%[email protected]%3E >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>
