Move PFValidation development to new fork? about cmssw

[hatakeyamak]

Good question.

I probably personally perfer merging it to the central CMSSW.
It helps to keep track of potential necessary modifications due to releaese updates.
We can do this merging when the development is relatively stable.

[jpata]

OK. So after the eventual merge to central CMSSW, any future updates to the PF/DQM code would also be done in private forks, followed up by central merges? I guess that's fine, too.

[hatakeyamak]

That's what I have in mind. We can make something like:
https://github.com/cms-btv-pog
but probably should wait until the re-organization is over.

[hatakeyamak]

I talked about this with @bendavid, and we thought, as long as the eventual developments go to CMSSW, we don't really need such group github. We can continue our current work scheme. Does it sound ok? We have been using jpata often as common place to develop a branch, @jpata you might have something more to say on this.

[jpata]

OK. I'm a little uncomfortable having central PF developments in my personal cmssw repo due to a possibility of mistakes, but as long as we don't nuke each others branches (like someone overwriting my master branch) it's ok.

[hatakeyamak]

Okay. I understand.

Well, apart from using your repo for issues, we can gradually move toward using our own repo. The first branch was highly collaborative and using your repo together was helpful, but from now on, I expect smaller incremental changes, so using a common repo won't be so necessary.

Thank you.