Skip to content

Instantly share code, notes, and snippets.

@luceos
Last active June 14, 2017 14:10
Show Gist options
  • Save luceos/04bd57e37105dec4ec743395b820e1b9 to your computer and use it in GitHub Desktop.
Save luceos/04bd57e37105dec4ec743395b820e1b9 to your computer and use it in GitHub Desktop.
Forking Flarum

Roadmap

  • Decide on a name & motto.
  • Open a community forum.
  • Create a new design.
  • Get 0.1.0 released asap.

Direct improvements

  • Work with a monthly release cycle, Gitlab style.
  • Use the boards on Github for close project management.
  • Get more developers involved in contributing, eg Reflar people.
  • Get a considerate staff team up, some with specific tasks to stimulate activity (off topics, polls, from the net etc).
  • Direct possibility of pledging on Patreon.

Ideas

  • Closely integrate with Patreon. Next features are decided on by patrons.
  • Drop packagist (not composer), use our own registry provided by our website. This requires devs to register their extensions.
    • This would also allow use to get paid extensions more easily into the fork.
    • In addition we could allow devs to publish paid extensions where we can keep a percentage of.
  • Drop flagrow.io and move logic to a new portal for the fork. This would
    • give a dashboard to any webmaster,
    • allow webmasters to receive mails on outdated versions,
    • possibly auto patch installations.
  • Invest money back by opening up challenges for code, design and documentation.
  • Skeleton for enterprise that moves vendor and other files outside of public_html.
  • Provide commercial/paid support.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment