Posted by ckknight Jun 17, 2008 at 20:36 UTC
Previously only files required manual approval, but since we've noticed a trend of empty projects showing up or attempts to be malicious, we've added manual approval for projects as well.
What does this mean to you?
Basically, you have to wait for an administrator to approve your new project (and as usual, your files). We're available pretty much all the time, though. So it shouldn't be a problem. If you feel we're slow, feel free to stop by IRC and poke us. Try poking Zyuu first, if it's regarding approvals.
IRC Information: #CurseForge @ irc.freenode.net
Posted by ckknight Dec 05, 2008 at 17:27 UTC
Hey, beautiful people.
I've been working on a per-project role-based access control system, and it's finally in place now. You may have guessed yesterday when the site was having some downtime that something was happening, and we were working out the final kinks of the system then.
Side note: Technically, this is per-repository and not per-project, but the mainline repository defines users' permissions in a project.
What this means:
Instead of just Project leader and authors, we can have multiple roles, e.g. Translators, QA, Documenters, Authors, Managers, and really anything that we can think of.
The way the system works:
There is a set of roles that we administrators define. Each role has a set of permissions attached to it.
Each repository has a set of role assignments which grant a user to one or more roles (Yes, you could be both QA and a Translator at the same time).
Each user would then have a set of permissions on a repository defined by the set of permissions of all their roles on that repository.
Here's the set of permissions:
As it stands, we only have Manager (which has all permissions) and Author (which doesn't have as many permissions).
We do want to work on adding more roles, but we need good ideas on what is wanted as far as that is concerned. So if you have some good ideas, feel free to contact us or just leave a comment here.
Currently, all managers are also authors, and any new projects will have the owner be both a manager and an author. Note that the manager can unassign himself as an author.
Posted by Kaelten Dec 28, 2008 at 17:38 UTC
Yesterday we launched a series of enhancements to the packager. Here is a quick rundown of the new features:
externals: libs/LibStub: svn://svn.wowace.com/wow/libstub/mainline/tags/1.0 libs/CallbackHandler-1.0: svn://svn.wowace.com/wow/callbackhandler/mainline/trunk/CallbackHandler-1.0 libs/LibMonkey-1.0: url: svn://svn.curseforge.net/wow/libmonkey-1-0/mainline/trunk libs/LibBanana-1.0: url: git://git.curseforge.net/wow/libbanana-1-0/mainline.git tag: 1.2 libs/LibSuit-2.0: url: http://hg.curseforge.net/wow/libsuit-2-0/mainline tag: latest libs/LibSubThingy-2.13: http://hg.curseforge.net/wow/libthingy-2-0/mainline/libsubthingy-2.13
These features have been tested, however issues may still exist, please notify us immediately if there are any issues.
Also if the examples aren't clear enough let me know ;)
Posted by Kaelten May 22, 2009 at 15:24 UTC
I just wanted to let everyone know that we've had to temporarily disable subscription signups for premium. There is a issue with PayPal and we'll have this worked out as soon as possible. Anyone who mistakingly received a canceled subscription email from PayPal will still receive uninterrupted Premium Service for the remainder of your subscription term.
Again, we apologize for any inconvenience and I'll keep you guys updated as things continue.
(UPDATE) This was fixed on saturday, again we apologize for any inconvenience anyone has had.
Posted by Ackis Oct 27, 2010 at 14:13 UTC
Good day everyone.
There have been some issues with the packager over the past week or two. It's a known bug, and there's a known work around for now. The root cause of the problem is being investigated and will be fixed.
Thank you for your patience and understanding.