ganhe dinheiro

Export Control of Debian OS

Dear Debian Project,

My name is Harry Nakayama worked w/ TOSHIBA TEC Corporation in Japan.

Now we are researching Debian OS Export control policy from Debian project
FAQ or others.
But we cannot made it so far.

So, we need your support/help in this regards.
Would you please tell me if you have ECCN and CCATS number already?
If you don't have it, pls be advice how we can handle or judge Debian OS
export control.

We really appreciate your early reply.

Best Regards,

Harry

 ****************************************************
   FUMIHARU (HARRY) NAKAYAMA
   中山　文治
   TOSHIBA TEC DOCUMENT PROCESSING SYSTEMS CO., LTD.
   東芝テック画像情報システム株式会社 (TDOS)
   Design Group 5
   Engineering Dept. 2
   TEL: (055)976-7446
        81-55-976-7446 (INTL)
   FAX: (055)976-7721
        81-55-976-7721 (INTL)
   E-Mail: fumiharu_nakayama <at> toshibatec.co.jp
 ****************************************************

NOTE:  　This email message and any information
attached to it may contain confidential information that is
legally privileged.  Any unauthorized disclosure, use, copying,
or distribution is strictly prohibited. If you are not the
intended recipient, please notify the author and destroy the
original transmission without reading or saving.  Thank you.

Re: Export Control of Debian OS

[Please post follow-ups to the list, I am subscribed]

2009/9/3 Fumiharu Nakayama <Fumiharu_Nakayama <at> toshibatec.co.jp>:

> Dear Debian Project,
>
> My name is Harry Nakayama worked w/ TOSHIBA TEC Corporation in Japan.
>
> Now we are researching Debian OS Export control policy from Debian project
> FAQ or others.
> But we cannot made it so far.
>
> So, we need your support/help in this regards.
> Would you please tell me if you have ECCN and CCATS number already?
> If you don't have it, pls be advice how we can handle or judge Debian OS
> export control.

The answer I gave last time this came up should be findable with
Google, but if not, it is here:

http://lists.debian.org/debian-project/2009/08/msg00359.html

No idea if we have a CCATS number though.

BTW, if you are shipping hardware containing Debian, please register a
wiki account and edit this wiki page:

http://wiki.debian.org/Hardware/ShippingWithDebian

Debian can always use more developers and donations, so if you are
using/selling Debian and are able to, please dedicate some resources
to Debian or to the annual Debian conference:

http://www.debian.org/intro/help
http://www.debian.org/donations
http://debconf.org/

--

-- 
bye,
pabs

http://wiki.debian.org/PaulWise

Re: Export Control of Debian OS

Hi Nakayama-san,

On Thu, Sep 03, 2009 at 04:10:36PM +0900, Fumiharu Nakayama wrote:
> Dear Debian Project,
> 
> My name is Harry Nakayama worked w/ TOSHIBA TEC Corporation in Japan.
> 
> Now we are researching Debian OS Export control policy from Debian project
> FAQ or others.
> But we cannot made it so far.
> 
> So, we need your support/help in this regards.
> Would you please tell me if you have ECCN and CCATS number already?
> If you don't have it, pls be advice how we can handle or judge Debian OS
> export control.

Have you read "http://www.bis.doc.gov/licensing/do_i_needaneccn.html"?

> How do I get an ECCN?
> 
> There are three ways to determine the ECCN for your product.
> 
> 1. Determine the classification yourself.
> 2. Go to the source.
> 3. Get an official classification from the Bureau of Industry and
> Security (BIS).

We are volunteer organization for software.  We can not be made liable
for judging such legal matter.  Thus 2nd option is not for you as I
understand.

Although it sounds harsh, the best thing to do is judge by eading
corresponding regulations.  That is what most companies do for exporting
anything these days.  Company such as yours should have department
taking care such matters.

Any advice or suggestion provided here should be considered as
"reference opinion" and no gurantee.  After all, Debian is provided as
is.  Unlike commercial vender of software, we are not selling software.

Osamu

PS: It will be nice to have some page for these issues on our web so
these FAQ can be addressed properly without making us liable.  

Re: Export Control of Debian OS

On Fri, Sep 04, 2009 at 09:29:23PM +0900, Osamu Aoki <osamu <at> debian.org> wrote:
> PS: It will be nice to have some page for these issues on our web so
> these FAQ can be addressed properly without making us liable.  

Translated in various languages would be a nice addition.

Mike

Re: Export Control of Debian OS

On Fri, Sep 04, 2009 at 03:00:13PM +0200, Mike Hommey wrote:
> On Fri, Sep 04, 2009 at 09:29:23PM +0900, Osamu Aoki <osamu <at> debian.org> wrote:
> > PS: It will be nice to have some page for these issues on our web so
> > these FAQ can be addressed properly without making us liable.  
> 
> Translated in various languages would be a nice addition.

If we put this to www.debian.org with wml, it will 

But tougher thing is to come up with the main text.

Osamu

time-based release freezes

Hello Debianteam,

I hope you understand my terrible english ;)

It is the fixed release cycles, my opinion ist that 2years are too short, because Debian is used more as a
server operating system, the people how would like an actuelly version of an program can use Debian testing.

I would make every 3years a feature freeze and every 1.5 years a "stable-and-a-half", then the topicality
also ensures version of Debian (kernel, Xorg, etc).

The old stable, must be supported for 6years, has been published until the new version(testing to stable)

I hope I could possibly give one food for thought ;)

Gruss Stefan

in german:

Hallo Debianteam,

ich hoffe ihr versteht mein schlechtes englisch ;)

Es geht um die festen release zyklen, ich finde 2jahre viel zu kurz, da Debian eher als Server
betriebssystem benutzt wird, die leute die aktuelle programmverionen nutzen möchten, können ja
Debian-testing nutzen

Ich würde alle 3jahre ein featurefreeze machen und alle 1,5jahre ein "stable-and-a-half", dann ist auch
die aktualität von Debian gewährleistet (kernel, Xorg, etc) 

Die alte stable version, sollte dann auch noch die komplette stable-version gepflegt werden, so das
odlstable insgesamt 6jahre (seit release) gepflegt wird.

Ich hoffe ich konnte eventuell einen denkanstoß geben ;)

Gruss Stefan 

-- 
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser

--

-- 
To UNSUBSCRIBE, email to debian-project-REQUEST <at> lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster <at> lists.debian.org

Re: Export Control of Debian OS

Hi,

In light of recent event
 http://lists.debian.org/debian-project/2009/08/msg00359.html

I have created wiki page to address FAQ on U.S. Export Control.

 http://wiki.debian.org/USExportControl

Please help improve this page.

Osamu

Re: time-based release freezes

Stefan Krueger wrote:
> 
> ich hoffe ihr versteht mein schlechtes englisch ;)
> 

Hi Stefan,

I have no comment on your proposal - it just amused me that you seem to
have included "I hope you understand my terrible english" in the German
version 

Cheers,

	David.

Re: time-based release freezes

Stefan Krueger schreef:
> Hello Debianteam,
> 
> I hope you understand my terrible english ;)
> 
> It is the fixed release cycles, my opinion ist that 2years are too
> short, because Debian is used more as a server operating system, 

But Debian is not only for servers.

> the people how would like an actuelly version of an program can use
> Debian testing.

Not well-tested enough for normal use by non-technical people.
At the moment I believe more in backports.
(I am sysadmin for both Debian desktops and servers)

> I would make every 3years a feature freeze and every 1.5 years a
> "stable-and-a-half", then the topicality also ensures version of
> Debian (kernel, Xorg, etc).
> 
> The old stable, must be supported for 6years, has been published
> until the new version(testing to stable)
>
> I hope I could possibly give one food for thought ;)

It would be nice to have a long support, but it is a lot of work.
Is it really such a problem to upgrade your servers?

Or is the real problem that your organisation or your customers do not
understand that an upgrade is important?

For me it is a problem that the support on the Mozilla products is so
short....
http://www.debian.org/releases/lenny/i386/release-notes/ch-information.en.html#mozilla-security
http://www.debian.org/security/2009/dsa-1753
http://www.debian.org/security/2009/dsa-1830

With regards,
Paul van der Vlis.

--

-- 
http://www.vandervlis.nl/