Skip to content

How to maintain this repository? #526

Open
@ddeboer

Description

@ddeboer
I'm torn, I'm not sure we actually want more things maintained here.

This repo is a collection of partially broken things, the promise for users is fairly low unfortunately. (because it's impossible to maintain all these extensions)

I'm wondering if we should just encourage people to have repos for the extensions they are actually maintaining instead of giving a false promise to users.

Anyway, that's a sidebar…

Originally posted by @mnapoli in #515 (comment)

I'm wondering if we should just encourage people to have repos for the extensions they are actually maintaining instead of giving a false promise to users.

Makes sense. Should the Bref docs then be updated to describe how to build your own extension layer?

Originally posted by @ddeboer in #515 (comment)

This repo is a collection of partially broken things, the promise for users is fairly low unfortunately. (because it's impossible to maintain all these extensions)

True, but most extensions have some basic test to validate if it’s been installed correctly.

Overall, this repository seems to have two problems:

  1. its maintenance burden, including merging PRs for each new PHP/extension version and publishing releases
  2. its unreliability, as stated by @mnapoli.

Would it make sense to phase out this repository? (Even though I’m using some layers from it.) If so, it would be nice if the Bref docs could describe to users how to build (and maintain) their own layers.

Or perhaps there’s some other solution?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions