-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Let's join forces #1
Comments
Hello @mpetuska. I definitely agree with joining forces, but I wonder which contributions I may bring to your project |
Nothing in particular at the moment, but mainly just looking after it with me to keep it in sync with kotlin releases as well as occasionally adding new features as they unlock in kotlin plugin. The idea is basically both of us spending efforts on a single tool (if any) rather than wasting that on duplicated effort. :) |
I can invite you as contributor to the repo in case you have some ideas in the future. What I'm trying to avoid here is fragmenting the community by having two separate plugins out there and then eventually ending up with different features on each - leaving the end user with having to make the choice between the two. Much better to just have a single plugin that has ALL the features. |
I total agree. I intend to proceed as follows:
If you add me as contributor in your project (both my accounts, if you don't mind) I can proceed autonomously. |
Sounds like a plan. No rush! If you find any missing features, but are too busy to implement them, feel free to raise an issue instead. I might be able to give it a go myself. I've added gciatto-unibo to contributors, what's your second account? |
Just @gciatto |
Sure, I'll add feature before doing anything. That's my usual workflow |
Hi! My team is recently adopting KMP and needs to export an npm module for our webapp. As I see you're both joining forces, which project should I consume to begin with? BTW, I'm excited that you both are joining forces. 🙏 |
Both should fulfil your needs for now (this project being a bit more lightweight), but looks like we'll be able to converge into npm-publish going forwards. |
Hey, I came across this recently ant looks like it shares the same mission as my own npm-publish plugin.
Thought I'd reach out to see if you'd be interested in joining forces on npm-publish (as it's a bit richer feature-wise at the moment) rather than maintaining two separate plugins in the kotlin ecosystem?
The text was updated successfully, but these errors were encountered: