Skip to content

Maybe a reorg? #2

@crertel

Description

@crertel

@aabecker et al., I was wondering if you have a Github organization?

If you do, it might make sense to use that as an umbrella collection for different repositories.

My logic is basically:

  • Each individual paper/project tends to be somewhat different from each other, though they may share base code.
  • Papers and projects tend to accumulate media files and revisions, and that can cause confusing histories
  • People having all-or-nothing access to the main codebase can result in comedy if they trample on papers or whatnot

My proposed solution is:

  • Create a Github organization for @aabecker 's lab
  • Create a master repository for the code that is shared between projects. Basically, just the framework stuff that each project would need itself.
  • Create repositories for each project, containing the code and paper stuff (keeping things nice and neat)

If this seems interesting, I'd be happy to give it a go. Just create the org, add me as an admin, let me know about the different projects/papers here, and I'll put together a trial layout. The original repo here need not be changed for the proof-of-concept, so it shouldn't interrupt you all.

Cheers!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions