I have a repository on github for a project that deals with importing/processing/sending reports to clients. There is now talk of creating a similar application for a different set of users, without the import part, but multiple send parts. The existing code base already has 90% of what the new application needs (and some extra that is not needed for this new project).

Should I fork the existing project and make the new project, or should I use the ‘import project’ function on github to create a new project based on the old project, or use the commandline to mirror the old project into a new project, or something else?

In future, there might be more projects that build on top of one of these projects with their own customizations, so I’m looking for a good approach that I can leverage again in future.

Please advise.

  • @canpolatM
    link
    English
    6
    edit-2
    1 year ago

    Not sure I got the question right, but it sounds like you can benefit from code reuse via shared projects or packaging different parts of the code into chunks.

    • @nieceandtowsOP
      link
      English
      21 year ago

      That’s a good idea to think about, thank you