React-grid-layout: Looking for Maintainers

[STRML]

Devs,

As is likely obvious at this point, I don't have the time to keep up with the large influx of issues on this repository. RGL works great for our use case at BitMEX but is clearly not as customizable as the community wants it to be.

My intention is for RGL to define proper extension points so that a vibrant plugin system may emerge, reducing the burden on this repository to implement custom functionality, such as compactors. For those reasons, I've prepared #346 which defines this in detail.

Are there any volunteers to help get the work started? I would be happy to review PRs but I simply don't have the time to spearhead this.

[JaneCoder]

My team at Duke University used this tool in building a web portal for our researchers and really love how it helped us implement a drag/drop, add/remove, responsive-design grid with 9 mini applications running in it, to meet a very tight deadline.

We are invested in this product and would love to contribute what we can. Our user analysts would also love it if we could implement lateral transforms instead of just vertical.

Most of us were Java, and more recently ruby-on-rails devs, so the React, JavaScript, Webpack world has been new for us. But I would surely love to give this a try. Perhaps some others on our team would too.

[STRML]

That would be really great. I'm happy to help along the way however I can. This kind of development environment can be daunting at first, but it should be enough to get started by simply installing dependencies (npm install) then running the environment locally (npm run dev).

[lukaswelinder]

Our team will be using this library heavily moving forward. I can't make any promises as far as time commitments (we're a small team working on a large project), but I am open to doing what I can to help maintain and improve react-grid-layout.

Specifically, I'd like to contribute to making the library more extensible, but if there are other areas of need (reviewing PR's, investigating issues, etc), let me know. At the very least I can lend a hand in my spare time.

I am fairly familiar with the project's architecture, but let me review the codebase and #346 before circling back with any questions I might have.

It would be good to chat with you about the current state of the project and your approach/style/process (I don't see a contributing or style guide in the repo).

Cheers,
Lukas

[STRML]

Would be happy to help out. See #346 for next steps. As for style, I don't get picky, but it's good to conform to what's in there / in the eslintrc and use Flow types.

I'd be open to using something like prettier so code style isn't even an issue.

As for the format of contributions: a PR explaining the change is plenty. If the changes are big, it's good to open a long-running PR and merge smaller PRs into the large one.

[rileylnapier]

i would be interested in helping. im looking to use this project and really don't want to start forking the repo to add updates.

what can i do? seems PR don't get attention or merged all that much.

is there a v2 branch to help dev? or is it all in theory?

[STRML]

At this point it's all planning, nothing in progress at the moment. I'd really appreciate the help, I just don't have the time day-to-day to address the needs of users ourside our primary use case for this lib.

[rileylnapier]

Sure. I'm in the same boat and have motive.

These include

Nested grids, or overlapping grid components
Stateless. Maybe make a hoc redux-rgl?
Tests and codecov and ci

With that said... I also think narrowing the scope and removing the
responsive rgl in favor for instructions on how to implement responsive
with size-me or component-queries and redux-responsive???

These are what Ive thought about. Since the project has trouble with
finding help, I think narrow the scope might help?

Thoughts?

--

http://symphonycommerce.com/

Riley Napier

[email protected]

symphonycommerce.com

1045 Bryant St.

San Francisco, CA 94103

(651)-216-1961

[STRML]

Narrowing could definitely help. I'd like to to be more of a reusable/composable set of building blocks, such that other repos can develop plugins or techniques in order to do responsive layouts, multiple grids, etc., etc.

To that end, a stateless core is key.

[rileylnapier]

I saw a PR where someone added a stateless option. Or maybe it was a
fork? Any reason why you didn't merge this one? This could get us
started??

How about you give me an issue to solve and I'll do a PR? Then we can go
in that direction? See if we vibe in direction of library?

[STRML]

Not sure about which one you're referring to.

[rileylnapier]

this one:

https://github.com/STRML/react-grid-layout/pull/445

[rileylnapier]

also, this one will be needed for my project: https://github.com/STRML/react-grid-layout/pull/549

[STRML]

Both of those are reasonable and I will re-review.

Riley wrote:
>

also, this one will be needed for my project: #549
https://github.com/STRML/react-grid-layout/pull/549

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/STRML/react-grid-layout/issues/573#issuecomment-313529333,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJFP2DuOglSclAzktL5LVhIehv5eZlUks5sLVbNgaJpZM4NsaOY.

[rileylnapier]

Let me know how I can help! Getting things like these merged is good for library but lack of tests means potential issues.

I think a good CI for this library where you create a PR and it auto launches and app for easy review would be nice :)

[STRML]

Yeah, we definitely need something going forward to test.

Riley wrote:
>

Let me know how I can help! Getting things like these merged is good
for library but lack of tests means potential issues.

I think a good CI for this library where you create a PR and it auto
launches and app for easy review would be nice :)

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/STRML/react-grid-layout/issues/573#issuecomment-313682638,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJFP7A-c8_hdKYqsO9w97ie8LQDn9wuks5sLjRtgaJpZM4NsaOY.

[rileylnapier]

I can help with the PR if you like too? Just let me know anything I can help with and I'll get started :)

[ndelangen]

I'm interested in co-maintaining this.

[tsaiDavid]

Interested in lending a hand here!

[amok]

is there a new maintainer found?

[daynin]

@STRML should we close this issue?