Hi Jon,
I want to register for:
MacOSX build, test and package
Raspberry Pi (Raspian) test and build
z/OS build and test - I have the machine now so we can start
It might be good if we could get into repositories, like apt-get, yum for the
different Linux distributions and instruction set architectures and for the
Mac, mac brew and mac ports. Mark H might know how to do this, as I can install
Regina for all of them. I know Bruce did a lot of work on Mac installers (after
I did that earlier) and Rony’s students also did some Mac installers - we
should get a 4.2.X installer online quickly. For the non-windows versions (that
cannot run ooDialog) I suggest we include BSF4ooRexx as stopgap. I would not
hurt for the windows installers, either.
best regards,
René.
> On 13 apr. 2015, at 18:38, Jon Wolfers <[email protected]> wrote:
>
> Thanks Michael and Erich,
>
> It's good to get the ball rolling.
>
> I've seen another omission to the list which is ooDialog - although we will
> later have to have some decisions about what to do with ooDialog, it is
> important to many of our users so I've added it to the list.
>
> I've put Erich and Michael's name next to the items that they have expressed
> interest in, but that should not prevent others from coming forward for the
> same items - no one is committed yet and many hands make light work.
>
> Erich, thank you for your offer of funds - I believe that RexxLa provided a
> machine for the builds, but that died some time ago, and David was kindly
> hosting the build machine on his own hardware, which he was no doubt eager to
> reclaim. The RexxLa board had a chat about this last week and think they
> have sufficient funds to host a future build machine on a leased server in a
> proper server farm. I believe David is going to send a zip of the code.
>
> One other thing I forgot to mention this morning was that I asked Les to
> administer the ooRexx mailing lists as he was keen to contribute.
>
> Here is the table now, hopefully I'm not misunderstanding or misrepresenting
> anyone's interest.
>
> A - The interpreter itself
> B - Linux expert
> C - Windows expert
> D - Project Lifecycle administrator
> E - Installer expert Michael
> F - Builds Michael (Linux)
> G - The test framework Erich
> H - The test suite (the actual tests written using the test framework)
> Erich (5.0)
> I - The documentation processing (Docbook). Erich (5.0 RexxRef)
> J - ooDialog
>
> thanks,
>
> Jon
>
>
> On 13 April 2015 at 12:47, Erich Steinböck <[email protected]
> <mailto:[email protected]>> wrote:
> G - The test framework
> H - The test suite (the actual tests written using the test framework)
> I - The documentation processing (Docbook).
>
> I'd be willing contribute with the following -
> document 5.0 features for ooRexx Reference
> write any needed test cases
> dive into the test framework (though I haven't yet had any look at it)
> (Any detailed hints regarding above are very welcome, e.g. what and how
> exactly needs to be installed for DocBook in a Windows environment)
>
> I'd also be willing to participate in any running costs we have, like, if
> maybe cost has been the reason why the build machine was shut down
>
> Erich
>
> On Mon, Apr 13, 2015 at 11:56 AM, Jon Wolfers <[email protected]
> <mailto:[email protected]>> wrote:
> Thanks Rick,
> Absolutely agree - New list (complete with letters):
>
> A - The interpreter itself
> B - Linux expert
> C - Windows expert
> D - Project Lifecycle administrator
> E - Installer expert
> F - Builds
> G - The test framework
> H - The test suite (the actual tests written using the test framework)
> I - The documentation processing (Docbook).
> Jon
>
>
> On 13 April 2015 at 10:48, Rick McGuire <[email protected]
> <mailto:[email protected]>> wrote:
> Some additional major areas:
>
> The test framework
> The test suite (the actual tests written using the test framework)
> The documentation processing (Docbook).
>
> Rick
>
> On Mon, Apr 13, 2015 at 3:43 AM, Jon Wolfers <[email protected]
> <mailto:[email protected]>> wrote:
> BCC: RexxLa Board
>
> Dear Developers,
>
> whilst I in no way wish to cut short the thanks to Rick and David - and
> goodness, they deserve it, I think the time has come to at least start a
> conversation about the future of the project.
>
> Rick and David and Mark covered all the bases, but it was a stretch for them,
> and they often wished that they received more assistance. It is not entirely
> clear what the future holds, but Rick and David have both said that whilst
> they are happy to advise, their period of doing the work is over.
>
> That means that if ooRexx is to remain a live project we are going to have to
> come up with people with the skills who are happy to do the things that need
> to be done, either from within our own ranks or from the Rexx community.
> Whether or not this is possible is what I want to ascertain over the next
> months.
>
> For myself, I have few of the technical attributes required for administering
> or even developing this project, but I am a seasoned user of ooRexx and I
> appreciate what a thing of beauty it is, and would like to carry on doing
> whatever I can to keep it alive. No-one wants to be tied to something very
> demanding if it turns out to be doomed to fail, so I am saying that I will
> give this a year and then review it. I definitely see myself as holding the
> position against the day that someone better equipped comes along.
>
> It seems to me that there are several major areas that we need active
> participants in:
> The interpreter itself
> Linux expert
> Windows expert
> Project Lifecycle administrator
> Installer expert
> Builds
> Perhaps there are other areas. I would welcome people coming forward, even
> if only to make tentative commitments in these areas. That will give us some
> idea of how ambitious or unambitious we need to be.
>
> Rick and David are no longer project administrators. I was unhappy with the
> idea of being the only administrator, so I asked Les Koehler from rexxLa to
> take on an administrative role, much as one might give a key to your next
> door neighbour for safe keeping - he is our safe pair of hands. I would like
> in time for most if not all committers to share the administration role, but
> we must see what emerges.
>
> There are some big questions to answer, particularly concerning ooRexx 5.0
> and ooDialog, but I think it would be helpful to review who we have on board
> and who we can find before attempting to put together a strategy.
>
> Let the conversation commence...
>
> Jon
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> <http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Oorexx-devel mailing list
> [email protected] <mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel>
>
>
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> <http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Oorexx-devel mailing list
> [email protected] <mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel>
>
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______________________________________________
> Oorexx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
