Re: tasks files maintence (Re: RFS: graph isomorphism)
Le Sat, Sep 05, 2009 at 09:27:49PM +0200, Andreas Tille a écrit : > On Fri, Aug 07, 2009 at 09:05:17AM +0900, Charles Plessy wrote: > > > > I think that ACLs can also handle multi-project write access, since it knows > > them as groups: > > > > ple...@alioth:~$ getfacl debian-med > > # file: debian-med > > # owner: scm-gforge > > # group: debian-med > > user::rwx > > group::rwx > > other::r-x > > > > I never used ACLs before, so I do not know if it would require the > > intervention > > of an Alioth admin or not??? > > I would really welcome if somebody would care for this. It would be a > quite reasonable solution. Hi all, I figured out that only Alioth admins can modify the repository ACLs. Now the Blends repository is writable for debian-med. As announced on the debian-blends mailing list, just let me know if you would like that the members of the debian-science Alioth project also get write access to the Blends subversion repository. This would enable each debian-science member to do ‘debcheckout -a debian-science’ and modify the task files. Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: tasks files maintence (Re: RFS: graph isomorphism)
On Fri, Aug 07, 2009 at 09:05:17AM +0900, Charles Plessy wrote: > > I think that ACLs can also handle multi-project write access, since it knows > them as groups: > > ple...@alioth:~$ getfacl debian-med > # file: debian-med > # owner: scm-gforge > # group: debian-med > user::rwx > group::rwx > other::r-x > > I never used ACLs before, so I do not know if it would require the > intervention > of an Alioth admin or not??? I would really welcome if somebody would care for this. It would be a quite reasonable solution. Kind regards Andreas. -- http://fam-tille.de Klarmachen zum Ändern! -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: tasks files maintence (Re: RFS: graph isomorphism)
On Thu, Aug 06, 2009 at 10:37:31AM -0300, David Bremner wrote: > On a related topic it would be nice if there was some semi-automatic > way to smooth the flow of ITPs into the tasks files. Perhaps > something along the lines of the Package Entropy Tracker watching the > git repos. Perhaps something useful will come out of the pkg-perl > teams investigations of git. I perfectly agree here and IMHO the apropriate way would be the following: 1. Move information of WNPP bugs into UDD 2. Put WNPP number into tasks file (instead of copying the WNPP info into tasks file 3. Render information from UDD on the tasks pages The problem is 1. because it depends from the quality of the bug reports to get really structured information. In principle the reportbug template is structured enough to enable automatic parsing - but reporters are sometimes not strict enough to follow the template. The procedure is one of my long term goals - I would not mind if somebody might tackle item 1. - the other items are really cheap to implement. Kind regards Andreas. -- http://fam-tille.de Klarmachen zum Ändern! -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: tasks files maintence (Re: RFS: graph isomorphism)
Le Thu, Aug 06, 2009 at 09:04:11PM +0200, Andreas Tille a écrit : > On Thu, Aug 06, 2009 at 10:37:31AM -0300, David Bremner wrote: > > > Or maybe there is some alioth magic that could make all debian-science > > members automatic members of blends. > > I don't think that there is such a magic. IMHO the only chance is > to open it for all alioth members. I would not have real problems > with this approach because I'm reading the commit list - but for the > moment there was not much need to do so. Hi Andreas, I think that ACLs can also handle multi-project write access, since it knows them as groups: ple...@alioth:~$ getfacl debian-med # file: debian-med # owner: scm-gforge # group: debian-med user::rwx group::rwx other::r-x I never used ACLs before, so I do not know if it would require the intervention of an Alioth admin or not… Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: tasks files maintence (Re: RFS: graph isomorphism)
On Thu, Aug 06, 2009 at 10:37:31AM -0300, David Bremner wrote: > For me, joining the blends group is fine. bremner-guest added to Blends project. > But in the long run I think > moving into debian-science svn would make it more a natural part of > the team workflow, rather than something you have to manage/encourage > by asking about what task a given new package goes in. Well, if it's only the workflos SVN knows external resources. These are used to put debian-edu and debian-gis source into the blends repository and in turn we might be able to do this in the Debian Science project as well (but I guess proper permissions are needed). I agree that its debatable where to keep the original source for the tasks file - but up to now nobody insisted on moving it and I'm not heavily motivated to change a running system. > Or maybe there is some alioth magic that could make all debian-science > members automatic members of blends. I don't think that there is such a magic. IMHO the only chance is to open it for all alioth members. I would not have real problems with this approach because I'm reading the commit list - but for the moment there was not much need to do so. > Would that be desirable from a > blends point of view delegate adding users like that? It doesn't > matter so much where the svn is I guess, I'm mainly thinking the extra > adminstrative hoop. Considering the number of really interested people it was easily maintainable. > On a related topic it would be nice if there was some semi-automatic > way to smooth the flow of ITPs into the tasks files. This would actually be a nice thing, but I have no idea how to approach this. Currently I'm watching ITPs as far as my time permits and just copy the information which is not that hard if proper ITPs are filed. > Perhaps > something along the lines of the Package Entropy Tracker watching the > git repos. Perhaps something useful will come out of the pkg-perl > teams investigations of git. Well, one slight chance I see is that ITPs might be moved in a structured way to UDD and we just pick by bug number. But that's a lot of work for only one use case (I do not see much other use for this information in UDD) and does not seem to be worth the effort. Kind regards Andreas. -- http://fam-tille.de Klarmachen zum Ändern! -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
tasks files maintence (Re: RFS: graph isomorphism)
Andreas Tille wrote: >On Thu, Aug 06, 2009 at 08:12:09AM -0300, David Bremner wrote: >Currently it is organised that way that you have to be a member of >Blends team on alioth. There is no explicite need for this and it >might also go into the debian-science SVN (but it has to be SVN for >the moment). I feel a bit lazy about moving from the blends repository >and would rather like to add people to this group - but if you think >that's an extra burden just ask me to move. Debian Edu and Debian GIS >have their tasks files in their SVN repositories - all other Blends >source packages are in the blends group. For me, joining the blends group is fine. But in the long run I think moving into debian-science svn would make it more a natural part of the team workflow, rather than something you have to manage/encourage by asking about what task a given new package goes in. Or maybe there is some alioth magic that could make all debian-science members automatic members of blends. Would that be desirable from a blends point of view delegate adding users like that? It doesn't matter so much where the svn is I guess, I'm mainly thinking the extra adminstrative hoop. On a related topic it would be nice if there was some semi-automatic way to smooth the flow of ITPs into the tasks files. Perhaps something along the lines of the Package Entropy Tracker watching the git repos. Perhaps something useful will come out of the pkg-perl teams investigations of git. All the best, David -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
