On Aug 8, 2006, at 4:43 PM, Jeremy Kemper wrote:
On Aug 8, 2006, at 3:47 PM, Michael Koziarski wrote:
For example I just submitted a documentation patch
(http://dev.rubyonrails.org/ticket/5762) for the :from option for
the
ActiveRecord find method. I'd think that adding support for this
opt
On Aug 8, 2006, at 3:47 PM, Michael Koziarski wrote:
For example I just submitted a documentation patch
(http://dev.rubyonrails.org/ticket/5762) for the :from option for the
ActiveRecord find method. I'd think that adding support for this
option should have had documentation associated with it w
For example I just submitted a documentation patch
(http://dev.rubyonrails.org/ticket/5762) for the :from option for the
ActiveRecord find method. I'd think that adding support for this
option should have had documentation associated with it when it was
added to begin with.
Just me 2 cents.
Tr
Another good example that lacks documentation is behavior
additions/changes. I.e.: the patch for has_one saving on create versus
saving on update where it used to save on both. The new patch doesn't
do what I expect and I has to bug poor Jonathan to clarify what his
expectations were on his p
On Aug 8, 2006, at 10:41 AM, Andrew Kaspick wrote:
The submission process for patches doesn't mention updating associated
documentation (as far as I can see). This should also be a
requirement along with test cases so that documentation stays up to
date.
+1
court3nay
___
I think at the moment it's heavily encouraged that documenation be
included with patches. What this turns out to mean commit side is that
if your patch has associated documentation and tests included it's
significantly more likely that it will be commited. More people just
need to know this (or ta
Andrew Kaspick wrote:
The submission process for patches doesn't mention updating associated
documentation (as far as I can see). This should also be a
requirement along with test cases so that documentation stays up to
date. If we're planning on having good documention and we use the
fund mo
Hello,
Just thought I'd make a remark regarding documentation.
The submission process for patches doesn't mention updating associated
documentation (as far as I can see). This should also be a
requirement along with test cases so that documentation stays up to
date. If we're planning on having
On Aug 5, 2006, at 2:28 PM, A. S. Bradbury wrote:
On Friday 04 August 2006 23:42, court3nay wrote:
Hey all,
#caboose has started a fund to hire someone, or offer a bounty, to
work in a dedicated fashion on documentation..
We've already raised over $800 in the first hour. (make that $900..)
(it
On Friday 04 August 2006 23:42, court3nay wrote:
> Hey all,
>
> #caboose has started a fund to hire someone, or offer a bounty, to
> work in a dedicated fashion on documentation..
> We've already raised over $800 in the first hour. (make that $900..)
> (it's gone up to $1120 in the time it took to
* court3nay ([EMAIL PROTECTED]) [060805 13:30]:
> By the way.. we just passed $13,000 in donations. Yay, community!
>
> I'm going to need a NPO (non-profit) to funnel this through, what do you (i.e.
> core-list) people think about a Rails foundation?
It takes a long time to get 501(c)(3)'s set u
On 8/5/06, Blake Watters <[EMAIL PROTECTED]> wrote:
$13,000 in what, 24 hours? Holy balls, that's some serious response!
It's really more like 18 hours... :)
--
Kevin Clark
http://glu.ttono.us
___
Rails-core mailing list
Rails-core@lists.rubyonrails
$13,000 in what, 24 hours? Holy balls, that's some serious response! Somebody should get another post up on Riding Rails with that sweet number.On Aug 5, 2006, at 2:28 PM, court3nay wrote:On Aug 4, 2006, at 5:39 PM, Charles O Nutter wrote:On 8/4/06, court3nay <[EMAIL PROTECTED]> wrote: On Aug 4, 20
That's what I emailed you about earlier today. ;-)
court3nay wrote:
Yup.. a coherent voice really helps.
By the way.. we just passed $13,000 in donations. Yay, community!
I'm going to need a NPO (non-profit) to funnel this through, what do
you (i.e. core-list) people think about a Rails fo
On Aug 4, 2006, at 5:39 PM, Charles O Nutter wrote:On 8/4/06, court3nay <[EMAIL PROTECTED]> wrote: On Aug 4, 2006, at 5:11 PM, Charles O Nutter wrote:> Perhaps taking a wiki approach would be a better way to target this> fundage? I'm thinking about doing this with RubySpec...get the> community cont
On 5-aug-2006, at 2:39, Charles O Nutter wrote:
That's fair too..I think any good wiki needs a steward (or a few
stewards) to keep it uniform. But a good wiki is quite an amazing
thing.
I absolutely _adored_ the Rails Hieraki. I would love to see it get
some attention instead of the wiki
On 8/4/06, court3nay <[EMAIL PROTECTED]> wrote:
On Aug 4, 2006, at 5:11 PM, Charles O Nutter wrote:> Perhaps taking a wiki approach would be a better way to target this> fundage? I'm thinking about doing this with RubySpec...get the> community contributing to the wiki, using the money as "prizes" f
On Aug 4, 2006, at 5:11 PM, Charles O Nutter wrote:
Perhaps taking a wiki approach would be a better way to target this
fundage? I'm thinking about doing this with RubySpec...get the
community contributing to the wiki, using the money as "prizes" for
the top contributors. I think it's impor
Perhaps taking a wiki approach would be a better way to target this fundage? I'm thinking about doing this with RubySpec...get the community contributing to the wiki, using the money as "prizes" for the top contributors. I think it's important that documentation efforts like this involve a larger c
On 8/4/06, court3nay <[EMAIL PROTECTED]> wrote:
Hey all,
#caboose has started a fund to hire someone, or offer a bounty, to
work in a dedicated fashion on documentation..
We've already raised over $800 in the first hour. (make that $900..)
(it's gone up to $1120 in the time it took to write this
Hey all,
#caboose has started a fund to hire someone, or offer a bounty, to
work in a dedicated fashion on documentation..
We've already raised over $800 in the first hour. (make that $900..)
(it's gone up to $1120 in the time it took to write this email)
The post is here: http://blog.caboo
21 matches
Mail list logo
