[Top][All Lists]

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

[DotGNU]Re: [CoreTeam]Draft list of 20 DotGNU development projects

From: tony stanco
Subject: [DotGNU]Re: [CoreTeam]Draft list of 20 DotGNU development projects
Date: Sat, 17 Nov 2001 19:57:22 -0500

Nice list, Norbert.

1. As a general note, can we watch out for the impact of our technology on
the disabled community? The Fed Government has recently passed laws that
require Universal Access (UA) for IT to all people with disabilities,
especially for e-Government. I met with the National Foundation of the Blind
yesterday and they promised to support us politically and for grant
applications, because proprietary constantly breaks their expensive devices
in upgrades and they like our inclusive principles generally.

If we have UA products that are better than proprietary (something that
proprietary doesn't really work on), the NFB will use the laws on the books
to have the Federal Agencies buy FreeSoftware products and if the agencies
don't, they will sue them under the current laws.

Also they have some money for grants and will generally support our grant
applications with others, too (and they have considerable political
influence in town). Further, they really want to support our community on

If we can keep an eye on their interests, it is the right thing to do and
will also help us to do well by doing good.

2. Also, we should note in our planing of DotGNU that the Federal Government
is TOTALLY committed to XML for ALL its documents. This will almost
certainly drive XML to become the standard over the coming years. We should
probably work with this wave, rather than fight it, since it breaks a lot of
the proprietary hooks in file formats that help to maintain proprietary's
unfair monopolies and hinder interoperability. [Interesting note: the
Federal Official responsible for the government's XML policy told a
Microsoft official at an Open Source investigatory meeting, "Let my
documents go!"]

Best regards,

Tony Stanco, Esq.
Senior Policy Analyst
Cyberspace Policy Institute
School of Engineering and
Applied Science
George Washington University
2033 K Street N.W., Suite 340
Washington, DC 20006
202-994-5513  Fax:202-994-5505

-----Original Message-----
From: Norbert Bollow <address@hidden>
To: address@hidden <address@hidden>; address@hidden
Cc: address@hidden <address@hidden>; address@hidden <address@hidden>
Date: Saturday, November 17, 2001 5:36 PM
Subject: [CoreTeam]Draft list of 20 DotGNU development projects

>I'd like to propose the following list of 20 development projects
>that would together form "DotGNU"... the idea is to have a
>not too long list of development projects for now; more can be
>added after "DotGNU 1.0" has been released.
>This proposal is valid only if the phpGroupWare and Savannah
>folks will be in agreement with making their projects part of
>DotGNU (I've listed them as items 15 and 16 on this list for
>now, if they're not in agreement this will of course have to
>be changed).  Otherwise we will probably need to look elsewhere
>for GroupWare style webservices that we can use to showcase
>DotGNU, and the plans for a "PHP plugin for SEE" (item 4) are
>likely to get dropped, too.
>1. SEE (Secure Execution Environment)
>   - a daemon, written in C++
>   - supports plugins
>   - must run on all major desktop systems
>2. CLR plugin for SEE
>   - must run on all major desktop systems
>3. Java VM plugin for SEE
>   - must run on all major desktop systems
>4. PHP plugin for SEE
>   - must run on all major desktop systems
>5. Parrot plugin for SEE
>   - must run on all major desktop systems
>6. DEE (Distributed Execution Environment)
>   - only needs to work on GNU systems
>   - executes webservice code in a SEE on the webservice server,
>     but also allows users to download the webservice code
>     (Anyone who is able to execute something on the server is
>     also able to download the program and execute the program
>     locally.)
>   - allows the owner of data to download the data
>   - facilitates distributed hosting of webservices
>   - must support transaction logging and roll-back
>   - Any program that works under DEE must also work under SEE
>     (However the converse of this will not be true.)
>7. XML-shell
>   - system administration tool for DEE
>8. Virtual Identities / auth project (a "horse race", no single project
>   endorsed at this stage)
>development tools
>9. C# -> CLR compiler
>   - written in C
>10. C# class library
>11. VisualBasic -> CLR compiler
>   - written in C
>12. CLR -> CLR optimizer
>13. CLR debugger
>(all of the below should be usable both as webservice components and as
>webservice application)
>14. searchable webservice directory
>   - Should be able to query listed webservices for the information,
>     i.e. webservice maintainers can maintain all the information
>     for directories on their own server, they don't need to separately
>     maintain listings in multiple directories
>   - Must be usable for specialized directories, like e.g. a directory
>     of software development projects.
>15. phpGroupWare webservice components and webservice application
>16. distributed Savannah
>17. load-balancing system
>18. distributed backup system
>19. Appointment Maker
>   - a webservice that manages the appointment-making process
>20. DotGNU webservice server checker
>   - a tool to potentially falsify the claim that a given webservice
>     server meets the requirements of a DotGNU webservice server.
>   - For webservices which store data in the DEE, this can only
>     be used by the owner of the data (i.e. by someone who has
>     the right to export the data).
>Greetings, Norbert.
>A member of FreeDevelopers and the DotGNU Steering Committee:
>Norbert Bollow, Weidlistr.18, CH-8624 Gruet   (near Zurich, Switzerland)
>Tel +41 1 972 20 59       Fax +41 1 972 20 69
>Your own domain with all your Mailman lists: $15/month
>CoreTeam mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]