Skip to content
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

Open
mpetuska opened this issue Jun 8, 2021 · 9 comments
Open

Let's join forces #1

mpetuska opened this issue Jun 8, 2021 · 9 comments

Comments

@mpetuska
Copy link

mpetuska commented Jun 8, 2021

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?

@gciatto
Copy link
Owner

gciatto commented Jun 8, 2021

Hello @mpetuska.
What a nice project of yours.

I definitely agree with joining forces, but I wonder which contributions I may bring to your project

@mpetuska
Copy link
Author

mpetuska commented Jun 8, 2021

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. :)

@mpetuska
Copy link
Author

mpetuska commented Jun 9, 2021

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.

@gciatto
Copy link
Owner

gciatto commented Jun 9, 2021

I total agree.
BTW I'm quite busy in this period of my life so I may need a few days/weeks before actually dismissing my library.

I intend to proceed as follows:

  1. try to switch to your plugin in my progects
  2. ensure everything works
  3. possibly, identify missing features I need, in that case I'll add them to your code base
  4. enjoy :)

If you add me as contributor in your project (both my accounts, if you don't mind) I can proceed autonomously.

@mpetuska
Copy link
Author

mpetuska commented Jun 9, 2021

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?

@gciatto
Copy link
Owner

gciatto commented Jun 9, 2021

Just @gciatto

@gciatto
Copy link
Owner

gciatto commented Jun 9, 2021

Sure, I'll add feature before doing anything. That's my usual workflow

@hbanzon
Copy link

hbanzon commented Jul 13, 2021

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. 🙏

@mpetuska
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants