[Global_chapter_committee] Kyiv Chapter operations issue

Vlad Styran vlad.styran at owasp.org
Mon Mar 26 18:53:27 UTC 2018

Dear Committee Members, 

I am writing this email to raise an issue that, according to the Chapter Handbook, is appropriate to address to this committee. 

Back in early 2017 Ihor Bliumental and I have decided to create a local OWASP Chapter in Kyiv, Ukraine, and started to investigate the ways to do that. There were already a couple of chapters around here, all of them dormant, so there was virtually no one to request an advice from locally. That lead us straight to the Community Manager, Tiffany Long at the time, and after a short period of time, we have met online for an induction call and had a very pleasant and promising conversation.

After clarifying all the details, we have established a chapter. We had a great year of OWASP promotion here: we held 4 meetings, raised the number of attendees to 100, established online streaming and recording of all talks and workshops, inspired a new chapter creation in Dnipro and so on. That is not an exaggeration to state that Kyiv Chapter is the most productive and well-known Application Security initiative in Ukraine to date, which we are proud to be part of. You can see the results of our work at the Chapter’s homepage: https://www.owasp.org/index.php/Kyiv <https://www.owasp.org/index.php/Kyiv>.

However, after completing the work on the last chapter meeting, our reimbursement request have met unprecedented obstacles. After discussing the situation with Dawn Aitken, we have clarified, that the Chapter’s operations during the last year have been largely facilitated by the Community Manager with virtually all the bureaucracy hidden from us. “New” nuances are now brought up, that, if they popped up earlier, would have shaped our operations very differently. However, now it is too late to request funding and apply for budget beforehand: things that we treated as a given through 2017 apparently don’t work without the Community Manager’s help. I am linking the two particular requests that I’m talking about, and I could copy and paste the communication that we are having there here, if you do not have access to the tickets.
https://owasporg.atlassian.net/servicedesk/customer/portal/4/OSD-731 <https://owasporg.atlassian.net/servicedesk/customer/portal/4/OSD-731> 
https://owasporg.atlassian.net/servicedesk/customer/portal/4/OSD-735 <https://owasporg.atlassian.net/servicedesk/customer/portal/4/OSD-735> 

This is the situation how I see it at the moment: we are having an outstanding reimbursement request and we are not having enough money in the budget, because (as we now have learned with Dawn’s help) we had to request that beforehand. Since the old ways are not working anymore, and we apparently are learning the new ways in a hard way, I have to raise this issue before the Global Chapter Committee in hope for its resolution. It is apparent that we have to reassess the information we have based Chapter operations on throughout the first year, and have another induction call or other way to adjust our understanding of OWASP Policies to avoid such situations in the future.

I thank you for your attention to this request and I am looking forward to hearing your decision on it.

Vlad Styran 
OWASP Kyiv Chapter Leader
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/global_chapter_committee/attachments/20180326/e8a3549b/attachment.html>

More information about the Global_chapter_committee mailing list