Maintainers needed

Question

Maintainers needed

bf4 opened this issue 8 years ago · comments

Benjamin Fleischer commented 8 years ago

Maintainers needed

Monica Giambitto commented 8 years ago

on it :)

Monica Giambitto · Answer 1 · Mon Sep 26 2016 02:48:46 GMT+0800 (China Standard Time)

I hope I can help, what do you have in mind? should I just pick a random issue and try to solve it, do you need help reviewing the prs, writing docs?

Sadiksha · Answer 2 · Mon Sep 26 2016 16:14:09 GMT+0800 (China Standard Time)

Hi,
I am also willing to help you. Like @nirnaeth said, how would it work? Should I take on an issue and work on it?

Thanks.

Jon Keam · Answer 3 · Wed Sep 28 2016 06:17:14 GMT+0800 (China Standard Time)

👍

We've got a few issues outstanding. I'd say grab one and open a PR for it. Thanks for helping!

Benjamin Fleischer · Answer 4 · Wed Sep 28 2016 07:30:44 GMT+0800 (China Standard Time)

@nirnaeth @sadiksha If you make a PR that looks good, I can add you. In the meantime, take a look at the outstanding issues. :)

Aashish Kiran · Answer 5 · Wed Jan 04 2017 00:25:21 GMT+0800 (China Standard Time)

Hi, I would like to help. Let me know about an issue to work.

Andrew Nutter-Upham · Answer 6 · Wed Mar 29 2017 21:52:38 GMT+0800 (China Standard Time)

Hi, I'm interested in helping as well. There is a bunch of good work sitting on master. How can I help get us to v4.13?

Sapna Prajapati · Answer 7 · Wed Jun 14 2017 13:05:34 GMT+0800 (China Standard Time)

Let me know what needs to be done, would like to work upon it.

Peter Boling · Answer 8 · Tue Feb 27 2018 15:41:21 GMT+0800 (China Standard Time)

If you want to help:

Work on open issues:
https://github.com/metricfu/metric_fu/issues

Review Pull Requests:
https://github.com/metricfu/metric_fu/pulls

Benjamin Fleischer · Answer 9 · Tue Feb 27 2018 23:29:42 GMT+0800 (China Standard Time)

Anyone want a release? Or plan what's next?

Andrew Nutter-Upham · Answer 10 · Tue Feb 27 2018 23:43:51 GMT+0800 (China Standard Time)

Hi @bf4 , I'm still interested in the 4.13 release. There are fixes already on master that would be useful to me. Releasing just that would be awesome.

Are there other things you'd like in this release? I looked through the tickets a bit this morning, and many of them are new feature work, or involve the online tooling (travis, launchy) which I'm not sure how to help with. #262 seems like a fixable bug; I could take a stab at that.

Jon Keam · Answer 11 · Wed Feb 28 2018 02:12:53 GMT+0800 (China Standard Time)

Same, I'd love a release :)

Andrew Nutter-Upham · Answer 12 · Wed Feb 28 2018 09:34:49 GMT+0800 (China Standard Time)

Having spent some time in the repo this evening I do have some interest in planning what's next. And what's next in my mind is nothing drastic, mostly just moving things forward to support the newest versions of ruby, and the newest versions of the metric tools.

Tests passed in more recent rubies (2.3.x, 2.4.x, and 2.5.x). I think we could alter the Gemfile to be a bit more permissive about new ruby versions, locking down the gem requirements only for older constraints and being hopeful about the future.

I'm also willing to through the issues and labeling them.

Jon Keam · Answer 13 · Wed Feb 28 2018 09:43:47 GMT+0800 (China Standard Time)

Love the idea!

…

On Tue, Feb 27, 2018 at 8:34 PM Andrew Nutter-Upham < ***@***.***> wrote: Having spent some time in the repo this evening I do have some interest in planning what's next. And what's next in my mind is nothing drastic, mostly just moving things forward to support the newest versions of ruby, and the newest versions of the metric tools. Tests passed in more recent rubies (2.3.x, 2.4.x, and 2.5.x). I think we could alter the Gemfile to be a bit more permissive about new ruby versions, locking down the gem requirements only for older constraints and being hopeful about the future. I'm also willing to through the issues and labeling them. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#280 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAC-2J0aNJjrjxAZtOFALCnl7gJYsSDjks5tZK05gaJpZM4J__t9> .

Benjamin Fleischer · Answer 14 · Thu Mar 01 2018 15:08:04 GMT+0800 (China Standard Time)

the alternative, is to sunset the project and recommend more active ones like pronto ( see https://github.com/metricfu/metric_fu/wiki/Code-Tools though I haven't updated it in a bit, the only new ones I can think of offhand are simplecov alternatives)

If people are really gung ho on working here, and I started because it was fun, so that's enough of a reason, here's what I've been thinking of doing: simplify each piece by building multiple gems in one project like https://github.com/kaminari/kaminari

kaminari https://github.com/kaminari/kaminari/blob/master/kaminari.gemspec
- kaminari-actionview https://github.com/kaminari/kaminari/blob/master/kaminari-actionview/kaminari-actionview.gemspec
- kaminari-activerecord https://github.com/kaminari/kaminari/blob/master/kaminari-activerecord/kaminari-activerecord.gemspec
- kaminari-core https://github.com/kaminari/kaminari/blob/master/kaminari-core/kaminari-core.gemspec

I had put a lot of thought and effort into making metric fu more modular but never finished. It should be pretty easy to break up metric_fu by components and make sure each is independent. This would also help you release changes for e.g. reek more easily

Ultimately, what I would have liked to have done would be to promote a common interface for metrics tools to take in the ASTs generated by either ruby_parser or parser, so that you'd only have to parse once. I spiked some work in Reek to do this once, but it's gone now, and I think there's a PR or something for flay?

Andrew Nutter-Upham · Answer 15 · Fri Mar 02 2018 03:39:38 GMT+0800 (China Standard Time)

Perhaps it is time to sunset this project and more actively recommend the alternatives. I can't say I'm gung ho; spare time is hard to come by. I have loved this project though. The nice wrapper around all these tools and the continuity of this history charts were great. Thanks again for all your work on this.

…

On Thu, Mar 1, 2018 at 2:08 AM Benjamin Fleischer ***@***.***> wrote: the alternative, is to sunset the project and recommend more active ones like pronto ( see https://github.com/metricfu/metric_fu/wiki/Code-Tools though I haven't updated it in a bit, the only new ones I can think of offhand are simplecov alternatives) If people are really gung ho on working here, and I started because it was fun, so that's enough of a reason, here's what I've been thinking of doing: simplify each piece by building multiple gems in one project like https://github.com/kaminari/kaminari - kaminari https://github.com/kaminari/kaminari/blob/master/kaminari.gemspec - kaminari-actionview https://github.com/kaminari/kaminari/blob/master/kaminari-actionview/kaminari-actionview.gemspec - kaminari-activerecord https://github.com/kaminari/kaminari/blob/master/kaminari-activerecord/kaminari-activerecord.gemspec - kaminari-core https://github.com/kaminari/kaminari/blob/master/kaminari-core/kaminari-core.gemspec I had put a lot of thought and effort into making metric fu more modular but never finished. It should be pretty easy to break up metric_fu by components and make sure each is independent. This would also help you release changes for e.g. reek more easily Ultimately, what I would have liked to have done would be to promote a common interface for metrics tools to take in the ASTs generated by either ruby_parser or parser, so that you'd only have to parse once. I spiked some work in Reek to do this once, but it's gone now, and I think there's a PR or something for flay? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#280 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADmmXpW1hv2HRF-AFJv0p4H4Q5f8h-sks5tZ55VgaJpZM4J__t9> .

Vijay Aravamudhan · Answer 16 · Sat Mar 30 2019 12:03:44 GMT+0800 (China Standard Time)

I'm also interested in this project - none of the alternatives seem to match up. What can we do to revive this codebase?

Mark Brooks · Answer 17 · Tue Jun 11 2019 23:45:28 GMT+0800 (China Standard Time)

I'm up to assist. What is needed?

Ernesto Tagwerker · Answer 18 · Fri Sep 13 2019 23:41:00 GMT+0800 (China Standard Time)

Hi @bf4 and all, I'm interested in co-maintaining metric_fu with the rest of the people who showed interest here.

I went ahead and submitted these PRs:

#308 which fixes #307
#306 which fixes #305

I'd love to get some feedback on those. 😃

Benjamin Fleischer · Answer 19 · Mon Sep 16 2019 15:31:00 GMT+0800 (China Standard Time)

sigh, sorry I'm not so present on this. Basically, before I give someone commit, I want to look at their code... and I haven't done much of the latter so I haven't done much of the former. Giving rubygems permissions for releasing new versions is more serious, so that'll take a little more attention on my part before I trust you enough :)

Jacob Beasley · Answer 20 · Tue Mar 31 2020 06:10:31 GMT+0800 (China Standard Time)

Somebody (or a group of people) probably just need to fork this repo at this point.

Benjamin Fleischer · Answer 21 · Tue Mar 31 2020 09:09:27 GMT+0800 (China Standard Time)

@jacobbeasley the issue isn't a need for a fork (though you're welcome to). If you can maintain it and are willing you, I'll give you commit. And if that looks good, I'll give you rubygems ownership.

Ernesto Tagwerker · Answer 22 · Tue Apr 28 2020 20:38:37 GMT+0800 (China Standard Time)

If anyone is interested, I started this fork: https://rubygems.org/gems/fastruby-metric_fu. It fixed #305 which is what was blocking me.

Luis · Answer 23 · Wed Jun 03 2020 11:39:24 GMT+0800 (China Standard Time)

Hello everyone.

metric_fu 4.13.0 was just released. The company I work for OmbuLabs will be sponsoring me and @etagwerker to dedicate some hours a month in the develop of metric_fu.

Thanks to @bf4 and the maintainers of metric_fu in the past for the the work and the trust on us. I hope we can help keep moving the project forward.

Please if you would like to help maintaining metric_fu contact any of @etagwerker or me thanks!