Steps confused about the Applicant's Checklist
Hello... I am interesting in the New Maintainer Application and try to take an exam for the developers. I read the steps of Applicant's Checklist. Something confused me about the first two. In the Initial Contact step two:The applicant's identity needs to be verified. The applicant needs to prepare the GPG key to be signed by a Developer or sponsor? And then, the Identification routine mentions that the way to prepare a GPG key and providing. Is the routine:Identification the same as the Initial Contact step two? sorry for my poor english. I will study hard to improve it...:-) Thx! asho
Re: Steps confused about the Applicant's Checklist
On Wed, 12 May 2004 09:41:16 -0700 (PDT) Matt Brubeck <[EMAIL PROTECTED]> wrote: > > Yes, the instructions in Step 2: Identity Verification are the same as > the "verification" mentioned in Step 1: Initial Contact. You need to > get your key signed *before* the initial contact; it will be verified by > your Application Manager *after* the initial contact (this is why it is > "Step 2", although this is not very clear from the NM Checklist pages). oh...So the goal of "Step 2" is that The AM will check the applicant did signed the key with his sponsor or not. > > I'm sure that debian-newmaint would welcome a patch to make these pages > less confusing... glad to hear that ... :> Thanks for solving my problem at all. I can go further to have a view of the exam...:) Thx! asho
Re: Steps confused about the Applicant's Checklist
On Wed, 12 May 2004 19:39:03 +0200 Nico Golde <[EMAIL PROTECTED]> wrote: Hello Nico Thanks for encouraging me to the work. I got the answer about that yesterday. Still thank you for helping me...:-) Wish you passing the exam :D > * Asho Yeh <[EMAIL PROTECTED]> [2004-05-12 19:09]: > > I am interesting in the New Maintainer Application and try to take an exam > > for the developers. > > Me too :) > > > In the Initial Contact step two:The applicant's identity needs to be > > verified. The applicant needs to prepare the GPG key to be signed by a > > Developer or sponsor? > > By a debian developer(one of the people with @debian.org), but your > sponsor have to be debian developer too :) > > > And then, the Identification routine mentions > > that the way to prepare a GPG key and providing. Is the > > routine:Identification the same as the Initial Contact step two? > > you verify your identity with your gpg key and some of the debian > developers who had signed your key quasi vouches that the key belongs to > a real person(you). > so only get a keysigning by a debian developer and then continue with > your work :)
Need sponsor for gcin, a new chinese input method for X
Hello. I am a newbie for packaging the debs. Now I am interesting in a new package called gcin. Gcin is another X input method for CJK environment.GCIN supports many input method such as cj, ar,dayi right now. The original website is http://www.csie.nctu.edu.tw/~cp76/gcin/. Anyone can download the src and binary packages here: deb http://people.debian.org.tw/~asho/deb gcin/ deb-src http://people.debian.org.tw/~asho/debsrc gcin/ I will try my best to write mans and hope these package can be a NMU upload ..:-) Best Regards, Asho Yeh
How to solve the upstream software which will break the build package policy?
Hi mentors: I maintained a XIM:gcin for the zh-TW users and met into problem. A program of the software which have the "help" function will read the /usr/share/doc/gcin/README (by gedit). I made a gcin.doc and wanted to install the README.zh-TW (I cp to a different filename and also modified the upstream software) and of course the dh_installdocs would gzip the file so that the gedit couldn't open it. I checked up the xine-ui source because xine-ui has the same situation like mime. The maintainer gunzip the README.*.gz file so that the help dialog works. Also, he knew that it might violate the policy. Should I also gunzip the README file to make the help function work or there are some ways to prove it? Thanks. Best Regards Asho Yeh
Steps confused about the Applicant's Checklist
Hello... I am interesting in the New Maintainer Application and try to take an exam for the developers. I read the steps of Applicant's Checklist. Something confused me about the first two. In the Initial Contact step two:The applicant's identity needs to be verified. The applicant needs to prepare the GPG key to be signed by a Developer or sponsor? And then, the Identification routine mentions that the way to prepare a GPG key and providing. Is the routine:Identification the same as the Initial Contact step two? sorry for my poor english. I will study hard to improve it...:-) Thx! asho -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Steps confused about the Applicant's Checklist
On Wed, 12 May 2004 09:41:16 -0700 (PDT) Matt Brubeck <[EMAIL PROTECTED]> wrote: > > Yes, the instructions in Step 2: Identity Verification are the same as > the "verification" mentioned in Step 1: Initial Contact. You need to > get your key signed *before* the initial contact; it will be verified by > your Application Manager *after* the initial contact (this is why it is > "Step 2", although this is not very clear from the NM Checklist pages). oh...So the goal of "Step 2" is that The AM will check the applicant did signed the key with his sponsor or not. > > I'm sure that debian-newmaint would welcome a patch to make these pages > less confusing... glad to hear that ... :> Thanks for solving my problem at all. I can go further to have a view of the exam...:) Thx! asho -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Steps confused about the Applicant's Checklist
On Wed, 12 May 2004 19:39:03 +0200 Nico Golde <[EMAIL PROTECTED]> wrote: Hello Nico Thanks for encouraging me to the work. I got the answer about that yesterday. Still thank you for helping me...:-) Wish you passing the exam :D > * Asho Yeh <[EMAIL PROTECTED]> [2004-05-12 19:09]: > > I am interesting in the New Maintainer Application and try to take an exam for the > > developers. > > Me too :) > > > In the Initial Contact step two:The applicant's identity needs to be > > verified. The applicant needs to prepare the GPG key to be signed by a > > Developer or sponsor? > > By a debian developer(one of the people with @debian.org), but your > sponsor have to be debian developer too :) > > > And then, the Identification routine mentions > > that the way to prepare a GPG key and providing. Is the > > routine:Identification the same as the Initial Contact step two? > > you verify your identity with your gpg key and some of the debian > developers who had signed your key quasi vouches that the key belongs to > a real person(you). > so only get a keysigning by a debian developer and then continue with > your work :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Need sponsor for gcin, a new chinese input method for X
Hello. I am a newbie for packaging the debs. Now I am interesting in a new package called gcin. Gcin is another X input method for CJK environment.GCIN supports many input method such as cj, ar,dayi right now. The original website is http://www.csie.nctu.edu.tw/~cp76/gcin/. Anyone can download the src and binary packages here: deb http://people.debian.org.tw/~asho/deb gcin/ deb-src http://people.debian.org.tw/~asho/debsrc gcin/ I will try my best to write mans and hope these package can be a NMU upload ..:-) Best Regards, Asho Yeh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
How to solve the upstream software which will break the build package policy?
Hi mentors: I maintained a XIM:gcin for the zh-TW users and met into problem. A program of the software which have the "help" function will read the /usr/share/doc/gcin/README (by gedit). I made a gcin.doc and wanted to install the README.zh-TW (I cp to a different filename and also modified the upstream software) and of course the dh_installdocs would gzip the file so that the gedit couldn't open it. I checked up the xine-ui source because xine-ui has the same situation like mime. The maintainer gunzip the README.*.gz file so that the help dialog works. Also, he knew that it might violate the policy. Should I also gunzip the README file to make the help function work or there are some ways to prove it? Thanks. Best Regards Asho Yeh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
