Ruby knowledge for DebConf wanted

[Joerg Jaspert]

Hi

Please respect Reply-To/Mail-Followup-To, which is set to
debconf-team@lists.debconf.org, 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.


pgpuAEXtYWauW.pgp
Description: PGP signature

Re: Proposal: Handling of changelog bug closures in Debian derived distros

[Guillem Jover]

On Fri, 2006-11-17 at 12:32:18 -0800, Tollef Fog Heen wrote:
 Guillem Jover skrev:
  For specs I would add a new syntax, which could be used by everyone
  equally, even Debian could start using it if desired. Do launchpad specs
  have a numeric value or are just strings?
 
 They are just strings.  But, as I wrote, they are just one example; we
 would probably want to associate uploads and bzr branches as well.  The
 LP syntax could be LP: #123 for closing bugs, LP: spec $specname for
 associating with a spec, and LP: bzr $product/$branchname (or something
 similar) for associating bzr branches with an upload.

Are those the only ones you'd need for now? Could the recently proposed
Vcs field help with the bzr branches or does this refer to upstream
branches only?

  What about Implements: foo (or similar), a proper regex would have
  to be defined, but you get the idea.
 
 Specs generally aren't implemented by a single upload, so it would be
 Spec-related or something like that.

Could you explain how would you use that information to associate
things? And is there some way you would mark that spec is fully
implemented?

 I would rather just have a namespace allocation and derivatives can do
 whatever they want within their namespace, but to a certain degree I see
 why this is problematic and it seems you are unhappy with that?

I'd prefer if we came up with something that is general and does not
need everyone around to implement their own solution. Granted some of
the work will still be specific per distribution, for example the
launchpad or bugzilla hooks into dak, but such solution would minimize
them, and most of the changes could be merged upstream w/o problem.

I suppose there would not be much of a problem with allocating a
namespace, but I'd like to go this route only as a last resort, in
case we find out that we cannot get a general solution that satisfies
everyone.

regards,
guillem


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

[user's view] about DFSG docs

[Oleg Verych]

Hallo. I'm new here; please, let me in.

I've just saw on emacsen list message, that questions DFSG vs GFDL is more
on topic here.

Our developers alone fail against them and started non-free packaging. As
ordinary Debian user, i decided to to write my own letter to FSF and GNU.
Their sites were down for quite a long time (from my part of web), thus
i've sent message to FSFEurope, and today bounced to [EMAIL PROTECTED]
FSFe employee told me, that everyone here is aware of the problem,
contact GNU project, we can't help you here, message was rejected. What
a silly situation? If somebody here wish to show way how users can
contact and bug FSF with GNU project, please give me idea.

TIA.

Message to them is added.

From olecom Sat Nov 18 18:34:55 2006
Date: Sat, 18 Nov 2006 18:34:55 +
To: Freedom Task Force [EMAIL PROTECTED]
Cc: Richard Stallman [EMAIL PROTECTED], discussion@fsfeurope.org,
debian-user@lists.debian.org
Subject: Licensing (GFDL)
Message-ID: [EMAIL PROTECTED]

Hallo.

I'm _ordinary_ user of *Free* operating system, full name of which is
`x86_64-pc-linux-gnu-debian'.

I hope you know, what Debian is. Just in case:
http://www.debian.org/intro/about

What's DFSG? It's a way to apply real-life rules. It's much more that
just to have a license in src directory and copyright note in every source
file. Meet users of your software, it's Stallman's write down your modified
version of recipe and share it with your friends.
http://www.debian.org/social_contract

What's result? Result is the most widely supported hardware architectures
ever, the biggest repository of *maintained* packages. It just works: on
servers and desktops (Debian), live (Knoppix and clones), it's host of
new generation of distributions (Ubuntu and clones). Fair enough!

Thus, you see, how Debian Free Software Guidelines led GNU+Linux to its
users. Commercial distribution creators are far behind. Yes, some of them
are playing significant role in software development, but i'm saying
about quality of distribution here. That is next step, they realized.
New brands: fedora, open*, free*, appeared. Non of which may be
compared to the Free GNU+Linux Operating System Debian.

Even Gentoo distribution turned to be just in one debian's packet called
apt-build. Close your windows and you will see real Debian !

Debian+HURD, Debian+kfreebsd. Yes, and it works.

Hell, what i'm talking about?!!!

,--*- shell -*-
|[EMAIL PROTECTED]:~$ nc fsfe.org 22
|SSH-2.0-OpenSSH_3.8.1p1 Debian-8.sarge.4
|
|[EMAIL PROTECTED]:~$
`--
(gnu.org, fsf.org currently down to check them)

So, why i'm here? I'm asking for help, Force to meet Freedom. Developers
of my OS fail to meet freedoms. They were proposing changes to GFDL v1.2,
that could led documentation of some programs to be Free, DFSG Free.
See my footer of nonsense FSF brought to proved Free Software Project.
Less that one screen page of whole section 4 here
http://www.debian.org/vote/2006/vote_001
will give you an idea what small changes are bringing down all FSF and
GNU Project on this stage.

o Forcing one GNU+Linux Operating System to be unable to develope, will
  led to unusable GNU Project.

o Forcing people not to have DFSG Free documentation will bring more
  problems to RMS and his propaganda and brainwashing.

This cost of Freedom is too high. Freedom to be free even from yourself
is very big deal.

Without new users, who can freely (debian/main) get and read manuals
(currently!) of most comprehensive development tools, Debian will R.I.P.
I can't find more words for that, what will happen.

I'm pretty sure my note currently must give you a *big fat warning*.

o main longterm glibc maintainer was forced to change license;
o copyrights assigments in GCC lead some people not to contribute really
  new and useful stuff;
o absence of license flexibility lead Linus Torvalds to write C
  front-end from scratch; and this guy really shows, us how to live
  with GNU GPLv2 in small scale of huge project of The Linux Kernel.

I bet he can write C compiler from ground, just for fun. And there
will be people on his size, note git source management system.
Pray he will use Fedora Core further, not Debian.

+ I'm personally using jed editor now, and i can see, how it can become
  GNU Emacs killer (among others, of course).

+ GNU make. `apt-cache search make build | grep -i make` in debian/main.

Please don't dig *your* grave.

[ initially i've put only FTF e-mail, but it archives are restricted,]
[ so, i'm adding discussion   e-mail to Cc list. ]

--
-o--=O`C  info emacs : not found  /. .\ ( is there any reason to live? )
 #oo'L O  info make  : not found  o (R.I.P. Debian Operating System)
___=E M  man gcc: not found.-- (  TNX, RMS.   )


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]