[Scummvm-devel] Bringing our Core Code to another Level?

Arnaud Boutonné strangerke at scummvm.org
Mon Aug 12 21:33:42 CEST 2013

I'm not sure it's so important to restrict the access to the code.
Currently, every team member has enough rights to modify things in the core
code, but in practical people self-restrict themselves, and use pull
I think some good common sense is more important than strict rules,
particularly as we always can reverse if a commit breaks things


On Mon, Aug 12, 2013 at 9:21 PM, A. Milburn <fuzzie at users.sourceforge.net>wrote:

> On Mon, Aug 12, 2013 at 09:49:46PM +0300, Filippos Karapetis wrote:
> > possibly with different maintainers per project. Thus, engine developers
> > will not have write access to OSystem itself, right? Again, I assume that
> > only the "core team" (LordHoto, wjp, fuzzie, possibly others too?) will
> > maintain the OSystem project? Or will all developers have write
> permissions
> > to the OSystem core?
> The porters would have to have access to their backends so it's not
> something you could easily restrict to some "core team".
> - Alyssa
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Scummvm-devel mailing list
> Scummvm-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/scummvm-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scummvm.org/pipermail/scummvm-devel/attachments/20130812/070612d1/attachment.html>

More information about the Scummvm-devel mailing list