OK, Thilo. I understand what your original mail meant for now. Basically I don't like to have two different accounts for our systems even though a user can setup the accounts to become same on SVN and trac. OSCAR users/developers who actually participate in the development/improvement of OSCAR should have only one account which can take care of all the access issues of the OSCAR system.
Currently we use SVNManger to manage the SVN accounts/repositories/groups and I think we can differentiate the permission in between SVN and trac account so that any user who creates accounts from SVNManager can access both OSCAR SVN repo and trac with the same login information. We should however notice that the OSCAR SVN repo(trunk) is open to the public with read-only permission and the SVN account who has been created via SVNManager has no different privileges from anonymous users but trac access. I think there is a drawback in this system that any anonymous user can not create an account without the admin's approval, which may have hindered the OSCAR community from participating in the OSCAR development but this has been good enough to take care of the access issues so far, I think. Do you think that it is too much hassle for the OSCAR community to ask the system admin for the account approval if anyone wants to participate? Regards, - DongInn On 7/24/09 4:57 AM, Thilo Bangert wrote: > Kim, DongInn skrev: >> Hi Thilo, >> >> Are you talking about the trac ticket systems on the > > oscar official website? > > yes. > >> If it is a trac configuration and you have a good > > suggestion on the trac configuration, please let us know. > > currently the trac instance uses http authtication, possibly using the > same user db as for svn. that means only users with an svn account can > authenticate with trac. or reversed: all trac users also get a svn account. > > there are two possibilities to enable trac participation for people who > shouldnt (yet) have a svn account: > > a) keeping the account settings as they are, but open up ticket and > wiki creation and editing to anonymous users. this is bad as it > opens the trac instance to spam. > b) separate the svn and trac accounts. developers would get 2 accounts, > one for trac and one for svn. regular users would be able to create > their own trac accounts with the trac AuthManager plugin. > > its solution b) i am proposing. > > I think it would open up for more community participation and help > organize the current influx of bug reports. > >> If it is not what a trac user can do, I think we have to talk to the trac >> developers. > > no need for that, AFAICT. > thanks > > kind regards > Thilo > > ------------------------------------------------------------------------------ > _______________________________________________ > Oscar-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oscar-devel ------------------------------------------------------------------------------ _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
