Subversion Bounty

[Noah Slater-3]

Hey,

I appreciate you're all very busy people, but I'm currently working on
a not-yet-released GNU project and would prefer to continue using
Subversion when I move to Savannah.

I don't know if this is something you are interested in, but I am
prepared to offer a bounty to whomever completes this work. What
figure would you think is fair?

Time scales? Perhaps the end of February.

Thanks,

--
Noah Slater <http://www.bytesexual.org/>

"Creativity can be a social contribution, but only in so
far as society is free to use the results." - R. Stallman

[Sylvain Beucler-2]

On Mon, Nov 26, 2007 at 11:42:11AM +0000, Noah Slater wrote:

> Hey,
>
> I appreciate you're all very busy people, but I'm currently working on
> a not-yet-released GNU project and would prefer to continue using
> Subversion when I move to Savannah.
>
> I don't know if this is something you are interested in, but I am
> prepared to offer a bounty to whomever completes this work. What
> figure would you think is fair?
>
> Time scales? Perhaps the end of February.

Hi,

We currently provide SVN for a few beta testers with missing
automation for several features (commit notifications & hooks
management, dump import, CVS->SVN migration).

When the automation job is complete, we will be ready to enable SVN
sitewide.

So the best would be to offer a bounty for implementing this
automation. As this is payment for code that will run on GNU Savannah,
it needs to be done by somebody the FSF trusts.

> What figure would you think is fair?

I don't really understand the question (not an English native
speaker). What do you mean?

--
Sylvain

[Noah Slater-4]

On 29/11/2007, Sylvain Beucler <beuc@...> wrote:
> So the best would be to offer a bounty for implementing this
> automation. As this is payment for code that will run on GNU Savannah,
> it needs to be done by somebody the FSF trusts.

Okay, I am prepared to offer a bounty of $400 to get this done properly.

As a caveat, I would like commit messages to be able to close bugs. So
that, for example, I could check-in a change with the message "Frobbed
the FooBar, Closed: #3454" and it would close issue #3454 in Savannah.

I won't be able to pay this until January, preferably 1st February 2008.

Let me know what the FSF thinks,

--
Noah Slater <http://www.bytesexual.org/>

"Creativity can be a social contribution, but only in so
far as society is free to use the results." - R. Stallman

[Sylvain Beucler-2]

On Thu, Nov 29, 2007 at 07:41:54PM +0000, Noah Slater wrote:

> On 29/11/2007, Sylvain Beucler <beuc@...> wrote:
> > So the best would be to offer a bounty for implementing this
> > automation. As this is payment for code that will run on GNU Savannah,
> > it needs to be done by somebody the FSF trusts.
>
> Okay, I am prepared to offer a bounty of $400 to get this done properly.
>
> As a caveat, I would like commit messages to be able to close bugs. So
> that, for example, I could check-in a change with the message "Frobbed
> the FooBar, Closed: #3454" and it would close issue #3454 in Savannah.
>
> I won't be able to pay this until January, preferably 1st February 2008.
>
> Let me know what the FSF thinks,

If you can make an agreement with somebody approved by the FSF to
implement this, they will accept.

The "caveat" doesn't looks like a big issue.

I may be interested in the offer.

--
Sylvain

[Noah Slater-4]

On 29/11/2007, Sylvain Beucler <beuc@...> wrote:
> If you can make an agreement with somebody approved by the FSF to
> implement this, they will accept.

Cool, just let me know. I'm in no rush.

--
Noah Slater <http://www.bytesexual.org/>

"Creativity can be a social contribution, but only in so
far as society is free to use the results." - R. Stallman

[Noah Slater-4]

Here are a more detailed list of "requirements" I would like:

1. Commit messages to affect tickets. I would like functionality similar to:

http://unfuddle.com/blog/2007/7/26/powerful-subversion-commit-messages

Note that syntax should be case insensitive and should allow for
"Closed: #123", "closed #123" or "closed #123, #234 and #345" like the
previous link shows.

2. Some way of browsing the subversion repository.

3. Some way of inspecting diffs between changesets.

I don't know how feasible this is, but optionally:

4. Some way of showing recent commits, a timeline like Trac.

Hmm, one more thing, I assume you provide a way to email changesets to
an email address?

Let me know if any of this is way off base.

Thanks,

--
Noah Slater <http://www.bytesexual.org/>

"Creativity can be a social contribution, but only in so
far as society is free to use the results." - R. Stallman