#186 Run worldcloudbot on @fedoracommunity Twitter account
Closed: Stale 10 months ago by jflory7. Opened 2 years ago by jflory7.

wordcloudbot is a bot that listens to fedmsg, makes fancy world clouds, and tweets them on Twitter. Once upon a time it existed but it fell by the wayside. It would be cool to revisit it now and try to deploy this.


Metadata Update from @jflory7:
- Issue tagged with: type - coding

2 years ago

Rather than running this on Twitter, perhaps GNU Social or Mastodon should be considered, possibly with a relay to Twitter if that is a must-have. Twitter is a proprietary centralized service, whereas GNU Social and Mastodon are FLOSS, decentralized, and can be run by anyone.

Discussed in 2018-11-21 meeting.


In yesterday's meeting, we agreed to put this ticket on target for completion during the Fedora 30 release cycle.

An older CommOps project, wordcloudbot, takes Fedora meeting minutes, generates a word cloud from most-used words in a meeting, and automatically posts the results to a Twitter account. It would be cool to get this working again and set up on the @fedoracommunity Twitter account.

Next steps likely include a revisit to the original code (some modernization might be needed), testing it out with existing Fedora meetings locally, and then getting it running on a server so the tweets happen automatically.

We’ll begin exploring this at the next CommOps meeting. Maybe @siddharthvipul1, @sumantrom, or @algogator could help get this added to GCI 2018.

We're having related discussion about this, including the above comment about Mastodon support, over on Discourse.

Metadata Update from @jflory7:
- Issue set to the milestone: Fedora 30 (to May 2019) (was: Future releases)

2 years ago

Metadata Update from @jflory7:
- Issue priority set to: next meeting (was: needs review)

2 years ago

Metadata Update from @jflory7:
- Issue tagged with: good first issue

2 years ago

Discussed in 2018-11-28 meeting.


In the meeting, we didn't have any immediate volunteers to work on this. We decided to do some promotion / visibility around this ticket to see if we can find a volunteer outside of a core team member. Next, we need to find a volunteer interested in Python and fedmsg. Some coding background is helpful, but only at a beginner level.

@bt0dotninja is working on a CommBlog post for "Winter 2018 CommOps easyfix tasks" and we'll use that to try and drive more participation in the team. We can follow it up with social media / user community coverage too. @jonatoni was going to experiment with Instagram Stories to highlight contribution opportunities, once this CommBlog post publishes.

We'll check in on the draft status at next week's meeting.

Metadata Update from @jflory7:
- Issue tagged with: team - infra

2 years ago

@bt0dotninja has a draft here. The content looks good to me.

@bt0dotninja, do you want to start a new thread on Discourse and request editor review as a next step?

Metadata Update from @jflory7:
- Issue assigned to bt0dotninja
- Issue priority set to: waiting on assignee (was: next meeting)

2 years ago

@jflory7 can I get more info about it ?

This is the main repository of worldcloudbot https://pagure.io/wordcloudbot , maybe we can work together to update the information get it up and running, what do you think @ektaarora3501 ?

Hi @bt0dotninja What is the next step to be followed ?

Is this issue still up, I would like to take it.

I would like to work on it too with @bt0dotninja

The requirements.txt needs updating. txWS and txZMQ require wheel package for building along with python3-devel package.

python-fabulous and tweepy rpm packages are no longer maintained. Finding another way to get them.

@bt0dotninja Please review the newly made PR here

Metadata Update from @bt0dotninja:
- Issue set to the milestone: None (was: Fedora 30 (to May 2019))

a year ago

Metadata Update from @bt0dotninja:
- Assignee reset

a year ago

Metadata Update from @bt0dotninja:
- Issue assigned to bt0dotninja

a year ago

@bt0dotninja, Notes

  • The module has a dependency on an installed site package instead of its own virtual environment, failing to meet which might make it unusable.
  • Just in case, this behaviour of relying on an installed site package is expected - the package must be updated every now and then to keep up with the latest version.
  • But what about the people having older version?
  • fedmsg is deprecated in favour of Fedora Messaging - It is a good thing as it is built from scratch as compared to the legacy PyZMQ based implementation.
  • Tweepy is still maintained. The primary task would be phase out PyZMQ based libraries entirely to bring in Fedora Messaging here.

amazing, I agree with the fedora messaging migration as the first task

Metadata Update from @bt0dotninja:
- Assignee reset

a year ago

Metadata Update from @bt0dotninja:
- Issue assigned to t0xic0der

a year ago

Discussed in 2020-08-08 Fedora Nest metrics hack session.


This ticket is blocked until we know if wordcloudbot actually works in its current form. @bee2502 is going to test if it still works or not.

If wordcloudbot works in its current state:

  1. Work with CPE team to provision AWS instance for wordcloudbot
  2. Check out toddlers to help with fedora-messaging bootstrapping (thanks @cverna for mentioning)
  3. Work to port to fedora-messaging from fedmsg

If wordcloudbot does NOT work in its current state:

Close this ticket as stale. It is a ticket that gets a lot of newcomer attention but it is a difficult ticket to help newcomers with because the stack is old.

Metadata Update from @jflory7:
- Issue untagged with: good first issue, help wanted, team - infra
- Issue assigned to bee2502 (was: t0xic0der)

10 months ago

I don't think I can work on this. I wasn't able to run it currently and I didn't have time to debug the issues i.e. if they were version issues or something more complex. If anybody wants to have another go, pls feel free to take this up.

Metadata Update from @bee2502:
- Assignee reset

10 months ago

Thanks for the follow-up @bee2502. As discussed at Nest, I am going to close this ticket as stale.

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

10 months ago

Login to comment on this ticket.

Metadata