Stagnating bundles, contributions, new participants

[merk]

Long text incoming, sorry :(

There is a lot of inactivity in FOS

There is a general feeling around the place that we're inactive, at least in a few of our bundles and to me that seems true enough. I'd like to see something done about it.

Active Maintainers

We've got quite a list of FOS contributors, but are we all active? Do we keep eyes on bundles? I want to build a list of bundles that each contributor keeps an eye on, and what level of contributions they'd be happy to admit. This will help us gauge the health of each bundle to make more decisions.

For example, I'm actively looking after FOSElasticaBundle and want to step up and clean up FOSUserBundle and clear issues and PRs.

I'd also like to see us adopt a way of letting others step up and volunteer to help out, if thats triaging tickets, cleaning up PRs to be mergable. The easiest way would be to 'copy' what Symfony have done where we have a list of primary maintainers of each bundle who can +1 something. This means we can even have primary maintainers who can just act in an more advisory role, letting other volunteers spend their time helping out.

Vision or roadmaps for active bundles

Can we please build a roadmap or vision paragraph about each bundle that we're going to actively maintain, which will help guide any current maintainers know if they're going to be able to critique a PR or reject it. We dont want to waste users time by commenting on issues with a PR only to find out the primary maintainer doesnt want that feature.

Bundles

FOSAdvancedEncoderBundle

• Stof

This bundle appears to be unnecessary as of Symfony 2.5. It can be maintained as a legacy bundle and probably needs very little attention.

FOSCommentBundle

• Unmaintained

I'm no longer using this bundle and have no time to maintain development or support for it. We either need to find a maintainer for it, or mark it unmaintained. I'd be happy to mentor someone with advice.

FOSElasticaBundle

• merk

I've been working on a roadmap for this bundle and while more help is always appreciated I believe this bundle to be okay at the moment.

FOSFacebookBundle

• Unmaintained

No longer maintained, we recommend using HWIOAuthBundle

FOSHttpCacheBundle

• dbu
• ddeboer

Nice and shiny, no issues here?

FOSJsRoutingBundle

• willdurand

Actively maintained.

FOSMessageBundle

• Unmaintained

I tried to take some initiative with this bundle, but lack of tests and time mothballed that attempt. Needs a maintainer and I'd be happy to assist with advice where I can.

FOSOAuthServerBundle

• alanbem

This one looks like it doesnt have a lead maintainer anymore. I've got an active project with this bundle and will make bug fixes when necessary.

FOSRestBundle

• lsmith
• willdurand

Actively maintained

FOSTwitterBundle

• Unmaintained

No longer maintained, we recommend using HWIOAuthBundle

FOSUserBundle

• Stof
• merk

I think the number of unclosed issues and PRs in this bundle is a big deal. FOSUserBundle is the first of our repositories most users are exposed to and outwardly it looks stagnated.

I've avoided picking up the torch because I'm not actually sure about the vision for this bundle, and dont want to bother Stof every time I have a question. Is there a plan for 2.0 stable? I've had jrobeson ask how he can contribute and I'm happy to enable contributions but without knowledge of where FOSUB needs to go it ends up being very difficult.

[merk]

Could we please have a roll call of all FOS contributors about their status, which bundles they use, watch and are willing to assist in maintaining?

There are obviously no strong commitments here but its about time we dealt with the inactivity and set up a structure that lets new people step up and help out!

Appologies for the pings, but I feel this is necessary to kick start this discussion and get a resolution. If you no longer have time or interest in helping out please speak up too.

@alanbem @arnaud-lb @asm89 @avalanche123 @cystbear @dbu @ddeboer @diegoholiveira @dstendardi @everzet @Herzult @jmikola @Kertz @khepin @kriswallsmith @leahaense @lsmith77 @richardmiller @schmittjoh @stof @tecbot @willdurand @zocimek

[stof]

FOSAdvancedEncoderBundle is maintained by me. But it is indeed in legacy mode as the feature is now available in core, and it has not required change since a long time.

FOSTwitterBundle should recommend HWIOAuthBundle as well.

for FOSRestBundle, I'm not really an active maintainer. I'm providing code review, like for most other bundles, but I don't work on it.

FOr FOSUserBundle, I have a bunch of things in mind, but I haven't spent time on it since a long time (I haven't enough time...). I will try to create issues for these things to allow other people to contribute. Next moday is a holyday in Frnce, so it might give me some time to work on it

[alanbem]

FOSOAuthServerBundle - lately i've been quite busy so my activity was
stripped to bare minimum (answering questions, closing issues, etc), but as
of this month I started working for very open-source friendly employer, so
it will change.

Simultaneously I've been working on some mayor rewrite of
FriendsOfSymfony/oauth2-php as its very hard to work with... :/

2014-07-07 14:06 GMT+02:00 Christophe Coevoet notifications@github.com:

FOSAdvancedEncoderBundle is maintained by me. But it is indeed in legacy
mode as the feature is now available in core, and it has not required
change since a long time.

FOSTwitterBundle should recommend HWIOAuthBundle as well.

for FOSRestBundle, I'm not really an active maintainer. I'm providing code
review, like for most other bundles, but I don't work on it.

FOr FOSUserBundle, I have a bunch of things in mind, but I haven't spent
time on it since a long time (I haven't enough time...). I will try to
create issues for these things to allow other people to contribute. Next
moday is a holyday in Frnce, so it might give me some time to work on it

—
Reply to this email directly or view it on GitHub
#46 (comment)
.

Pozdrawiam,
Alan Bem
http://www.recovery.pl/

[willdurand]

Hi @merk, @alanbem is lead on the FOSOAuthServerBundle, and I am following the FOSRestBundle development.

[diegoholiveira]

As a member of FOS, i'm in charge of FOSFacebookBundle, since we decide to deprecate it I'm no longer involved in any project, but I love to contribute more with FOS and the Symfony ecosystem.

If anyone can help me to involve in some project, I can help with code or documentation.

:)

[merk]

So I think the best approach here is to list maintainers who are actively interested in steering projects, and make the assumption that maintainers who keep watch for code reviews or easy merges dont need to be listed.

@stof If you could, I'll step up and help go through the FOSUB issues/PRs and clean it all up (with the help of jrobeson). With a bit of insight into what you want to achieve we can plan out a roadmap.

@alanbem, @willdurand - thanks

@diegoholiveira You're welcome to help out on any FOS bundle, there are always issues that need triaging, and if you're up for it there is a lot of work to be done. Maybe ask maintainers to see which bits need the most attention and love?

I'd really like to see some talk about FOSRestBundle being split into pieces, it seems like a swiss army knife to me at the moment... (there may already be an issue or talk about it, I havent been following development).

[merk]

I have added a note to FOSCommentBundle and FOSMessageBundle that they're currently unmaintained and seeking a maintainer, and a note to FOSTwitterBundle that HWIOAuthBundle is preferred.

[dbu]

thanks for the initiative!

yes, i maintain HttpCache and HttpCachebundle actively together with @ddeboer and we hope to release a stable version soonish. i have occasionally worked with the user bundle and elasticabundle, but don't have the resources to promise anything there.

[zocimek]

I can maintain FOSMessage bundle but currently since several months I have very limited time to do it so it would be very helpful If someone could help me with selecting issues. Currently I'm about to write some tests.

[dbu]

regarding the roadmap discussion: what about using milestones with descriptions and just link them from the README? i think this has a chance of less being forgotten to be updated than in the readme.

[jmikola]

@merk: As part of this, should we take inventory of those listed in the FOS project teams and clean up the membership lists?

After removing myself from FOSElasticaBundle, I'm only a member of the general FOS team. I'd defer to the more active folks to decide if emeritus members should be kept around there; however, I don't think inactive contributors should be on project teams, as it makes it difficult to determine which bundles are maintained at a glance.

[merk]

@zocimek right now, the biggest dilemma is open untriaged tickets, even if regular development isnt occuring.

@jmikola I dont think theres any need to prune the primary list of contributors, people come and go as things change in real life. As for team lists it does make sense to modify them - but are they visible to users to see who they can talk to? I'd like to approach it as a public list of those who are actively maintaining bundles.

I also think people are using the team lists to get notifications for certain projects?