Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upFile per meeting, or another format #4
Comments
This comment has been minimized.
This comment has been minimized.
both are right :) but if this sticks around, merges will get less frequent and easier over time |
This comment has been minimized.
This comment has been minimized.
Surely they'd get more frequent, since each meeting will have to have its |
This comment has been minimized.
This comment has been minimized.
But that will be spread over a full year |
This comment has been minimized.
This comment has been minimized.
That's fair. I'm not sure I can think of a good alternative that wouldn't become limiting later[1] and that isn't just "put bunches of stuff in arbitrary files", or "group by initial", though. And I think small files are nicer for editing and for probably for letting people see how to do new submissions, too. [1] For example: if you box by category, you get into some very blurry areas and you probably just want to have (multiple) tags for particular meeting interests anyway if that's a categorisation exercise you want to get into. (Non-specific you.) |
This comment has been minimized.
This comment has been minimized.
Yeh, I thought about one file per category, then I decided that'd just results in disputes over categorisation and/or lack of ability to find things when you disagreed over category with the contributor. So I don't like that idea. |
jamespjh commentedOct 2, 2019
@danielskatz suggests one-file-per-meeting is annoying.
@jamespjh thinks one-file-per-meeting is better for merges.
Comments?