You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Patricia Shanahan <pa...@acm.org> on 2016/07/04 14:08:45 UTC
Attic? Was: Re: Lotj - languages other than java
I think it is time to raise on the user list moving River to the attic.
There is no sign of progress on a release. What interest there is in
development seems to be going in different directions. Using portions of
River code in other projects would still be feasible with it in the
attic, but there would be no need for a PMC, and board reports.
Patricia
On 7/4/2016 6:44 AM, Simon IJskes - QCG wrote:
...
> But then again, there are a lot of people reading this, and a big part
> of them having no interest at all in incompatible improvements, and i
> see no other option than leaving them behind, with a jini compatible
> maintenance release. This will certainly tear the river community apart,
> or at least cause a lot of friction. So when i see only the two of us,
> moving in a new direction, i can't help feeling, what is the use of it all.
>
> G. Simon
>
>
>
Re: Attic? Was: Re: Lotj - languages other than java
Posted by Bryan Thompson <br...@blazegraph.com>.
I look at git in terms of the ease of use for branch/merge patterns and the
support of pull requests for code review and historical change tracking.
It is really far superior in its flexibility. Even just the diff facility
if a big step forward.
I do agree that projects benefit significantly from governance. If it
degenerates to everyone creating their own fork then nothing good would
come of that. I am not suggesting git because it makes forking easier.
But because it makes team development easier.
Bryan
On Wednesday, July 6, 2016, Simon IJskes - QCG <si...@qcg.nl> wrote:
> On 05-07-16 14:51, Bryan Thompson wrote:
>
>> GitHub (at least) provides excellent tracking. It is a matter of how you
>> define policy for PRs. We do not accept PRs unless the author is a
>> contributor with appropriate CLAs for the project. So it works out very
>> nicely for us. Every single commit and its authorship remains visible and
>> that metadata can be easily accessed.
>>
>
> Is changing the version control system really going to change the problems
> we have?
>
> The same goes for maven or not, gradle or ant, etc.
>
> One direction wants a stable release with bugfixes, and strict maintaining
> of the original api, the other side wants to change things.
>
> No resolution in sight. I really like the Apache governance, and it gives
> everybody the freedom to fork it under its own. Apache is definitly not the
> problem here.
>
> Apache is a tool, a tool that shows us that we need to cooperate in order
> to make progress. You can switch to git, and fork all you like, like so
> many other projects. But then you have a few forks, sitting stale on
> github. With sometimes an individual caring about it, or more times not.
> Apache goes beyond individuals, and currently it shows we haven't made that
> step.
>
> G. Simon
>
> --
> QCG, Software development, 071-5890970, http://www.qcg.nl
> Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
>
Re: Attic? Was: Re: Lotj - languages other than java
Posted by Simon IJskes - QCG <si...@qcg.nl>.
On 05-07-16 14:51, Bryan Thompson wrote:
> GitHub (at least) provides excellent tracking. It is a matter of how you
> define policy for PRs. We do not accept PRs unless the author is a
> contributor with appropriate CLAs for the project. So it works out very
> nicely for us. Every single commit and its authorship remains visible and
> that metadata can be easily accessed.
Is changing the version control system really going to change the
problems we have?
The same goes for maven or not, gradle or ant, etc.
One direction wants a stable release with bugfixes, and strict
maintaining of the original api, the other side wants to change things.
No resolution in sight. I really like the Apache governance, and it
gives everybody the freedom to fork it under its own. Apache is
definitly not the problem here.
Apache is a tool, a tool that shows us that we need to cooperate in
order to make progress. You can switch to git, and fork all you like,
like so many other projects. But then you have a few forks, sitting
stale on github. With sometimes an individual caring about it, or more
times not. Apache goes beyond individuals, and currently it shows we
haven't made that step.
G. Simon
--
QCG, Software development, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
Re: Attic? Was: Re: Lotj - languages other than java
Posted by Tom Hobbs <tv...@googlemail.com>.
+1 for Bryan’s PR/GitHub email. I don’t see any way we couldn’t attribute any code change to some user with a CLA active at any given time.
I don’t think the attic represents defeat, I’m reluctant to let it go to the attic but right now it seems that more work is being done on the ASF administrative stuff than actual code. That’s not a criticism of Peter or anyone else and all the effort has been put into various branches and so on. Rather it’s a statement of fact that there are very few us and we’re all busy.
River could always be taken back out of the attic should a new community grow around it.
I would be tempted to vote for the attic, whilst simultaneously moving River code (v3 if Peter is willing) into a GitHub repo and give the current PMC/committers read/write access to it. (Those that want it, of course.) Provide a link from the ASF page to GitHub and back again. We can carry on much the same as before, but without the overhead of filing reports and so on. As long as we stick to Bryan’s PR rules below, there shouldn’t be any problem giving any changes we eventually make back to the ASF should it be decided to do so.
The attic isn’t a defeat, it’s an evolution.
> On 5 Jul 2016, at 13:51, Bryan Thompson <br...@blazegraph.com> wrote:
>
> GitHub (at least) provides excellent tracking. It is a matter of how you
> define policy for PRs. We do not accept PRs unless the author is a
> contributor with appropriate CLAs for the project. So it works out very
> nicely for us. Every single commit and its authorship remains visible and
> that metadata can be easily accessed.
>
> Thanks,
> Bryan
>
> On Jul 5, 2016 2:12 AM, "Patricia Shanahan" <pa...@acm.org> wrote:
>
>> On 7/5/2016 1:26 AM, Peter wrote:
>>
>>> Can we move to git, without moving to GitHub?
>>>
>>
>> Not currently. There is an experiment underway for a system that uses
>> GitHub with an Apache-controlled mirror. I will look again at the status of
>> that project.
>>
>> We can get a read-only git mirror. See http://www.apache.org/dev/git.html
>>
>>
>>> https://www.linux.com/blog/apache-hadoop-transitions-git
>>>
>>> A concern I have with moving to GitHub is DCMA take down notices and IP:
>>>
>>> https://github.com/github/dmca
>>>
>>> The Apache foundation provides us with legal support as well as
>>> governance.
>>>
>>
>> The git and legal issues are very closely related. One of Apache's
>> objectives is to be able to tie every change in any Apache code to a
>> license agreement. The foundation wants to be able to say, for example
>> "That block of code was checked in on date X by person Y, and here is an
>> ICLA from Y that was in effect on date X."
>>
>> As I understand the issue, normal Git is too flexible to give the required
>> provenance tracking.
>>
>>
>>> I always thought we could find a common code base that people can agree
>>> on, without hobbling the abilities or ambitions of those that want to do
>>> more.
>>>
>>> The next steps for me, when I have time, will be to update trunk version
>>> to River 2.3.0 from River 3.0.0, update the release notes, generate and
>>> sign the release artifacts with our new code signing certs, that Apache
>>> recently paid for, for our next round of voting.
>>>
>>> I'm not ready to admit defeat yet, that's what the attic represents.
>>> The project has survived longer periods of stagnation or disagreement in
>>> the past, such as during incubation and become active again.
>>>
>>
>> OK - I'll wait to see what happens.
>>
>> Patricia
>>
Re: Attic? Was: Re: Lotj - languages other than java
Posted by Bryan Thompson <br...@blazegraph.com>.
GitHub (at least) provides excellent tracking. It is a matter of how you
define policy for PRs. We do not accept PRs unless the author is a
contributor with appropriate CLAs for the project. So it works out very
nicely for us. Every single commit and its authorship remains visible and
that metadata can be easily accessed.
Thanks,
Bryan
On Jul 5, 2016 2:12 AM, "Patricia Shanahan" <pa...@acm.org> wrote:
> On 7/5/2016 1:26 AM, Peter wrote:
>
>> Can we move to git, without moving to GitHub?
>>
>
> Not currently. There is an experiment underway for a system that uses
> GitHub with an Apache-controlled mirror. I will look again at the status of
> that project.
>
> We can get a read-only git mirror. See http://www.apache.org/dev/git.html
>
>
>> https://www.linux.com/blog/apache-hadoop-transitions-git
>>
>> A concern I have with moving to GitHub is DCMA take down notices and IP:
>>
>> https://github.com/github/dmca
>>
>> The Apache foundation provides us with legal support as well as
>> governance.
>>
>
> The git and legal issues are very closely related. One of Apache's
> objectives is to be able to tie every change in any Apache code to a
> license agreement. The foundation wants to be able to say, for example
> "That block of code was checked in on date X by person Y, and here is an
> ICLA from Y that was in effect on date X."
>
> As I understand the issue, normal Git is too flexible to give the required
> provenance tracking.
>
>
>> I always thought we could find a common code base that people can agree
>> on, without hobbling the abilities or ambitions of those that want to do
>> more.
>>
>> The next steps for me, when I have time, will be to update trunk version
>> to River 2.3.0 from River 3.0.0, update the release notes, generate and
>> sign the release artifacts with our new code signing certs, that Apache
>> recently paid for, for our next round of voting.
>>
>> I'm not ready to admit defeat yet, that's what the attic represents.
>> The project has survived longer periods of stagnation or disagreement in
>> the past, such as during incubation and become active again.
>>
>
> OK - I'll wait to see what happens.
>
> Patricia
>
Re: Attic? Was: Re: Lotj - languages other than java
Posted by Patricia Shanahan <pa...@acm.org>.
On 7/5/2016 1:26 AM, Peter wrote:
> Can we move to git, without moving to GitHub?
Not currently. There is an experiment underway for a system that uses
GitHub with an Apache-controlled mirror. I will look again at the status
of that project.
We can get a read-only git mirror. See http://www.apache.org/dev/git.html
>
> https://www.linux.com/blog/apache-hadoop-transitions-git
>
> A concern I have with moving to GitHub is DCMA take down notices and IP:
>
> https://github.com/github/dmca
>
> The Apache foundation provides us with legal support as well as governance.
The git and legal issues are very closely related. One of Apache's
objectives is to be able to tie every change in any Apache code to a
license agreement. The foundation wants to be able to say, for example
"That block of code was checked in on date X by person Y, and here is an
ICLA from Y that was in effect on date X."
As I understand the issue, normal Git is too flexible to give the
required provenance tracking.
>
> I always thought we could find a common code base that people can agree
> on, without hobbling the abilities or ambitions of those that want to do
> more.
>
> The next steps for me, when I have time, will be to update trunk version
> to River 2.3.0 from River 3.0.0, update the release notes, generate and
> sign the release artifacts with our new code signing certs, that Apache
> recently paid for, for our next round of voting.
>
> I'm not ready to admit defeat yet, that's what the attic represents.
> The project has survived longer periods of stagnation or disagreement in
> the past, such as during incubation and become active again.
OK - I'll wait to see what happens.
Patricia
Re: Attic? Was: Re: Lotj - languages other than java
Posted by Peter <ji...@zeus.net.au>.
Can we move to git, without moving to GitHub?
https://www.linux.com/blog/apache-hadoop-transitions-git
A concern I have with moving to GitHub is DCMA take down notices and IP:
https://github.com/github/dmca
The Apache foundation provides us with legal support as well as governance.
I always thought we could find a common code base that people can agree
on, without hobbling the abilities or ambitions of those that want to do
more.
The next steps for me, when I have time, will be to update trunk version
to River 2.3.0 from River 3.0.0, update the release notes, generate and
sign the release artifacts with our new code signing certs, that Apache
recently paid for, for our next round of voting.
I'm not ready to admit defeat yet, that's what the attic represents.
The project has survived longer periods of stagnation or disagreement in
the past, such as during incubation and become active again.
Regards,
Peter.
On 5/07/2016 1:47 AM, Patricia Shanahan wrote:
> See https://attic.apache.org/ for an introduction.
>
> The question I am raising is whether River is viable as an Apache
> project, not whether it is a valuable body of code. Your second
> paragraph is exactly my point.
>
> Apache brings some good stuff to its projects in the form of licensing
> with carefully controlled provenance and signed, tested releases. The
> downside is a process that is incompatible with Github, and some
> bureaucracy around the release process.
>
> If that is not currently the right trade-off for River the best thing
> to do is to move to the attic. Any individual, or group of
> individuals, can download the code and use it any way they like that
> is compatible with Apache's license, which allows a lot. In
> particular, people who agree on a direction can start their own Github
> repository based on the River code. They do have to preserve some
> notices and make it clear that they have modified the code. See
> http://www.apache.org/licenses/LICENSE-2.0 for details.
>
> Patricia
>
> On 7/4/2016 7:49 AM, Bryan Thompson wrote:
>> I am just not that familiar with Apache policy. However, river is a
>> real,
>> functional, deployed in use platform. I certainly agree that there is
>> deadlock at this point in terms of the people and process. However,
>> I am
>> not sure that an attic is the right place for a well grounded and
>> fielded
>> technology. While the community might not be able to move ahead along a
>> clear roadmap, there is still support from the community for the
>> technology.
>>
>> Maybe a move to github would help to break things loose? Open up the
>> development and release process more? Right now things are hung up
>> in part
>> on Apache process. Maybe Apache is just not the right place at this time
>> for this technology?
>>
>> Thanks,
>> Bryan
>>
>> On Mon, Jul 4, 2016 at 10:08 AM, Patricia Shanahan <pa...@acm.org> wrote:
>>
>>> I think it is time to raise on the user list moving River to the attic.
>>>
>>> There is no sign of progress on a release. What interest there is in
>>> development seems to be going in different directions. Using
>>> portions of
>>> River code in other projects would still be feasible with it in the
>>> attic,
>>> but there would be no need for a PMC, and board reports.
>>>
>>> Patricia
>>>
>>> On 7/4/2016 6:44 AM, Simon IJskes - QCG wrote:
>>> ...
>>>
>>>> But then again, there are a lot of people reading this, and a big part
>>>> of them having no interest at all in incompatible improvements, and i
>>>> see no other option than leaving them behind, with a jini compatible
>>>> maintenance release. This will certainly tear the river community
>>>> apart,
>>>> or at least cause a lot of friction. So when i see only the two of us,
>>>> moving in a new direction, i can't help feeling, what is the use of it
>>>> all.
>>>>
>>>> G. Simon
>>>>
>>>>
>>>>
>>>>
>>
>
Re: Attic? Was: Re: Lotj - languages other than java
Posted by Patricia Shanahan <pa...@acm.org>.
See https://attic.apache.org/ for an introduction.
The question I am raising is whether River is viable as an Apache
project, not whether it is a valuable body of code. Your second
paragraph is exactly my point.
Apache brings some good stuff to its projects in the form of licensing
with carefully controlled provenance and signed, tested releases. The
downside is a process that is incompatible with Github, and some
bureaucracy around the release process.
If that is not currently the right trade-off for River the best thing to
do is to move to the attic. Any individual, or group of individuals, can
download the code and use it any way they like that is compatible with
Apache's license, which allows a lot. In particular, people who agree on
a direction can start their own Github repository based on the River
code. They do have to preserve some notices and make it clear that they
have modified the code. See http://www.apache.org/licenses/LICENSE-2.0
for details.
Patricia
On 7/4/2016 7:49 AM, Bryan Thompson wrote:
> I am just not that familiar with Apache policy. However, river is a real,
> functional, deployed in use platform. I certainly agree that there is
> deadlock at this point in terms of the people and process. However, I am
> not sure that an attic is the right place for a well grounded and fielded
> technology. While the community might not be able to move ahead along a
> clear roadmap, there is still support from the community for the technology.
>
> Maybe a move to github would help to break things loose? Open up the
> development and release process more? Right now things are hung up in part
> on Apache process. Maybe Apache is just not the right place at this time
> for this technology?
>
> Thanks,
> Bryan
>
> On Mon, Jul 4, 2016 at 10:08 AM, Patricia Shanahan <pa...@acm.org> wrote:
>
>> I think it is time to raise on the user list moving River to the attic.
>>
>> There is no sign of progress on a release. What interest there is in
>> development seems to be going in different directions. Using portions of
>> River code in other projects would still be feasible with it in the attic,
>> but there would be no need for a PMC, and board reports.
>>
>> Patricia
>>
>> On 7/4/2016 6:44 AM, Simon IJskes - QCG wrote:
>> ...
>>
>>> But then again, there are a lot of people reading this, and a big part
>>> of them having no interest at all in incompatible improvements, and i
>>> see no other option than leaving them behind, with a jini compatible
>>> maintenance release. This will certainly tear the river community apart,
>>> or at least cause a lot of friction. So when i see only the two of us,
>>> moving in a new direction, i can't help feeling, what is the use of it
>>> all.
>>>
>>> G. Simon
>>>
>>>
>>>
>>>
>
Re: Attic? Was: Re: Lotj - languages other than java
Posted by Patricia Shanahan <pa...@acm.org>.
I just hope a move to git does not become yet another reason to delay a
release. A few months ago we were really close - just a matter of fixing
a qa build failure.
On 7/5/2016 11:44 PM, Peter wrote:
> Thanks Brian,
>
> Hang in there, I think we can get back on track without fragmenting,
> I've seen the developers on this project work well together in the
> past. I do agree GitHub is less work for releases, I'm going to attempt
> to get access to Apache's git wip repository. My experience has been
> that much more communication occurs on Apache River mail lists. The
> traffic I get with my fork on GitHub relates to input validation for
> deserialization.
>
> Regards,
>
> Peter.
>
>
> On 5/07/2016 12:49 AM, Bryan Thompson wrote:
>> I am just not that familiar with Apache policy. However, river is a
>> real,
>> functional, deployed in use platform. I certainly agree that there is
>> deadlock at this point in terms of the people and process. However, I am
>> not sure that an attic is the right place for a well grounded and fielded
>> technology. While the community might not be able to move ahead along a
>> clear roadmap, there is still support from the community for the
>> technology.
>>
>> Maybe a move to github would help to break things loose? Open up the
>> development and release process more? Right now things are hung up in
>> part
>> on Apache process. Maybe Apache is just not the right place at this time
>> for this technology?
>>
>> Thanks,
>> Bryan
>>
>> On Mon, Jul 4, 2016 at 10:08 AM, Patricia Shanahan<pa...@acm.org> wrote:
>>
>>> I think it is time to raise on the user list moving River to the attic.
>>>
>>> There is no sign of progress on a release. What interest there is in
>>> development seems to be going in different directions. Using portions of
>>> River code in other projects would still be feasible with it in the
>>> attic,
>>> but there would be no need for a PMC, and board reports.
>>>
>>> Patricia
>>>
>>> On 7/4/2016 6:44 AM, Simon IJskes - QCG wrote:
>>> ...
>>>
>>>> But then again, there are a lot of people reading this, and a big part
>>>> of them having no interest at all in incompatible improvements, and i
>>>> see no other option than leaving them behind, with a jini compatible
>>>> maintenance release. This will certainly tear the river community
>>>> apart,
>>>> or at least cause a lot of friction. So when i see only the two of us,
>>>> moving in a new direction, i can't help feeling, what is the use of it
>>>> all.
>>>>
>>>> G. Simon
>>>>
>>>>
>>>>
>>>>
>
Re: Attic? Was: Re: Lotj - languages other than java
Posted by Peter <ji...@zeus.net.au>.
Thanks Brian,
Hang in there, I think we can get back on track without fragmenting,
I've seen the developers on this project work well together in the
past. I do agree GitHub is less work for releases, I'm going to attempt
to get access to Apache's git wip repository. My experience has been
that much more communication occurs on Apache River mail lists. The
traffic I get with my fork on GitHub relates to input validation for
deserialization.
Regards,
Peter.
On 5/07/2016 12:49 AM, Bryan Thompson wrote:
> I am just not that familiar with Apache policy. However, river is a real,
> functional, deployed in use platform. I certainly agree that there is
> deadlock at this point in terms of the people and process. However, I am
> not sure that an attic is the right place for a well grounded and fielded
> technology. While the community might not be able to move ahead along a
> clear roadmap, there is still support from the community for the technology.
>
> Maybe a move to github would help to break things loose? Open up the
> development and release process more? Right now things are hung up in part
> on Apache process. Maybe Apache is just not the right place at this time
> for this technology?
>
> Thanks,
> Bryan
>
> On Mon, Jul 4, 2016 at 10:08 AM, Patricia Shanahan<pa...@acm.org> wrote:
>
>> I think it is time to raise on the user list moving River to the attic.
>>
>> There is no sign of progress on a release. What interest there is in
>> development seems to be going in different directions. Using portions of
>> River code in other projects would still be feasible with it in the attic,
>> but there would be no need for a PMC, and board reports.
>>
>> Patricia
>>
>> On 7/4/2016 6:44 AM, Simon IJskes - QCG wrote:
>> ...
>>
>>> But then again, there are a lot of people reading this, and a big part
>>> of them having no interest at all in incompatible improvements, and i
>>> see no other option than leaving them behind, with a jini compatible
>>> maintenance release. This will certainly tear the river community apart,
>>> or at least cause a lot of friction. So when i see only the two of us,
>>> moving in a new direction, i can't help feeling, what is the use of it
>>> all.
>>>
>>> G. Simon
>>>
>>>
>>>
>>>
Re: Attic? Was: Re: Lotj - languages other than java
Posted by Bryan Thompson <br...@blazegraph.com>.
I am just not that familiar with Apache policy. However, river is a real,
functional, deployed in use platform. I certainly agree that there is
deadlock at this point in terms of the people and process. However, I am
not sure that an attic is the right place for a well grounded and fielded
technology. While the community might not be able to move ahead along a
clear roadmap, there is still support from the community for the technology.
Maybe a move to github would help to break things loose? Open up the
development and release process more? Right now things are hung up in part
on Apache process. Maybe Apache is just not the right place at this time
for this technology?
Thanks,
Bryan
On Mon, Jul 4, 2016 at 10:08 AM, Patricia Shanahan <pa...@acm.org> wrote:
> I think it is time to raise on the user list moving River to the attic.
>
> There is no sign of progress on a release. What interest there is in
> development seems to be going in different directions. Using portions of
> River code in other projects would still be feasible with it in the attic,
> but there would be no need for a PMC, and board reports.
>
> Patricia
>
> On 7/4/2016 6:44 AM, Simon IJskes - QCG wrote:
> ...
>
>> But then again, there are a lot of people reading this, and a big part
>> of them having no interest at all in incompatible improvements, and i
>> see no other option than leaving them behind, with a jini compatible
>> maintenance release. This will certainly tear the river community apart,
>> or at least cause a lot of friction. So when i see only the two of us,
>> moving in a new direction, i can't help feeling, what is the use of it
>> all.
>>
>> G. Simon
>>
>>
>>
>>