#576 Encourage to be package maintainers to introduce themselves in devel list
Closed None Opened 13 years ago by sundaram.

= Proposal topic =

Other sub projects encourage new contributors to introduce themselves in the appropriate mailing list. However http://fedoraproject.org/wiki/Join_the_package_collection_maintainers has no such step. It is useful to get to know new contributors to gain a bit more familiarity with each other and by posting their review request, they gain more visibility and hopefully interested people will see that and sign up to review/sponsor them

I propose to add a section to the above wiki page or create a new wiki page and link to it, along these lines (based on the docs project page)

" == Introduce yourself =="

When a new package maintainer joins the Fedora Project, we ask that he/she introduces themselves on the Fedora Devel mailing list. To sign up for the list, visit the devel list signup page . The primary purpose of this is to begin the process of building trust by learning about the writer/editor, and downloading their GPG key.

The purpose of all this is to break anonymity and foster real-world community within the project. You are under no obligation to reveal personal secrets. The objective is to establish a level of trust with yourself and the other members of the project.

Subject

Self-Introduction:

Body

What other projects or writing have you worked on in the past?
What level and type of computer skills do you have?
What other skills do you have that might be applicable?  Programming, etc.
What makes you an excellent match for the project?
Link to your review request and a brief description of the software you packaged
GPG KEYID and fingerprint
    See Creating GPG Keys for help and instructions if you don't have a GPG key.
    Be sure that your GPG key is uploaded to pgp.mit.edu. Use "gpg --keyserver pgp.mit.edu --send-key KEYID".
    Your GPG fingerprint is 40 hexadecimal characters long, while your KEYID is the last 8 digits.
    Below is an example of the GPG text suitable for cut & paste into your self-introduction e-mail.

[warren@computer ~] # gpg --fingerprint 54A2ACF1
pub 1024D/54A2ACF1 2002-11-25 Warren Togami (Linux) warren@togami.com
Key fingerprint = 785A 304B 08C1 F291 F54F 9A68 6BDD FE8E 54A2 ACF1
sub 2048g/4AD75982 2002-11-25 [expires: 2007-11-24] "

I am not just adding it directly because I think this is somewhat of a significant change in our workflow.


Adding the meeting keyword here. We will discuss at the next meeting. ;)

Thanks.

As a addendum, I would also like to modify the http://fedoraproject.org/wiki/How_to_sponsor_a_new_contributor to add a step recommending the sponsor announce that a person has been sponsored is now a package maintainer maintaining foo or bar to the devel list. FWIW, I follow these procedures in the Fedora India community (c.f. fedora india mailing list) and new contributors tend to be very appreciative of it.

I would add it as recommended, non-mandatory.
+1 for proposal

FESCo approved adding this. Not sure the gpg key information is all that usefull, perhaps it should be optional? Also, the entire thing should be just recommended, not required.

We would prefer not to add the sponsors sending a note anytime they sponsor someone as that seems duplicated effort from the new maintainer mailing about themselves.

If you could make the changes or let us know if there are outstanding issues with wording, that would be great.

Added

https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Introduce_yourself

https://fedoraproject.org/wiki/How_to_sponsor_a_new_contributor#Welcome_Note

I would appreciate a review of these. The idea behind having both a introduction and a welcome note is that is that a number of people who are subscribed to fedora devel just trying to get a idea of the community would see both of these and feel motivated in addition to the contributors themselves. This might seem a bit of noise but in practise I have found that this work really well for gaining new contributors.

FESCo is fine with these for now.

We can revisit/adjust down the road if the volume becomes troublesome.

Login to comment on this ticket.

Metadata