floblockchain / chores Goto Github PK

update coingecko.com's FLO repo listing from https://github.com/flo-blockchain to https://github.com/floblockchain

Forget the massive overhaul at this point. Let's just update the links and the text. Example: get rid of the Florincoin reference on the Documentation page. Bury the tZERO references since they are no longer using FLO (or at least suspended their use). Update the exchanges to include Abra, etc. Eliminate references to things that happened in 2019 and update it with things that happened in 2020.

(https://wiki.flo.cash/index.php/Main_Page).

It is being attacked by a bot. We need to either move it, or fix the software that runs it so that changes need to be approved. I understand we don't want to centralize that control, but we also don't want to destroy the entire wiki project for the sake of decentralization. This is a baby of mine, since I put all the work in to create it.

• change page and content to reflect current state of FLO development.

• require community member to takeover and manage Instagram page.

• only 6 posts last posted in 2018 yet we have 563 followers who have not been updated with FLO updates.

• potential to use hashtags to attract more developers and community developers who are interested in open source projects.

• Convert the video files to audio for first three episodes
• Write brief description of Episodes 2 and 3; create related metatags (Davi/FTW)
• Set up Soundcloud account
• Set up and link iTunes account
• Set up and link Spotify account
• Discuss and target additional distribution
• Create/purchase intro/outro bumper
• Discuss creating intro descriptions to be added post production
• Add last two episodes
• Write descriptions and metatags for last two episodes (FTW)
• Set up and link Google Play
• Get all the videos on Youtube
• Put together official announcement
• Tweet out individual episodes
• Fix Google Play Feed issue

I am stumbling through this for the first time... I am highly motivated so the learning curve does not deter me. Lets make it easier for non-tech users to contribute to FLO by adding a minimalistic walkthrough for first time users on how to contribute... perhaps this should ultimately be hosted on the wiki to mitigate clutter.

Ideally, we would make a continuous deployment on a master branch and allow/test PRs in a development branch, like any other project.

• Flesh out all the details and write a summary of the proposal with goals, value added, etc.
• Determine costs to develop