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

The future of this project #112

Open
vitusortner opened this issue Nov 15, 2022 · 13 comments
Open

The future of this project #112

vitusortner opened this issue Nov 15, 2022 · 13 comments

Comments

@vitusortner
Copy link

Given the current situation at Twitter, can we expect this library to still be maintained?

@svenjacobs
Copy link

Since both @mrmans0n and @chrisbanes left Twitter (sorry guys 😢), the future doesn't look so bright. At least not under Twitter's scope. Maybe this project can find a new home at Google, for instance?

@mrmans0n
Copy link
Contributor

mrmans0n commented Nov 20, 2022

I'm thinking about forking it, but I need to look into the license and all that.

@chrisbanes
Copy link
Contributor

You can fork easily with Apache 2.0: https://tldrlegal.com/license/apache-license-2.0-%28apache-2.0%29

You need to make sure you keep any existing license and copyright (headers), but you can add your own headers on top for modifications.

@kenyee
Copy link
Contributor

kenyee commented Nov 20, 2022 via email

@ege-ah
Copy link

ege-ah commented Jan 26, 2023

+1 please fork @mrmans0n or assign it to Elon Musk idk

@mrmans0n
Copy link
Contributor

I started my fork in https://github.com/mrmans0n/compose-rules

First order of business was supporting ktlint 0.48.x and kotlin 1.8.x. I submitted them as a PR in this repo too, to ease with transition, but I doubt anybody is looking on the Twitter side (all the admins of this repo don't work at the company any longer, and our permissions were removed).

I will work towards a maven central publication for my fork as soon as possible.

@kenyee
Copy link
Contributor

kenyee commented Jan 30, 2023

LOL...they took away all of our approval permissions? 😹 🤦

@kenyee
Copy link
Contributor

kenyee commented Jan 30, 2023

Yo Elon...not cool

@digitalbuddha
Copy link
Contributor

I'd like to suggest moving the project to the mobile native foundation rather than your personal. This would allow you to move on someday with minimal changes

@mrmans0n
Copy link
Contributor

mrmans0n commented Jan 30, 2023

It was much easier using my own, tbh (sonatype coordinates are already approved, plus setup is done). What's a compelling reason to use an org? (asking from my complete ignorance of what the mobile native foundation stands for, how it operates, etc 😅 )

LOL...they took away all of our approval permissions? 😹 🤦

Mine were removed at least, 100%. Can't do anything in this repo anymore. It's fair but still hurts a little given how much work I've put into this 🤣

@digitalbuddha
Copy link
Contributor

It is under the Linux foundation. Mostly I thought it would help to decouple the project from any one person. I successfully moved a project there rather than personal when leaving Dropbox. It was a fairly simple process of signing one doc and telling them which maven coordinates I wanted.

I see this similar to a project moving to apache or some other foundation. No big advantage just planting seeds for a healthy future oss ecosystem

@mrmans0n
Copy link
Contributor

mrmans0n commented Feb 1, 2023

Interesting, I will look into that then, GitHub can help me move the project when the time comes and it adds a redirection from the old URL to the new URL, so no biggie.

I was mostly interested from the technical standpoint what the maven coordinates would be for the dependency, so I moved the fork to use a domain I have permissions to publish on (which won't likely need to change) and I already got a version in maven central.

@digitalbuddha
Copy link
Contributor

It would be something like org.mobilenativefoundation.composerules

Happy to discuss further or get ball rolling if there is interest.

amal added a commit to fluxo-kt/fluxo that referenced this issue Feb 23, 2023
…ed fork (mrmans0n/compose-rules)

See for details:
twitter/compose-rules#112 (comment)

Signed-off-by: Artyom Shendrik <[email protected]>
amal added a commit to fluxo-kt/fluxo that referenced this issue Feb 23, 2023
…ed fork (mrmans0n/compose-rules)

See for details:
twitter/compose-rules#112 (comment)

Signed-off-by: Artyom Shendrik <[email protected]>
amal added a commit to fluxo-kt/fluxo-kmp-conf that referenced this issue Oct 15, 2023
…ed fork (mrmans0n/compose-rules)

See for details:
twitter/compose-rules#112 (comment)

Signed-off-by: Artyom Shendrik <[email protected]>
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

7 participants