Manu Sporny | 13 Jun 2013 23:50
Gravatar

KickStarter for Debian packages - crowdfunding/donations for development

I'd like to add a feature to apt that enables people to donate money or
crowdfund a particular project or developer. The inspiration for the
project comes from [1]Gittip.

I've already contacted the APT project and they directed me here, as
they felt it needed to be discussed by the larger Debian community.

My name is [2]Manu Sporny and I'm the current chair of the Web Payments
group at the World Wide Web Consortium (W3C). I'm also the project
leader for the [3]PaySwarm project, which is an initiative to create a
universal payment standard for the Web. We're also currently [4]working
with Mozilla to build payments into the browser. Each of these
initiatives is a patent-free and royalty-free open standard that we'd
like to try and apply to the Debian project.

The general idea with apt-based donations is to enable every package in
Debian to be able to accept funding and/or donations for the project.
Here are some of the ideas we were kicking around:

 1. Simple donations. Donate a fixed dollar amount $1, $2.50,
 $5, or $10 to a project. This could be opt-in or automatic.

 2. Split donations. Donate a fixed dollar amount to a project,
 where 50% of the donation goes to the project and 50% of the
 donation is split equally among the project dependencies (by
 reading the Debian control file).

 3. Recurring donations. Same as the first item above, but
 happens on a recurring basis.

(Continue reading)

Brian Gupta | 12 Jun 2013 06:38
Gravatar

Answers to questions raised about registering the Debian Logo as our trademark

I finally had a chance to discuss with our legal counsel, and have
some answers to the questions raised in the discussion.

The summary of the Q&A is (from list and some of my own):

1) Does registering logo require any changes to TM policy?
A: No changes required

2) What are the costs to register in the US and internationally using
the Madrid Protocol?
A: ~$275 for US only, ~$3347 for the probable international
registrations we'd want.

3) Should we register in the US only or register internationally?
A: Being as US registration is mandatory to extend internationally
start with the US, and then later Debian can make a decision on
international registration.

4) What is the impact of registering in the US only?
A: We would still only have Common law protection in those countries
we don't register the logo. We'd gain no benefit in those
jurisdictions, but it wouldn't hurt us either. However, being that
getting a registration in the US is a prerequisite for applying for
international registration, this is largely an academic distinction.

5) Can overzealous law enforcement officers act against infringers
without our permission?
A: Not in the US. Outside the US requires further research.

6) Can we have logo protected under copyright law and trademark law,
(Continue reading)

Lucas Nussbaum | 9 Jun 2013 22:35
Picon
Favicon

next DPL helpers meeting on tuesday (2013-06-11)

Hi,

The next DPL helpers meeting is next tuesday on #debian-dpl:
2013-06-11 Tue 17:00 UTC (date -d  <at> 1370970000)

The agenda is online[1]. If you are listed on one of the pending
actions, it would be great if you could describe its status, and the
possible points needing discussion on titanpad (That should allow to be
more efficient during the meeting).
Also, feel free to add other points to discuss during the meeting.

[1] http://titanpad.com/debiandpl-20130611

Lucas
Picon

Minimum size of a distribution kit


Hello !

 What is minimum size of a distribution kit, excepting netinst ?
Can i use first CD for minimal installation and graphical desktop ?

Thanks in advance, ice.

Justin Breithaupt | 3 Jun 2013 05:38
Picon

Get your Linux Distribution / Project Listed !

I noticed your not listed on Distrowatch.com 
I'd like to help you get exposure for free, so please check out: http://mindblowingidea.com/distrolist/get-your-distro-listed/

My Linux Distribution is JULinux www.justuselinux.com and I noticed that Distrowatch is backed up on the waiting list to 2004, so I decided to make this site recently so that you can post your own distribution releases for free, on your own, once you set up a free account, and I approve you and give you rights to blog post ;)

I hope this helps people with Linux projects everywhere.
Daniel Pocock | 2 Jun 2013 12:12
Picon

when/how DDs can use the Debian name


There are many places where a DD may have an opportunity to use the
Debian name in a public sense.

However, I just want to seek some clarification about this

For example, if somebody is talking at some non-Debian IT event, and
they need to specify their organisation and position on their profile
could they simply put:

  Organisation:  Debian
  Position:      Debian Developer

or is this a privilege that is only reserved for office holders and
potentially the DPL's delegates?

I had a quick look at the constitution and it makes no specific
reference to how developers may use the Debian name or reference their
connection to the Debian Project.

Regards,

Daniel

Mònica Ramírez Arceda | 2 Jun 2013 09:26
Picon
Favicon

OPW; the result of the experiment

Hi,

OPW; the result of the experiment:

Background: Debian participated for the first time in Outreach Program
for Women [0]. We decided that this round would be an "experiment" to
see how it works.

Projects: We had the same coding projects than GSoC, we only had coding
projects, since there was too little time to prepare non-coding
projects. I want to thank Debian GSoC admins for helping in coordinating
OPW-GSoC!

Applicants: We had 4 applicants (3 gsoc/opw applicants and 1 only-opw
applicants). 1 of these 4 applicants was accepted, but she received a
slot in GSoC, so the OPW internship was not "used".

Future: OPW is run every 6 months and we should decide how Debian will
continue to participate. 

What is needed to continue:
* Sponsors to pay internships.
* More coordinating efforts: in this round we have taken advantage that
GSoC was running as well, but if we participate in Jan-Apr round, we
can't rely on GSoC efforts to bring in applicants and mentors.
* Projects and mentors for the next round
* Advertising opportunities to get the information out to interested
women students and those starting in technology.

So, what do you think? Should we continue with OPW? Are there more
volunteers?

Those interested are more than welcome to join #debian-opw. :)

Cheers!

[0] http://wiki.debian.org/OutreachProgramForWomen

Debian FTP Masters | 2 Jun 2013 04:02
Picon
Favicon

Debian Maintainers Keyring changes

The following changes to the debian-maintainers keyring have just been activated:

berto <at> igalia.com
    Full name: Alberto Garcia

costamagnagianfranco <at> yahoo.it
    Full name: Gianfranco Costamagna
    Added key: 2985B56E5FBC9D9C21E9597B8B6EF2528F075E1D

ebourg <at> apache.org
    Full name: Emmanuel Bourg
    Added key: B8CE4DE21080DCF903E16C40F513C419E4B9D0AC

geofft <at> mit.edu
    Full name: Geoffrey Thomas
    Added key: 8896E71B57BAF57C0CB5481D5C5245265C413520

prachpub <at> gmail.com
    Full name: Prach Pongpanich
    Added key: 0CA75D987B8ECF6EA9443AD839091E8123CE1C09

simon <at> yubico.com
    Full name: Simon Josefsson

Debian distribution maintenance software,
on behalf of the Keyring maintainers

Lucas Nussbaum | 27 May 2013 10:03
Picon
Favicon

next DPL helpers meeting tomorrow (2013-05-28)

Hi,

The next DPL helpers meeting is tomorrow on #debian-dpl:
2013-05-28 Tue 17:00 (date -d  <at> 1369760400)

The agenda is online[1]. If you are listed on one of the pending
actions, it would be great if you could describe its status, and the
possible points needing discussion on titanpad (That should allow to be
more efficient during the meeting).
Also, feel free to add other points to discuss during the meeting.

http://titanpad.com/debiandpl-20130528

Lucas
Adrian Herrera | 25 May 2013 21:23
Picon

Problem with ram memory

I speak spanish. Debian 7 solo me reconoce 3͵4 gb de memoria ram. Y yo tengo 6 gb de memoria ram.
Windows7. Si me reconoce los 6 gb de ram. Esto es un problema de debian???

Wouter Verhelst | 21 May 2013 10:32
Picon
Gravatar

Revising the Code of Conduct

Hi,

I've long thought that our code of conduct, as currently written, is
fairly useless. Because it contains things that are totally irrelevant
("swearing is illegal on packet radio, some people receive mailinglists
on packet radio, so don't swear"??? [citation needed]) and some things
that are ineffective in today's world ("don't spam"), people tend to
ignore it.

As such, one of the things I wanted to do if elected last year would be
to overhaul the code of conduct[1]. Since I didn't get elected, I didn't
pursue this with as much vigour as would have been the case otherwise;
but I still think this is useful.

So I'd like to propose the following *draft* update of the code of
conduct. The methodology used for this was:
- Rather than have several items enumerating things you shouldn't do,
  merge related items into one. Items in this class include:
  - Most of the first item ("no abuse") with the penultimate ("don't
    flame) are merged into a generic point, the first item in my new
    CoC.
  - Two form-related items ("plain text only" and "wrap content at 80
    characters") are merged together with a recommendation to use
    mail-followup-to: (see below) into a "fix your mailer" point (number
    4)
  - merge the "no off-topic" and the "use the proper list" into a point
    3.
- Remove or replace things that aren't relevant anymore, or that could
  be done differently.
  - I've replaced the "Don't Cc" recommendation with a "Respect
    Mail-Followup-To:" recommendation. As I've stated before, I
    personally believe the "Do not Cc" recommendation is a very bad
    idea, because, first, some people actually prefer to be Cc'd if
    they're not subscribed to a mailinglist; and second, it goes against
    the defaults of many MUA's, which is contrary to my goal of having
    our code of conduct be easy for people to follow, not difficult.  By
    recommending that people use a mailer which respects that header,
    people can express their preference.
    However, I do recognize that this particular change may be
    controversial; if there is significant opposition, I don't insist on
    it.
  - The "don't spam" and "swearing is illegal" bits have been removed,
    as well as the "use common sense" bit. What's "common" sense depends
    very much on culture and background, which isn't something we can
    rely on in a Debian context.
  - The "don't send subscription requests" item belongs in the
    mailinglist documentation, not in the code of conduct. If people
    don't read documentation, repeating that documentation in the code
    of conduct isn't likely to help (they're unlikely to read that, too,
    anyway), so I think we should remove it.
  - The "don't send test messages" should be moved to the documentation
    IMHO, also stating that if you have issues, you should talk to
    listmasters. I was a bit in doubt about this one, but finally
    decided that it feels too much like singling out one type of
    messages that doesn't belong on our lists, which isn't something I
    think a generic code of conduct should do.
- Add some things that aren't there but, I think, do belong in a code of
  conduct:
  - Note that in general, replies to a post should go to the same
    mailinglist. Replying in private robs the rest of the list from that
    particular part of the discussion; replying to a different list can
    be disruptive to a discussion, too, and is unlikely to succeed.
    There are some exceptions where this is the right thing to do, so
    note them.
  - Add some final language with advise on what to do when misbehaviour
    is observed. This also formalizes what today already is effectively
    the case, namely that listmasters may ban people temporarily or
    permanently from posting on our mailinglists for behaviour contrary
    to the code of conduct.

So, without further ado, here's my draft:

---
The Debian mailinglists exist to foster the development and use of
Debian. This Code of Conduct exists to help towards that goal.

In particular, the following rules should be adhered to by participants
to discussion on Debian mailinglists:

1. Do not flame, use foul language, or in general be abusive or
   disrespectful towards other people on the mailinglists or elsewhere
   in Debian. That type of behaviour is not constructive and can quickly
   lead to a degradation of the quality of a discussion.
2. Make sure to use the correct language when sending mails to our
   mailinglists. This is usually English, unless otherwise noted in the
   description of the mailinglist in question.
3. Use the correct list when posting a question. If unsure, use
   debian-user for support-related questions, or debian-mentors for
   development-related questions. Be prepared to ask your question on a
   different mailinglist if told to do so.
4. Configure your mailer to send mail in plain text format, wrapping
   lines at 80 characters for regular content. Exceptions to the
   word-wrapping rule may include things like quoted parts of other
   people's mails you are replying to, or computer-generated output that
   is relevant to the discussion. You should preferably also use a
   mailer which respects the Mail-Followup-To: header, or make a
   best-effort attempt at respecting it manually if you don't.
5. If you wish to be part of a discussion, you should preferably
   subscribe to the relevant mailinglist, even if only temporarily. If
   you choose not to, you should remember that you may lose out on part
   of the discussion, even if you use an appropriate Mail-Followup-To:
   header.
6. You should avoid sending attachments; this generates a lot of
   unnecessary bandwidth on our listservers. Instead, put the file you
   would like to attach online somewhere and post a link.
7. Please ensure that your mail system never sends automatic replies to
   the list. If you do, listmasters may remove you from the list with
   immediate effect to avoid flooding or annoying participants. You may
   resubscribe when the automatic messages have been disabled.
8. Replies to a post on a mailinglist should, in general, go to the same
   mailinglist. Do not send private replies, unless posting something
   sensitive. Do not change the mailinglist, unless you are posting
   something that is no longer relevant to the original discussion and
   clearly off-topic for the mailinglist where it is being discussed.

While these rules should be adhered to by participants, we recognize
that sometimes people may have a bad day, or be unaware of some of the
rules in this code of conduct. When that happens, you may reply to them
and point out this code of conduct. Such messages may be on the list or
off the list, whatever is most appropriate. However, regardless of
whether the message is on- or off-list, it should still adhere to the
relevant parts of this code of conduct.

Repeated offenders may be temporarily of permanently banned from posting
to our mailinglists at the Debian listmasters' prerogative.
---

Thoughts?

[1] see <https://lists.debian.org/debian-vote/2012/03/msg00047.html>,
    for instance.

--

-- 
This end should point toward the ground if you want to go to space.

If it starts pointing toward space you are having a bad problem and you
will not go to space today.

  -- http://xkcd.com/1133/


Gmane