Learn more about these different git repos.
Other Git URLs
We should create a template for prospective contributors to use when introducing themselves.
Besides obvious biographical data, it should have some entertaining character related points. Filling out a form is droll, but if we can make it fun, it hits the "Friends" foundation early on.
Metadata Update from @linuxmodder: - Issue assigned to linuxmodder (was: mailga)
Will add a template file as an attachment and native file for those cloning.
Metadata Update from @linuxmodder: - Issue tagged with: team
Metadata Update from @dhanesh95: - Issue tagged with: next-meeting
Metadata Update from @ankursinha: - Issue untagged with: next-meeting - Issue tagged with: meeting
some time for ticket was opened, time flies and :fedora: runs and changes quickly...
The Fedora JOIN SIG now has a process to reclute new talent with its proper workflow...
as far I can tell Fedora join team has a template and separate pagure instance to welcome! new commers and new workflow as I said before... but we don't have a specific template for introduce newcommers themselves.... like
1.- fas id. 2.- skill's 3.- What are your Interesting areas of fedora?
That is the typical TOPIC used by the newcomers..... in their introduce request....
Regards.,
But this template should be added to the Join docs? Btw I think that a template is pretty pointless nowadays. In addition in the welcome thicket we already suggest what to include in the introduction message: "Then, could you please introduce yourself (preferably on the list) so that the community can get to know you? (interests, skills, anything you wish to say about yourself really)"
Anyway I see that people sending introduction emails (to Join SIG or to other teams) are generally diligent in introducing themselves. No need to add bureaucracy there. So, IMHO, we can close this ticket.
you can read more info here: in SOP of Fedora Join TEAM:
https://docs.fedoraproject.org/en-US/fedora-join/#_post_a_self_introduction
I know :-D
So what we do with this ticket?
+1 to close
Metadata Update from @alciregi: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.