search

ruby / www.ruby-lang.org

Source of the https://www.ruby-lang.org website.
883 stars 611 forks source link

Announce / Advertise new site #74

Closed stomar closed 11 years ago

stomar commented 11 years ago

Probably needed/appropriate:

  1. a general announcement and invitation to contribute
    • here, on www.ruby-lang.org
    • on the ruby-talk mailing list (@chikamichi)
    • on the ruby-dev and ruby-list(@hsbt)
    • rubyinside (@chikamichi)
    • reddit (@postmodern)
    • rubyflow (@postmodern)
    • on regional communities (Ruby France for @chikamichi, for instance)
  2. additional information for maintainers
    • on vit-core (@chikamichi)
  3. conference announcement
    • RubyKaigi 2013 (@hsbt)
    • ReddotRubyconf 2013 (@hsbt)

Updated; Feel free to add to this list

chikamichi commented 11 years ago

Let's be remembered of http://www.rubyinside.com/official-ruby-site-not-so-good-5248.html which was one of the motivating factors for the Jekyll+git port. We may thus want to include rubyinside, and maybe other news site, in our "press release" list.

postmodern commented 11 years ago

I can post to reddit / rubyflow as well.

hsbt commented 11 years ago

I'm going to announce new site and contribution of vit-core team in rubykaigi 2013. and ruby-list(in japanese)

postmodern commented 11 years ago

Do people still read footers in the year 2013? :P

hsbt commented 11 years ago

Can I announce new site soon after migration? Should I wait before vit-core team announce?

postmodern commented 11 years ago

We :+1: doing a silent migration, and then initiating the post-migration phase. Post-migration should cleanup and simplify the structure of the site. This will make it easier for people to contribute to the new site. I like the idea of doing an official announcement at Ruby Kaigi.

hsbt commented 11 years ago

@postmodern It's ok. but I'll announce only webmaster of ruby-lang.org such as shugo and eban.

postmodern commented 11 years ago

@hsbt ah of course, definitely tell the other webmasters / infrastructure people.

chikamichi commented 11 years ago

I feel all warm inside :) It's been 2 years…

postmodern commented 11 years ago

Soon...

stomar commented 11 years ago

Regarding the somewhat vague term "vit-core team": if I'm not mistaken, of the 5 people that contributed to the repo or took part in the discussions only 2 actually are members of the team (@JEG2 and @chikamichi). I'm really not sure how many of the group are still active. The feedback on the vit-core mailing list during the last months always has been rather disappointing... :(

stomar commented 11 years ago

@postmodern: What "cleanup" and "simplification" of the site structure do you have in mind? Besides some smaller fixes that have been hold off or the removing of the import tasks I do not see a necessity for changes.

JEG2 commented 11 years ago

Just remember, "silence means consent," so we're all full up on approval. ;)

stomar commented 11 years ago

Good to know, I assumed I had been spam filtered...

Considering the nearing switch, who does volunteer to compose the wording of the announcement? (I'm out of this.)

stomar commented 11 years ago

@hsbt, @postmodern, all: shouldn't we announce now?

@JEG2: I believe from the persons present here you are the one with the longest connection to ruby-lang.org. Also, as far as I'm concerned, it was essentially you who gave the thumbs up on reviving postmodern's Jekyll port a couple of months ago. Plus you are a native speaker. Could you imagine writing a couple of lines...? :)

JEG2 commented 11 years ago

Hey all.

You have my full support.

However, I'm really busy right now and I would really like it if we could offload the English maintenance work to someone else for now. A good first step would be getting that person to write the announcements.

Any takers?

postmodern commented 11 years ago

I can volunteer a couple hours of proof-reading. Is this the formal announcement for RubyKaigi or a mailing list announcement? BTW, I updated the count-down on our teaser site for RubyKaigi.

JEG2 commented 11 years ago

I think it should be announced on the VIT mailing list, Twitter, the site itself, etc., personally.

stomar commented 11 years ago

I would say that essentially one (short) text for a news post here would suffice. The same text could be sent (if necessary with minor changes) to the mailing lists.

The vit-core mail would probably need an additional note that maintainers should open a pull request for getting a commit bit.

@postmodern What's the point of waiting another month??? Afaik, the next patch level release is announced for second week of May. IMO we should conclude the migration before that or rather right now.

postmodern commented 11 years ago

@stomar might want to coordinate with @hsbt, who will also be announcing it at RubyKaigi next month.

chikamichi commented 11 years ago

Hum, Ruby Kaigi is held on May, 30th - June, 1st. If it acts as our "deadline", I guess we should prepare our announcement to be cross-posted (#74). What about creating a topic branch and creating a pull-request (to be not merged)? This way we could rework the thing in iterations :)

postmodern commented 11 years ago

:+1: Let's prepare for a announcement blitzkrieg.

hsbt commented 11 years ago

I'm going to announce "renewal of ruby-lang.org" in RubyKaigi. my talk is http://rubykaigi.org/2013/talk/S08

chikamichi commented 11 years ago

Pff, I've been overwhelmed with work and entirely blacked this out. I am in the process of sending emails to the various mailing lists (ruby-core/dev, ruby-talk, vit-core with additional info, ruby-france in French). Would this text fit our requirements?

On behalf of the Ruby community, we are pleased to announce to you that a brand new ruby-lang.org is now live!

Ruby's official website has stalled over the years, leading to a situation where only a subset of the available languages were actually maintained. Still, their content may not even be relevant in the current Ruby ecosystem. Something had to be done! A few rubyists thus gathered to build a whole new contribution platform, switching from a private CMS to an opened process.

Everyone is now able to edit the content and fix kinks in no time! We have set up a git-based process and Jekyll now powers the website: head to https://github.com/ruby/www.ruby-lang.org/wiki to learn more about the project and how to contribute.

We hope to be hearing from you and reviewing your Pull Requests,

Hal Brodigan (postmodern), Jean-Denis Vauguet (chikamichi), Marcus Stollsteimer (stomar), James Edward Gray II (JEG2), Hiroshi Shibata (hsbt).

@JEG2 as long as the form is concerned, any English mistakes/clumsiness to fix?

chikamichi commented 11 years ago

@hsbt @stomar @postmodern ping.

JEG2 commented 11 years ago

It sounds great to me.

chikamichi commented 11 years ago

@hsbt @stomar @postmodern @JEG2 I created a announcement branch to ease copyediting/reviewing: https://github.com/ruby/www.ruby-lang.org/commit/11d463a803694246b1ffd09eefbd47418213f530

stomar commented 11 years ago

Sounds good to me. GitHub-based or git-based? (I'm fine with both.)

chikamichi commented 11 years ago

I purposely chose git-based as to not emphasize on GitHub, the SaaS, but git, the tool.

chikamichi commented 11 years ago

I will send this tomorrow, around 12:00 UTC, if that's ok with you folks.

postmodern commented 11 years ago

@chikamichi looks good. Should we include a mention about needing Translation Maintainers and the new Guidelines? What sites will you be posting the announcement on? I'd recommend emailing Ruby5.

hsbt commented 11 years ago

I introduced ruby/www.ruby-lang.org and vit-core team in rubykaigi 2013.

postmodern commented 11 years ago

I posted my countdown website to RubyFlow, Reddit and Twitter. Although, an official announcement would be less confusing.

chikamichi commented 11 years ago

@postmodern I wanted to keep it short, so I linked to the wiki rather than the project's index, so that people see the guidelines first. Is that ok?

postmodern commented 11 years ago

@chikamichi fair enough. We should link to the Translator Guidelines on the frontpage of the Wiki.

chikamichi commented 11 years ago

Sent to Ruby-Talk, Ruby-Core, VIT-Core, Ruby5, Ruby Weekly, Reddit, Ruby Flow FR.

rubyflow.com and rubyinside.com are currently unreachable or very slow, preventing me from posting there.

hsbt commented 11 years ago

finished to announce at RedDotRubyConf, I got to offer help for `id`` locale and more.

Can we close this issue?

stomar commented 11 years ago

Also post here?

postmodern commented 11 years ago

Just need to make a news post and we can close this.