Apache River - My Lowly Impression
First off let me say I am a huge fan of Apache River, and its predecessor Jini. I even have a Jini leather jacket. :-) I think this technology has a lot of potential to do some amazing things especially in my area of interest, distributed computing. I think the people who are working as developers on this project have done an amazing job. That being said great technology all the time does not mean that it will be used or even noticed. I think River is lacking in certain areas that has nothing to do with the programming, or the ideas behind it. The following list of things is not meant to assign blame to anyone, or anything. These are just things that I think need to be addressed in my very humble opinion. 1. *Accessibility* River is an incredible concept, but the conceptual ideas can be daunting to people starting out with it. I think explaining the concepts by using real world examples, this could attract more people and make River more approachable. As an example I found the explanation behind the MapReduce incredibly easy and I was able to get a system setup, tested, and run in a few hours. It provided some great examples, as well as explained why they worked. Furthermore it explained some real world cases for using it, such as log querying. Increasing the ease of people approaching Jini will probably increase the number of people/companies who want to be involved in it. I would love to start playing around with River but I don't know how to start. The "Getting Started" page says that I need to check out the code from SVN trunk, and build it myself. Has this changed? 2. *River Site* The site itself doesn't provide much information about the project except that it has been released. When I explore a little deeper I noticed some broken links to sites including the links to original Jini documentation, and the link to Jan Newmarch Jini tutorial is broken. This directly impacts the first impression that people get when they are looking into River. Is anyone in charge of the site? 3. *Roadmap* What is the future of River? What is the overall goal of each point release. What about goals for major releases? I think if we come to a general consensus on what are goals are we can move forward together as a group of programmers since we all know where we are heading. 4. *Mission* One of the overall thoughts I have had while reading the correspondence in the group is that I don't know what the mission is? I know the group is to continue the development and advancement of Jini technology but that is a very broad and generic statement. Does this group want to help people implement the technology, only work on the specifications, what level in the tech stack does River start and stop, or is some combination of all of these? Are any of these things the group as a whole interested in implementing? What are your feeling on this? As a side question: Could something like the Hadoop YARN be implemented using River? -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: New Chair for Apache River PMC
While I enjoy River I think that shelving it as is may be the best option. I think this project may have run its course in its current state and this doesn't encourage new development or interest in participating in the project. However, I would like to present a strawman proposal to the group. The current committers put out a last maintenance release fixing any bugs that may have been been resolved but not yet released. After that the 2.* branch is abandoned. At that point the River community decides if it is possible and worthwhile to start over from scratch. We begin this new project from day 1 with deciding what we want to accomplish, and how we accomplish. No code is written until a good set of requirements are written and voted upon. We keep the development community in mind and make sure that River 3.0 is approachable from scratch. While this may take more time and at times probably be very tedious at times I think it gives the project a fresh start and not be beholden to old code, and requirements. Just my 2 cents on the subject. ~Jeremy On Mon, May 12, 2014 at 8:59 AM, Greg Trasuk wrote: > > On May 11, 2014, at 12:30 AM, Peter wrote: > > > > > > > Ultimately, if community involvement continues to decline, we may have > to send River to the attic. > > > > Distributed computing is difficult and we often bump into the > shortcomings of the java platform, I think these difficulties are why > developers have trouble agreeing on solutions. > > > > But I think more importantly we need increased user involvement. > > > > Is there any advise or resources we can draw on from other Apache > projects? > > > > It may be, ultimately, that the community has failed and River is headed > to the Attic. The usual question is “Can the project round up the 3 ‘+1’ > votes required to make an Apache release?” Historically, we have been able > to do that, at least for maintenance releases, and I don’t see that > changing, at least for a while. > > The problem is future development and the ongoing health of the project. > On this point, we don’t seem to have consensus on where we want the > project to go, and there’s limited enthusiasm for user-focused > requirements. Also, my calls to discuss the health of the project have had > no response (well, there was a tangent about the build system, but > personally I think that misses the point). > > I will include in the board report the fact that no-one has expressed an > interest in taking over as PMC chair, and ask if there are any other expert > resources that can help. > > Cheers, > > Greg Trasuk. -- Jeremy R. Easton-Marks "être fort pour être utile"
RE: [VOTE] Patricia Shanahan for PMC Chair
+1 On May 19, 2014 7:33 AM, "Bishnu Gautam" wrote: > > +1 thenFrom Bishnu > > Bishnu Prasad Gautam > > > > Date: Mon, 19 May 2014 21:19:38 +1000 > > From: j...@zeus.net.au > > To: dev@river.apache.org > > Subject: [VOTE] Patricia Shanahan for PMC Chair > > > > Come on people, we need at least three votes to nominate a new Chair. > > > > Lets give this project one last shot. > > > > Tom & I have already voted in favour. > > > > Peter. >
Re: Time to retire from Apache
Hi Peter, Thank you for all your guidance and support of the Apache River project. I understand your position and respect it. As someone who is a fan and user of that project and the concept of free speech I also feel torn. I hope you will consider contributing and supporting the Apache River project again in the future. I know the project will welcome you back. Jeremy R. Easton-Marks On Tue, Feb 23, 2021 at 4:21 PM Peter Firmstone wrote: > Hello River folk, > > Recently the Apache board cancelled a PMC member / founder of another > Apache project, for posts on Twitter, no doubt this will become public > knowledge in the near future. I am personally in favor of free speech, > regardless of whether it's offensive or whether I agree or disagree, I > have voluntarily cancelled my membership, no doubt this will be of > little significance to an organization as large as Apache, but I > wouldn't feel comfortable turning a blind eye. Apache is free to make > decisions about who it wants participating and I am not about to argue > with that. The person in question appeared to be making a political > statement against cancel culture by publishing deliberately offensive > speech and has been cancelled by Apache as a result, I guess that > shouldn't be a surprise. We used to have some heated discussions on > River's mailing lists, at no time, would I have considered cancelling > someone with whom I disagreed, I would debate till the cows came home, > but never cancel another contributors voice. I appreciate the > contributions and participation of everyone who is part of the River > community, however I think the project is likely long overdue for a new > chair to lead, and it is time for people to discuss and nominate someone > they think is most suited to take care of the River community. > > Today I retire from my role as River PMC Chair and volunteer development > work for Apache. > > I wish you all well and hope to see you in future. > > -- > Regards, > > Peter Firmstone. > > -- Jeremy R. Easton-Marks "être fort pour être utile"
New Interim / Full-Time Apache River Chair
All, With the resignation of our PMC Chair Peter Firmstone we find ourselves without a leader. I am not sure of the proper procedure for nominating a new one but I would rather get it wrong and show effort then let this project fade into darkness and be shut down. The Apache River project faces a couple of big decisions and projects on going and coming up. A couple of these were mentioned in the Project Health / Interest email chain. 1. SVN to Git Migration 2. Website Migration 3. Moving to module builds, possibly with gradle. I would also like to add a 4th, does Apache River have a path forward or should it be sunsetted? If it does, what is that path forward? How does Apache River fit into the future of computing? Would anyone like to step up as the Chair in either an interim or full-time basis? Also if anyone knows how to formally/officially do this that would be great. :-) -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: Serializing data in River
I think this would be an interesting path to explore. I like the idea of being able to write in other languages. It could increase the approachability of River, especially in the IOT field. Would this mean completely abandoning the lookup service? How do you think we should explore this more? On Fri, Mar 5, 2021, 1:28 PM Gregg Wonderly wrote: > I don’t recall if we’ve talked about Google Protocol Buffers as another > means of serialization. This seems like something that could be > investigated as a gateway to support for many other languages/platforms > that already have such support. > > https://developers.google.com/protocol-buffers < > https://developers.google.com/protocol-buffers> > > > Gregg Wonderly
Re: Serializing data in River
Hi Phil, Can you elaborate a little bit on how you use JavaSpaces in AI Blackboard system space? I think having some examples might help us better flesh out this idea. I am also just curious from a research perspective. :-) On Sun, Mar 7, 2021 at 4:05 PM Phillip Rhodes wrote: > On Sun, Mar 7, 2021 at 1:40 PM Bryan Thompson > wrote: > > I agree that making River relevant to non java ecosystems would be a good > > idea. > > +1 > > Just to share one anecdote, a lot of my interest in River relates to > using the JavaSpaces stuff, and experimenting with Blackboard systems, > with an eye towards applications in AI. And while a lot of my work is > done on the JVM (Java/Groovy, mostly), the idea of being able to > easily integrate a sub-system written in, say, Python or C++ or Julia > or $WHATEVER, is very appealing. > > Phil > -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: Call for PMC volunteers for Apache River
I'd be interested in joining the Apache River PMC. On Thu, Mar 11, 2021 at 5:29 PM Roy T. Fielding wrote: > Hello again, > > The River project seems to be short on PMC members, which is a > problem for Apache projects because we require at least three active > PMC members to continue. > > This is a call for volunteers. If you would like to be on the River PMC > and have demonstrated some form of contribution to the project > (via email, bug reports, documentation, testing, teaching, etc.), > please respond to this message. It doesn't have to be a huge > contribution -- just enough to show that your heart is in the right > place and you are willing to contribute. > > After we collect a list of volunteers (if any), I will ask the board to > consider a resolution to recreate the PMC from that list, plus > Patricia Shanahan and Bryan Thompson (who have already > volunteered to continue on the PMC). > > Cheers, > > Roy T. Fielding > Board Chair, The Apache Software Foundation > > -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: Serializing data in River
This could be really interesting. Just thinking quickly I could see using the JavaSpaces Primary(Master)-Worker being used. Where the Primary hands out work for each of the workers to work on their part of the problem with the primary being the integrator. As you mentioned getting a shared data model representing the knowledge would be the difficult part and solutions may be best done on a domain-specific basis. Would something like the below work as a proof of concept? *Problem Description* Annotation of an image with multiple workers in which each worker is specialized in a specific type of "recognition" (e.g., Dogs, People, Cars) *Flow* 1) A Primary sends out the image data to each worker. 2) Each Worker analyzes the image for it's specific type of recognition. 3) Each Worker sends back the location and type of object it detects back to the Primary 4) The Primary then analyzes the information and interprets the image *Google Protocol-Buffer Portion* - The Workers broadcast what they are capable of using a neutral format - All data is sent in Google Protocol Buffer Format - Individual Workers can translate the data into whatever language they run - Workers send back data in a similar format to a Primary that can use in its language On Fri, Mar 12, 2021 at 3:30 PM Phillip Rhodes wrote: > > Hi Phil, > > Can you elaborate a little bit on how you use JavaSpaces in AI Blackboard > > system space? I think having some examples might help us better flesh out > > this idea. I am also just curious from a research perspective. :-) > > Only in a conceptual sense. I haven't written any code to this end > yet. Not knowing how familiar anyone reading this post will be with > the basic idea of Blackboard Systems (or even Tuple Spaces as far as > that goes) I'll share these two links first: > > https://en.wikipedia.org/wiki/Blackboard_system > https://en.wikipedia.org/wiki/Tuple_space > > So my interest is in using Java Spaces as the "shared space" where the > "experts" (eg, "agents" in another vernacular) share information. The > devil, of course, is in the details. One big "detail" is working out > what the representation of "knowledge" put into the blackboard should > be. Something really fine-grained like RDF style triples could be an > option, but there are all sorts of knowledge representation languages. > And that's assuming you want something symbolic. An even deeper > question gets into how you might integrate symbolic / sub-symbolic > agents in a model like this. Unfortunately I have more questions than > I do answers. But generally speaking, this kind of "stuff" is where a > lot of my interest lies. > > > Phil > -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: Your project website
Hi Andrew, Who should we reach out to on the Infra team? What type of investment in time/resources do you estimate it would take to switch over? ~Jeremy On Thu, Feb 4, 2021 at 3:07 PM Peter Firmstone wrote: > Thanks Andrew, > > Which option is the fastest path / least work required for transition? > I don't have time to look into each option, so any such advise will be > much appreciated. > > Regards, > > Peter. > > On 4/02/2021 10:57 pm, Andrew Wetmore wrote: > > Hi: > > > > We were hoping to have all projects migrated by the end of last year. > There > > are still a number using the Apache CMS, and we have not set a hard > > deadline for shutting it down. However, the system is becoming less > > reliable, so moving sooner rather than later is probably a good idea. > > > > Andrew > > > > On Wed, Feb 3, 2021 at 8:08 PM Peter Firmstone < > peter.firmst...@zeus.net.au> > > wrote: > > > >> Thanks Andrew, > >> > >> What's the timeframe for migration? > >> > >> Regards, > >> > >> Peter. > >> > >> On 1/02/2021 11:55 pm, Andrew Wetmore wrote: > >>> Hi, and happy New Year! > >>> > >>> I know you folks are busy with your svn-to-git migration, but I wanted > >> to bring up again the need to migrate your website off the Apache CMS. > >> Please let me know what your plans are, and whether you need help from > >> Infra. > >>> Andrew Wetmore > >>> > >>> On 2020/08/10 10:39:31, Zsolt Kúti wrote: > >>>> Hi Andrew, > >>>> > >>>> As no reaction has arrived until now, I, as probably the last one who > >> dealt > >>>> with our website, take the liberty of answering. > >>>> > >>>> Yes, our project uses Apache CMS [see here: > >>>> https://river.apache.org/user-doc/website.html]. > >>>> I hope somebody is going to step up for being a contact and/or for > >>>> transferring our website content to one of the alternatives. > >>>> If not, I'll be around somewhen in September, after back from my > >> holidays > >>>> and may do what is needed for it. > >>>> > >>>> Thanks for contacting us and offering help! > >>>> Zsolt > >>>> > >>>> > >>>> On Fri, Aug 7, 2020 at 2:51 PM Andrew Wetmore > >> wrote: > >>>>> Hi: > >>>>> > >>>>> I am part of the Infrastructure team, and am writing to ask whether > >> your > >>>>> project is still using the Apache CMS for your project website. As > you > >>>>> know, the CMS is reaching end-of-life, and we need projects to move > >> their > >>>>> websites onto a different option within the next few weeks. > >>>>> > >>>>> There are several alternatives available, including those listed on > >> this > >>>>> page [1] on managing project websites. Infra is assembling a Wiki > page > >> [2] > >>>>> on migrating a website from the CMS, and is looking forward to > helping > >>>>> projects with this transition. > >>>>> > >>>>> Please let me know whether your site is still on the Apache CMS and, > >> if so, > >>>>> who will be the project point-of-contact with Infra for the > migration. > >>>>> > >>>>> Thank you! > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> [1] https://infra.apache.org/project-site.html > >>>>> > >>>>> [2] > >>>>> > >>>>> > >> > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS > >>>>> > >>>>> -- > >>>>> Andrew Wetmore > >>>>> > >>>>> http://cottage14.blogspot.com/ > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> < > >>>>> > >> > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail > >>>>> Virus-free. > >>>>> www.avast.com > >>>>> < > >>>>> > >> > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail > >>>>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > >>>>> > >> -- > >> Regards, > >> > >> Peter Firmstone > >> 0498 286 363 > >> Zeus Project Services Pty Ltd. > >> > >> > -- > Regards, > > Peter Firmstone > 0498 286 363 > Zeus Project Services Pty Ltd. > > -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: Your project website
Thanks Zsolt. Please let us know what when you hear back from Gavin and/or Andrew. Depending on the timing I may be able to offer a few cycles to help. On Wed, Mar 17, 2021 at 11:33 AM Zsolt Kúti wrote: > Hi, > > I volunteered earlier for the task. My apologies that in the meantime I > started getting some basic info/guidance in the background. > Andrew forwarded my questions to Gavin McDonald, as of now no answer yet. > As soon as I have the information and some decision is needed I will come > back to the list with it. > If anyone wants this task I'd be glad to hand it over. Alternatively, > anyone willing to participate is welcome. > > Zsolt > > On Wed, Mar 17, 2021 at 4:41 PM Jeremy R. Easton-Marks < > j.r.eastonma...@gmail.com> wrote: > > > Hi Andrew, > > Who should we reach out to on the Infra team? What type of investment in > > time/resources do you estimate it would take to switch over? > > > > ~Jeremy > > > > > > On Thu, Feb 4, 2021 at 3:07 PM Peter Firmstone < > > peter.firmst...@zeus.net.au> > > wrote: > > > > > Thanks Andrew, > > > > > > Which option is the fastest path / least work required for transition? > > > I don't have time to look into each option, so any such advise will be > > > much appreciated. > > > > > > Regards, > > > > > > Peter. > > > > > > On 4/02/2021 10:57 pm, Andrew Wetmore wrote: > > > > Hi: > > > > > > > > We were hoping to have all projects migrated by the end of last year. > > > There > > > > are still a number using the Apache CMS, and we have not set a hard > > > > deadline for shutting it down. However, the system is becoming less > > > > reliable, so moving sooner rather than later is probably a good idea. > > > > > > > > Andrew > > > > > > > > On Wed, Feb 3, 2021 at 8:08 PM Peter Firmstone < > > > peter.firmst...@zeus.net.au> > > > > wrote: > > > > > > > >> Thanks Andrew, > > > >> > > > >> What's the timeframe for migration? > > > >> > > > >> Regards, > > > >> > > > >> Peter. > > > >> > > > >> On 1/02/2021 11:55 pm, Andrew Wetmore wrote: > > > >>> Hi, and happy New Year! > > > >>> > > > >>> I know you folks are busy with your svn-to-git migration, but I > > wanted > > > >> to bring up again the need to migrate your website off the Apache > CMS. > > > >> Please let me know what your plans are, and whether you need help > from > > > >> Infra. > > > >>> Andrew Wetmore > > > >>> > > > >>> On 2020/08/10 10:39:31, Zsolt Kúti wrote: > > > >>>> Hi Andrew, > > > >>>> > > > >>>> As no reaction has arrived until now, I, as probably the last one > > who > > > >> dealt > > > >>>> with our website, take the liberty of answering. > > > >>>> > > > >>>> Yes, our project uses Apache CMS [see here: > > > >>>> https://river.apache.org/user-doc/website.html]. > > > >>>> I hope somebody is going to step up for being a contact and/or for > > > >>>> transferring our website content to one of the alternatives. > > > >>>> If not, I'll be around somewhen in September, after back from my > > > >> holidays > > > >>>> and may do what is needed for it. > > > >>>> > > > >>>> Thanks for contacting us and offering help! > > > >>>> Zsolt > > > >>>> > > > >>>> > > > >>>> On Fri, Aug 7, 2020 at 2:51 PM Andrew Wetmore < > cottag...@gmail.com> > > > >> wrote: > > > >>>>> Hi: > > > >>>>> > > > >>>>> I am part of the Infrastructure team, and am writing to ask > whether > > > >> your > > > >>>>> project is still using the Apache CMS for your project website. > As > > > you > > > >>>>> know, the CMS is reaching end-of-life, and we need projects to > move > > > >> their > > > >>>>> websites onto a different option within the next few weeks. > > > >>>>> > > > >>>>
Re: Git conversion (was Re: Project Health / Interest)
an start to “break things” (literally > >> and figuratively) into smaller repos. The underlying assumption is > >> just about everything will be easier to do (merging, etc) with a > >> git repo. > >> > >> Either way, I’ll start looking for lines along which I could break > >> things. > >> > >> Dan > >> > >> > >> > On Feb 9, 2021, at 3:42 AM, Peter Firmstone > >> mailto:peter.firmst...@zeus.net.au>> > >> wrote: > >> > > >> > Thanks Dan, > >> > > >> > https://infra.apache.org/svn-to-git-migration.html > >> <https://infra.apache.org/svn-to-git-migration.html> > >> > > >> > https://gitbox.apache.org/setup/newrepo.html > >> <https://gitbox.apache.org/setup/newrepo.html> > >> > > >> > http://svn.apache.org/viewvc/river/ > >> <http://svn.apache.org/viewvc/river/> > >> > > >> > https://gitbox.apache.org/repos/asf#river > >> <https://gitbox.apache.org/repos/asf#river> > >> > > >> > I just created a git repository for the "Apache river JiniTM > >> Technology Lookup, Discovery, and Join Compatibility Kit", I > >> figure it might be easier to start with something that's had > >> relatively few commits as an experiment. > >> > > >> > But basically everything we have on svn needs to be broken up > >> into separate projects, typical of what people are used to seeing > >> on github. > >> > > >> > The QA test suite is an ant build project, it's currently part > >> of trunk, but I was thinking of separating it out into it's own > >> build. > >> > > >> > On 9/02/2021 12:31 pm, Dan Rollo wrote: > >> >> Hi Peter, > >> >> > >> >> I’m apologize for not being more help. I haven’t had much time > >> of late. Is there a thread I could pull regarding the Git > >> migration? Where to start? > >> >> > >> >> The plan you itemize makes sense to me. > >> >> > >> >> Dan Rollo > >> >> > >> >>> On Feb 8, 2021, at 8:35 PM, Peter Firmstone > >> mailto:peter.firmst...@zeus.net.au>> > >> wrote: > >> >>> > >> >>> Hello River folk, > >> >>> > >> >>> There's an upcoming board report due shortly, I wanted to > >> gauge people's interest in the project. > >> >>> > >> >>> We've got two pending tasks: > >> >>> > >> >>> 1. SVN to Git Migration > >> >>> 2. Website migration > >> >>> > >> >>> Following the Git Migration, the plan is to continue with the > >> modular build, using gradle? > >> >>> > >> >>> Lately we don't have a lot of participation, I was hoping that > >> we would have some more buy in, especially with the Git migration. > >> >>> > >> >>> I don't want to be making decisions alone, are there people on > >> this list who have time to assist, are willing to assist or intend > >> to do so in future when they have time? > >> >>> > >> >>> -- > >> >>> Regards, > >> >>> Peter Firmstone > >> >>> > >> > -- > >> > Regards, > >> > Peter Firmstone > >> > > >> > -- > Regards, > > Peter Firmstone > 0498 286 363 > Zeus Project Services Pty Ltd. > > -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: Git conversion (was Re: Project Health / Interest)
> Added back DEV. For tracking purposes: https://issues.apache.org/jira/browse/INFRA-21600 On Fri, Mar 19, 2021 at 6:43 AM Jeremy R. Easton-Marks < j.r.eastonma...@gmail.com> wrote: > Hi Dennis, > Thanks for the update. I think your repo would be the best jumping off > point, as you had already completed the work. > > I guess step number one would be to figure out who has access to the repo > and to see what it would take to get access. I'll reach out to the Apache > Infrastructure team. > > ~Jeremy > > On Thu, Mar 18, 2021 at 10:37 AM Dennis Reedy > wrote: > >> Hi Jeremy, >> >> I have not done anything with the git migration. The Git repo I created >> (which is also a gradle build) can be accessed and cloned from here >> <https://github.com/dreedyman/apache-river>. I wouldn't know where to >> commit the project into, as in what the coordinates of the Apache River Git >> repository is. If anyone would like to jump in and do this, I'm here to >> help as needed. >> >> Regards >> >> Dennis >> >> On Wed, Mar 17, 2021 at 10:34 PM Jeremy R. Easton-Marks < >> j.r.eastonma...@gmail.com> wrote: >> >>> Hi Dennis, >>> I wanted to resurrect this thread to see how things are going with the >>> migration and to see what, if any, help you needed. >>> >>> ~Jeremy >>> >>> > > -- > Jeremy R. Easton-Marks > > "être fort pour être utile" > -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: Git conversion (was Re: Project Health / Interest)
A Quick Update: I did some research on how to get code into our GitHub and it looks like you need to be a committer. Which requires approval from the PMC, which is currently in an inbetween state(?). Once everything is settled I will request committer access or at least see if we can get someone to commit a README file so we can start creating branches and pull requests to bring Dennis' code over. If a committer wants to create a README.md file we can always go from there. On Fri, Mar 19, 2021 at 6:50 AM Jeremy R. Easton-Marks < j.r.eastonma...@gmail.com> wrote: > > Added back DEV. > > For tracking purposes: https://issues.apache.org/jira/browse/INFRA-21600 > > > On Fri, Mar 19, 2021 at 6:43 AM Jeremy R. Easton-Marks < > j.r.eastonma...@gmail.com> wrote: > >> Hi Dennis, >> Thanks for the update. I think your repo would be the best jumping off >> point, as you had already completed the work. >> >> I guess step number one would be to figure out who has access to the repo >> and to see what it would take to get access. I'll reach out to the Apache >> Infrastructure team. >> >> ~Jeremy >> >> On Thu, Mar 18, 2021 at 10:37 AM Dennis Reedy >> wrote: >> >>> Hi Jeremy, >>> >>> I have not done anything with the git migration. The Git repo I created >>> (which is also a gradle build) can be accessed and cloned from here >>> <https://github.com/dreedyman/apache-river>. I wouldn't know where to >>> commit the project into, as in what the coordinates of the Apache River Git >>> repository is. If anyone would like to jump in and do this, I'm here to >>> help as needed. >>> >>> Regards >>> >>> Dennis >>> >>> On Wed, Mar 17, 2021 at 10:34 PM Jeremy R. Easton-Marks < >>> j.r.eastonma...@gmail.com> wrote: >>> >>>> Hi Dennis, >>>> I wanted to resurrect this thread to see how things are going with the >>>> migration and to see what, if any, help you needed. >>>> >>>> ~Jeremy >>>> >>>> >> >> -- >> Jeremy R. Easton-Marks >> >> "être fort pour être utile" >> > > > -- > Jeremy R. Easton-Marks > > "être fort pour être utile" > -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: Git conversion (was Re: Project Health / Interest)
Awesome sauce. Here is what I found: Apache: https://git-wip-us.apache.org/repos/asf?p=river-container.git;a=tree https://git-wip-us.apache.org/repos/asf?p=river-ldj-tests.git;a=tree GitHub https://github.com/apache/river-container/pulls https://github.com/apache/river-ldj-tests I'm not sure if the Apache or GitHub one is the correct one to use but I think the river-container would be the correct repository. You may also need to do something here: https://gitbox.apache.org/setup/ Let us know if it works. On Mon, Mar 22, 2021 at 10:48 PM Dennis Reedy wrote: > Hi Jeremy, > > What’s the git repository url? That’s what I was referring to when I > mentioned I don’t know where to commit the work into. > > If you can let me know that, I’ll clone it, add what I have and push to > the git repository. > > Regards > > Dennis > > On Mar 22, 2021, at 10:43 PM, Jeremy R. Easton-Marks < > j.r.eastonma...@gmail.com> wrote: > > > A Quick Update: > I did some research on how to get code into our GitHub and it looks like > you need to be a committer. Which requires approval from the PMC, which is > currently in an inbetween state(?). Once everything is settled I will > request committer access or at least see if we can get someone to commit a > README file so we can start creating branches and pull requests to bring > Dennis' code over. > > If a committer wants to create a README.md file we can always go from > there. > > On Fri, Mar 19, 2021 at 6:50 AM Jeremy R. Easton-Marks < > j.r.eastonma...@gmail.com> wrote: > >> > Added back DEV. >> >> For tracking purposes: https://issues.apache.org/jira/browse/INFRA-21600 >> >> >> On Fri, Mar 19, 2021 at 6:43 AM Jeremy R. Easton-Marks < >> j.r.eastonma...@gmail.com> wrote: >> >>> Hi Dennis, >>> Thanks for the update. I think your repo would be the best jumping off >>> point, as you had already completed the work. >>> >>> I guess step number one would be to figure out who has access to the >>> repo and to see what it would take to get access. I'll reach out to the >>> Apache Infrastructure team. >>> >>> ~Jeremy >>> >>> On Thu, Mar 18, 2021 at 10:37 AM Dennis Reedy >>> wrote: >>> >>>> Hi Jeremy, >>>> >>>> I have not done anything with the git migration. The Git repo I created >>>> (which is also a gradle build) can be accessed and cloned from here >>>> <https://github.com/dreedyman/apache-river>. I wouldn't know where to >>>> commit the project into, as in what the coordinates of the Apache River Git >>>> repository is. If anyone would like to jump in and do this, I'm here to >>>> help as needed. >>>> >>>> Regards >>>> >>>> Dennis >>>> >>>> On Wed, Mar 17, 2021 at 10:34 PM Jeremy R. Easton-Marks < >>>> j.r.eastonma...@gmail.com> wrote: >>>> >>>>> Hi Dennis, >>>>> I wanted to resurrect this thread to see how things are going with the >>>>> migration and to see what, if any, help you needed. >>>>> >>>>> ~Jeremy >>>>> >>>>> >>> >>> -- >>> Jeremy R. Easton-Marks >>> >>> "être fort pour être utile" >>> >> >> >> -- >> Jeremy R. Easton-Marks >> >> "être fort pour être utile" >> > > > -- > Jeremy R. Easton-Marks > > "être fort pour être utile" > > -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: River project reboot
This is great news. Congratulations on the appointment and I look forward to seeing what happens next. On Mon, Apr 26, 2021 at 12:14 PM Roy T. Fielding wrote: > Hi all, > > The board decided to appoint me as a temporary chair for River > so that we can reboot the PMC and bring in some new contributors. > > The first thing I am doing is cleaning up the list moderation so that > I can see who is on the project lists and establish that the existing PMC > can make decisions. If so, I will ask the PMC to add more PMC members > and committers, and submit those to the board or infra more new > accounts (if needed). > > Cheers, > > Roy > > -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: JEP 411 - end of Apache River?
I'm not sure how much JEP 411 will impact River. I agree with the overall direction that it proposes in removing the security manager. However, I am worried that removing security features is going to cause some other problems in the Java ecosystem. Beyond the potential impact of River. I do think what affect it will have on Apache River should be explored. I am of the opinion that Apache River should look beyond just being a Java only project and that we may need to rethink the way that we approach building distributed systems. On Thu, Apr 29, 2021 at 1:10 PM Simon Roberts < si...@dancingcloudservices.com> wrote: > On Thu, Apr 29, 2021 at 11:40 AM Roy T. Fielding > wrote: > > > > On Apr 28, 2021, at 9:24 PM, Michał Kłeczek > wrote: > > > > > > Hi All, > > > > > > I’ve just learned JEP 411 (https://openjdk.java.net/jeps/411 < > > https://openjdk.java.net/jeps/411>) moved to Candidate status. > > > > > > Does this JEP mean end of mobile code and hence Apache River? > > > > No, it's just code. If the code needs to be replaced, it can be replaced. > > > > Roy > > > > > I'm not sure how you reach that conclusion Roy (which is not an attempt to > claim that I'm qualified to disagree with you, though I *believe* I > understand the core functioning of this stuff at a reasonable level). > > On the one hand, I'm not sure how many people run River systems in entirely > trusted infrastructures, and for those that do, perhaps they won't care if > the security manager goes away anyway. > > On the other hand, if the security manager and everything that goes with it > disappears, I don't see how you can simply "replace" that from a library. > We're not talking about "capabilities" we're talking about built-in > restrictions in the core libraries for Java SE that are essential to the > behavior of the security manager. If that all goes away, the only way I can > see to put the functionality back is to provide a replacement > implementation of core libraries. That's effectively distributing an > alternate version of Java (though the actual JVM, and the platform specific > binaries can be retained.) Can you explain how you see adding back security > from a library level? Or is your assertion just that you don't see people > caring? > > Of course, that only matters if people want the security manager, which I > admit is not something I've witnessed in 26 years of trying to persuade > them that they do! And it's long been clear that Oracle doesn't see > sufficient value in mobile code for them to bother trying to make it > secure. Frankly I've been struggling to explain the value to people for the > same 26 years. > > -- > Simon Roberts > (303) 249 3613 > -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: JEP 411 - end of Apache River?
Hi Michal, I think you should definitely share your opinions about this ( https://bugs.openjdk.java.net/browse/JDK-8264713). I think they may not know about Apache River and they probably should address the issues around dynamically loaded code. I would cite other Java examples other than just River. Android is able to operate without the Java Security Manager and maybe the JDK should look into adopting the Android way. On Fri, Apr 30, 2021 at 4:38 AM Michał Kłeczek wrote: > > > > On 30 Apr 2021, at 04:42, Jeremy R. Easton-Marks < > j.r.eastonma...@gmail.com> wrote: > > > > I'm not sure how much JEP 411 will impact River. I agree with the overall > > direction that it proposes in removing the security manager. > > IMHO JEP 411 gives unconvincing reasons to ditch SecurityManager: > > - brittle permission model > This one is really well summarized in the same paper: The Security Manager > does not allow negative permissions that could express "grant permission > for all operations except reading files”. > > Why not fix that??? Especially that it has been done before: > https://github.com/olukas/pro-grade > > - poor performance > Why not fix that??? Especially that it has been done before by… yes - > Apache River (thanks Peter!). > > - difficult programming model > This one is difficult to sensibly assess without comparing alternatives. > Simply speaking: security is difficult - there is no free lunch. > > Example from the document (ie. client code needs to be granted permissions > required by library code if doPrivileged is not used) has it completely > backwards as that’s the whole point of stack walking based security: avoid > confused deputee issue. > > It also looks like there is another huge misconception in the industry: > "running untrusted code on the server is a big no-no and once you only run > trusted code SecurityManager is not needed anymore”. > The point really is: there is no such a thing as “trusted code” - that’s > illusion. See for example: https://news.ycombinator.com/item?id=26087064 > > Similar misconception: one should avoid dynamically loaded code (or even > from the JEP 411 itself: nobody is interested in dynamically loaded code). > Well… Docker images _are_ dynamically loaded code. > And k8s or Helm yaml descriptors defining what this dynamically loaded > code can access are by no means simpler than security policy files. Quite > the opposite. > > > > However, I am > > worried that removing security features is going to cause some other > > problems in the Java ecosystem. Beyond the potential impact of River. > > > > I do think what affect it will have on Apache River should be explored. > > > > I am of the opinion that Apache River should look beyond just being a > Java > > only project and that we may need to rethink the way that we approach > > building distributed systems. > > Killing mobile code is killing Apache River as IMHO that’s the defining > feature of it. > > The question is whether killing SecurityManager is killing mobile code. > > Regards, > Michal > > -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: River and Kubernetes
I haven't tried it but if it works it would be an easy way to set up everything for a demo. I imagine it would be a little difficult getting the network connections working correctly. On Wed, May 19, 2021 at 11:49 AM Dennis Reedy wrote: > Hi all, > > Has anyone been successful deploying River services on a Kubernetes > cluster? > > Regards > > Dennis > -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: Welcome to Apache River
Hi everyone! I am excited to join as a committer to the River project as I have been a fan of Jini/River for a long time now. I am looking forward to helping out where I can. Congratulations to Dennis Reedy for joining the PMC and the others who have been granted commit access. Thank you to Roy Fielding for stepping in as chair while we go through this revamp. In regards to Roy's list: > 1) Migrate "https://river.apache.org/"; to a different site generator > (it is currently using the old ASF CMS, which is ending service soon) > and update the associated content. I know Andrew Wetmore, and Zsolt Kúti had been looking into this. I am not sure of the status. > 2) Move version control to git Does Apache have a best practices guide for how to do this? I know we have had some movement forward on this but I think we got stalled out somewhere. > 3) Make a release I think item #2 might take care of this. If not is there a low level bug/quick feature that we could quickly put up to get a version going? 4+ One of the things I have struggled with is what Apache River can be used for. I remember my father setting up Jini demos back when it was first being promoted by Sun. They all seemed cool but in an abstract way. I don't know what or why I would use it for today. I know it has a purpose and it could be very helpful but I am not sure how or what to do with it. Would anyone be interested in working on a doc about what we think Apache River can be used for? This doc can help us decide a couple of things. The first being what direction we should be taking and second how to "market" this to the greater computing community. ~Jeremy On Thu, May 20, 2021 at 5:15 PM Roy T. Fielding wrote: > Hello everyone, > > The River PMC was rebooted to include > > - Roy T. Fielding (temporary chair) > - Dan Rollo > - Patricia Shanahan > - Bryan Thompson > > and our first decision was an invitation to the PMC for > > - Dennis Reedy(added to the PMC on 2021-04-30) > > followed by a second decision to grant commit access to four > new contributors: > > - Jeremy R. Easton-Marks > - Norman Kabir > - Phillip Rhodes > - Michael Sobolewski > > Congratulations to Dennis and all of our new contributors! > They should all have accounts now and privileges to commit. > (If not, let me know of any access issues -- I may have missed > a spot, like in jira, where I haven't checked). > > So, now comes the hard part. We have to do something to get River > over a hill and running again. There are three immediate needs that > I know about: > > 1) Migrate "https://river.apache.org/"; to a different site generator > (it is currently using the old ASF CMS, which is ending service soon) > and update the associated content. > > 2) Move version control to git > > 3) Make a release > > You probably know of more. Don't be shy, just add to the list or send a > link if it is already in the JIRA issues. > > Please, don't wait for someone else to lead an effort. This is your > project. > Let's work together as much as possible, but don't be afraid to start > moving! Just let us all know (here) when you decide to take on a big > task and assume everyone agrees unless they tell you otherwise. > Feel free to do the work even if someone disagrees, assuming it can > be done on a branch without impacting others. > > Like all Apache projects, we will depend upon open and honest opinions > for making decisions. In the rare cases when people actually disagree, > we will try to work out our differences or vote upon a direction. > We are all volunteers, so work on what you want to work on, help > each other whenever possible, and return the favor when you can. > > My job, as chair, is to facilitate the making of decisions and removal of > external obstacles to a release (i.e., communicating with the board, > pressing buttons on infrastructure, etc.). I am not here to lead the group, > nor to make technical decisions for the products! Eventually, > I will ask one of you to take over the role of chair, once the group > is making decisions on its own. > > Cheers, > > Roy > > -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: CMS Migration for River
Thanks Dave. Do you need anything from the River team for this process? On Sat, May 29, 2021 at 11:43 AM Dave Fisher wrote: > As you may recall the Apache CMS has been deprecated for over five years > now and will be decommissioned > by July 31, 2021. > > I’ve been tasked with moving River's website away from the Apache CMS. > I will migrate your website to a Pelican build with GitHub Flavored > Markdown (GFM). > For your reference the already migrated www-site is here > https://github.com/apache/www-site/ > > The following will occur. > - A new git repository is created. river-site is preferred. > - CMS mdtext files are converted to md and stored in the content tree. > - Permalinks are created in the same manner. > - Page templates will be converted essentially as is with some minor > improvements. > - Site data feeds are analyzed. If required a data model will be created. > - HTML files (apidocs) built separately are copied into the content tree. > I’ll make a judgement call on > if these can be wrapped into the template. > > The Apache CMS had a cumbersome process of individual checkouts -> staging > -> publishing. > The new branching strategy is as follows: > - main will have the site content sources and any additional docs (like > api docs). > - asf-site will have the production website which is automatically > deployed to river.apache.org. > During the migration we will deploy to river.staged.apache.org > - preview/release will have the website prepared for the next release. You > will add release specific docs to this branch > - preview/release-staging will have the built preview website which is > automatically deployed to river-release.staged.apache.org > > This new plan allows for a redesign of your site without danger of > premature deployment. > If you decide that GFM is not for river then you can switch to a different > process within a preview branch. > > Release steps for the website could be: > - Branch main as preview/release > - Make your updates to preview/release > - Confirm your changes on river-release.staged.apache.org > - Pull your changes from preview/release to main. river.apache.org is > automatically updated. > > All The Best, > Dave Fisher -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: CMS Migration for River
Hi Dave, This looks good. Every link looks like it worked and the site material looks like it moved over correctly. I found some stuff that we need to update on our end that I am going to take a look at. ~Jeremy On Tue, Jun 1, 2021 at 6:35 PM Dave Fisher wrote: > Hi - > > Please find your staged migrated site at https://river.staged.apache.org < > https://river.staged.apache.org/> > > The repository is at https://github.com/apache/river-site < > https://github.com/apache/river-site> > > I’ll be updating the README.md files in the next day or two including > notes on the migration. > > All The Best, > Dave > > > On May 29, 2021, at 12:45 PM, Dave Fisher wrote: > > > > I may have questions once the migration is started. > > > > I’ll definitely need review once the new repository with the migrated > content is ready. > > > >> On May 29, 2021, at 11:28 AM, Jeremy R. Easton-Marks < > j.r.eastonma...@gmail.com> wrote: > >> > >> Thanks Dave. Do you need anything from the River team for this process? > >> > >> On Sat, May 29, 2021 at 11:43 AM Dave Fisher wrote: > >> > >>> As you may recall the Apache CMS has been deprecated for over five > years > >>> now and will be decommissioned > >>> by July 31, 2021. > >>> > >>> I’ve been tasked with moving River's website away from the Apache CMS. > >>> I will migrate your website to a Pelican build with GitHub Flavored > >>> Markdown (GFM). > >>> For your reference the already migrated www-site is here > >>> https://github.com/apache/www-site/ > >>> > >>> The following will occur. > >>> - A new git repository is created. river-site is preferred. > >>> - CMS mdtext files are converted to md and stored in the content tree. > >>> - Permalinks are created in the same manner. > >>> - Page templates will be converted essentially as is with some minor > >>> improvements. > >>> - Site data feeds are analyzed. If required a data model will be > created. > >>> - HTML files (apidocs) built separately are copied into the content > tree. > >>> I’ll make a judgement call on > >>> if these can be wrapped into the template. > >>> > >>> The Apache CMS had a cumbersome process of individual checkouts -> > staging > >>> -> publishing. > >>> The new branching strategy is as follows: > >>> - main will have the site content sources and any additional docs (like > >>> api docs). > >>> - asf-site will have the production website which is automatically > >>> deployed to river.apache.org. > >>> During the migration we will deploy to river.staged.apache.org > >>> - preview/release will have the website prepared for the next release. > You > >>> will add release specific docs to this branch > >>> - preview/release-staging will have the built preview website which is > >>> automatically deployed to river-release.staged.apache.org > >>> > >>> This new plan allows for a redesign of your site without danger of > >>> premature deployment. > >>> If you decide that GFM is not for river then you can switch to a > different > >>> process within a preview branch. > >>> > >>> Release steps for the website could be: > >>> - Branch main as preview/release > >>> - Make your updates to preview/release > >>> - Confirm your changes on river-release.staged.apache.org > >>> - Pull your changes from preview/release to main. river.apache.org is > >>> automatically updated. > >>> > >>> All The Best, > >>> Dave Fisher > >> > >> > >> > >> -- > >> Jeremy R. Easton-Marks > >> > >> "être fort pour être utile" > > > > -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: CMS Migration for River
I created a PR <https://github.com/apache/river-site/pull/1> to fix some of the dead links and spelling mistakes. I don't have write access yet for this repo so please merge it when you can. On Tue, Jun 1, 2021 at 8:52 PM Jeremy R. Easton-Marks < j.r.eastonma...@gmail.com> wrote: > Hi Dave, > This looks good. Every link looks like it worked and the site material > looks like it moved over correctly. I found some stuff that we need to > update on our end that I am going to take a look at. > > ~Jeremy > > On Tue, Jun 1, 2021 at 6:35 PM Dave Fisher wrote: > >> Hi - >> >> Please find your staged migrated site at https://river.staged.apache.org >> <https://river.staged.apache.org/> >> >> The repository is at https://github.com/apache/river-site < >> https://github.com/apache/river-site> >> >> I’ll be updating the README.md files in the next day or two including >> notes on the migration. >> >> All The Best, >> Dave >> >> > On May 29, 2021, at 12:45 PM, Dave Fisher wrote: >> > >> > I may have questions once the migration is started. >> > >> > I’ll definitely need review once the new repository with the migrated >> content is ready. >> > >> >> On May 29, 2021, at 11:28 AM, Jeremy R. Easton-Marks < >> j.r.eastonma...@gmail.com> wrote: >> >> >> >> Thanks Dave. Do you need anything from the River team for this process? >> >> >> >> On Sat, May 29, 2021 at 11:43 AM Dave Fisher wrote: >> >> >> >>> As you may recall the Apache CMS has been deprecated for over five >> years >> >>> now and will be decommissioned >> >>> by July 31, 2021. >> >>> >> >>> I’ve been tasked with moving River's website away from the Apache CMS. >> >>> I will migrate your website to a Pelican build with GitHub Flavored >> >>> Markdown (GFM). >> >>> For your reference the already migrated www-site is here >> >>> https://github.com/apache/www-site/ >> >>> >> >>> The following will occur. >> >>> - A new git repository is created. river-site is preferred. >> >>> - CMS mdtext files are converted to md and stored in the content tree. >> >>> - Permalinks are created in the same manner. >> >>> - Page templates will be converted essentially as is with some minor >> >>> improvements. >> >>> - Site data feeds are analyzed. If required a data model will be >> created. >> >>> - HTML files (apidocs) built separately are copied into the content >> tree. >> >>> I’ll make a judgement call on >> >>> if these can be wrapped into the template. >> >>> >> >>> The Apache CMS had a cumbersome process of individual checkouts -> >> staging >> >>> -> publishing. >> >>> The new branching strategy is as follows: >> >>> - main will have the site content sources and any additional docs >> (like >> >>> api docs). >> >>> - asf-site will have the production website which is automatically >> >>> deployed to river.apache.org. >> >>> During the migration we will deploy to river.staged.apache.org >> >>> - preview/release will have the website prepared for the next >> release. You >> >>> will add release specific docs to this branch >> >>> - preview/release-staging will have the built preview website which is >> >>> automatically deployed to river-release.staged.apache.org >> >>> >> >>> This new plan allows for a redesign of your site without danger of >> >>> premature deployment. >> >>> If you decide that GFM is not for river then you can switch to a >> different >> >>> process within a preview branch. >> >>> >> >>> Release steps for the website could be: >> >>> - Branch main as preview/release >> >>> - Make your updates to preview/release >> >>> - Confirm your changes on river-release.staged.apache.org >> >>> - Pull your changes from preview/release to main. river.apache.org is >> >>> automatically updated. >> >>> >> >>> All The Best, >> >>> Dave Fisher >> >> >> >> >> >> >> >> -- >> >> Jeremy R. Easton-Marks >> >> >> >> "être fort pour être utile" >> > >> >> > > -- > Jeremy R. Easton-Marks > > "être fort pour être utile" > -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: CMS Migration for River
+1 Thanks for the work in converting this. On Sun, Jun 13, 2021 at 5:56 PM Roy T. Fielding wrote: > > On Jun 13, 2021, at 3:28 PM, Dave Fisher wrote: > > > > Hi, > > > > The site is ready to go. https://river.staged.apache.org > > > > The README on https://github.com/apache/river-site has a pointer to the > Infra documentation and to migration notes which includes a diff on the > markdown including the PR. > > > > I would like to make this migration live in 72 hours. > > > > All The Best, > > Dave > > +1. I will update the people page after the switch. > > Roy > > -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: [DISCUSS] Moving Apache River to the Attic
I, sadly, agree that it is time to move this project to the Attic. While I hoped to work on this as a side project, I have not been able to carve out time for it. While I do think this project has a lot of potential, without some type of sponsorship in time and resources I don't see it moving forward. Thank you Roy for stepping up as the chair as well as the rest of the River team for contributing to this project over the years. It has been great watching the discussions in these threads. On a personal note, seeing this project move into the Attic while sad, it will hopefully be cathartic. My father, Peter C. Marks, was one of the original developers at Sun who worked on Jini. I remember him being very excited about the potential for the technology and he enjoyed demoing it. I even remember accompanying him to Amsterdam to demo it at a conference when I was younger. I have some of the original Jini books sitting in my office right now that have been signed by some of the original team members. I had hoped to see the project keep going, maybe with it moving into the Attic River can move forward in a different way. On Mon, Feb 7, 2022 at 6:41 PM Roy T. Fielding wrote: > Hello everyone, > > It's that time of year when I try to figure out what I am doing and > what I am not, and try to cut back on the stuff that seems unlikely > to succeed. I suspect the same is true of others. > > I had hoped that more new people at River would result in more activity, > but that hasn't occurred over the past 9 months and doesn't seem likely > in the future. Aside from ASF echoes and Infra-driven website replacement, > there has been nothing to report about River the entire time that I have > been the chair pro tem, and there hasn't been any chatter by users either. > > Please feel free to let me know if I am missing something. > > If not, I'd like us to accept the reality of this situation and move the > River project to the Attic. The code will still be available there, and > folks are welcome to copy it under the license, move it to Github, or > otherwise seek to re-mold it into a collaborative project wherever is > most convenient for them. > > Cheers, > > Roy > > -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: [VOTE] dropping support for java version 5 and earlier (tally)
+1 non-binding On Jan 28, 2012 9:02 AM, "Simon IJskes - QCG" wrote: > Vote tally until now: > > +1 Simon IJskes > +1 Peter Firmstone > +1 Dan Creswell > +1 Gregg Wonderly (nb) > +1 Christopher Dolan > +1 Patricia Shanahan > +1 Dennis Reedy > > > Last call > > > -- > QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl > Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397 >
