Releasing a forked WP plugin separately

  • Resolved Ramesh (thecodeisclear)

    (@thecodeisclear)


    10 years, 2 months ago

    Hi,

    I tried looking around for any feedback or guidelines on this, but couldn’t find any. What is the general opinion of WordPress Admins & the group on releasing a fork of an existing plugin separately. I will retain the original author name, links to their site etc and mention in what way this fork differs from the original.

    License-wise, I may be covered, but is this generally acceptable behavior or is it frowned upon.

    Thanks.

Viewing 4 replies - 1 through 4 (of 4 total)

  • I will retain the original author name, links to their site etc and mention in what way this fork differs from the original.

    …is this generally acceptable behavior…

    Yes. All for one and one for all without any one robbing from any other.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Please remember to retain any and all copyright information. You’re fine ??

    Now keep in mind, we’d all rather you collaborate with the original author and improve the xisting plugin, but sometimes that’s not possible. Do try to get a hold of them, if this is just a fixit fork, and ask if you can help out ??

    Thread Starter Ramesh (thecodeisclear)

    (@thecodeisclear)

    Thank you leejosepho & ipstenu.

    I would also prefer to collaborate and have submitted a pull request on Github and contacted the author separately. This is my last resort.

    Thread Starter Ramesh (thecodeisclear)

    (@thecodeisclear)

    Marking this as resolved. I have added new features to my fork, however, I will work on it a bit more and release it after getting plugin feedback.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Releasing a forked WP plugin separately’ is closed to new replies.