it's not ACL, this "simplisime" ACL like, and you look like that you did not understand my point, maybe you did not read correctly, many third part of open-source projects need sometimes "open" but not redistributable code in other shape than binaries, for instance it was the case for Sun's JVM before releasing it under GPL3, and this is still the case for ACPI, and it's exactly what happens on FreeBSD repository, only APIC implementation is public hosted, but for convinience you need the private parts to be shared between team members, go further than your nose.
Cheers! On Fri, Apr 10, 2009 at 9:03 AM, Ryan Schmidt <[email protected]> wrote: > > On Apr 10, 2009, at 10:37, mm w wrote: > >> anyway I dream that one day google subversion system handles the >> fact to set >> privilege flags on file, something a la "ACL" (), and like this you >> could specify >> public / owner / owners / group (if it's a directory: recursive) >> and sure those >> privileges should apply dependently from the time line so you could >> be able >> to control a lock system for all your project can be useful in >> certain project: >> >> example: I am working on a ACPI implementation, I cannot redistribute >> the Intel source (license), >> but anyway I would like to host a version src, and maybe devel >> binaries, internal devel tools for my team > > Google Code is for hosting open-source projects only. All the code > must be visible to anyone who wants to see it. So I don't see a point > to offering ACLs in the repository. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
