I won't be at Rubyconf, but would be interested in helping with
documentation too.

-J

On Thu, Nov 12, 2009 at 1:24 PM, Jacques Crocker <[email protected]> wrote:

> Cool, would love your help with some merb hacking and docs update at
> RubyConf. I also sold my ticket and will just be hanging around the area,
> focusing on Merb dev. I'll send out details about where people can meet up
> (will be either in the hotel or walking distance from it). Free food and
> drinks to anyone willing to join up to watch and/or code!
>
>
> On Nov 12, 2009, at 12:22 PM, Dylan Clendenin wrote:
>
> I would love to help with documentation materials in any way I can. I'm
> planning on spending as much of my RubyConf time as possible on Merb stuff.
> Maybe I should just sell my ticket?
>
> On Thu, Nov 12, 2009 at 7:00 AM, MarkMT <[email protected]> wrote:
>
>>
>> Thank you!
>>
>>
>> Martin Gamsjaeger wrote:
>> > Mark,
>> >
>> > Good catch! I enabled the Issues feature in the repos that still needed
>> it.
>> >
>> > cheers
>> > snusnu
>> >
>> > On Thu, Nov 12, 2009 at 15:17, MarkMT <[email protected]> wrote:
>> > >
>> > > MarkMT wrote:
>> > >> One thing I'm not clear on is the github issue tracking for gems not
>> > >> in the main repository. I haven't used github for this before and I'm
>> > >> having difficulty finding this feature. Can you maybe post a link to
>> > >> this feature for one of the repos, say merb_cucumber?
>> > >
>> > > Ok I figured out why I couldn't find the issues feature... you need to
>> > > explicitly turn this on in the admin panel for each project.
>> > >
>> > >
>> > >
>> > > >
>> > >
>>
>>
>
>
> --
> Dylan Clendenin
> 831.331.1484
>
>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"merb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/merb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to