<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
All,<br>
<br>
I created a new page on the wiki:<br>
<br>
<a class="moz-txt-link-freetext" href="https://wiki.evergreen-ils.org/doku.php?id=dev:auxiliary_supplementary_code">https://wiki.evergreen-ils.org/doku.php?id=dev:auxiliary_supplementary_code</a><br>
<br>
I've seeded it with some links that I could remember (most of them
are ours). Please amend/supplant with any and all links to other
Evergreen-code!<br>
<br>
I do like the idea of corralling all of these things into a single
place on the internet. Github? These things get unorganized and
slammed into a single repo (for me) and probably deserve their own
repo. Wouldn't it be cool if we had a single repo with sub folders
for each of the main ideas (import, export)?<br>
<br>
But this page is the next best thing.<br>
<br>
<pre class="moz-signature" cols="72">-Blake-
Conducting Magic
MOBIUS</pre>
<div class="moz-cite-prefix">On 12/22/2022 9:10 AM, Jason Boyer
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:8B189A65-C412-4EB3-BF40-8878456F9974@equinoxOLI.org">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
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.<br>
<div>
<meta charset="UTF-8">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0,
0, 0); letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal; word-spacing:
0px; -webkit-text-stroke-width: 0px; text-decoration: none;
word-wrap: break-word; -webkit-nbsp-mode: space; line-break:
after-white-space;">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color:
rgb(0, 0, 0); letter-spacing: normal; text-align: start;
text-indent: 0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none; word-wrap: break-word;
-webkit-nbsp-mode: space; line-break: after-white-space;">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color:
rgb(0, 0, 0); letter-spacing: normal; text-align: start;
text-indent: 0px; text-transform: none; white-space:
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none; word-wrap: break-word;
-webkit-nbsp-mode: space; line-break: after-white-space;">
<div><br>
</div>
<div>Jason</div>
<div><br>
-- <br>
Jason Boyer<br>
Senior System Administrator<br>
Equinox Open Library Initiative<br>
<a class="moz-txt-link-abbreviated" href="mailto:JBoyer@equinoxOLI.org">JBoyer@equinoxOLI.org</a><br>
+1 (877) Open-ILS (673-6457)<br>
<a class="moz-txt-link-freetext" href="https://equinoxOLI.org/">https://equinoxOLI.org/</a></div>
</div>
</div>
</div>
</div>
<div><br>
<blockquote type="cite">
<div>On Dec 22, 2022, at 9:57 AM, Rogan Hamby via
Evergreen-dev <a class="moz-txt-link-rfc2396E" href="mailto:evergreen-dev@list.evergreen-ils.org"><evergreen-dev@list.evergreen-ils.org></a>
wrote:</div>
<br class="Apple-interchange-newline">
<div>
<div dir="ltr">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 <a
href="https://wiki.evergreen-ils.org/doku.php?id=library:export_scripts"
moz-do-not-send="true" class="moz-txt-link-freetext">https://wiki.evergreen-ils.org/doku.php?id=library:export_scripts</a>
<div><br>
</div>
<div>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?</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Dec 21, 2022 at
5:43 PM Blake Henderson via Evergreen-dev <<a
href="mailto:evergreen-dev@list.evergreen-ils.org"
moz-do-not-send="true" class="moz-txt-link-freetext">evergreen-dev@list.evergreen-ils.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">All,<br>
<br>
I brought up an agenda item at today's dev meeting. I
was wondering <br>
where I should put my project.<br>
<br>
<a
href="http://irc.evergreen-ils.org/evergreen/2022-12-13#i_517622"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">http://irc.evergreen-ils.org/evergreen/2022-12-13#i_517622</a><br>
<br>
And it brought up a greater discussion of having more of
an "official" <br>
repo/place/something for "all things export".<br>
<br>
Does anyone have an opinion on where we as a community
should be putting <br>
such things? I know there are several repos on Github,
and some inside <br>
of sub-folders within various contrib repos.<br>
<br>
It's probably a tall order to get everyone to put this
stuff in a single <br>
place, so, at the very least, we could probably use a
wiki page with <br>
links and descriptions to all the places where all the
useful code lives<br>
<br>
-- <br>
-Blake-<br>
Conducting Magic<br>
Will consume any data format<br>
MOBIUS<br>
<br>
_______________________________________________<br>
Evergreen-dev mailing list<br>
<a href="mailto:Evergreen-dev@list.evergreen-ils.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">Evergreen-dev@list.evergreen-ils.org</a><br>
<a
href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev</a><br>
</blockquote>
</div>
_______________________________________________<br>
Evergreen-dev mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Evergreen-dev@list.evergreen-ils.org">Evergreen-dev@list.evergreen-ils.org</a><br>
<a class="moz-txt-link-freetext" href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev</a><br>
</div>
</blockquote>
</div>
<br>
</blockquote>
<br>
</body>
</html>