# New submission process for feature enhancements

**URL:** <https://klipper.discourse.group/t/new-submission-process-for-feature-enhancements/9818>\
**Category:** Developers\
**Created:** [August 6, 2023, 7:37pm UTC](https://klipper.discourse.group/t/new-submission-process-for-feature-enhancements/9818 "2023-08-06T19:37:57Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![nelsongraca](https://avatars.discourse-cdn.com/v4/letter/n/5f9b8f/32.png) [@nelsongraca](https://klipper.discourse.group/u/nelsongraca)\
**Post date:** [March 28, 2024, 2:12pm UTC](https://klipper.discourse.group/t/new-submission-process-for-feature-enhancements/9818/17 "2024-03-28T14:12:47Z")

</div>

> [@Sineos](#):
>
> I think you misunderstood Kevin’s statement.  
> He wants to spend time on developing Klipper’s core functionality and exactly doing such chore work like refactoring etc. See [Klipper development goals for 2024](https://klipper.discourse.group/t/klipper-development-goals-for-2024/12808)

Maybe I misunderstood, but to me the sentence seems pretty clear, more time on new features, not reviewing existing features (cleaning up and refactoring), but I think Kevin is the best person to answer that.

I did see that topic as well, besides the 2 quoted below it all seems like new features to me.

> [@Klipper development goals for 2024](https://klipper.discourse.group/t/klipper-development-goals-for-2024/12808/1):
>
> - Rework of Klipper’s “homing” and “probing” code.
> - Rework the documentation and installation scripts to recommend Moonraker and Klipper specific frontends.

---

_[View the full topic](https://klipper.discourse.group/t/new-submission-process-for-feature-enhancements/9818)._
