Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Misc notes on paper building process. #687

Open
Carreau opened this issue May 18, 2022 · 3 comments
Open

Misc notes on paper building process. #687

Carreau opened this issue May 18, 2022 · 3 comments

Comments

@Carreau
Copy link

Carreau commented May 18, 2022

These are some misc notes on collaborating with someone to write one of the proceeding.

  1. I think the rst file should be removed from the output folder after build, or renamed. Reason begin there is a non zero risk for someone to start editing the things in output/build/paper.rst, and loose work later. 😭

  2. the default branch not being named main (or master), seem to be confusing.

Thanks !

@deniederhut
Copy link
Member

the default branch not being named main (or master), seem to be confusing.

The logic there is that we have a different branch for each year of the conference, and that this keeps giant clumps of paper paraphernalia (like pngs) out of the dev, the development branch. I would be happy to chat with you about more clever ways of achieving these goals.

I think the rst file should be removed from the output folder after build, or renamed.

Yup. We do have a make clean target, but that's probably not sufficient.

@Carreau
Copy link
Author

Carreau commented May 27, 2022

The logic there is that we have a different branch for each year of the conference, and that this keeps giant clumps of paper paraphernalia (like pngs) out of the dev, the development branch. I would be happy to chat with you about more clever ways of achieving these goals.

What about renaming master/main or whatever once the proceeding is published, so that at least during the submission period, it's a name that is commonly used ?

@deniederhut
Copy link
Member

Not a bad idea -- I'll bring it up with the committee

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants