[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debian-users:47678] FYI (Forward: Ruby knowledge for DebConf wanted)

武藤＠Debianã·ã‚ã˜ã‡ãã¨ã§ã™ã€‚

æ¥å¹´é–‹å‚¬ã®Debconf 7ã®ã‚µã‚¤ãƒˆã®æ§‹ç¯‰ã«RubyonRailsを使ã£ãŸã‚‚ã®ã®ã€
スタッフå´ã®æ‰‹ã«ä½™ã‚‹ã®ã§ã‚«ã‚¹ã‚¿ãƒžã‚¤ã‚ºã§ãる人を募集中ã®ã‚ˆã†ã§ã™ã€‚
ã©ãªãŸã‹è¯éº—ã«ç™»å ´ã—ã¦åå‰ã‚’覚ãˆã¦ã‚‚らã†ã¨ã€ã„ã‚ã„ã‚ã¨å¥½éƒ½åˆãª
ã“ã¨ãŒã‚ã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“ :)
--- Begin Message --- 
Hi

Please respect Reply-To/Mail-Followup-To, which is set to
debconf-team@xxxxxxxxxxxxxxxxx, thanks.


As people who followed the recent Call for Papers/Registration for
DebConf7 may have seen we are now using a new system (Pentabarf) to manage the
attendees and talks. This system is written in Ruby (and a bit
Javascript), using the RubyonRails framework, storing its data in a
postgresql database.

While upstream is nice and usually responds quickly and also helps a lot
if one has issues, the thing is currently very dependant on
myself. Which is a thing I dont like. There should be other persons who
know how to deal with it, just in case the magic bus finds me...

So, Im looking for people who want to help.

What you need to know:

- Ruby and RubyonRails, obviously :)
- SQL
- a bit Javascript and HTML

What you have to do:

- deal with me. And also with the DebConf teams wishes for changes.
- adapt PentaBarf to our needs. Most things we needed for the
  Registration phase are done, but there are some open tasks for the
  schedule, some reports can be done, etc.

The whole work will be done in an svn, so we can easily track changes,
merge in upstream changes, etc. As said earlier upstream is nice and
helps wherever possible, so we give back everything thats not too
DebConf-specific.

If you are interested in helping out either reply to this mail or talk
to me on irc (irc.debian.org, #debconf-team).

-- 
bye Joerg
I read the DUMP and agree to it.

Attachment: pgpM4cCJW2q8g.pgp
Description: PGP signature


--- End Message ---