style: update billinge email

[cadenmyers13]

No description provided.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 52.63%. Comparing base (c7f7b8c) to head (1d27a4b).
Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #247   +/-   ##
=======================================
  Coverage   52.63%   52.63%           
=======================================
  Files           2        2           
  Lines          19       19           
=======================================
  Hits           10       10           
  Misses          9        9           

[sbillinge]

These should be templated. Let's loop in Bob

[bobleesj]

@sbillinge @cadenmyers13

yes lgtm. the modification is in cookiecutter.json so the new email (correct) will be all templated throughout once a new proj is created running scikit-package.

[sbillinge]

@sbillinge @cadenmyers13

yes lgtm. the modification is in cookiecutter.json so the new email (correct) will be all templated throughout once a new proj is created running scikit-package.

Ah, I see, these are the user prompts. I think we should maybe remove my name from these altogether perhaps, and use more generic exemplar names?

[sbillinge]

On the other hand, if we are the main users of this, having defaults that work for us would be good.

How about an infrastructure where we can have a config.json file where you can define local defaults?

[bobleesj]

@sbillinge

I think we should maybe remove my name from these altogether perhaps

I think having specific examples can indeed help reduce cognitive overload and for the email, it provides a sense of who is currently maintaining and developing this software as a contact point.

How about an infrastructure where we can have a config.json file where you can define local defaults?

We could try to see if this approach works and whether we can import information into cookiecutter.json from another file. This will be actually semi-required for package update to be seamless.

[bobleesj]

@sbillinge created issue #248. This can be addressed while also addressing #237 (package update)

If we are okay with the default values of sbillinge info, this PR could be merged.

[sbillinge]

@bobleesj in light of your comments, maybe we can leave my name there in general. I agree that a specific example is better than a generic one. But I also like the idea of a local config option. I could imagnie the "Bob Lee Group" in the future and you would much rather Bob Lee is the default than Simon Billinge for you and all your students.......

[bobleesj]

Yes agreed!