Expand our Open Source Project Rubberduck VBA with UX or UI [on hold]

We wished to ask the UX stack exchange group for guidance into how to go about in starting and understanding how user experience for the Open-Source Rubberduck VBA code could be "stepped up" from its current baseline experience toward helping our user's experience further.

Our project has evolved from two coders since October 2014 of their first GitHub issue ticket to as reported by Open Hub Project as currently 32 active contributors which any contributors are welcome.

The add-in we provide helps coders to further refine and improve their coding experience using modern programming practices for code quality with code inspections similarly as talking with a plastic rubber duck to solve problems.

Our audience is a number of coders who had downloaded our current release (as I understand at the moment are ranged from various roles like Business Analyst to Engineers) using our add-in for their host of Microsoft Excel/Access/Word and other associated software products that use Visual Basic for Applications code needs.

We use the provided GitHub platform which converts user feedback from Issue (Bugs) into Pull requests to implement features or fixes where our design can be looked closely or refactor (re-written) into another way to reduce technical debt (least expensive means or way of making computing changes). Once certain features are stable enough, we pull over from development into a fully stable release. We do offer development stages to allow users to try out and verify to close some issues. We also welcome users and converse between developers on the Stack Exchange chat to discuss/support coding practices and design implementations.

On Social Media aspect, our codebase owner Mathieu Guindon has shared some insights using his blog and twitter. Currently we are looking into our brand so we asked the Graphic Design on Stack Exchange their thoughts.

Any suggestions welcome.

Thanks.