Re: report from darcs hacking sprint #1

Yay!  It looks like good progress for darcs!

Thanks everybody, and thanks to kowey for organizing, cheerleading,  
and writing up the results.

What about kowey's automatic benchmarking and zookeeping scripts --  
weren't those sprint material?  I'm pretty excited about that project  
-- automatic benchmarking and zookeeping.

Regards,

Zooko 

Re: darcs patch: Fix issue1183

On Fri, Oct 31, 2008 at 1:00 AM, Florent Becker
<florent.becker <at> ens-lyon.org> wrote:
>> Also note that if you make the patch name start with "resolve issue1183:",
>> then the bug will be automatically closed when I push, and if you mention
>> what change you made (or what the bug was) in the patch name, that's also
>> helpful.
>>
>> David
>
> This information might be worth putting into the repository motd. (On a side
> note, would a 'darcs show remote' feature to show a longer motd for the
> repository you would pull from/send to be interesting?)

This is a good point.

Eric, could you please update the motd in the unstable repo to say
something like this:
------- begin motd --------------
Welcome to the darcs stable repository.

If you would like to contribute, please read our guide for contributors:
http://wiki.darcs.net/DarcsWiki/DeveloperGettingStarted

Thanks and happy hacking!
-------- end motd ---------------

The motd doesn't appear to be a version controlled file or I would
have sent a patch.

Thanks!

Re: darcs patch: Fix issue1183

On Fri, Oct 31, 2008 at 6:34 PM, Jason Dagit <dagit <at> codersbase.com> wrote:
> On Fri, Oct 31, 2008 at 1:00 AM, Florent Becker
> <florent.becker <at> ens-lyon.org> wrote:
>>> Also note that if you make the patch name start with "resolve issue1183:",
>>> then the bug will be automatically closed when I push, and if you mention
>>> what change you made (or what the bug was) in the patch name, that's also
>>> helpful.
>>>
>>> David
>>
>> This information might be worth putting into the repository motd. (On a side
>> note, would a 'darcs show remote' feature to show a longer motd for the
>> repository you would pull from/send to be interesting?)
>
> This is a good point.
>
> Eric, could you please update the motd in the unstable repo to say
> something like this:

Er...I meant stable.  But, maybe unstable could have a similar message.

Jason

Re: report from darcs hacking sprint #1

On Fri, Oct 31, 2008 at 6:27 PM, zooko <zooko <at> zooko.com> wrote:
> Yay!  It looks like good progress for darcs!
>
> Thanks everybody, and thanks to kowey for organizing, cheerleading,
> and writing up the results.
>
> What about kowey's automatic benchmarking and zookeeping scripts --
> weren't those sprint material?  I'm pretty excited about that project
> -- automatic benchmarking and zookeeping.

We had lots of ideas before the sprint, but we found that once we were
at the sprint people had energy to tackle certain problems -- not
always the originally intended tasks.

There has been a lot of progress on the zoo and auto benchmarking
since the sprint though.  Simon and Eric (perhaps others?) have made
good progress on this front:
http://lists.osuosl.org/pipermail/darcs-users/2008-October/015312.html
http://lists.osuosl.org/pipermail/darcs-users/2008-October/015347.html

Thanks for the kind words!
Jason

Re: report from darcs hacking sprint #1

dagit:
> On Fri, Oct 31, 2008 at 6:27 PM, zooko <zooko <at> zooko.com> wrote:
> > Yay!  It looks like good progress for darcs!
> >
> > Thanks everybody, and thanks to kowey for organizing, cheerleading,
> > and writing up the results.
> >
> > What about kowey's automatic benchmarking and zookeeping scripts --
> > weren't those sprint material?  I'm pretty excited about that project
> > -- automatic benchmarking and zookeeping.
> 
> We had lots of ideas before the sprint, but we found that once we were
> at the sprint people had energy to tackle certain problems -- not
> always the originally intended tasks.

This is typical of hackathons, in my experience. As people get to know
the code better, they're better able to predict what they can actually
achieve on that code, during a 2 day sprint.

More sprints are called for 

-- Don

Re: style conventions and HACKING [was: shell_harness script in haskell]

Christian Kellermann <Christian.Kellermann <at> nefkom.net> writes:

>> We don't seem to have any hard and fast rules about line length, but
>> this one does seem overly long.  This might be a bit easier for
>> people:
>
> There does not need to me a rule, the above is indeed ugly, agreed.

Perhaps there should be a HACKING file that references some general
Haskell style guides, and describes any conventions for Darcs code?

Re: style conventions and HACKING [was: shell_harness script in haskell]

On Fri, Oct 31, 2008 at 7:05 PM, Trent W. Buck <trentbuck <at> gmail.com> wrote:
> Christian Kellermann <Christian.Kellermann <at> nefkom.net> writes:
>
>>> We don't seem to have any hard and fast rules about line length, but
>>> this one does seem overly long.  This might be a bit easier for
>>> people:
>>
>> There does not need to me a rule, the above is indeed ugly, agreed.
>
> Perhaps there should be a HACKING file that references some general
> Haskell style guides, and describes any conventions for Darcs code?

No objections to that.  We're currently hashing this document out on the wiki:
http://wiki.darcs.net/DarcsWiki/DeveloperGettingStarted
http://wiki.darcs.net/DarcsWiki/CodingStyle

And I've asked Eric to kindly update the motd to mention those
documents as well.

I know you tend to be web browser adverse, but the wiki seems to be a
nice way to collaborate on documentation.  So I hope you don't mind
collaborating there...

Thanks!
Jason

darcs patch: Add stub HACKING reference for new hackers.

Re discussion in "Re: darcs patch: shell_harness script in haskell" thread.

Sat Nov  1 13:26:08 EST 2008  Trent W. Buck <trentbuck <at> gmail.com>
  * Add stub HACKING reference for new hackers.

_______________________________________________
darcs-users mailing list
darcs-users <at> darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users

Re: style conventions and HACKING [was: shell_harness script in haskell]

trentbuck:
> Christian Kellermann <Christian.Kellermann <at> nefkom.net> writes:
> 
> >> We don't seem to have any hard and fast rules about line length, but
> >> this one does seem overly long.  This might be a bit easier for
> >> people:
> >
> > There does not need to me a rule, the above is indeed ugly, agreed.
> 
> Perhaps there should be a HACKING file that references some general
> Haskell style guides, and describes any conventions for Darcs code?

FWIw, we have a STYLE file with xmonad,

    http://code.haskell.org/xmonad/STYLE

Re: style conventions and HACKING [was: shell_harness script in haskell]

On Fri, Oct 31, 2008 at 07:11:34PM -0700, Jason Dagit wrote:
> On Fri, Oct 31, 2008 at 7:05 PM, Trent W. Buck <trentbuck <at> gmail.com> wrote:
> > Christian Kellermann <Christian.Kellermann <at> nefkom.net> writes:
> >
> >>> We don't seem to have any hard and fast rules about line length, but
> >>> this one does seem overly long.  This might be a bit easier for
> >>> people:
> >>
> >> There does not need to me a rule, the above is indeed ugly, agreed.
> >
> > Perhaps there should be a HACKING file that references some general
> > Haskell style guides, and describes any conventions for Darcs code?
> 
> No objections to that.  We're currently hashing this document out on the wiki:
> http://wiki.darcs.net/DarcsWiki/DeveloperGettingStarted
> http://wiki.darcs.net/DarcsWiki/CodingStyle
> 
> And I've asked Eric to kindly update the motd to mention those
> documents as well.
> 
> I know you tend to be web browser adverse, but the wiki seems to be
> a nice way to collaborate on documentation.  So I hope you don't
> mind collaborating there...

Sure; I'm prepared to accept increased suck for me in that respect
because a wiki is easier for "normal" people.

I *would* like it if we had something like ikiwiki providing a wiki
interface on top of an easy-for-me-to-use darcs repository full of
reST documents, but that isn't production-ready yet (in particular,