Timeline for Best practices for sharing tiny snippets of code across projects
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 30, 2013 at 18:24 | comment | added | pdr | Oh, I see. Yeah, you can definitely put whatever you like in the description and that becomes searchable, but I think we've grouped the packages well enough that it doesn't seem to be a problem. | |
| Mar 30, 2013 at 18:16 | comment | added | Kofi Sarfo | Ah, yes. Those too. By issues around discover-ability I mean that given a sufficient number of little packages with specific function maybe it becomes more difficult to catalogue (and find) each. For example, how does your team make known which packages contain various functions? (showing nuget search ignorance here) | |
| Mar 30, 2013 at 16:09 | comment | added | pdr | In what sense do you expect them not to be discoverable? We use a large, and growing, number of nuget packages in that way. The biggest issue we have is with managing versioning and dependencies. | |
| Mar 30, 2013 at 15:07 | history | answered | Kofi Sarfo | CC BY-SA 3.0 |