fedora-join / Fedora-Join

#6 Join SIG introduction template for seasoned contributors looking to help out
Closed: Invalid by alciregi. Opened by immanetize.

Closed: Invalid
Reopen Issue

We should create a template for people to use when introducing themselves as someone interested in joining the SIG. Other groups have such templates, with varying degrees of detail and formality - the template we create should be adaptable for other SIGs to use as well (think includes; much content will be universally applicable, some will not be)

Here's what I think the template should include:

  1. Who you are, your IRC nick, your user page, your blog and so on?
  2. What teams in Fedora are you most active in?
  3. How do you want to/How can you help new folks join the community?
  4. Any tips for new members?

I also think we should publish these introductions somewhere - if the magazine wants them, or just add all these links to a wiki page - would aid visibility?

We should figure out the template before I send out the mass mail. Opening a new ticket for that one.

randomuser, isn't this a dup of ticket #7?

7 is about a generic, extensible template for introductions for use by any group in the community. This ticket is how we want to extend the general introduction to ask for extra information we'd want from prospective SIG members.

Metadata Update from @dhanesh95:
- Issue tagged with: next-meeting

I think the commblog is better for a communication like this to be out.
But I'm totally +1 to have this guide.

Metadata Update from @ankursinha:
- Issue assigned to ankursinha (was: mailga)

Metadata Update from @immanetize:
- Issue assigned to mailga (was: ankursinha)

Metadata Update from @immanetize:
- Issue assigned to ankursinha (was: mailga)

Metadata Update from @immanetize:
- Issue assigned to mailga (was: ankursinha)

Metadata Update from @immanetize:
- Issue assigned to ankursinha (was: mailga)

Metadata Update from @immanetize:
- Issue assigned to mailga (was: ankursinha)

Metadata Update from @immanetize:
- Issue assigned to ankursinha (was: mailga)

Metadata Update from @immanetize:
- Issue assigned to mailga (was: ankursinha)

Metadata Update from @immanetize:
- Issue assigned to ankursinha (was: mailga)

Metadata Update from @immanetize:
- Issue assigned to mailga (was: ankursinha)

Metadata Update from @immanetize:
- Issue assigned to ankursinha (was: mailga)

Metadata Update from @immanetize:
- Issue assigned to mailga (was: ankursinha)

Metadata Update from @immanetize:
- Issue assigned to ankursinha (was: mailga)

Metadata Update from @immanetize:
- Issue assigned to mailga (was: ankursinha)

Metadata Update from @immanetize:
- Issue assigned to ankursinha (was: mailga)

Metadata Update from @immanetize:
- Issue assigned to mailga (was: ankursinha)

Metadata Update from @immanetize:
- Issue assigned to ankursinha (was: mailga)

Metadata Update from @immanetize:
- Issue assigned to mailga (was: ankursinha)

Metadata Update from @immanetize:
- Issue assigned to ankursinha (was: mailga)

Metadata Update from @immanetize:
- Issue assigned to mailga (was: ankursinha)

Metadata Update from @immanetize:
- Issue assigned to ankursinha (was: mailga)

Metadata Update from @immanetize:
- Issue assigned to mailga (was: ankursinha)

Metadata Update from @immanetize:
- Issue assigned to ankursinha (was: mailga)

Metadata Update from @immanetize:
- Issue assigned to mailga (was: ankursinha)

Metadata Update from @immanetize:
- Issue assigned to ankursinha (was: mailga)

Metadata Update from @immanetize:
- Issue assigned to mailga (was: ankursinha)

Metadata Update from @immanetize:
- Issue assigned to ankursinha (was: mailga)

Metadata Update from @immanetize:
- Issue assigned to mailga (was: ankursinha)

Metadata Update from @immanetize:
- Issue assigned to ankursinha (was: mailga)

Metadata Update from @immanetize:
- Issue assigned to mailga (was: ankursinha)

Metadata Update from @immanetize:
- Issue assigned to ankursinha (was: mailga)

Metadata Update from @ankursinha:
- Issue untagged with: next-meeting
- Issue tagged with: meeting

You don't think this is old enough, Join SIG implement a lot during this time:

  • Join SIG has news activities
  • Join SIG has newcomers procedure
  • Join SIG has a Standard Operation Procedure
  • Join Sig has special pagure site for newcomers and template for them

+1 to close it

also this ticket -> https://pagure.io/fedora-join/Fedora-Join/issue/7

Regards.,
Edited by hhlp

+1

+1

Metadata Update from @alciregi:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

This ticket has been migrated to the forgejo instance. Please find the new ticket here
https://forge.fedoraproject.org/join/Fedora-Join//issues/6
Metadata

S: Future-meeting

None
None
Highest
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.