Hi. Sylvain Beucler - Inria <sylvain.beuc...@inria.fr> writes:
> Hi, > > Le 28/05/2014 11:30, Dionysios Fryganas a écrit : >> I have constructed a few non-complete suggestions about the project's >> import/export features that should be visible available in the web >> interface. >> >> >> Import/Export placement and link associations >> >> >> Project specific >> >> The plugin import and export features would be meaningful to be placed >> in the project/admin section under the admin->tools tab. >> If that is the default position (haven't looked into that) , as an >> admin/user then it would be friendlier to have a separate >> "import/export" tab under the admin section of the project. >> > Remember the main criticism from ESR's blog post (the one that obergix > pointed you at): > /1. Hosting Sites Are Data Jails/ > Consequently import/export is available to everybody including anonymous > users. > > Of course, export of private data will be restricted to members with > read privileges. Anonymous users will be shown which type of information > they can export and which type are restricted. > > Bottom-line: it's not a user (not admin) feature, and it's mandatory > (all projects have it). It could be a new tab just like "SCM", and/or it > could be linked from the tools. > I agree that in general public forges hosting (mainly) Free/Libre/Open source projects, like it is the case for Alioth (which is the main target of your work, right ;-) should offer anyone the capacity to "fork" a project by getting an export as complete as possible, even if the admins of the forge aren't reachable or the admins of a project have locked members out (refer back to esr's post). But in the more general context of FusionForge which can also host enterprise projects, where confidentiality, access and workflows aren't all the same, I think it would be better to make it configurable who can export data from a project (and maybe make it configurable which data can be exported to refine a bit more). So I'd see some dedicated ACL for anonymous/unauthenticated, members and admins, in the classical way for other tools of the forge. For export, it's a different story: here, only admins are allowed, as I see it, in all cases, but again, with ACL, this could be delegated to a class of users which aren't necessarily forge or project admins. Also, I'm not sure you have taken this into consideration : some of the export/import features are going to involve some volumetry / length of processing issues, which will probably imply some asynchronous processing where the UI is just a mean to ask for import or export, and the real processing is later done by a daemon/cron/slave (whatever is available in fusionforge at the tim : we have some ongoing plans about async processing rework, using a software bus, etc.), and the UI then allows to browse the resulting report and download available dumps, for instance. Hope this all makes sense. Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) _______________________________________________ Fusionforge-general mailing list Fusionforge-general@lists.fusionforge.org http://lists.fusionforge.org/cgi-bin/mailman/listinfo/fusionforge-general
