Re: future of developers list

2003-02-02 Thread Martin Michlmayr
* Josip Rodin <[EMAIL PROTECTED]> [2003-02-01 21:02]: > > > I heard on IRC that all the applicants that are sponsored (or all > > > sponsorees > > > that are applicants) would be registered in a database, for easier > > > handling. > > > > Yeah, we were talking about this on IRC recently. It ha

Re: future of developers list

2003-02-01 Thread Osamu Aoki
On Sat, Feb 01, 2003 at 01:56:59PM +0100, Josip Rodin wrote: > On Fri, Jan 31, 2003 at 09:10:38PM +0800, Andrew Shugg wrote: > > > I don't understand why "another field for native character (set)" will > > > fix the name order problem. > > > > What I believe is being proposed is: > > > > - one f

Re: future of developers list

2003-02-01 Thread Josip Rodin
On Sat, Feb 01, 2003 at 09:03:48PM +0100, Martin Michlmayr wrote: > > Just a way to get names and surnames separately. > > OK, that will be easy. However, how do you intend to match those > against the Maintainers file. What if the use a different email > address or a nick name? Approximately t

Re: future of developers list

2003-02-01 Thread Martin Michlmayr
* Josip Rodin <[EMAIL PROTECTED]> [2003-02-01 21:02]: > Just a way to get names and surnames separately. OK, that will be easy. However, how do you intend to match those against the Maintainers file. What if the use a different email address or a nick name? -- Martin Michlmayr [EMAIL PROTECTED

Re: future of developers list

2003-02-01 Thread Josip Rodin
On Sat, Feb 01, 2003 at 08:09:51PM +0100, Martin Michlmayr wrote: > > > > developers' database data per objectclass=debiandeveloper and the > > > > developer > > > > applicant database data (I'm told that this is definitely planned to be > > > > done > > > > as part of the NM system) as authorita

Re: future of developers list

2003-02-01 Thread Martin Michlmayr
* Josip Rodin <[EMAIL PROTECTED]> [2003-01-30 23:16]: > > > developers' database data per objectclass=debiandeveloper and the > > > developer > > > applicant database data (I'm told that this is definitely planned to be > > > done > > > as part of the NM system) as authoritative, and then cross-r

Re: future of developers list

2003-02-01 Thread Josip Rodin
On Fri, Jan 31, 2003 at 08:00:13AM +0900, Tomohiro KUBOTA wrote: > I think another field for native character is a good idea. However, > however, why not UTF-8 rather than native character set? (You mean, > native expression and you didn't want to talk about character encoding?) Yes, I didn't me

Re: future of developers list

2003-02-01 Thread Josip Rodin
On Fri, Jan 31, 2003 at 09:10:38PM +0800, Andrew Shugg wrote: > > I don't understand why "another field for native character (set)" will > > fix the name order problem. > > What I believe is being proposed is: > > - one field for the name to be displayed in the Western convention > - one field

Re: future of developers list

2003-01-31 Thread Tomohiro KUBOTA
Hi, From: Andrew Shugg <[EMAIL PROTECTED]> Subject: Re: future of developers list Date: Fri, 31 Jan 2003 21:10:38 +0800 > - one field for the name to be displayed in the Western convention > - one field for the name to be displayed in the local convention (and >optiona

Re: future of developers list

2003-01-31 Thread Andrew Shugg
Tomohiro KUBOTA said: > I don't understand why "another field for native character (set)" will > fix the name order problem. What I believe is being proposed is: - one field for the name to be displayed in the Western convention - one field for the name to be displayed in the local convention (

Re: future of developers list

2003-01-30 Thread Tomohiro KUBOTA
Hi, From: Josip Rodin <[EMAIL PROTECTED]> Subject: future of developers list Date: Thu, 30 Jan 2003 16:15:37 +0100 > Another added benefit would be that we could then extend our LDAP database > schemas to include another field for people's names in native character set, > wh

Re: future of developers list

2003-01-30 Thread Josip Rodin
On Thu, Jan 30, 2003 at 06:26:31PM +0100, Martin Michlmayr wrote: > > We should eventually rewrite the engine that generates the page to take the > > developers' database data per objectclass=debiandeveloper and the developer > > applicant database data (I'm told that this is definitely planned to

Re: future of developers list

2003-01-30 Thread Martin Michlmayr
* Josip Rodin <[EMAIL PROTECTED]> [2003-01-30 16:15]: > We should eventually rewrite the engine that generates the page to take the > developers' database data per objectclass=debiandeveloper and the developer > applicant database data (I'm told that this is definitely planned to be done > as part

future of developers list

2003-01-30 Thread Josip Rodin
Hi, I think that the underlying point that all the devel/people discussions prove is that extracting developer information from Packages files is flawed by design -- the Maintainer fields are vaguely suitable, but certainly neither flexible nor consistent enough for our purposes. We should eventu