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

🚨 ⚠️ Looking for a MAINTAINER ⚠️ 🚨 #210

Closed
MoOx opened this issue May 11, 2016 · 14 comments
Closed

🚨 ⚠️ Looking for a MAINTAINER ⚠️ 🚨 #210

MoOx opened this issue May 11, 2016 · 14 comments

Comments

@MoOx
Copy link
Contributor

MoOx commented May 11, 2016

Following #169 (comment)

@marcustisater
Copy link
Member

marcustisater commented May 11, 2016

Are we keeping the repository under org?

@MoOx
Copy link
Contributor Author

MoOx commented May 11, 2016

It's (I think) a really important piece of the fragile PostCSS ecosystem, so I think it should stay here yes.

@wc-matteo
Copy link

Coud you elaborate on fragile?

@MoOx
Copy link
Contributor Author

MoOx commented May 11, 2016

Not in this issue to avoid noise :)

@marcustisater
Copy link
Member

marcustisater commented May 11, 2016

That's not relevant, the repository is not transferring complete ownership. I was just confused about the collab settings, sorry for bringing that up... 😞

@rajasekarm
Copy link

I can help!!

@zgreen
Copy link

zgreen commented Oct 12, 2016

Same.

@MoOx
Copy link
Contributor Author

MoOx commented Oct 24, 2016

If people want to help, 2 solutions:

  • Investigate a little bit on current opened issues, found dups etc
  • Discuss if we should revert to v7 or keep v8

v8 brings some enhancement but since it has been out, the author of the refactor (@TrySound) is completely off the radar and never responded. I don't have much time and can help on v7 since the codebase was still simple.

But I am not alone to decide (I barely use postcss-import in 1 or 2 projects this days)...

Want v7 as a v9?

  • git checkout 7.1.3
  • git checkout -b 9.0.0
  • update CHANGELOG (removed, added back etc)

Most opened issue are related to v8.x.

We will need to explain why this change: mostly because nobody is helping on current version.

If someone want to help on 8.x, start with #168 (and then #169 since there is a breaking test case).

@simonsmith
Copy link
Contributor

Would be a shame to lose things like returning a promise from transform in 8.x.

Was 8 a total rewrite as well as new features? Perhaps a starting point might be to list the features to add back and start over from 7.x as the base. I certainly found the latest version difficult to pick though, including the tests.

@MoOx
Copy link
Contributor Author

MoOx commented Oct 24, 2016

Was 8 a total rewrite as well as new features?

yes

@MoOx
Copy link
Contributor Author

MoOx commented Nov 3, 2016

@RyanZim fixed the long standing bug #168 so he is now the boss here :)
Hope some others will helps too!

@MoOx MoOx closed this as completed Nov 3, 2016
@NekR
Copy link

NekR commented Nov 21, 2016

Reverted to v7 for now.. Hope some people will find time to handle v8.

@RyanZim
Copy link
Collaborator

RyanZim commented Nov 21, 2016

@NekR I am now the maintainer here, trying to fix bugs as fast as I can.

What issue are you encountering?

@vyorkin
Copy link

vyorkin commented Dec 5, 2016

I'll try to provide a minimal example repo demonstrating the issue on the weekends (hope I won't forget and have enough time for this)

UPD: sorry, I don't have much time :(

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

9 participants