Hi Dan, Thank you for your comments. We will discuss this more on Tuesday.
> It seems to me that a fork would be a bad idea if it can possibly > be avoided. I agree, especially if the aim is to merge the branches eventually with sage-main rather than having a separate project. Travis brought up the idea of forks. > Maybe what would work would be to have a second combinat repository. > This would have to be rebased this regularly with the main sage repository. > Maybe the master branches would be identical. In other words, someone would > rebase the master branch on the combinat repository with the master branch on > the main repository. This would not be difficult, maybe it could be automated. > > But the combinat repo would have many branches, and rebasing these > would be the responsibility of their owners. If there is a branch on partitions and a branch on tableaux, someone might be interested in merging them. So I guess we could also keep merged branches in the combinat repository. I discussed some of these issues already tonight with Mike and Mathieu and we seem mostly in agreement on what to do. Best, Anne -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
