Brian,
Did you have any suggested changes to the forks section wording to clear up
my intent for that section?
I'd like to start wrapping this up and move towards making it official
Everyone else,
Time to shout out if you have any issues / suggested improvements on the
content
- Stephen
On
Some small formating or typos.
Added commas in a long sentence around line 280 and another one around
l298. I generally find it hard to concentrate on a whole sentence without
commas (or even periods separating ideas).
See https://gist.github.com/Batmat/6155302 for proposed patch.
If you need any
Yes, I will take a pass tonight.
On Mon, Aug 5, 2013 at 6:55 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
Brian,
Did you have any suggested changes to the forks section wording to clear up
my intent for that section?
I'd like to start wrapping this up and move towards making
On Fri, Aug 2, 2013 at 5:47 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
I didn't use gerrit nor have seen anybody using it.
Gerrit was created by and for Android: https://android-review.googlesource.com
It's used for Gerrit itself https://gerrit-review.googlesource.com
(dogfooding), Chromium
I have updated the project-roles with my thoughts resulting from the
healthy debate on the list and some debates elsewhere.
If anyone wants to look at the resulting Work In Progress document as a
whole:
I think the bulk of this is pretty good. On the fork section, specifically:
As soon as changes in that
fork are identified which should be brought back to the project those
changes should be introduced into at least a branch hosted on the Apache Maven
source control in order to facilitate the
Hi Stephen,
If anyone wants to look at the resulting Work In Progress document as
a whole:
http://svn.apache.org/viewvc/maven/site/trunk/content/markdown/project-roles.md?revision=1509594view=markup
Thoughts?
Big thumbs up to all your changes. Nice work.
Some brief comments from a
On 2 August 2013 16:07, Brian Fox bri...@infinity.nu wrote:
I think the bulk of this is pretty good. On the fork section, specifically:
As soon as changes in that
fork are identified which should be brought back to the project those
changes should be introduced into at least a branch
Furthermore, I'd like to see explicit procedural rules on Maven Core and
forking. For example, if there's a critical component needing development
for Core, and a PMC expresses that such development will be done outside of
Apache and then used as a dependency, shouldn't there be a vote on that?
On 2 August 2013 16:32, Paul Benedict pbened...@apache.org wrote:
Furthermore, I'd like to see explicit procedural rules on Maven Core and
forking. For example, if there's a critical component needing development
for Core, and a PMC expresses that such development will be done outside of
Hi Paul,
then used as a dependency, shouldn't there be a vote on that?
Wouldn't there be a vote for the adoption of any dependency, anyway? Or at
least a code review process on the changes that bring in that dependency...?
Regards,
Curtis
On Fri, Aug 2, 2013 at 10:32 AM, Paul Benedict
On 2 August 2013 16:08, Curtis Rueden ctrue...@wisc.edu wrote:
Hi Stephen,
If anyone wants to look at the resulting Work In Progress document as
a whole:
http://svn.apache.org/viewvc/maven/site/trunk/content/markdown/project-roles.md?revision=1509594view=markup
Thoughts?
Big
Le vendredi 2 août 2013 10:08:42 Curtis Rueden a écrit :
True, and it is good to warn about this. However, ultimately I think Git is
a better choice (than SVN) because it often makes code review much easier.
I didn't use gerrit nor have seen anybody using it. But I hear about it more
and more
I don't understand the iron hand analogy. I was expressing the use of a
vote to allow or disallow critical development outside of Apache. The vote
would lead to a consensus, no?
On Fri, Aug 2, 2013 at 10:41 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On 2 August 2013 16:32,
We cannot stop somebody from developing something outside of Apache.
So I could go off and write a High Performance Logging API... now I could
be doing that because I want to foist that Logging API on Maven... or I
could be doing it as an experiment that, if successful, I may offer for
Maven to
Hi Herve,
I didn't use gerrit nor have seen anybody using it. ... Is this pure
theory? a dream? a reality for a minority of experts, talking about it
loudly but no mere mortal can use it?
Google uses it (of course). For example, for Chromium:
https://gerrit.chromium.org/
Kitware uses it. ITK,
On Fri, Aug 2, 2013 at 12:10 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
So anyway, I now have this ultra whizzbang high performance logging API and
I am aware of some deficit in the logging performance of Maven, so I spin
up a private fork (it could be a hidden private fork, or
I've stated from the beginning of this thread that it's impossible to
prevent someone from developing outside of Apache. I stand by that still.
That can't be prevented and any attempt will fail since it's not practical.
If my words today aren't clear, I'll try again. My stance isn't about
halting
Line 238, 246 opertunity - opportunity
I wonder if a statement of policy should have so much procedure written
into it.
The procedures will change over time as people change their ideas about
best practices whereas policies should be less volatile.
It might be easier to state the goals of
thank you Curtis: all the pointers you gave are of great value!
I perfectly understand your Githubs examples: pull requests + work to give
pull requests most chances to be accepted
In fact, in our case, for somebody having commit privileges, using such pull
requests isn't the first thing I
On 02/08/2013 12:29 PM, Paul Benedict wrote:
I've stated from the beginning of this thread that it's impossible to
prevent someone from developing outside of Apache. I stand by that still.
That can't be prevented and any attempt will fail since it's not practical.
If my words today aren't
On 02/08/2013 11:32 AM, Paul Benedict wrote:
Furthermore, I'd like to see explicit procedural rules on Maven Core and
forking. For example, if there's a critical component needing development
for Core, and a PMC expresses that such development will be done outside of
Apache and then used as a
Le 2 août 2013 17:48, Hervé BOUTEMY herve.bout...@free.fr a écrit :
Le vendredi 2 août 2013 10:08:42 Curtis Rueden a écrit :
True, and it is good to warn about this. However, ultimately I think
Git is
a better choice (than SVN) because it often makes code review much
easier.
I didn't use
Le 2 août 2013 20:27, Baptiste MATHUS m...@batmat.net a écrit :
Le 2 août 2013 17:48, Hervé BOUTEMY herve.bout...@free.fr a écrit :
Le vendredi 2 août 2013 10:08:42 Curtis Rueden a écrit :
True, and it is good to warn about this. However, ultimately I think
Git is
a better choice
On Aug 2, 2013, at 12:30 PM, Paul Benedict pbened...@apache.org wrote:
I've stated from the beginning of this thread that it's impossible to
prevent someone from developing outside of Apache. I stand by that still.
That can't be prevented and any attempt will fail since it's not practical.
25 matches
Mail list logo
