How can we help Bouncer get to 1.0?

marcusmoore commented 8 years ago

Hello!

Do you have a checklist of features or ideas that need to be hashed out before you're comfortable tagging a 1.0 release that anyone might be able to help with?

I want to start contributing to OSS and Bouncer might be a good place to start.

tormjens commented 4 years ago

Not to be a nag or anything; but is there any news on a 1.0? I've been using Bouncer on the regular for the last 2 years and haven't experienced much issues at all. I only get reminded that Bouncer is "unreleased" when I install one of my packages that depend on Bouncer in a new project. I always have to change minimum-stability in my composer.json for that.

Is there a plan on how to get to 1.0? Happy to help get there as well.

alec-joy commented 4 years ago

@JosephSilber I'm also curious if there's anything we can do to help get this to what you would consider a 1.0 release, I have a week off in the near future that I'd be willing to dedicate to getting this done as well as some scheduled FOSS time I give myself every week. Bouncer is exactly the package I'm looking for but unfortunately my org has minimum stability requirements so I can't use Bouncer for that project without a 1.0, even if the current RC is stable enough for production use (which it seems to be).

If there are specific open issues you'd like the community to tackle or if it's a matter of getting a documentation site together or something like that I'd be willing to dive in. This is still your project though, not trying to push you into handing it over or anything, just want to help if I can.

JosephSilber commented 4 years ago

There are two features currently in limbo (half implemented):

Per-entity roles
Model ability constraints

Both of these are part of the DB structure (in the migrations), but are only partially implemented.

I don't feel like it makes sense to release a 1.0 with the code in this state.

ajoy39 commented 3 years ago

There are two features currently in limbo (half implemented):
1. Per-entity roles

2. Model ability constraints
Both of these are part of the DB structure (in the migrations), but are only partially implemented.

I don't feel like it makes sense to release a 1.0 with the code in this state.

Hi, I am also @alec-joy but that was a work account for a company I no longer work for

In my new position I have a lot more leeway to work on FOSS stuff, especially if we use it in our application. Some time in early January I'll be given 6 weeks to essentially integrate this package into our application. During that time I would like to help get to 1.0. You mentioned Per-entity roles and model ability constraints are the two things left, can you go into a bit more detail on whats left and what state their in? I don't want to create a ton of extra work for you to get this all documented but if I can get some info on those two items I can get approval to spend a not-insignificant amount of time working on Bouncer during that 6 week period.

JosephSilber commented 3 years ago

@ajoy39 thanks for offering your help :+1:

I'll try to find some time to write up what those features are supposed to do, how they're supposed to work, and which parts are already done.

No promises, but I'll try.

realmxsandr commented 3 years ago

@JosephSilber Hi! I would like to get some update on this topic.

Our company using this great package for our purposes and it fits perfect, but unfortunately we have minimum stability requirements too and having some difficulties at this point, just as @alec-joy said before.

We are ready to offer some free hands to help this package get its first stable release.

Please, If there is anything I can do, I would like to help get things done.

Thank you!

Btw, we are using rc10 in production environment at this moment and it looks to be fine.