[Brug-talk] Setup BRUG website

[Hans verschooten]

Maarten,

it is the Ruby user group :-)
I know that a lot of people come to Ruby via Rails, but we never know
what the future will bring us. Maybe Ruby will outlive Rails. So
better focus on the language than the framework, I guess.

Cheerio,
Hans

On 10/4/07, Maarten Porters <maarten at fastfocus.be> wrote:
> That logo kicks ass! :) Really cool. Maby I'm wrong but maby the rails
> aspect
> should be more involved in the logo or name. Because I have a feeling
> that most people
> use Ruby for rails. Again, maby I'm wrong.
>
> Greetz,
>
> Maarten
>
>
> Hans verschooten schreef:
> > Hi all,
> >
> > I couldn't resist so, here is my proposal for the logo. http://tintr.net/
> >
> > What do you think?
> >
> > Cheers,
> > Hans
> >
> > On 10/4/07, Peter Vanbroekhoven <peter at xaop.com> wrote:
> >
> >> Hi all,
> >>
> >> One of the things I wanted to discuss yesterday, but which we didn't get
> >> to anymore in the end, is how we are going to set up a website for our
> >> user group. I think we need the following:
> >>
> >> * hosting
> >> * one or a few people to create the site (Rails programmers, website
> >> designers)
> >> * a few people to create and manage the content
> >>
> >> These three groups needn't be disjunct, but they can be.
> >>
> >> We need volunteers for each of these jobs.
> >>
> >> Components for the website that I believe we certainly need are:
> >>
> >> * a wiki for putting together information (specific to BRUG and BRUG
> >> events, but also about Rails and Ruby in general)
> >> * news + feed (announcing events, project/library releases, ...)
> >>
> >> I propose using the brug project at Rubyforge for development
> >> (libraries, Rails plugins, ...). We can set our own website as the home
> >> page at Rubyforge. This way, Rubyforge ties us to the rest of the Ruby
> >> community and allows Rubyists all over the world to find us and our
> >> projects in the obvious place. This is independent from advertising our
> >> Ruby user group via other channels.
> >>
> >> Another nice thing to have would be a logo for BRUG. If someone feels up
> >> to the task of designing one or more candidates, you can find the Ruby
> >> logo here: http://rubyidentity.org/ruby-logo-kit.zip . The Rails logo is
> >> trademarked, so using that requires more care.
> >>
> >> Finally, I'm in the process of setting up a mailing list + Google group
> >> mirror for the BRUG admins. There are several reasons why it's nice to
> >> have this:
> >>
> >> * As pointed out by Peter, not everyone is interested in the
> >> administrative part, so it doesn't belong on the general list
> >> * A mailing list allows everyone who *is* interested to enter the
> >> discussions if so desired
> >> * A mailing list provides an archive of these discussions
> >> * Changes in the core admin group are easy to effectuate, just
> >> add/remove users to/from the list.
> >>
> >> I'll let you know when I receive notification that the list is created
> >> and then anyone interested can subscribe.
> >>
> >> Kind regards,
> >> Peter Vanbroekhoven
> >> _______________________________________________
> >> Brug-talk mailing list
> >> Brug-talk at rubyforge.org
> >> http://rubyforge.org/mailman/listinfo/brug-talk
> >>
> >>
> > _______________________________________________
> > Brug-talk mailing list
> > Brug-talk at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/brug-talk
> >
> >
>
> _______________________________________________
> Brug-talk mailing list
> Brug-talk at rubyforge.org
> http://rubyforge.org/mailman/listinfo/brug-talk
>