[Evergreen-dev] Code organization

[Jason Boyer]

I can see some value in dropping them in a contrib repo or a contrib/ dir in the main repo; namely you always know where to go for the latest versions and where to submit improvements. I know there were at least 2-3 different versions of the CollectionHQ scripts around because at one point I customized some things for EGIN and I'm not sure if all of those changes made it back to the main repo. I also told CHQ "no" to a few requested changes for patron privacy reasons, which is an easier thing to do more consistently in a community repo.

Jason

-- 
Jason Boyer
Senior System Administrator
Equinox Open Library Initiative
JBoyer at equinoxOLI.org
+1 (877) Open-ILS (673-6457)
https://equinoxOLI.org/

> On Dec 22, 2022, at 9:57 AM, Rogan Hamby via Evergreen-dev <evergreen-dev at list.evergreen-ils.org> wrote:
> 
> The Wiki page would be the lowest hanging fruit and I suspect useful even if everything was gathered into one git repo to rule them all in and in the cloud bind them.  I can easily imagine not-git inclined people using the wiki to research and then point more technically inclined colleagues to.  This is an example of what I imagine for it https://wiki.evergreen-ils.org/doku.php?id=library:export_scripts
> 
> Does that negate the value of a unifying repo?  I don't think so.  But, at least at this moment, I don't have strong feelings about gathered versus dispersed. My internal question goes back to a question that was raised in IRC of, if they are worth gathering into a central repo for community use should they just go into the distribution?  If it's a more laissez faire approach is the wiki page enough?
> 
> 
> 
> 
> 
> On Wed, Dec 21, 2022 at 5:43 PM Blake Henderson via Evergreen-dev <evergreen-dev at list.evergreen-ils.org <mailto:evergreen-dev at list.evergreen-ils.org>> wrote:
>> All,
>> 
>> I brought up an agenda item at today's dev meeting. I was wondering 
>> where I should put my project.
>> 
>> http://irc.evergreen-ils.org/evergreen/2022-12-13#i_517622
>> 
>> And it brought up a greater discussion of having more of an "official" 
>> repo/place/something for "all things export".
>> 
>> Does anyone have an opinion on where we as a community should be putting 
>> such things? I know there are several repos on Github, and some inside 
>> of sub-folders within various contrib repos.
>> 
>> It's probably a tall order to get everyone to put this stuff in a single 
>> place, so, at the very least, we could probably use a wiki page with 
>> links and descriptions to all the places where all the useful code lives
>> 
>> -- 
>> -Blake-
>> Conducting Magic
>> Will consume any data format
>> MOBIUS
>> 
>> _______________________________________________
>> Evergreen-dev mailing list
>> Evergreen-dev at list.evergreen-ils.org <mailto:Evergreen-dev at list.evergreen-ils.org>
>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev
> _______________________________________________
> Evergreen-dev mailing list
> Evergreen-dev at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-dev/attachments/20221222/f300397a/attachment.htm>