El 09/03/2015, a las 22:30, "W. Trevor King" <[email protected]> escribió:
> On Mon, Mar 09, 2015 at 10:19:56PM -0400, Ivan Gonzalez wrote: >> In a year or so, could we run into the problem of having a lot >> unmaintained, no-merge branches with outdated content? > > Absolutely. We'd want to unlink any lessons that lost their > maintainers, but having a bunch of closed pull-requests referencing > old, previously-interesting work wouldn't be a problem. It's a useful > stash of ideas for folks developing the lessons, and no load on anyone > other than GitHub (and they can probably spare the disk space ;). > What do you see as the drawback? So the workflow would be: 1) make your whole modified lesson a new branch named after your workshop, 2) make a PR labeled "workshop-archive" also named after your workshop and close it (maybe after a few days after), 3) people pick from your branch what is useful and maybe merge into master, 4) the branch never gets deleted and serves as archive Something like this? It may work, I don't really know. Ivan _______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
