#172 Can we Automate Welcome Newcomers in some way?
Closed: Invalid by hhlp. Opened by hhlp.

I've read pagure api https://pagure.io/api/0/ and I wonder if we can accomplish something like this:

We have two task:

  1. Newcomers, -Welcome Message,

    • User Login in Pagure
    • for each user in user.txt
      write a pre-format Welcome Message
    • Done
  2. Follow up, Newcomers

    • for each Issue in pagure/join-welcome
    • if issue = open && issue-date > 1 week (we can also validate tag's in any way)
      write some like this:
      * How well is your trip being?
      * Are you Join in any TEAM?
      * Were you accepted?
      * Have you encountered any kind of impediment?
    • eif
    • Done
  3. We can still contact with newcomers

and run in our PC:

podman run user/join-welcome

Idea come from here: https://github.com/asamalik/magazine-schedule

WDYT?

Regards.,


I'm wary of automation here at the moment. The idea of the new process is to make it people focused so that newcomers can interact with the people of Fedora. So if we automate and replace manual tasks that we, the people, do, we lose some of that.

althought the idea is not loose user contact, just automate this two step

... maybe in near future

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

I quote @ankursinha, we are not here to automate things. The main idea is to talk with people and invite people to interact.
Btw some sort of script could be useful to look at tickets status at a glance. Hey, we don't hear anything from this person since some time, let's try to ping him/her.

@alciregi Yes you go it

if issue = open && issue-date > 1 week
Hey, we don't hear anything from this person since some time, let's try to ping him/her.

That is precisely we have to do in the next next days

Regards.,

I was thinking we could restart weekly/bi-weekly meetings, and use them to go over tickets? Newbies could also join the meetings and learn how things work there?

A more human approach +1

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

Metadata