search

bdrister / AquaticPrime

Mac software licensing code using cryptographically signed license files
http://github.com/bdrister/AquaticPrime
307 stars 91 forks source link

AquaticPrime License Tool Updates #39

Closed alfwatt closed 4 months ago

alfwatt commented 10 years ago

Various updates to get the license tool working.

bdrister commented 9 years ago

I'm terribly sorry that I haven't responded to this for so long. Somehow checking the address on this account slipped through the cracks for a long time so I never received the notification.

Given that this pull request is somewhat stale at this point, are there any other updates that need to be made to bring this up-to-date? Perhaps it would make sense to work with the other devs with outstanding pull requests to ensure they all work together and can be merged in all at once. I've made the same suggestion on the other requests, so they should be expecting some contact.

Again, sorry about the unresponsiveness.

alfwatt commented 9 years ago

No problem, only an issue if you really want to the be maintainer of the project moving forward, I take it Lucas isn't handling it all all.

bdrister commented 9 years ago

Both Lucas and I have subsequently moved on to other things. If another branch has taken over as being a reliable authoritative branch, I'm more than happy to defer to that. Otherwise I figure I should still try and keep my branch somewhat up to date since there's a lot of references to it around.

alfwatt commented 9 years ago

Besides these changes I have a bunch of updates to the php adapters for various payment services. Was going to add MAS receipt validation at some point.

johndpope commented 9 years ago

bdrister - why not consider adding some core people as contributors to the project? depending on finding a relibable fork on github is painful. It's so hidden and sunset that the majority of users are going to keep banging their heads against the master branch.

bdrister commented 9 years ago

Finding a reliable fork is effectively the same problem as finding a reliable contributor, so I'm not sure that's going to really change the problem. If somebody else who's done a good bit of work on this wants to take over as the primary maintainer, I'd be delighted, but nobody's offered, so debating the mechanics of that is a bit of a moot point.