Sounds great. I’ll send poll out on Monday.

*Ruth Frasur Davis, Coordinator*
*Evergreen Collaborative Development Initiative*
https://evergreencdi.org
(765) 580-1137


On Fri, May 9, 2025 at 4:37 PM Bill Erickson <[email protected]> wrote:

> Hi All,
>
> Thanks for the feedback!  So glad to see there's interest.
>
> Ruth, with many thanks, I will take you up on your offer to schedule a
> meeting.
>
> I'll put together some talking points for an intro session, but of course
> if anyone has any particular topics or questions in mind, I'm all ears.
>
> Thanks,
>
> -b
>
> On Fri, May 9, 2025 at 11:45 AM Ruth Davis via Evergreen-dev <
> [email protected]> wrote:
>
>> Bill,
>>
>> If you'd like, I can begin the process of scheduling an introductory
>> meeting for this group.
>>
>> *Ruth Frasur Davis, Coordinator*
>> *Evergreen Collaborative Development Initiative*
>> https://evergreencdi.org
>> (765) 580-1137
>>
>>
>> On Fri, May 9, 2025 at 10:14 AM Stephanie Leary via Evergreen-dev <
>> [email protected]> wrote:
>>
>>> I am also interested, but my time is exceedingly limited at the moment.
>>>
>>> Stephanie Leary
>>> Front End Developer
>>> Equinox Open Library Initiative
>>> [email protected]
>>> https://www.equinoxOLI.org
>>> phone: 877-OPEN-ILS (673-6457)
>>>
>>>
>>> On Fri, May 9, 2025 at 8:10 AM Mike Rylander via Evergreen-dev <
>>> [email protected]> wrote:
>>>
>>>> Can't fight the future, right? I'm interested in being dragged into
>>>> the (a?) modern era. :)
>>>>
>>>> --
>>>> Mike Rylander
>>>> Research and Development Manager
>>>> Equinox Open Library Initiative
>>>> 1-877-OPEN-ILS (673-6457)
>>>> work: [email protected]
>>>> personal: [email protected]
>>>> https://equinoxOLI.org
>>>>
>>>> On Wed, May 7, 2025 at 1:30 PM Bill Erickson via Evergreen-dev
>>>> <[email protected]> wrote:
>>>> >
>>>> > Hi All,
>>>> >
>>>> > I've been learning and working with Rust [1] a lot over the last few
>>>> years.  What started as an educational journey has evolved into building
>>>> working code, as I've ported various OpenSRF and Evergreen components to
>>>> Rust.  We're now using this code more and more at KCLS and it's been going
>>>> well.  (Migration notes:
>>>> https://github.com/kcls/evergreen-pub/wiki/KCLS-Rust-Migration).
>>>> >
>>>> > I've found Rust to be fast, capable, and a joy to work with once you
>>>> learn the basics.  And of course, there's the growing popularity [2].
>>>> >
>>>> > I'm writing today to see if there's any interest in forming a Rust
>>>> working group within the Evergreen community to learn the language and
>>>> potentially assess the viability of adding Rust to Evergreen as a supported
>>>> language.
>>>> >
>>>> > I propose starting with a limited duration series of meetings, maybe
>>>> 6 months.  We can use that time to cover the basics and reassess from 
>>>> there.
>>>> >
>>>> > I would also be seeking assistance/guidance in setting up and running
>>>> such a group, at least initially, since it's not something I've done 
>>>> before.
>>>> >
>>>> > Let me know if anyone's interested.
>>>> >
>>>> > Thanks,
>>>> >
>>>> > -b
>>>> >
>>>> > [1] https://www.rust-lang.org/
>>>> > [2]
>>>> https://github.blog/developer-skills/programming-languages-and-frameworks/why-rust-is-the-most-admired-language-among-developers/
>>>> >
>>>> > _______________________________________________
>>>> > Evergreen-dev mailing list -- [email protected]
>>>> > To unsubscribe send an email to
>>>> [email protected]
>>>> _______________________________________________
>>>> Evergreen-dev mailing list -- [email protected]
>>>> To unsubscribe send an email to
>>>> [email protected]
>>>>
>>> _______________________________________________
>>> Evergreen-dev mailing list -- [email protected]
>>> To unsubscribe send an email to
>>> [email protected]
>>>
>> _______________________________________________
>> Evergreen-dev mailing list -- [email protected]
>> To unsubscribe send an email to
>> [email protected]
>>
>
_______________________________________________
Evergreen-dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to