Fork of strucchange?

[GreatEmerald]

So far we didn't have a big need to change the code of strucchange, but I'm slowly but surely finding more and more bugs there as well, so a fork may be inevitable. In that case, we'll also need to do #35 also for the new fork, so should we fork it sooner rather than later?

Also, should we do the same for strucchange as we have for bfast with the contributor guidelines etc.? And what about new CRAN releases for strucchange?

[GreatEmerald]

Alternatively, perhaps it should just be moved here from @appelmar. What do you think?

[appelmar]

I've transferred the ownership of the repository to the bfast2 organization, so all members should have commit rights now. In any case, we should also think about either contributing our modifications back to the original strucchange package, or moving new functions and modifications to the bfast package. Otherwise it might be difficult to update bfast on CRAN.

[GreatEmerald]

OK, that seems to have worked fine, thanks a lot!