# Contributing to Logstash plugins open source

**URL:** <https://discuss.elastic.co/t/contributing-to-logstash-plugins-open-source/205903>\
**Category:** Logstash\
**Created:** [October 30, 2019, 3:54pm UTC](https://discuss.elastic.co/t/contributing-to-logstash-plugins-open-source/205903 "2019-10-30T15:54:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![AustinTag](https://avatars.discourse-cdn.com/v4/letter/a/977dab/32.png) [@AustinTag](https://discuss.elastic.co/u/AustinTag)\
**Post date:** [October 30, 2019, 3:54pm UTC](https://discuss.elastic.co/t/contributing-to-logstash-plugins-open-source/205903/1 "2019-10-30T15:54:41Z")

</div>

I have had a PR to a logstash owned plugin open for a few weeks:

> <https://github.com/logstash-plugins/logstash-mixin-aws/pull/39>

Is there any way to escalate the PR, or does anyone have tips on getting this looked at by package owners? This change is blocking a change to a plugin that we own. Any help is greatly appreciated!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 27, 2019, 3:54pm UTC](https://discuss.elastic.co/t/contributing-to-logstash-plugins-open-source/205903/2 "2019-11-27T15:54:46Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
