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
Consider unifying some/many task-specific files #9
Comments
I would prefer the merged version as well. As you said it is easier to browse through. Frequency of contributing is much smaller than reading through. |
Cool. Any more opinions? |
Given the pace that new tasks and new results are being added (which is awesome!), I'm a bit more concerned now that a single page will both become unwieldy and at some point also less clear pretty quickly. In light of that, I think I'm in favour of the current format. |
Perhaps a twitter poll? My one last pitch here. IMO, as-is, I'll have a hard time coming back and re-visiting this resource. There are many other ways to alleviate this, to provide better searchability etc., but it is hard to beat single file plus grep (ctrl+f), without a bunch of work. I'm not entirely unique, but perhaps we are a minority. :) Last alternate, somewhat simple thought--
|
Cool, yeah, I just wanted to voice my current sentiment. I can definitely still be swayed. :) |
Sorry, that was clearly confusing! Those were a single idea:
|
In response to #6:
For me: Having a single README (or, potentially, at least a smaller number than we have now) makes it easier (for me) to skim through all numbers, papers, results, etc.
Request to open for discussion:
Opening this for discussion at request of @sebastianruder .... polling community to see what would be easiest.
I will concede that in the long run, either way, there may be a pressure to split things back up (as tasks & papers accumulate), but my (personal!) leaning would be to keep things merged, for now, and then split things back up at some future point.
The text was updated successfully, but these errors were encountered: