# Contributing

**URL:** <https://forums.plex.tv/t/contributing/3511>\
**Category:** Dev/API Corner\
**Tags:** other-dev\
**Created:** [January 29, 2010, 12:48pm UTC](https://forums.plex.tv/t/contributing/3511 "2010-01-29T12:48:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ltucker](https://avatars.discourse-cdn.com/v4/letter/l/da6949/32.png) [@ltucker](https://forums.plex.tv/u/ltucker)\
**Post date:** [January 29, 2010, 12:48pm UTC](https://forums.plex.tv/t/contributing/3511/1 "2010-01-29T12:48:03Z")

</div>

Hi,   
  
  
  
I’ve been playing around with some changes to enable the xbmc karoke code in Plex and I’m wondering what the correct way to contribute is these days. I have some rough work, but I could use some feedback and help understanding the conventions and “right” ways of doing things.  
  
  
  
I found [http://wiki.plexapp.com/index.php/How\_to\_Compile#Contributing](http://wiki.plexapp.com/index.php/How_to_Compile#Contributing) but I’m doubting I can push a branch directly back and the Plex repo appears to be too large to fork with a free account on github ☹ Is posting patches on here the way to go? self-hosting a repo? How do most of you push changes back?  
  
  
  
Also, is elan’s v0.8 github branch the main line of development that we should be targeting changes against?  
  
  
  
Sorry if this is all answered somewhere that I haven’t discovered  
  
  
  
Thanks,

- Luke

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [December 20, 2019, 8:36pm UTC](https://forums.plex.tv/t/contributing/3511/2 "2019-12-20T20:36:01Z")

</div>

Closed on December 20, 2019, 8:36pm UTC

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